Try nuking the entire data directory. As in rm -rf .../data. Although
why it should report a problem with the lock file I'm not quite sure.
Best,
Erick
On Mon, Jun 23, 2014 at 12:10 AM, atp wrote:
> hi ,
>
> After rebooting all the cluster machine , we unable to start the solr .
> getting error
hi ,
After rebooting all the cluster machine , we unable to start the solr .
getting error messge like in solr log file,
We removed index directory contents solr//data/index.*/
and restared but getting 'â Recovery failed' from one of the node. please
help to resolve this.
666058 [RecoveryThr
Hi Markus ,
It been recoverd automatically after several attempts ,
once again thanks a lot for your help.
Now all the nodes are became live.
[zk: Hadoop-Main:7001(CONNECTED) 0] get /clusterstate.json
{"collection1":{
"shards":{
"shard1":{
"range":"8000-",
Thank you so much Markus ,
I have removed the contents from Index , now its working but one of the node
went Recovering state, the log says, please help this to make to live.
"â Unable to get file names for indexCommit generation: 2"
12118803 [qtp1490747277-11] INFO org.apache.solr.core.So
Hi - remove the lock file in your solr//data/index.*/
directory.
Markus
On Thursday, June 19, 2014 04:10:51 AM atp wrote:
> Hi experts,
>
> i have cnfigured solrcloud, on three machines , zookeeper started with no
> errors, tomcat log also no errors , solr log alos no errors reported but all
>
