get_scheduler_factory() fails assertion.

Bug #362972 reported by Jay Pipes
2
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Medium
Monty Taylor

Bug Description

jpipes@serialcoder:~/repos/drizzle/trunk$ ./drizzled/drizzled --datadir=/home/jpipes/repos/drizzle/trunk/var --innodb_buffer_pool_size=64M --innodb_log_buffer_size=8M --innodb_log_file_size=32M --innodb_thread_concurrency=0 --scheduler=multi-thread --port=9999 &
[1] 3755

InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins.
090417 11:31:38 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090417 11:31:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
090417 11:31:38 InnoDB Plugin 1.0.3 started; log sequence number 46419
./drizzled/drizzled: ready for connections.
Version: '2009.04.994-trunk' socket: '' port: 9999 Source distribution
jpipes@serialcoder:~/repos/drizzle/trunk$ ./client/drizzle --port=9999 --shutdown
drizzled: scheduling.cc:59: Scheduler& get_thread_scheduler(): Assertion `scheduler_factory != __null' failed.
drizzled: scheduling.cc:59: Scheduler& get_thread_scheduler(): Assertion `scheduler_factory != __null' failed.
ERROR:
drizzle_state_read:read:end of file
[1]+ Aborted ./drizzled/drizzled --datadir=/home/jpipes/repos/drizzle/trunk/var --innodb_buffer_pool_size=64M --innodb_log_buffer_size=8M --innodb_log_file_size=32M --innodb_thread_concurrency=0 --scheduler=multi-thread --port=9999

Revision history for this message
Jay Pipes (jaypipes) wrote :

Not just on shutdown. Assertion fails for a simple client connection:

jpipes@serialcoder:~/repos/drizzle/trunk$ ./client/drizzle --user=root --port=9999
drizzled: scheduling.cc:59: Scheduler& get_thread_scheduler(): Assertion `scheduler_factory != __null' failed.
drizzled: scheduling.cc:59: Scheduler& get_thread_scheduler(): Assertion `scheduler_factory != __null' failed.
ERROR:
drizzle_state_read:read:end of file
[1]+ Aborted ./drizzled/drizzled --datadir=/home/jpipes/repos/drizzle/trunk/var --innodb_buffer_pool_size=64M --innodb_log_buffer_size=8M --innodb_log_file_size=32M --innodb_thread_concurrency=0 --scheduler=multi-thread --port=9999

Changed in drizzle:
assignee: nobody → eday
importance: Undecided → Medium
summary: - assert() failed on shutdown
+ get_scheduler_factory() fails assertion.
Revision history for this message
Jay Pipes (jaypipes) wrote :

Setting back to medium. This only occurs when setting --scheduler=multi-thread. Re-assigning to Monty, since these seems plugin-only related...

Monty, this only occurs when someone makes a typo setting the scheduler...

Changed in drizzle:
importance: Medium → Critical
status: New → Confirmed
assignee: eday → mordred
importance: Critical → Medium
Revision history for this message
Jay Pipes (jaypipes) wrote :

This was fixed some time ago...

Changed in drizzle:
milestone: none → aloha
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.