-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total? Ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn5wHEACgkQvRJB9CBtvwiG0ACfXzNNsyz9b5QuLA5qJOLRfQiN ZecAoJkS2YAS1zpXV/eTB1hNYPJ7dpaz =91WO -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Whatever was happening was out of control. It was killing a number of our websites and was eating up all the connections I needed to get in there and revoke privileges. I had to drop the database. I can provide last nights dump, but I don't think we can run on our database server in this state. Ken Kenneth Raffenetti wrote:
Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total?
Ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn5wXoACgkQvRJB9CBtvwhCXQCeIOp7N5BNOTKYmDFx74SGt1wf dkMAoI7u1gPGE/pnaaAxEjSAZuYZ1mzv =q3/t -----END PGP SIGNATURE-----
Ken, My access to the MySQL COBALT database shouldn't be more that a handful of connections at a time, not in the hundreds. I am defining a connection as a (in my case) PERL handle to the database but many read/write/updates. Note that there are other people using this database also. Can you send me some log information so I can track down which code I am running is causing problems? Anthony Kenneth Raffenetti wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Whatever was happening was out of control. It was killing a number of our websites and was eating up all the connections I needed to get in there and revoke privileges. I had to drop the database. I can provide last nights dump, but I don't think we can run on our database server in this state.
Ken
Kenneth Raffenetti wrote:
Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total?
Ken
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn5wXoACgkQvRJB9CBtvwhCXQCeIOp7N5BNOTKYmDFx74SGt1wf dkMAoI7u1gPGE/pnaaAxEjSAZuYZ1mzv =q3/t -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was seeing all of the connections from am-macs[1-8]. I will try to dig up the logs. When I bumped the max connection limit, I just got another 100 connections from the same machines to COBALT. Ken Anthony Jazokas wrote:
Ken,
My access to the MySQL COBALT database shouldn't be more that a handful of connections at a time, not in the hundreds. I am defining a connection as a (in my case) PERL handle to the database but many read/write/updates. Note that there are other people using this database also.
Can you send me some log information so I can track down which code I am running is causing problems?
Anthony
Kenneth Raffenetti wrote: Whatever was happening was out of control. It was killing a number of our websites and was eating up all the connections I needed to get in there and revoke privileges. I had to drop the database. I can provide last nights dump, but I don't think we can run on our database server in this state.
Ken
Kenneth Raffenetti wrote:
Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total?
Ken
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn5xhsACgkQvRJB9CBtvwjBwwCglFPcmnXKPWK1O82l9AHQT2EU 34YAoLSwL6s0hjNaZINddJJQ6RfW9wUX =a6nv -----END PGP SIGNATURE-----
If a program has a connection to COBALT table and the program ends without explicitly closing it will that keep using the available connection or will it get released automatically? I assume read/write/updates to the table do not use up connections? Is there a command I can run to see what connections I am using and how many are available? If so, can I kill the connection from the command line? Anthony Kenneth Raffenetti wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I was seeing all of the connections from am-macs[1-8]. I will try to dig up the logs. When I bumped the max connection limit, I just got another 100 connections from the same machines to COBALT.
Ken
Anthony Jazokas wrote:
Ken,
My access to the MySQL COBALT database shouldn't be more that a handful of connections at a time, not in the hundreds. I am defining a connection as a (in my case) PERL handle to the database but many read/write/updates. Note that there are other people using this database also.
Can you send me some log information so I can track down which code I am running is causing problems?
Anthony
Kenneth Raffenetti wrote: Whatever was happening was out of control. It was killing a number of our websites and was eating up all the connections I needed to get in there and revoke privileges. I had to drop the database. I can provide last nights dump, but I don't think we can run on our database server in this state.
Ken
Kenneth Raffenetti wrote:
Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total?
Ken
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn5xhsACgkQvRJB9CBtvwjBwwCglFPcmnXKPWK1O82l9AHQT2EU 34YAoLSwL6s0hjNaZINddJJQ6RfW9wUX =a6nv -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Answers in-line. Ken Anthony Jazokas wrote:
If a program has a connection to COBALT table and the program ends without explicitly closing it will that keep using the available connection or will it get released automatically?
Yes, but those connections will have to timeout first. Timeouts take 5 seconds, but they were clearly piling up quickly.
I assume read/write/updates to the table do not use up connections?
Reads/writes/updates *do* use connections.
Is there a command I can run to see what connections I am using and how many are available? If so, can I kill the connection from the command line?
You can log into the database from the command-line and use the "show processlist;" command to see current connections.
Anthony
Kenneth Raffenetti wrote: I was seeing all of the connections from am-macs[1-8]. I will try to dig up the logs. When I bumped the max connection limit, I just got another 100 connections from the same machines to COBALT.
Ken
Anthony Jazokas wrote:
Ken,
My access to the MySQL COBALT database shouldn't be more that a handful of connections at a time, not in the hundreds. I am defining a connection as a (in my case) PERL handle to the database but many read/write/updates. Note that there are other people using this database also.
Can you send me some log information so I can track down which code I am running is causing problems?
Anthony
Kenneth Raffenetti wrote: Whatever was happening was out of control. It was killing a number of our websites and was eating up all the connections I needed to get in there and revoke privileges. I had to drop the database. I can provide last nights dump, but I don't think we can run on our database server in this state.
Ken
Kenneth Raffenetti wrote:
Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total?
Ken
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn5ywwACgkQvRJB9CBtvwjl0wCcDB8ms8wsomOVnPydRWgE1sTP 6CkAoLjh/oThu5ZrL7G5YPA+GJfdnPap =uhOX -----END PGP SIGNATURE-----
Can you restore the COBALT database? Kenneth Raffenetti wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Answers in-line.
Ken
Anthony Jazokas wrote:
If a program has a connection to COBALT table and the program ends without explicitly closing it will that keep using the available connection or will it get released automatically?
Yes, but those connections will have to timeout first. Timeouts take 5 seconds, but they were clearly piling up quickly.
I assume read/write/updates to the table do not use up connections?
Reads/writes/updates *do* use connections.
Is there a command I can run to see what connections I am using and how many are available? If so, can I kill the connection from the command line?
You can log into the database from the command-line and use the "show processlist;" command to see current connections.
Anthony
Kenneth Raffenetti wrote: I was seeing all of the connections from am-macs[1-8]. I will try to dig up the logs. When I bumped the max connection limit, I just got another 100 connections from the same machines to COBALT.
Ken
Anthony Jazokas wrote:
Ken,
My access to the MySQL COBALT database shouldn't be more that a handful of connections at a time, not in the hundreds. I am defining a connection as a (in my case) PERL handle to the database but many read/write/updates. Note that there are other people using this database also.
Can you send me some log information so I can track down which code I am running is causing problems?
Anthony
Kenneth Raffenetti wrote: Whatever was happening was out of control. It was killing a number of our websites and was eating up all the connections I needed to get in there and revoke privileges. I had to drop the database. I can provide last nights dump, but I don't think we can run on our database server in this state.
Ken
Kenneth Raffenetti wrote:
Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total?
Ken
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkn5ywwACgkQvRJB9CBtvwjl0wCcDB8ms8wsomOVnPydRWgE1sTP 6CkAoLjh/oThu5ZrL7G5YPA+GJfdnPap =uhOX -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have restored it as well as bumped the max connection limit again. Ken Anthony Jazokas wrote:
Can you restore the COBALT database?
Kenneth Raffenetti wrote: Answers in-line.
Ken
Anthony Jazokas wrote:
If a program has a connection to COBALT table and the program ends without explicitly closing it will that keep using the available connection or will it get released automatically?
Yes, but those connections will have to timeout first. Timeouts take 5 seconds, but they were clearly piling up quickly.
I assume read/write/updates to the table do not use up connections?
Reads/writes/updates *do* use connections.
Is there a command I can run to see what connections I am using and how many are available? If so, can I kill the connection from the command line?
You can log into the database from the command-line and use the "show processlist;" command to see current connections.
Anthony
Kenneth Raffenetti wrote: I was seeing all of the connections from am-macs[1-8]. I will try to dig up the logs. When I bumped the max connection limit, I just got another 100 connections from the same machines to COBALT.
Ken
Anthony Jazokas wrote:
Ken,
My access to the MySQL COBALT database shouldn't be more that a handful of connections at a time, not in the hundreds. I am defining a connection as a (in my case) PERL handle to the database but many read/write/updates. Note that there are other people using this database also.
Can you send me some log information so I can track down which code I am running is causing problems?
Anthony
Kenneth Raffenetti wrote: Whatever was happening was out of control. It was killing a number of our websites and was eating up all the connections I needed to get in there and revoke privileges. I had to drop the database. I can provide last nights dump, but I don't think we can run on our database server in this state.
Ken
Kenneth Raffenetti wrote:
Please try to limit the number of connections you are making to the MySQL server. I have bumped the maximum number from 150 to 250. How many is your code going to make total?
Ken
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn50aYACgkQvRJB9CBtvwieAgCfSBa4UpAYG+B5i6U52poseFQa 3iEAniMDpXbLAE0NfPbQLrKs01oSXAK+ =HEo7 -----END PGP SIGNATURE-----
participants (2)
-
Anthony Jazokas -
Kenneth Raffenetti