Hi Edwin, I'm using Solr 6.5.1
Am 04.05.2017 um 04:35 schrieb Zheng Lin Edwin Yeo: > Which version of Solr are you using? > > I am using Solr 6.4.2, it seems that both nodes are trying to write to the > same archived file. > > > Exception in thread "main" java.nio.file.FileSystemException: > C:\edwin\solr\server\logs\solr_gc.log.0.current -> > C:\edwin\solr\server\logs\archived\solr_gc.log.0.current: The process > cannot access the file because it is being used by another process. > > > Regards, > Edwin > > > On 3 May 2017 at 23:42, Erick Erickson <erickerick...@gmail.com> wrote: > >> That does look weird. Does the 7574 console log really get archived or >> is the 8983 console log archived twice? If 7574 doesn't get moved to >> the archive, this sounds like a JIRA, I'd go ahead and raise it. >> >> Actually either way I think it needs a JIRA. Either the wrong log is >> getting moved or the message needs to be fixed. >> >> Best, >> Erick >> >> On Wed, May 3, 2017 at 5:29 AM, Bernd Fehling >> <bernd.fehl...@uni-bielefeld.de> wrote: >>> While looking into SolrCloud I noticed that my logging >>> gets moved to archived dir by starting a new node. >>> >>> E.g.: >>> bin/solr start -cloud -p 8983 >>> -> server/logs/ has solr-8983-console.log >>> >>> bin/solr start -cloud -p 7574 >>> -> solr-8983-console.log is moved to server/logs/archived/ >>> -> server/logs/ has solr-7574-console.log >>> >>> Is this how it should be or do I have a misconfig? >>> >>> Regards >>> Bernd >> > -- ************************************************************* Bernd Fehling Bielefeld University Library Dipl.-Inform. (FH) LibTec - Library Technology Universitätsstr. 25 and Knowledge Management 33615 Bielefeld Tel. +49 521 106-4060 bernd.fehling(at)uni-bielefeld.de BASE - Bielefeld Academic Search Engine - www.base-search.net *************************************************************
