400
> Subject: Re: Solr 4.3 Master/Slave Issues
> From: erickerick...@gmail.com
> To: solr-user@lucene.apache.org
>
> kill -9 is evil, you aren't certain what the state is afterwards,
> so the presence of the lock file is not surprising..
>
> solrconfig.xml has a commented-out
server and take a long time,
> so i do issue a kill -9 command. Any other suggestion to do this without
> the locking.
>
> I would initiate a backup again and send the logs.
>
> regards,
> Ayush
>
> > Date: Fri, 5 Jul 2013 19:40:12 +0530
> > Subject: Re: So
s. This was not happening with our earlier setup of
> > solr3.6
> >
>
> Just to confirm, are you using the backup command of replication
> handler? Can you post a thread dump of the process to pastebin or
> http://apaste.info/ ?
>
> > Regards,
> >
> >
&g
read dump of the process to pastebin or
http://apaste.info/ ?
> Regards,
>
>
>> Date: Fri, 5 Jul 2013 16:49:24 +0530
>> Subject: Re: Solr 4.3 Master/Slave Issues
>> From: shalinman...@gmail.com
>> To: solr-user@lucene.apache.org
>>
>> This can mean mult
s not happening with our earlier setup of solr3.6
Regards,
> Date: Fri, 5 Jul 2013 16:49:24 +0530
> Subject: Re: Solr 4.3 Master/Slave Issues
> From: shalinman...@gmail.com
> To: solr-user@lucene.apache.org
>
> This can mean multiple things:
> 1. You had killed a solr process
This can mean multiple things:
1. You had killed a solr process earlier which left the lock file in place
2. You have more than one Solr core pointing to the same data directory
3. A solr process is already running and you are trying to start
another one with the same config.
On Fri, Jul 5, 2013 a
