[ 
https://issues.apache.org/jira/browse/SOLR-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636792#comment-13636792
 ] 

Erick Erickson commented on SOLR-4742:
--------------------------------------

I would be very surprised if this were a problem and you're the only one who 
has run into it, so I'm guessing it's probably something you're doing.

First, what's your evidence? You have to give a lot more details before anyone 
can help you.

The maxTime and maxDocs parameters don't start counting until a doc has been 
indexed, so that's the first thing I'd look at.

Optimize should be pretty irrelevant except that it will force a commit.

As for your slaves, these parameters are completely irrelevant for your slaves. 
The slaves replicate from the master, so any delay here is 
1> the delay before committing on the master 
plus
2> the polling interval you have configured on your slave.

In future, please raise this kind of issue on the user's list before making a 
JIRA to be sure you're actually seeing a problem and not mis-interpreting 
expected behavior. You'll get lots faster responses there too.
                
> Autocommit configuration is not working
> ---------------------------------------
>
>                 Key: SOLR-4742
>                 URL: https://issues.apache.org/jira/browse/SOLR-4742
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (scripts), update
>    Affects Versions: 3.6.1
>         Environment: Red Hat Enterprise Linux Server release 5.7 (Tikanga)
> Weblogic 11g
>            Reporter: Gustavo Zopelari Nasu
>
> We've configured solrconfig.xml to autocommit after 500 docs added or 30 
> seconds as following the configuration bellow:
> <autoCommit>
>   <maxDocs>500</maxDocs>
>   <maxTime>30000</maxTime>
> </autoCommit>
> The problem that has been occured is after some time the commit is executed 
> after a long time reaching 40 minutes.
> That same problem has been happened with the slaves. The new documents 
> appears after a long time on the slaves.
> We executed the optimize but the problem happened again.

--
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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to