Thanks...5 seconds should be quick enough. I suppose the upside to
this is that I can keep my indexes on the local machine.

Will let you know if I run into any problems.


On Jun 29, 7:48 pm, Pat Allan <[email protected]> wrote:
> In Delayed Job 1.8.5, it looks it checks for jobs every 5 seconds, but you 
> can change that:
>
>   Delayed::Worker.sleep_delay = 2
>
> I assume it's the same in the 2.x releases (when I last checked, I don't 
> think the code had changed that dramatically).
>
> --
> Pat
>
> On 30/06/2010, at 12:41 PM, gmoniey wrote:
>
>
>
> > I see...I guess my only option is to go with delayed jobs. From what I
> > have read in the docs, the delayed_delta job is a long living process
> > which periodically checks for delta objects. Do you have any details
> > on how often it wakes up and processes deltas? Is possible to set this
> > field?
>
> > Thanks.
>
> > arash
>
> > On Jun 29, 6:35 pm, Pat Allan <[email protected]> wrote:
> >> Yup, that's exactly the problem you'd be facing.
>
> >> --
> >> Pat
>
> >> On 30/06/2010, at 11:30 AM, gmoniey wrote:
>
> >>> Hi Pat,
>
> >>> Thanks for responding. I would like to stay away from delayed deltas
> >>> as we need items to be added to the indexes in realtime. If the index
> >>> files are accessible by all servers, is the issue then contention over
> >>> the same files when attempting to update the deltas?
>
> >>> On Jun 29, 5:55 pm, Pat Allan <[email protected]> wrote:
> >>>> When you're dealing with multiple servers, the best delta approach is 
> >>>> delayed deltas - and so you have the delayed job queue running on the 
> >>>> same machine that your index files (and probably searchd) are located on.
>
> >>>> That way, all the Sphinx files and processes are in one place, and delta 
> >>>> requests get put into the database, and then are handled by the queue.
>
> >>>> --
> >>>> Pat
>
> >>>> On 30/06/2010, at 10:45 AM, gmoniey wrote:
>
> >>>>> I'm transitioning my app to a multiple server setup, and I am trying
> >>>>> to figure out what the best approach is. From what I gather, the
> >>>>> following should be fine:
>
> >>>>> 1. Run searchd on 1 machine, and have it point to indexes on a nas
> >>>>> (which is accesible by all machines)
> >>>>> 2. Point other machines to the 1 searchd instance.
>
> >>>>> My concern/confusion is with deltas; from what I have read on the
> >>>>> other posts, the delta indexing may fail, but I'm not quite sure why.
> >>>>> Is it that multiple apps may be trying to write to the same files on
> >>>>> the nas?
>
> >>>>> --
> >>>>> You received this message because you are subscribed to the Google 
> >>>>> Groups "Thinking Sphinx" group.
> >>>>> To post to this group, send email to [email protected].
> >>>>> To unsubscribe from this group, send email to 
> >>>>> [email protected].
> >>>>> For more options, visit this group 
> >>>>> athttp://groups.google.com/group/thinking-sphinx?hl=en.
>
> >>> --
> >>> You received this message because you are subscribed to the Google Groups 
> >>> "Thinking Sphinx" group.
> >>> To post to this group, send email to [email protected].
> >>> To unsubscribe from this group, send email to 
> >>> [email protected].
> >>> For more options, visit this group 
> >>> athttp://groups.google.com/group/thinking-sphinx?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Thinking Sphinx" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/thinking-sphinx?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en.

Reply via email to