QueueCatalog Tool Inadvertantly Triggers Indexing
I've recently installed QueueCalalog (with PloneQueueCatalog) and either I don't understand how it is intended to work (lacks documentation), or it isn't working the way it's intended to. My objects, which are similar to the ATFile content type of Archetypes, have PDF or MS Word files attached and bog down Zope if indexing is done on the SearchableText index for these immediately, while users are logged in and doing work during the day. When I configure QueueCatalog to select all of my indexes except SearchableText as ones that should update immediately, it seems to successfully queue a new first object I've created in Plone (and not convert and index the object by doing a portal_transform on its 'file' attachment attribute. This is fine for the first object, but as soon as I attempt to create a second such object, the queue gets processed. The way I understand queue processing is, there are two things that would trigger the processing of the queue: 1) A site manager logs into the ZMI, goes to the portal_catalog's Queue tab and clicks the 'Process' button. 2) The Process class of the QueueCatalog product is a thread and (by default) is hardcoded to sleep for 60 seconds at a time. When it wakes up, it will process the queue. With that in mind, I modified the Process.py to increase the interval fro 60 to 6000 seconds, but my queue still gets immediately processed upon the creation of a second object. Is this a bug, or am I misusing or misunderstanding the tool's design? Thanks in advance for any help - I couldn't find any good pointers on how to use the product. Ken Wasetis SPR Inc. kwasetis@sprinc.com
Ken Wasetis wrote:
Is this a bug, or am I misusing or misunderstanding the tool's design?
ATFile is making use of a special hook of TextIndexNG2 from Andreas Jung. The hook is called txng_get. It might (!) have to do something with the hook. That's the only thing that is special about ATFile in the sense of cataloging. I'm the main author of ATCT and the release manager of Archetypes. Please contact me if you were able to locate the issue. Christian PS: Please unfuck your mail/news client. It's not breaking the lines properly.
Ken Wasetis wrote at 2005-2-18 12:07 -0600:
I've recently installed QueueCalalog (with PloneQueueCatalog) and either I don't understand how it is intended to work (lacks documentation), or it isn't working the way it's intended to.
We are using "QueueCatalog" (a slightly optimized version) without problems. -- Dieter
That's great. So, in your case, what triggers the processing of the queue? Did you write a cron job to run at a certain time? Did you modify the hardcoded sleep interval of the Processor.py? Do you manually run it through the ZMI using the portal_catalog 'Queue' tab? Other? -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Saturday, February 19, 2005 12:46 PM To: Ken Wasetis Cc: zope-dev@zope.org Subject: Re: [Zope-dev] QueueCatalog Tool Inadvertantly Triggers Indexing Ken Wasetis wrote at 2005-2-18 12:07 -0600:
I've recently installed QueueCalalog (with PloneQueueCatalog) and either I don't understand how it is intended to work (lacks documentation), or it isn't working the way it's intended to.
We are using "QueueCatalog" (a slightly optimized version) without problems. -- Dieter
Ken Wasetis wrote at 2005-2-21 07:41 -0600:
So, in your case, what triggers the processing of the queue?
We have an external queue processor. Usually, it looks every second whether there is work to do and if so, processes the queue. -- Dieter
participants (3)
-
Christian Heimes -
Dieter Maurer -
Ken Wasetis