[
https://issues.apache.org/jira/browse/SOLR-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734510#action_12734510
]
Noble Paul edited comment on SOLR-1305 at 7/23/09 1:09 AM:
-----------------------------------------------------------
bq.With a little help from Zookeeper, is that the plan?
not yet. Please help with details on how we can incorporate zookeeper into
this. I guess it should be a pluggable
was (Author: noble.paul):
bq.With a little help from Zookeeper, is that the plan?
not yet. Please help me with details on how we can incorporate zookeeper into
this. I guess it should be a pluggable
> Notification based replication instead of polling
> -------------------------------------------------
>
> Key: SOLR-1305
> URL: https://issues.apache.org/jira/browse/SOLR-1305
> Project: Solr
> Issue Type: New Feature
> Components: replication (java)
> Reporter: Noble Paul
> Fix For: 1.5
>
>
> Currently the only way for the slave to know about the availability of of new
> commit points is by polling. This means slaves should 'poll' very frequently
> to ensure that it gets the commit point immediately. if the changes to the
> master is less frequent, then this can be an unnecessary overhead. If would
> be nice if the slave can register itself with the master for notification on
> availability of new changes. After receiving the notification , the slave can
> trigger a poll and do what it does now. This may require SOLR-727 so that
> the slave can register its url with the master
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
