maria-discuss team mailing list archive

[Reindl Harald <h.reindl@xxxxxxxxxxxxx>]

Am 17.07.2017 um 15:22 schrieb Vladislav Vaintroub:
> On 17.07.2017 15:14, Reindl Harald wrote:
> > Am 17.07.2017 um 15:02 schrieb Vladislav Vaintroub:
> > > You are getting HY000/2002, the range starting with 2000 (ending iirc 
> > > 3000) is the error originating on client.  If I was to guess it is a 
> > > client-side connection timeout
> >
> > are you aware that the strace output below with "EAGAIN (Resource 
> > temporarily unavailable)" is from running strace on the myslqd PID?
> And what does it prove? With server doing non-blocking socket reads, 
> EAGAIN is expected , and handled by switching to poll(). Since long time 
> (if memory serves me right 10.0/MySQL 5.6), this is how 
> net_read_timeout/net_write_timeout are handled on Unixes,on the server 
> side

after 10.2.8 fixed https://jira.mariadb.org/browse/MDEV-13375 it proves 
that all the talking about timeouts and issue on the client side was 
nonsense as i said from the very begin

[harry@srv-rhsoft:~]$ ab -c 150 -n 1000000 -k http://corecms
Concurrency Level:      150
Time taken for tests:   214.193 seconds
Complete requests:      1000000
Failed requests:        0
Keep-Alive requests:    1000000
Total transferred:      4188197222 bytes
HTML transferred:       3777430423 bytes
Requests per second:    4668.69 [#/sec] (mean)
Time per request:       32.129 [ms] (mean)
Time per request:       0.214 [ms] (mean, across all concurrent requests)
Transfer rate:          19095.09 [Kbytes/sec] received

so longer any "HY000/2002): Resource temporarily unavailable"