Howard,
a client can be blacklisted, but in that case is Aborted connection to
be increased since the connection request is refused upfront.
@Johan, you say "I'm having trouble with clients aborting, but for some
reason they don't get logged."
could you please tell which exactly is the proble
On 06/12/2012 05:10 AM, Johan De Meersman wrote:
- Original Message -
From: "Claudio Nanni"
" Print out warnings such as Aborted connection... to the error log."
the dots are not telling if they comprise Aborted clients as well.
Hah, how's that for selective blindness. Totally missed t
Joey,
" I can not afford any downtime and the data is realtime. "
This is a very good reason for asking help to consultants.
If you ask "What is the best method for this setup? master-master or
master-slave?"
then the simple answer is master-slave, for any mysql setup, that is the
only safe mysq
It sounds like you are all consultants.
On Mon, Jun 11, 2012 at 4:46 PM, Baron Schwartz wrote:
> Yeah -- that was an unintentional omission. There are solo consultants
> like Ronald Bradford too.
>
> On Mon, Jun 11, 2012 at 3:14 PM, Andrew Moore wrote:
>> Not forgetting Pythian, Baron ;)
>>
>>
On 6/12/2012 9:37 AM, Johan De Meersman wrote:
... but too lazy to look for it myself right now :-p
I'm going to be running into (woot, scheduled problems :-p ) the 5.0 to 5.1
upgrade collation issue where German β is now collated as 's' instead of as
'ss', causing duplicate key errors.
The b
... but too lazy to look for it myself right now :-p
I'm going to be running into (woot, scheduled problems :-p ) the 5.0 to 5.1
upgrade collation issue where German β is now collated as 's' instead of as
'ss', causing duplicate key errors.
The basic solution is to set the collation to utf8_bin
Good morning.
The application is Java.
The database version is : Server version: 5.1.49-3 (Debian)
This is an example of the problem:
__
mysql> SET collation_connection = utf8_unicode_ci;
Query OK, 0 rows affected (0.00 sec)
mysql> show variables like '%colla%';
+-
No logging happens to /var/log/syslog|messages - I prefer and enable mysql's
own errorlog. The app logs are pretty much useless due to Java. Guess I'll just
have to badger the developers into profiling and at the same time set up
tcpdump schedules to analyze what happens on the wire.
For all I
- Original Message -
> From: "Claudio Nanni"
> " Print out warnings such as Aborted connection... to the error log."
> the dots are not telling if they comprise Aborted clients as well.
Hah, how's that for selective blindness. Totally missed that :-)
> I find the MySQL error log extreme
or you can check application logs to see why the client lost connectivity
from the app
On Tue, Jun 12, 2012 at 5:12 PM, Ananda Kumar wrote:
> is there anything you can see in /var/log/messages
>
>
> On Tue, Jun 12, 2012 at 5:08 PM, Claudio Nanni wrote:
>
>> Johan,
>>
>> "Print out warnings such
is there anything you can see in /var/log/messages
On Tue, Jun 12, 2012 at 5:08 PM, Claudio Nanni wrote:
> Johan,
>
> "Print out warnings such as Aborted connection... to the error log."
> the dots are not telling if they comprise Aborted clients as well.
> I find the MySQL error log extremely po
Johan,
"Print out warnings such as Aborted connection... to the error log."
the dots are not telling if they comprise Aborted clients as well.
I find the MySQL error log extremely poor, as far as I know it is one of
the MySQL features (like authentication) stuck to the dawn of MySQL times.
Very ha
Yo,
I'm having trouble with clients aborting, but for some reason they don't get
logged.
The documentation at http://preview.tinyurl.com/27w9a4x clearly states "If a
client successfully connects but later disconnects improperly or is terminated,
the server increments the Aborted_clients stat
13 matches
Mail list logo
