You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Nikhil Chhaochharia <ni...@yahoo.com> on 2013/01/20 05:11:07 UTC
updateLog in Solr 4.1
Hi,
We run a SolrCloud cluster using Solr 4.0 updateLog is not configured since replication etc. is not required.
When we switched to Solr 4.1 RC1, we got the following exception and Solr failed to start. It looks like an updateLog in essential in Solr 4.1 The description for updateLog in solrconfig.xml says
"The log can grow as big as uncommitted changes to the index, so use of a hard autoCommit is recommended"
We index ~1TB data periodically (offline, no searches during indexing, start with empty index) and commit only after all the documents have been added. If we enable the updateLog, then the log will grow too large and if we commit periodically, then the indexing slows down substantially. Is there a way to use Solr 4.1 with the updateLog disabled? Any other suggestions?
Thanks,
Nikhil
Jan 19, 2013 10:06:22 AM org.apache.solr.cloud.SyncStrategy sync
SEVERE: No UpdateLog found - cannot sync
Jan 19, 2013 10:06:22 AM org.apache.solr.common.SolrException log
SEVERE: :java.lang.NullPointerException
at org.apache.solr.cloud.ShardLeaderElectionContext.runLeaderProcess(ElectionContext.java:187)
at
org.apache.solr.cloud.LeaderElector.runIamLeaderProcess(LeaderElector.java:156)
at org.apache.solr.cloud.LeaderElector.checkIfIamLeader(LeaderElector.java:100)
at org.apache.solr.cloud.LeaderElector.joinElection(LeaderElector.java:266)
at org.apache.solr.cloud.ZkController.joinElection(ZkController.java:842)
at org.apache.solr.cloud.ZkController.register(ZkController.java:668)
at org.apache.solr.cloud.ZkController.register(ZkController.java:634)
at org.apache.solr.core.CoreContainer.registerInZk(CoreContainer.java:890)
at org.apache.solr.core.CoreContainer.registerCore(CoreContainer.java:874)
at org.apache.solr.core.CoreContainer.register(CoreContainer.java:823)
at org.apache.solr.core.CoreContainer$3.call(CoreContainer.java:633)
at org.apache.solr.core.CoreContainer$3.call(CoreContainer.java:624)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Re: updateLog in Solr 4.1
Posted by Mark Miller <ma...@gmail.com>.
Indexing should def not slow down substantially if you commit every minute or something. Be sure to use openSearcher=false on the auto hard commit.
- Mark
On Jan 19, 2013, at 11:11 PM, Nikhil Chhaochharia <ni...@yahoo.com> wrote:
>
>
> Hi,
>
> We run a SolrCloud cluster using Solr 4.0 updateLog is not configured since replication etc. is not required.
>
>
> When we switched to Solr 4.1 RC1, we got the following exception and Solr failed to start. It looks like an updateLog in essential in Solr 4.1 The description for updateLog in solrconfig.xml says
> "The log can grow as big as uncommitted changes to the index, so use of a hard autoCommit is recommended"
>
> We index ~1TB data periodically (offline, no searches during indexing, start with empty index) and commit only after all the documents have been added. If we enable the updateLog, then the log will grow too large and if we commit periodically, then the indexing slows down substantially. Is there a way to use Solr 4.1 with the updateLog disabled? Any other suggestions?
>
>
> Thanks,
> Nikhil
>
>
>
> Jan 19, 2013 10:06:22 AM org.apache.solr.cloud.SyncStrategy sync
> SEVERE: No UpdateLog found - cannot sync
> Jan 19, 2013 10:06:22 AM org.apache.solr.common.SolrException log
> SEVERE: :java.lang.NullPointerException
> at org.apache.solr.cloud.ShardLeaderElectionContext.runLeaderProcess(ElectionContext.java:187)
> at
> org.apache.solr.cloud.LeaderElector.runIamLeaderProcess(LeaderElector.java:156)
> at org.apache.solr.cloud.LeaderElector.checkIfIamLeader(LeaderElector.java:100)
> at org.apache.solr.cloud.LeaderElector.joinElection(LeaderElector.java:266)
> at org.apache.solr.cloud.ZkController.joinElection(ZkController.java:842)
> at org.apache.solr.cloud.ZkController.register(ZkController.java:668)
> at org.apache.solr.cloud.ZkController.register(ZkController.java:634)
> at org.apache.solr.core.CoreContainer.registerInZk(CoreContainer.java:890)
> at org.apache.solr.core.CoreContainer.registerCore(CoreContainer.java:874)
>
> at org.apache.solr.core.CoreContainer.register(CoreContainer.java:823)
> at org.apache.solr.core.CoreContainer$3.call(CoreContainer.java:633)
> at org.apache.solr.core.CoreContainer$3.call(CoreContainer.java:624)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)