dbTalk Databases Forums  

Connection Timers

mailing.database.mysql-plusplus mailing.database.mysql-plusplus


Discuss Connection Timers in the mailing.database.mysql-plusplus forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Michael Katz
 
Posts: n/a

Default Connection Timers - 12-11-2005 , 08:00 PM






We have an application that uses the mysqlclient++ libraries for email
archival. We have recently been getting killed because of
http://bugs.mysql.com/bug.php?id=4143. It seems that mysql keels over
during a big query on a large database and it will not let our client
write to the db until the queries are completed. Since there are no
connection timers in the default client our app was hanging until the
query was completed. We applied the patches in the bug and we have a
patched client with connection timers but I want to ask a few questions
relative to these types of issues.


1) A lack of connection timers seems like a massive omission. There is
a patch for Linux, but as far as I know there is nothing available for
other OS's. It is impossible to build reliable database applications
without connection timers as we have learned. If we want to contribute
connection timer patches for other OS's for the ++client how can we go
about doing this?

2) Has anyone else been burned by this bug? If not, beware as there is
a lurking time bomb if your db can not keep up with load or fails for
some reason.

Thanks,
MK


--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw


Reply With Quote
  #2  
Old   
Warren Young
 
Posts: n/a

Default Re: Connection Timers - 12-12-2005 , 08:12 AM






Michael Katz wrote:
Quote:
1) A lack of connection timers seems like a massive omission.
MySQL++ doesn't do any network communication at all. None. All of that
is handled by libmysqlclient. Therefore, you should take this up on the
main MySQL mailing list. Any fixes to that underlying layer will also
fix MySQL++.

If there is any change needed to MySQL++, it will simply be to push
through any C-level API for changing the timeouts. If/when such APIs
are implemented, the necessary change to MySQL++ will probably be obvious.

Quote:
If we want to contribute
connection timer patches for other OS's for the ++client how can we go
about doing this?
Before submitting MySQL++ patches, read the HACKERS file that comes with
the distribution. For MySQL itself, I have no idea.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw



Reply With Quote
  #3  
Old   
Michael Katz
 
Posts: n/a

Default Re: Connection Timers - 12-12-2005 , 08:59 AM



Warren Young wrote:

Quote:
Michael Katz wrote:


1) A lack of connection timers seems like a massive omission.


MySQL++ doesn't do any network communication at all. None. All of
that is handled by libmysqlclient. Therefore, you should take this up
on the main MySQL mailing list. Any fixes to that underlying layer
will also fix MySQL++.
Thank you, I was confusing the 2 libraries. I will talk to the main
list about it.

Quote:
If there is any change needed to MySQL++, it will simply be to push
through any C-level API for changing the timeouts. If/when such APIs
are implemented, the necessary change to MySQL++ will probably be
obvious.

If we want to contribute connection timer patches for other OS's for
the ++client how can we go about doing this?


Before submitting MySQL++ patches, read the HACKERS file that comes
with the distribution. For MySQL itself, I have no idea.


--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.