I really wouldn't go there, it sounds like there are endless
opportunities for errors!

How "real-time" is "real-time"? Could you fix this entirely
by
1> adjusting expectations for, say, 5 minutes.
2> adjusting your commit (on the master) and poll (on the slave) appropriately?

Best
Erick

On Thu, Jun 16, 2011 at 11:41 AM, zarni aung <zau...@gmail.com> wrote:
> Hi,
>
> I am designing my indexes to have 1 write-only master core, 2 read-only
> slave cores.  That means the read-only cores will only have snapshots pulled
> from the master and will not have near real time changes.  I was thinking
> about adding a hybrid read and write master core that will have the most
> recent changes from my primary data source.  I am thinking to query the
> hybrid master and the read-only slaves and somehow try to intersect the
> results in order to support near real time full text search.  Is this
> feasible?
>
> Thank you,
>
> Zarni
>

Reply via email to