Print

Print
Hi Fabrice,

I'm having a bit of trouble getting to this issue. I'm hoping you can find the time to check.

The line that caused the kernel panic is in modules/mysql/MySqlConnection.cc line 151.
Currently the line is fine and is:
        std::string const killSql = "KILL QUERY " + std::to_string(threadId);

This version of the line will occasionally cause the kernel panic (note the missing %1% that should be after KILL QUERY).
        std::string killSql = boost::str(bo ost::format("KILL QUERY ") % threadId);

Inserting that into any working version of qserv should cause the worker to crash occasionally. If you can't
find the time, I'll try it next time I'm working on the cluster.



On 01/19/16 01:19, Yvan Calas wrote:
[log in to unmask]" type="cite"> 
Hello,


On 15 Jan 2016, at 10:55, Fabrice Jammes <[log in to unmask]> wrote:

On my side, I think CentOS 7.x would be an excellent choice because it is supported by Docker install procedure.

If yes, CC-IN2P3 enginner could start upgrading ccqserv124 to CentOS 7 next week, in order to train for total cluster upgrade.

The server ccqserv124 has been reinstalled with CentOS 7. Docker-engine-1.9.1 (taken from [1]) has also been installed (@Fabrice: I let you finalise the configuration of Docker). In case of trouble or if I forgot to install something, let me know...

When you are ready, please try to reproduce the "kernel panic" issue ;)

Thanks,

Yvan


[1] http://yum.dockerproject.org/repo/main/centos/7/Packages/

---
Yvan Calas
CC-IN2P3 -- Storage Group
21 Avenue Pierre de Coubertin
CS 70202
F-69627 Villeurbanne Cedex
Tel: +33 4 72 69 41 73


########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1


Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1