Bug 1002468
Summary: | Dist-geo-rep : geo-rep monitor process crashed in set_term_handler after worker crashed with IO error. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Vijaykumar Koppad <vkoppad> |
Component: | geo-replication | Assignee: | Aravinda VK <avishwan> |
Status: | CLOSED DUPLICATE | QA Contact: | amainkar |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.1 | CC: | aavati, avishwan, csaba, david.macdonald, racpatel, rhs-bugs, sdharane, vagarwal |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-12-29 06:18:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Vijaykumar Koppad
2013-08-29 09:36:31 UTC
the monitor crash is a side effect of the worker process dying, which obviously should not happen as the monitor is responsible to restart the worker if it gets killed (here it should be within a minute, as that's the time interval monitor checks for worker correctness). The problem here is that the signalling mechanism is not working as expected as the monitor process in multi-threaded, ie. one thread for each worker on a given node. *** This bug has been marked as a duplicate of bug 1044420 *** |