No idea - logs might help.
- Mark
On Jan 22, 2013, at 4:37 PM, Marcin Rzewucki <mrzewu...@gmail.com> wrote:
> Sorry, my mistake. I did 2 tests: in the 1st I removed just index directory
> and in 2nd test I removed both index and tlog directory. Log lines I've
> sent are related to the first case. So Solr could read tlog directory in
> that moment.
> Anyway, do you have an idea why it did not download files from leader ?
>
> Regards.
>
> On 22 January 2013 22:04, Mark Miller <markrmil...@gmail.com> wrote:
>
>> The logging shows that its finding transaction log entries.
>>
>> Are you doing anything else while bringing the nodes up and down?
>> Indexing? Are you positive you remove the tlog files? It can't really have
>> any versions if it doesn't read them from a tlog on startup...
>>
>> - Mark
>>
>> On Jan 22, 2013, at 3:31 PM, Marcin Rzewucki <mrzewu...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I'm using SolrCloud4.0 with 2 shards and I did such test: stopped Solr on
>>> shard1 replica, removed "index" and "tlog" directories and started Solr
>>> process again. Both directories were recreated fine. I was hoping that
>>> index files will be downloaded from shard1 leader. Unfortunately, they
>> were
>>> not. I tried many things to bring those files from leader, like:
>> collection
>>> reload, core reload, solr restart, cluster restart and nothing. There are
>>> no exceptions in log file:
>>>
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.cloud.RecoveryStrategy doRecovery
>>> INFO: Attempting to PeerSync from http://<leader_host>:8983/solr/ofac/
>>> core=ofac - recoveringAfterStartup=true
>>>
>>> INFO: Creating new http client,
>>>
>> config:maxConnectionsPerHost=20&maxConnections=10000&connTimeout=30000&socketTimeout=30000&retry=false
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.update.PeerSync sync
>>> INFO: PeerSync: core=ofac url=http://<replica_host>:8983/solr START
>>> replicas=[http://<leader_host>:8983/solr/ofac/] nUpdates=100
>>>
>>> INFO: Using Lucene MatchVersion: LUCENE_40
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.update.PeerSync handleVersions
>>> INFO: PeerSync: core=ofac url=http://<replica_host>:8983/solr Received
>> 100
>>> versions from http://<leader_host>:8983/solr/ofac/
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.update.PeerSync handleVersions
>>> *INFO: PeerSync: core=ofac url=http://<replica_host>:8983/solr Our
>>> versions are newer. ourLowThreshold=1420977810881642497
>>> otherHigh=1420977810935119873*
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.update.PeerSync sync
>>> INFO: PeerSync: core=ofac url=http://<replica_host>:8983/solr DONE. sync
>>> succeeded
>>>
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.core.SolrDeletionPolicy onInit
>>> INFO: SolrDeletionPolicy.onInit: commits:num=1
>>>
>>>
>> commit{dir=/solr/cores/ofac/data/index,segFN=segments_1,generation=1,filenames=[segments_1]
>>>
>>> INFO: QuerySenderListener done.
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.core.SolrCore registerSearcher
>>> INFO: [ofac] Registered new searcher
>>> Searcher@724d05famain{StandardDirectoryReader(segments_1:1)}
>>>
>>> INFO: Reading Solr Schema
>>> Jan 22, 2013 2:27:07 PM org.apache.solr.cloud.RecoveryStrategy doRecovery
>>> INFO: PeerSync Recovery was successful - registering as Active. core=ofac
>>>
>>> Only the one bolded line is weird for me. Why replica says that it has
>>> newer version ? Why it does not download index from the leader ?
>>> If it is well known bug, could you confirm that there's a patch for this
>> in
>>> 4.1 ?
>>>
>>> Kind regards.
>>
>>
