Bug #54015 | mysql cluster data node not sync | ||
---|---|---|---|
Submitted: | 27 May 2010 6:50 | Modified: | 8 Nov 2010 12:49 |
Reporter: | patcharee sirichavalit | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S1 (Critical) |
Version: | 5.0.44sp1 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[27 May 2010 6:50]
patcharee sirichavalit
[27 May 2010 8:51]
Hartmut Holzgraefe
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL.
[27 May 2010 9:02]
patcharee sirichavalit
i found this info too , is it enough info Error in longtime queue 2336 Error in longtime queue No:2336
[27 May 2010 9:10]
patcharee sirichavalit
status not change to open . why?
[27 May 2010 9:20]
Hartmut Holzgraefe
No, this only shows that an overflow has happened in that queue, but not why. We at least need to see the full cluster and mysqld configuration and log files and a description of what you were doing with the cluster at the time the error was logged. If you can reproduce the problem a description of how to do that would be even better.
[27 May 2010 9:27]
patcharee sirichavalit
Error in longtime queue 2336 Error in longtime queue No:2336 will not help anything ,right?
[27 May 2010 9:45]
Hartmut Holzgraefe
again: that information only shows *that* this error was triggered (which indicates *some* sort of overload), but not *why* ... Most likely this isn't even a bug but due to misconfiguration or due to hitting a general limitation. But without further information how your system is configured, what was done with it at the time of the error, and complete error log files (hostname.err from mysqld, ndb_*_cluster.log, ndb_*_error.log, ndb_*_trace.log.*, ndb_*_out.log from management and data nodes) i'll still keep this in "Can't repeat"
[27 May 2010 9:49]
patcharee sirichavalit
we have 2 server (aa and bb ) on aa server , we have 2 datanode (1,3) on bb server ,we have 2 datanode (2,4) it 's mount different lun . My admin format datanode (1,3) and it show Error in longtime queue 2336 Error in longtime queue No:2336. After that mysql can't syn data between 2 server . this is help ?
[27 May 2010 10:02]
Hartmut Holzgraefe
No, we really, really need those log files ...
[27 May 2010 10:15]
patcharee sirichavalit
we will try to get log and send it to you . anyway how to send log to you ?
[2 Jun 2010 4:56]
patcharee sirichavalit
Time: Saturday 6 March 2010 - 17:42:13 Status: Temporary error, restart node Message: Error in long time queue (Internal error, programming error or missing error message, please report a bug) Error: 2336 Error data: Too many in Long Time Queue Error object: TimeQueue.C Program: /usr/sbin/ndbd Pid: 10013 Trace: /data/data-1/ndb_1_trace.log.10 Version: Version 5.0.45 ***EOM*** ndb_error.log
[10 Jun 2010 2:47]
patcharee sirichavalit
Hi All, Any update?
[22 Jun 2010 4:49]
patcharee sirichavalit
Hi All, I already send ndb_error to you . So this is a bug?
[22 Jun 2010 7:13]
Hartmut Holzgraefe
We need the *complete* log files (ndb_*_cluster.log, ndb_*_error.log, ndb_*_trace.log.*, ndb_*_out.log) from all data and management nodes, not just a snippet of the failing nodes error log file ... Please let *us* decide which parts of the logs are of interest ...
[22 Jul 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[23 Jul 2010 1:59]
patcharee sirichavalit
Hi All, Please wait around 1 week , i will try to get log that you need and send it to you. Best Regards,
[8 Oct 2010 12:49]
Valeriy Kravchuk
So, what about the logs requested?
[9 Nov 2010 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".