Hi Sundar Yes, if FlagAsDeletedJob runs *after* DeltaIndexJob, then you should not see this problem. Is there a way to enforce that in Delayed Job?
— Pat > On 30 Jun 2015, at 8:14 am, Sundar Rajamanickam > <[email protected]> wrote: > > Hi > > I have a hourly (cron based) full indexer and delayed delta indexer setup. > > Say, when I update an object of 'Article' class - two delayed jobs get > enqueued - DeltaIndexJob and FlagAsDeletedJob. > > If only the FlagAsDeletedJob gets executed, and DeltaIndexJob does not get > executed. Now when the full indexer starts, it cleans up all the existing > jobs in the DJ queue - means the updated 'Article' object will not be > available in both the core and delta indices till the full indexing completes. > > Our full indexer runs for about 12-15 minutes everytime because of the size > of the database. This results in a significant delay, that the object becomes > available for search. > > Ensuring that the FlagAsDeletedJob runs after the DeltaIndexJob will help > reduce the impact, right? > > Thanks > Sundar Rajamanickam > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/thinking-sphinx > <http://groups.google.com/group/thinking-sphinx>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/thinking-sphinx. For more options, visit https://groups.google.com/d/optout.
