Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <165697283.1253158917689.JavaMail.jira@brutus>
Date: Wed, 16 Sep 2009 20:41:57 -0700 (PDT)
From: "Noble Paul (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1439) Enhance PollInterval for Java
 Replication
In-Reply-To: <177984296.1253158557626.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Noble Paul commented on SOLR-1439:
----------------------------------

isn't it same as SOLR-1431?

> Enhance PollInterval for Java Replication
> -----------------------------------------
>
>                 Key: SOLR-1439
>                 URL: https://issues.apache.org/jira/browse/SOLR-1439
>             Project: Solr
>          Issue Type: New Feature
>          Components: replication (java)
>         Environment: ALL
>            Reporter: Bill Bell
>             Fix For: 1.4
>
>
> I am not a huge fan of PollInterval. It would be great to add an option to get the Index based on exact time: PollTime="*/15 * * * *" That would run at every 15 minutes based on the clock. i.e. 1:00pm, 1:15pm, 1:30pm, 1:45pm, etc. All my slaves are sync'd using NTP, so this would work better. Since each slave starts differently, we cannot set the PollInterval="00:15:00" since they would get different indexes based on when they start. The other option would be to suspend polling - and start - which would be very manual I guess. Setting the PollInterval to 10 seconds would be getting a new index when the old one is still warming up. Even 10 seconds interval would not be good, since we get so many updates, each server would have different indexes. With Snap we don't have this issue.
> We get SOLR updates frequently and since they are large we cannot wait to do a commit at the 15 minute mark using cron. Optimize just takes too long.
> On our system we need to limit how often the slaves get the new index. We would like all slaves to get the index at the same time.
> From Noble Paul:
> The default pollInterval can behave the way you want (so that the fetches are synchronized in time by the clock). Raise a separate issue and we can fix it

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.