Comment 5 for bug 455137
Revision history for this message
| Brian Aker (brianaker) wrote Re: [Bug 455137] Re: Drizzleslap hangs with over 175 connections | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi!
Odd are... bug in drizzleslap. I've not looked at it in sometime. It
is still using the my_getopt junk so it links to the mysys mess... so
it probably has stuff dinking with its threads.
Cheers,
-Brian
On Nov 5, 2009, at 6:33 PM, Eric Day wrote:
> Something seems to be broken once we exceed the back_log count. Once
> getting drizzleslap to hang, I dumped the active sockets for each
> process:
>
> eday@orisndriz0
> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
> drizzlesl 32531 eday 3u IPv4 10320113 TCP localhost:54858-
> >localhost:9306 (CLOSE_WAIT)
> drizzlesl 32531 eday 185u IPv4 10324113 TCP localhost:56240-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 186u IPv4 10324115 TCP localhost:56241-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 187u IPv4 10324117 TCP localhost:56242-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 188u IPv4 10324119 TCP localhost:56243-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 189u IPv4 10324121 TCP localhost:56244-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 190u IPv4 10324123 TCP localhost:56245-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 191u IPv4 10324125 TCP localhost:56246-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 192u IPv4 10324127 TCP localhost:56247-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 193u IPv4 10324129 TCP localhost:56248-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 194u IPv4 10324131 TCP localhost:56249-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 195u IPv4 10324133 TCP localhost:56250-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 196u IPv4 10324135 TCP localhost:56251-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 197u IPv4 10324137 TCP localhost:56252-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 198u IPv4 10324139 TCP localhost:56253-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 199u IPv4 10324141 TCP localhost:56254-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 200u IPv4 10324143 TCP localhost:56255-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 201u IPv4 10324145 TCP localhost:56256-
> >localhost:9306 (ESTABLISHED)
> drizzlesl 32531 eday 202u IPv4 10324147 TCP localhost:56257-
> >localhost:9306 (ESTABLISHED)
> eday@orisndriz0
> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
> drizzled 20886 eday 10u IPv4 10302592 TCP *:9306 (LISTEN)
> eday@orisndriz0
> tcp 0 0 127.0.0.1:56243 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56255 127.0.0.1:9306
> ESTABLISHED
> tcp 1 0 127.0.0.1:54858 127.0.0.1:9306
> CLOSE_WAIT
> tcp 0 0 127.0.0.1:56247 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56252 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56249 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56256 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56251 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56240 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56257 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56254 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56245 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56241 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56246 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56242 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56248 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56250 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56244 127.0.0.1:9306
> ESTABLISHED
> tcp 0 0 127.0.0.1:56253 127.0.0.1:9306
> ESTABLISHED
>
>
> As you can see, drizzleslap thinks it has valid connections and are
> all blocking in poll(), but the server has no knowledge of the
> active connections. The OS should be causing poll() to return
> POLLERR or POLLHUP inside of drizzleslap, rather than have them
> block indefinitely for POLLIN.
>
> --
> Drizzleslap hangs with over 175 connections
> https:/
> You received this bug notification because you are a member of
> Drizzle-
> developers, which is subscribed to Drizzle.
>
> Status in A Lightweight SQL Database for Cloud and Web: Confirmed
>
> Bug description:
> Running drizzleslap with any number connections great than 175
> causes it to hang:
>
> Example:
> drizzleslap --port=9306 --label=write --concurrency=200 --
> iterations=10 --engine=innodb --number-int
> -cols=2 --number-
> add-autoincrement --auto-genera
> te-sql-
>
> attaching to the process through gdb gives:
> (gdb) bt
> #0 0x00007f3c0d98756d in pthread_
> from /lib/libpthread
> #1 0x00000000004051c2 in run_scheduler (sptr=0xa462e0,
> stmts=0xa44350, concur=200, limit=0) at client/
> #2 0x0000000000408e12 in concurrency_loop (con=0x7fff16fd
> current=200, eptr=0xa45970) at client/
> #3 0x0000000000409101 in main (argc=0, argv=0xa44178) at client/
> drizzleslap.cc:377
>
> adding -v -v -v for lots of verbose output shows that it hangs while
> doing a bunch of inserts:
> ........
> INSERT INTO t1 VALUES (NULL,
> 1576223060,
> ,'nHujWOi8H3Sww
> ','3gREyYw2S9ls
> ','4dgQpQ2FFmHe
> ');
> INSERT INTO t1 VALUES (NULL,
> 1322166549,
> ,'7ugNokudvtyn2
> ','vKZ4d0C52570
> ','3eiPRAISuv1e
> ');
> INSERT INTO t1 VALUES (NULL,
> 116314197,805287600
> ,'e8YWNpN1C9JgA
> ','Qi9fT8HrX4S4
> ','8t2WJuJx7Fam
> ');
> INSERT INTO t1 VALUES (NULL,
> 1407841593,32683953
> ,'YZeAmRm1NWuht
> ','XumsvTL8Dzbx
> ','zMdGYMnyJhxl
> ');
> INSERT INTO t1 VALUES (NULL,
> 1471079933,
> ,'a1vMmjn2ZKuaF
> ','4QZ4NXTJ5SDe
> ','lGr5WzIy2vC6
> ');
>
> For now modifying all tests at http://
> to only use a max of 175 connections