Percona crashes when doing multi-connection update against it (PPC, xenial and above)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
percona-xtradb-cluster-5.6 (Ubuntu) |
In Progress
|
Undecided
|
Mario Splivalo | ||
Xenial |
New
|
Undecided
|
Mario Splivalo | ||
Zesty |
New
|
Undecided
|
Mario Splivalo | ||
Artful |
In Progress
|
Undecided
|
Mario Splivalo |
Bug Description
percona-
The installation proceeds without an issue, and running single-connection sysbench benchmark completes fine. However when number of connections increase percona will segfault almost immediately.
This is excerpt from the error.log file:
Thread pointer: 0x1002c0f1080
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 3ffe87cbe6a0 thread_stack 0x30000
/usr/sbin/
/usr/sbin/
[0x3fff80ab04d8]
/usr/sbin/
[0x3fff3800fc68]
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/powerpc64l
/lib/powerpc64l
I am attaching the error.log as well as my.cnf to this bug report too.
This bug is similar to Bug #1657256, but not the same. As codebase is different (percona-
This bug was created to separate SRU effort as fix for percona-
Changed in percona-xtradb-cluster-5.6 (Ubuntu Zesty): | |
assignee: | nobody → Mario Splivalo (mariosplivalo) |
Changed in percona-xtradb-cluster-5.6 (Ubuntu Xenial): | |
assignee: | nobody → Mario Splivalo (mariosplivalo) |