Bug #77022 Make it easier to identify duplicate ndbrequire() incidents

• Submitted: 13 May 2015 10:56
• Modified: 18 Jun 2015 9:23
• Reporter: Hartmut Holzgraefe
• Status: Verified
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S4 (Feature request)
• Version: ndb-7.4.4; any
• OS: Any
• CPU Architecture: Any

[13 May 2015 10:56] Hartmut Holzgraefe

Description:
As the only information included in ndbrequire() error output are source file and line number of the ndbrequire() statement itself it is very hard to identify whether a certain assertion failure has already been seen in the past. Line numbers change too easily between releases to be able to quickly say "Yes, this new incident seems to be the same in that specific previous report(s)"

A fix for the request in bug #77021 would at least partly resolve this, but as almost 1/4 of the ndbrequire() calls are of the form "ndbrequire(false)" alone (492 of a total of 2157 in 7.4.4) a better way to be able to tell "I'm indeed looking at the same ndbrequire failure here" would still be needed.

How to repeat:
See Description above

Suggested fix:
Not really sure ... adding a unique identification number to each ndbrequire() would probably be over the top ...?

[18 Jun 2015 9:23] Gustaf Thorslund

Hi Hartmut,

Thank you for two reasonable feature requests.

Regards,
Gustaf