Bug #40922 exiting ndb_mgm client sometimes hangs

• Submitted: 21 Nov 2008 11:18
• Modified: 14 Jan 2009 17:06
• Reporter: Oli Sennhauser
• Status: Closed
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: 6.3.18, 6.3.19, 6.2-bzr, 6.4.0
• OS: Any
• Assigned to: Magnus Blåudd
• CPU Architecture: Any

[21 Nov 2008 11:18] Oli Sennhauser

Description:
Exiting ndb_mgm client sometimes hangs for long time. Can be forced by ^C.

How to repeat:
Can be sometimes reproduced but not at will.

When I set a strace on ndb_mgm during hang I got the following:

# sudo strace -p 14350
Process 14350 attached - interrupt to quit
futex(0xb7f20bd8, FUTEX_WAIT, 14356, NULL) = ? ERESTARTSYS (To be restarted)
--- SIGINT (Interrupt) @ 0 (0) ---
Process 14350 detached

Suggested fix:
No idea.

[22 Nov 2008 10:13] Sveta Smirnova

Thank you for the report.

Verified as described.

[22 Dec 2008 11:32] Sveta Smirnova

Bug #40922 was marked as duplicate of this one.

Bug #40922 contains more information about when problem occurs.

[22 Dec 2008 11:33] Sveta Smirnova

s/40922/bug #41669/ in previous comment

[9 Jan 2009 10:40] Oli Sennhauser

All customers who rely on the ndb_mgm client to monitor their cluster have possibly a problem now.

[9 Jan 2009 10:41] Oli Sennhauser

Duplicat bug #39679

[9 Jan 2009 14:31] Magnus Blåudd

ndb_mgm is waiting for the event thread to exit

[14 Jan 2009 10:47] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/63202

2787 Magnus Svensson	2009-01-14
      Bug#40922 exiting ndb_mgm client sometimes hangs
       - Hanged waiting for the event listener thread in 'ndb_logevent_get_next'
       - Each call to 'in.gets' is maximized to "timeout_millisconds"
         but since the ndb_mgmd sends <PING> with 500 milliseconds
         interval, the timeout would never expire and thus the function
         never return.

[14 Jan 2009 14:14] Bugs System

Pushed into 5.1.30-ndb-6.2.17 (revid:[e-mail]-20090114140628-toxqf65xjdtlxhdl) (version source revid:[e-mail]-20090114140628-toxqf65xjdtlxhdl) (merge vers: 5.1.30-ndb-6.2.17) (pib:6)

[14 Jan 2009 14:15] Bugs System

Pushed into 5.1.30-ndb-6.3.21 (revid:[e-mail]-20090114141134-0hjvl7k4c114ac09) (version source revid:[e-mail]-20090114141034-5jkbzyzxr120z6hr) (merge vers: 5.1.30-ndb-6.3.21) (pib:6)

[14 Jan 2009 14:17] Bugs System

Pushed into 5.1.30-ndb-6.4.1 (revid:[e-mail]-20090114141212-wg97k24qcjmshs8w) (version source revid:[e-mail]-20090114141040-1vee2xxsehm2l6rd) (merge vers: 5.1.30-ndb-6.4.1) (pib:6)

[14 Jan 2009 17:06] Jon Stephens

Documented bugfix in the NDB-6.2.17/6.3.21/6.4.1 changelogs as follows:

        Issuing EXIT in the management client sometimes caused the
        client to hang.

[10 Feb 2009 20:13] Bugs System

Pushed into 6.0.10-alpha (revid:[e-mail]-20090210194937-s7xshv5l3m1v7wi9) (version source revid:[e-mail]-20090123110300-k3vjhnm1iop8c0h7) (merge vers: 6.0.10-alpha) (pib:6)

[12 Feb 2009 10:06] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/66011

2814 He Zhenxing	2009-02-12 [merge]
      Auto merge 6.0 -> 6.0-rpl