Discussion

PR_SYS_WORKINDEXER_QUEUE Entries

“PR_SYS_WORKINDEXER_QUEUE” table is used to have entries for lucene update while Rules and work objects are enabled for Data Text Indexing.

if any rules got deleted, will those entries from the “PR_SYS_WORKINDEXER_QUEUE” table be deleted automatically?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Comments

Keep up to date on this post and subscribe to comments

May 22, 2012 - 8:50pm

The sys-workindexer queue is used for DATA and WORK indexing. Rule indexing is a legacy process that does not use a queue. Workindexer records are deleted after the index entry has been applied.

Keep in mind that the lucene index is 'owned' by only one node on one system, and that nodeID and hostname is set in a dysnamic system setting.

WorkIndexer agent must run on the specific node per the system setting to process a lucene index queue entry. If workindexer agent runs on any other node, it simply puts the record back in queue.

Check that you have properly configured your agent and index settings.

Stop the workindexer on all nodes other than the index owning node - its just wasting resources.

Btw - do you really WANT to use lucene index for DATA or WORK? DATA is enabled by default. I find it to be of dubious value.

It is not uncommon to see the lucene index settings to be incorrect and a massive amount of DATA index records piled up in the workindexer queue.
It is not uncommon to

May 22, 2012 - 8:52pm

The sys-workindexer queue is used for DATA and WORK indexing. Rule indexing is a legacy process that does not use a queue. Workindexer records are deleted after the index entry has been applied.

Keep in mind that the lucene index is 'owned' by only one node on one system, and that nodeID and hostname is set in a dysnamic system setting.

WorkIndexer agent must run on the specific node per the system setting to process a lucene index queue entry. If workindexer agent runs on any other node, it simply puts the record back in queue.

Check that you have properly configured your agent and index settings.

Stop the workindexer on all nodes other than the index owning node - its just wasting resources.

Btw - do you really WANT to use lucene index for DATA or WORK? DATA is enabled by default. I find it to be of dubious value.

It is not uncommon to see the lucene index settings to be incorrect and a massive amount of DATA index records piled up in the workindexer queue.
It is not uncommon to

Pega
May 3, 2012 - 11:21am

Firstly, have you reviewed whether records are piling up in the related queue? These should get processed and if not they need to be further investigated. This table holds work and data to be processed.

May 4, 2012 - 3:05pm

According to PDN class System-Work-Indexer Supports, advanced search for work objects. Used by the Pega-RULES agent to hold agent queue entries after a new work object is created. After Lucene indexing is complete, the agent queue entry is removed.

http://pdn.pega.com/productsupport/products/pegarulesprocesscommander/documents/prpc/help_v55/zstandardrules/rule-obj-classsystem-.asp

February 3, 2015 - 3:36pm

In one environment we had records in table PR_SYS_WORKINDEXER_QUEUE that were not getting cleared up.

I have done following steps to fix that.

1. In System -> Settings -> Search, Verify node ID was is correct or update it. This node ID gets updated to Dynamic System Setting indexing/hostid

2. Click on Re-Index button

3. Verify in SMA that SystemWorkIndexer agent is running. If not then stop and start it. If it doesn't start in first attempt then try couple of times.

 

After above steps, records are getting removed in table PR_SYS_WORKINDEXER_QUEUE.