 |
 |
Bug or not bug, but we got past that issue. Adding that line helped. Thanks! We will add it to the qserv documentation. Jacek On 07/28/2015 01:49 PM, Andrew Hanushevsky wrote: > Hi Jacek, > > It's a bug, sigh. You can get around it by using the following directive: > > cms.space mwfiles linger 0 > > Notice the addition of another option. The code wants at least one > option and while it accepts and uses mwfiles it doesn't recognize that > it valid as the only option. The error message in the log file sort of > tells you that. > > Andy > > -----Original Message----- From: Jacek Becla > Sent: Tuesday, July 28, 2015 12:44 PM > To: qserv-l ; Thukral, Vaikunth ; Andrew Hanushevsky > Subject: Re: [QSERV-L] Fwd: Re: [QSERV-L] Error provisioning, msg=Unable > to write file; multiple files exist > > Andy, > > I tried adding that line but the cmsd won't start. > > The log file attached. > > Are you at slac? Maybe you wanna stop by? > > Jacek > > > > > > > On 07/27/2015 04:44 PM, Jacek Becla wrote: >> Thanks Andy, it is simpler than I expected :) >> >> I am forwarding to the list. >> >> Vaikunth, can you try? >> >> Jacek >> >> >> >> -------- Forwarded Message -------- >> Subject: Re: [QSERV-L] Error provisioning, msg=Unable to write file; >> multiple files exist >> Date: Mon, 27 Jul 2015 16:03:42 -0700 >> From: Andrew Hanushevsky <[log in to unmask]> >> To: Jacek Becla <[log in to unmask]> >> >> Yes, I recall this. Daniel had a patch for this and it got rolled into >> the >> mainline controlled by an option. You must specify the option in the >> config file to get around this issue. The directive and option is: >> >> cms.space mwfiles >> >> you might have additional options in effect. Simply add he mwfiles if so. >> Only the redirector uses this option but it's OK to have it everywhere. >> >> Andy >> >> On Mon, 27 Jul 2015, Jacek Becla wrote: >> >>> We run into a problem... when we running a query that has no results >>> >>> select * from Object where id <non existent id> >>> >>> qserv can't map it to any chunk (makes sense), and it ends up executing >>> >>> SELECT * >>> FROM qservTest_case01_qserv.Object_1234567890 AS QST_1_ >>> WHERE objectId=430213989000 >>> >>> the chunk 1234567890 is a special chunk and it exists on all nodes. >>> >>> And that upsets our code >>> >>> (build/qdisp/QueryResource.cc:61) - Error provisioning, msg=Unable to >>> write >>> file; multiple files exist. code=2 >>> >>> So I suspect if we started replicating our chunks we'd be in trouble >>> too.... >>> >>> Anyway, we should open a ticket and fix that, but I wanted to collect >>> more info before doing it, especially since I seem to recall we talked >>> about something similar with AndyH. >>> >>> Any recollections anyone? >>> >>> Jacek >>> >>> ######################################################################## >>> 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 > ######################################################################## 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