lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhuojunjian (JIRA)" <>
Subject [jira] [Commented] (SOLR-4506) [solr4.0.0] many index.{date} dir in replication node
Date Fri, 01 Mar 2013 09:35:12 GMT


zhuojunjian commented on SOLR-4506:

we have duplicated the issue today.
step 1: kill one replicate node (node A) , and make it not running.
step 2: import many data to the solrcloud so that its leader node created too many new indexes.
step 3: make node A running normally, and it will download files from its leader node.
step 4: before node A finishes the download operation, kill node A again.
step 5: then make node A running normally again, we will find there are two index dirs in
the ../data/., and if we continue step 3 ~ step 4 , the number of index dirs will increase

I think it may be a bug. do you have any idea about that? 
> [solr4.0.0] many index.{date} dir in replication node 
> ------------------------------------------------------
>                 Key: SOLR-4506
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0
>         Environment: the solr4.0 runs on suse11.
> mem:32G
> cpu:16 cores
>            Reporter: zhuojunjian
>             Fix For: 4.0
>   Original Estimate: 12h
>  Remaining Estimate: 12h
> in our test,we used solrcloud feature in solr4.0(version detail :
> the solrcloud configuration is 3 shards and 2 replications each shard.
> we found that there are over than 25 dirs which named index.{date} in one replication
node belonging to shard 3. 
> for example:
> index.20130217233335864  index.20130218012211880  index.20130218015714713  index.20130218023101958
 index.20130218030424083  tlog
> index.20130218005648324  index.20130218012751078  index.20130218020141293  
> the issue seems like SOLR-1781. but it is fixed in 4.0-BETA,5.0. 
> so is solr4.0 ? if it is fixed too in solr4.0, why we find the issue again ?
> what can I do?   

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message