random slave crash on master crash + restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Confirmed
|
High
|
Unassigned | ||
7.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
7.1 |
Confirmed
|
High
|
Unassigned |
Bug Description
When running the randgen test for master crash + recovery, we are seeing random instances where the slave crashes.
This occurs ~1 in 20 times and I have seen several different stack traces for this.
To repeat: ./dbqp --mode=randgen --randgen-
Backtrace:
110411 13:43:29 - drizzled got signal 6;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
read_buffer_
max_used_
connection_count=2
It is possible that drizzled could use up to
(read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Number of stack frames obtained: 26
/drizzle/
()
gsignal()
abort()
()
()
cfree()
__gnu_cxx:
std::_Vector_
std::_Vector_
/drizzle/
__gnu_cxx:
/drizzle/
std::queue<
/drizzle/
drizzled:
drizzled:
()
()
()
()
()
thread_proxy()
()
clone()
summary: |
- random slave crash on master crash + restart + Buy Ambien Online Overnight: Diagnosis And Treatment Options |
description: | updated |
summary: |
- Buy Ambien Online Overnight: Diagnosis And Treatment Options + random slave crash on master crash + restart |
description: | updated |
NOTE: this has been detected in trunk. Need to retest against elliott to make certain it is present there. including elliott as a target / will update accordingly when finished