Clustered samba is configured on virtual machines with a single CPU. When running SMB load, ctdb becomes unresonsive and starts consuming 100% of CPU. Here is the stack trace of the process: #0 0x00007f763794d1e0 in __write_nocancel () from /lib64/libpthread.so.0 #1 0x00007f7637dc92e6 in sys_write (fd=25, buf=buf@entry=0x7f7638ec9930, count=count@entry=48) at ../ctdb/common/system_util.c:403 #2 0x00007f7637dd4a68 in ctdb_queue_send (queue=0x7f7638bdb5d0, data=0x7f7638ec9930 "0", length=<optimized out>) at ../ctdb/common/ctdb_io.c:313 #3 0x00007f7637d927c8 in daemon_call_from_client_callback (state=<optimized out>) at ../ctdb/server/ctdb_daemon.c:358 #4 0x00007f7637da9339 in ctdb_become_dmaster (ctdb_db=ctdb_db@entry=0x7f7638c350d0, key=..., data=..., rsn=<optimized out>, record_flags=record_flags@entry=0, hdr=0x7f7638e734b0, hdr=0x7f7638e734b0) at ../ctdb/server/ctdb_call.c:408 #5 0x00007f7637da9a23 in ctdb_request_dmaster (ctdb=ctdb@entry=0x7f7638bbaba0, hdr=hdr@entry=0x7f7638e734b0) at ../ctdb/server/ctdb_call.c:638 #6 0x00007f7637da4089 in ctdb_input_pkt (ctdb=0x7f7638bbaba0, hdr=0x7f7638e734b0) at ../ctdb/server/ctdb_server.c:347 #7 0x00007f7637dd4714 in queue_io_read (queue=0x7f7638bdb9b0) at ../ctdb/common/ctdb_io.c:209 #8 queue_io_handler (ev=<optimized out>, fde=<optimized out>, flags=<optimized out>, private_data=<optimized out>) at ../ctdb/common/ctdb_io.c:279 #9 0x00007f76370ee2bb in epoll_event_loop (tvalp=0x7ffff73f1170, epoll_ev=0x7f7638bcac90) at ../lib/tevent/tevent_epoll.c:728 #10 epoll_event_loop_once (ev=<optimized out>, location=<optimized out>) at ../lib/tevent/tevent_epoll.c:926 #11 0x00007f76370ec787 in std_event_loop_once (ev=0x7f7638bcaa50, location=0x7f7637ddd360 "../ctdb/server/ctdb_daemon.c:1325") at ../lib/tevent/tevent_standard.c:114 #12 0x00007f76370e8f5d in _tevent_loop_once (ev=ev@entry=0x7f7638bcaa50, location=location@entry=0x7f7637ddd360 "../ctdb/server/ctdb_daemon.c:1325") at ../lib/tevent/tevent.c:530 #13 0x00007f76370e90fb in tevent_common_loop_wait (ev=0x7f7638bcaa50, location=0x7f7637ddd360 "../ctdb/server/ctdb_daemon.c:1325") at ../lib/tevent/tevent.c:634 #14 0x00007f76370ec727 in std_event_loop_wait (ev=0x7f7638bcaa50, location=0x7f7637ddd360 "../ctdb/server/ctdb_daemon.c:1325") at ../lib/tevent/tevent_standard.c:140 #15 0x00007f7637d93f7b in ctdb_start_daemon (ctdb=ctdb@entry=0x7f7638bbaba0, do_fork=<optimized out>, use_syslog=<optimized out>) at ../ctdb/server/ctdb_daemon.c:1325 #16 0x00007f7637d8e4a8 in main (argc=<optimized out>, argv=<optimized out>) at ../ctdb/server/ctdbd.c:321
Created attachment 10800 [details] Patch for 4.2
Hi Karo, Here's another ctdb defect for 4.2. Thanks.
Pushed to autobuild-v4-2-test.
Pushed to v4-2-test. Closing out bug report. Thanks!