Bug 1475258
Summary: | [Geo-rep]: Geo-rep hangs in changelog mode | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Niels de Vos <ndevos> |
Component: | geo-replication | Assignee: | Niels de Vos <ndevos> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.12 | CC: | bugs, khiremat, ndevos, srangana |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.12.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1475255 | Environment: | |
Last Closed: | 2017-09-05 17:37:29 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: | |||
Bug Depends On: | 1475255 | ||
Bug Blocks: | 1473826 |
Description
Niels de Vos
2017-07-26 10:10:01 UTC
REVIEW: https://review.gluster.org/17915 (mem-pool: track and verify initialization state) posted (#1) for review on release-3.12 by Niels de Vos (ndevos) REVIEW: https://review.gluster.org/17916 (changelog: add mem-pool initialization) posted (#1) for review on release-3.12 by Niels de Vos (ndevos) COMMIT: https://review.gluster.org/17915 committed in release-3.12 by Shyamsundar Ranganathan (srangana) ------ commit c2742e4dd118e416fbd7fdf865350a5a3c92490c Author: Niels de Vos <ndevos> Date: Sun Jul 30 09:13:29 2017 +0200 mem-pool: track and verify initialization state It is possible that pthread_getspecific() returns a non-NULL value in case the pthread_key_t is not initialized. The behaviour for pthread_getspecific() is not defined in this case. This can happen when applications use mem-pools from libglusterfs.so, but did not call mem_pools_init_early(). By tracking the status of the mem-pools initialization, it is now possible to prevent calling pthread_getspecific() in case the pthread_key_t is not initialized. In future, we might want to exend this more to faciliate debugging. Cherry picked from commit b5fa5ae05f73e03023db37e43fb203267b719160) > Reported-by: Kotresh HR <khiremat> > Tested-by: Jiffin Tony Thottan <jthottan> > Change-Id: I6255419fe05792dc78b1eaff55bc008fc5ff3933 > Fixes: 1e8e62640 ("mem-pool: initialize pthread_key_t pool_key in mem_pool_init_early()") > BUG: 1475255 > Signed-off-by: Niels de Vos <ndevos> > Reviewed-on: https://review.gluster.org/17899 > Smoke: Gluster Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: jiffin tony Thottan <jthottan> > Reviewed-by: Jeff Darcy <jeff.us> Change-Id: I6255419fe05792dc78b1eaff55bc008fc5ff3933 BUG: 1475258 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: https://review.gluster.org/17915 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Shyamsundar Ranganathan <srangana> COMMIT: https://review.gluster.org/17916 committed in release-3.12 by Shyamsundar Ranganathan (srangana) ------ commit bb4571f72c0e794f7c3da8c2f64ed20906cfa2fe Author: Niels de Vos <ndevos> Date: Sun Jul 30 09:14:22 2017 +0200 changelog: add mem-pool initialization With recent changes to the mem-pool initialization, mem_pools_init_early() and mem_pools_init_late() need to be called before mem_get() is usable. This change has been tested manually with the included test from xlators/features/changelog/lib/examples/c/get-changes.c. Cherry picked from commit 1bc3cd9bd59e3826fd14fc239322f039d7a814da) > Change-Id: I139563c4ff78a566cef2ff7e3da2ee10306def92 > BUG: 1475255 > Reported-by: Kotresh HR <khiremat> > Signed-off-by: Niels de Vos <ndevos> > Reviewed-on: https://review.gluster.org/17900 > Smoke: Gluster Build System <jenkins.org> > Reviewed-by: Kotresh HR <khiremat> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Jeff Darcy <jeff.us> Change-Id: I139563c4ff78a566cef2ff7e3da2ee10306def92 BUG: 1475258 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: https://review.gluster.org/17916 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Shyamsundar Ranganathan <srangana> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.12.0, please open a new bug report. glusterfs-3.12.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/ |