Bug #37338 Api disconnect (or unsubscribe) during SUMA nf-handling, can lead to sp100-hang

Submitted:	11 Jun 2008 12:19	Modified:	2 Jul 2008 18:42
Reporter:	Jonas Oreland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Jonas Oreland	CPU Architecture:	Any

Description:
when API disconnect (and hence SUB_GCP_COMPLETE_REP will not be sent)
and buffer is partially full and a node fails.

then the resend can fail (hang forever)
causing node restart to hang.

How to repeat:
run new test prg

Suggested fix:
add gci to buffer if resend is ongoing
compute correct gci interval to resend
(it is currently correct, unless all api nodes has disconnected)

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/47755

2622 jonas@mysql.com	2008-06-11
      ndb - bug#37338
        Fix weird case with node failure and api failure
        cause subsequent node restart to fail

disconnect (or unsubscribe) during SUMA nf-handling, can lead to sp100-ha

Documented fix in NDB 6.2.16 and 6.3.16 changelogs.

Pushed into 6.0.6-alpha  (revid:jonas@mysql.com-20080611194915-dv2aytywy37rfd6q) (version source revid:jonas@mysql.com-20080812185642-1nevjb94zj621dqx) (pib:5)

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.