Thank you this is something that I wanted to hear. I knew the design was most likely flawed because I have never done Solr or any kind of full text searching, but needed an unbiased opinion. I think that if I were to tune the configs and pay close attention to the logs with lots of performance testing I might be able to achieve close to near real time (1-5 mins). I've been reading this mailing list, Hathi Trust, Lucid Imagination and other sites for insights.
Again Thank you. Zarni On Thu, Jun 16, 2011 at 9:49 PM, Erick Erickson <erickerick...@gmail.com>wrote: > 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 > > >
