Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 5.5
-
Fix Version/s: None
-
Component/s: OTHER
-
Labels:None
-
Environment:centos 6.x
Description
Hello,
Recently we've upgraded all our mysql servers to mariadb 5.5, and now started using pool of threads on a few systems. Systems are different, but all have MyISAM.
Unlike in thread-per-connection mode, while using pool of threads I see many unauthenticated connections in login state. Looks like it's 2nd phase and server awaits for final (authentication) connection after initial handshake been made. The connections come and immediately disappear. I checked with mysqlsniffer and couldn't find anything strange, everything works and looks like it's a normal behavior. Still I don't know if it's a normal thing : to see any "bad" states in processlist. So based on mysqlsniffer, all these threads numbers I see for unauth users are normally finishing. No aborted clients or any other error. Servers doing around 2-8 qps (under low load I don't see anyproblems). We use default settings for pool of threads, it's only enabled and using cpu number as num of pools.
So, wanted to ask if that's a normal behavior or not? (couldn't find anything anywhere). Of course resolving disabled...
Thanks!
Alex
| 5455148 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455163 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455172 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455187 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455196 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455211 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455220 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455235 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455244 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455259 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455268 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
| 5455283 | unauthenticated user | connecting host | NULL | Connect | NULL | login | NULL | 0.000 |
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I think it's normal if they don't hang there for long (and according your description they don't). Since a new connection needs to obtain a thread from the pool, there might be some delay comparing to thread-per-connection, so they stay in this state long enough to make it to the processlist. But I'm speaking without a real knowledge of internals, so I'll assign it to Sergei Golubchik for the second opinion.