I commented out the _queryMetadata lines from my current branch, and the 
test has been running without incident for several minutes.

-John

On 09/24/15 11:22, Salnikov, Andrei A. wrote:
> Hi John,
>
> I doubt that QMeta can overload mysql, it's relatively low volume
> queries compared to other stuff that we do on that mysql instance.
> Do we have anything interesting in mysql logs? Is mysql still alive
> after you see that error?
>
> Cheers,
> Andy
>
> John Gates wrote on 2015-09-24:
>> Andy S.,
>>
>> The latest code is overloading mysql when we run 60 queries
>> simultaneously (before it worked with over 100) the error is:
>>
>> SessOpen: [0x5be19400924 19:40:57.563 [0x7fa65218f700] ERROR
>> qmeta.QMetaMysql (core/modules/qmeta/QMetaMysql.cc:414) - SQL query
>> failed: UPDATE QInfo SET completed = NOW(), status = 'COMPLETED' WHERE
>> queryId = 21
>> ] Opening xroot://10.158.37.100:1094//chk/LSST/700
>> 0924 19:40:57.563 [0x7fa64116d700] ERROR qmeta.QMetaTransaction
>> (core/modules/qmeta/QMetaTransaction.cc:62) - Failed to abort
>> transaction: mysql error: (2006) MySQL server has gone away Unable to
>> execute query: ROLLBACK
>>
>>
>>
>> 0924 19:40:57.564 [0x7fa64116d700] ERROR root
>> (core/modules/ccontrol/userQueryProxy.cc:128) - Query ID is not
>> registered in metadata: 29 [in function completeQuery at
>> core/modules/qmeta/QMetaMysql.cc:420]
>>
>> ########################################################################
>> 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