dbt2 fails with 1024 connections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
High
|
Jay Pipes |
Bug Description
dbt2 will randomly fail when trying to run with 1024 connections, builds before that are fine. It appears that drizzled stops responding - see the logs on orisndriz01 at http://
See the complete log file at http://
From drizzled error log:
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: Version: '2009.12.1247' Source distribution (staging-
Wed Dec 23 13:37:24 2009 INFO: terminate called after throwing an instance of 'std::out_of_range'
Wed Dec 23 13:37:24 2009 INFO: what(): basic_string:
Wed Dec 23 13:37:24 2009 INFO: 091223 13:32:28 - drizzled got signal 6;
Wed Dec 23 13:37:24 2009 INFO: This could be because you hit a bug. It is also possible that this binary
Wed Dec 23 13:37:24 2009 INFO: or one of the libraries it was linked against is corrupt, improperly built,
Wed Dec 23 13:37:24 2009 INFO: or misconfigured. This error can also be caused by malfunctioning hardware.
Wed Dec 23 13:37:24 2009 INFO: We will try our best to scrape up some info that will hopefully help diagnose
Wed Dec 23 13:37:24 2009 INFO: the problem, but since we have already crashed, something is definitely wrong
Wed Dec 23 13:37:24 2009 INFO: and this may fail.
Wed Dec 23 13:37:24 2009 INFO:
Wed Dec 23 13:37:24 2009 INFO: key_buffer_
Wed Dec 23 13:37:24 2009 INFO: read_buffer_
Wed Dec 23 13:37:24 2009 INFO: max_used_
Wed Dec 23 13:37:24 2009 INFO: connection_
Wed Dec 23 13:37:24 2009 INFO: It is possible that drizzled could use up to
Wed Dec 23 13:37:24 2009 INFO: key_buffer_size + (read_buffer_size + sort_buffer_
Wed Dec 23 13:37:24 2009 INFO: bytes of memory
Wed Dec 23 13:37:24 2009 INFO: Hope that's ok; if not, decrease some variables in the equation.
Wed Dec 23 13:37:24 2009 INFO:
Wed Dec 23 13:37:24 2009 INFO: session: 0x3cd6b70
Wed Dec 23 13:37:24 2009 INFO: Attempting backtrace. You can use the following information to find out
Wed Dec 23 13:37:24 2009 INFO: where drizzled died. If you see no messages after this, something went
Wed Dec 23 13:37:24 2009 INFO: terribly wrong...
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /lib/libpthread
Wed Dec 23 13:37:24 2009 INFO: /lib/libc.
Wed Dec 23 13:37:24 2009 INFO: /lib/libc.
Wed Dec 23 13:37:24 2009 INFO: /usr/lib/
Wed Dec 23 13:37:24 2009 INFO: /usr/lib/
Wed Dec 23 13:37:24 2009 INFO: /usr/lib/
Wed Dec 23 13:37:24 2009 INFO: /usr/lib/
Wed Dec 23 13:37:24 2009 INFO: /usr/lib/
Wed Dec 23 13:37:24 2009 INFO: /usr/lib/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /home/drizzle/
Wed Dec 23 13:37:24 2009 INFO: /lib/libpthread
Wed Dec 23 13:37:24 2009 INFO: /lib/libc.
Wed Dec 23 13:37:24 2009 INFO: Trying to get some variables.
Wed Dec 23 13:37:24 2009 INFO: Some pointers may be invalid and cause the dump to abort...
Wed Dec 23 13:37:24 2009 INFO: session->query at 0x3cdc4b8 = UPDATE order_line
Wed Dec 23 13:37:24 2009 INFO: SET ol_delivery_d = current_timestamp
Wed Dec 23 13:37:24 2009 INFO: WHERE ol_o_id = 2101
Wed Dec 23 13:37:24 2009 INFO: AND ol_w_id = 10
Wed Dec 23 13:37:24 2009 INFO: AND ol_d_id = 3
Wed Dec 23 13:37:24 2009 INFO: session-
Wed Dec 23 13:37:24 2009 INFO: session-
Wed Dec 23 13:37:24 2009 INFO: pure virtual method called
Wed Dec 23 13:37:24 2009 INFO: terminate called recursively
Related branches
- Brian Aker: Pending requested
- Drizzle Developers: Pending requested
-
Diff: 129 lines (+23/-23)2 files modifieddrizzled/temporal_format.cc (+23/-22)
drizzled/temporal_format.h (+0/-1)
Changed in drizzle: | |
status: | In Progress → Fix Committed |
Changed in drizzle: | |
status: | Fix Committed → Fix Released |
Attaching valgrind out put, this part is pretty scary!
valgrind: the 'impossible' happened: c:140) c:215) core_panic_ at (m_libcassert. c:220) c:225) alloc_ThreadSta te (scheduler.c:187) amd64_linux_ sys_clone_ before (syswrap- amd64-linux. c:205) client_ syscall (syswrap- main.c: 942) NORETURN (syswrap- linux.c: 89)
VG_N_THREADS is too low
==17024== at 0x3802A7AC: report_and_quit (m_libcassert.
==17024== by 0x3802A8C4: panic (m_libcassert.
==17024== by 0x3802A932: vgPlain_
==17024== by 0x3802A951: vgPlain_core_panic (m_libcassert.
==17024== by 0x3804CE91: vgPlain_
==17024== by 0x380966F9: vgSysWrap_
==17024== by 0x380501A0: vgPlain_
==17024== by 0x3804D672: handle_syscall (scheduler.c:824)
==17024== by 0x3804E676: vgPlain_scheduler (scheduler.c:1018)
==17024== by 0x38060CB0: run_a_thread_