08-26-2015 06:35 AM
Hello all,
Due to an issue with indxing running behind, I ran a dtrace on the EVIndexVolumesProcessor.
I restarted the indexig service.
I see at the end of the log :
20477 15:28:42.778 [61920] (EVIndexVolumesProcessor) <Work Item enqueuing thread:39356> EV-M {IndexVolumesManager} There are currently no available slots in the work items queue.
Are the items queued, and handled when slots are available? How do they come available? Can I check if the slots are 'moving'?
Thanks.
EV11SP1CHF2 on W2008R2
Solved! Go to Solution.
10-23-2015 07:51 PM
open a perfmon and add the EV index volume process. You can see the index volumes moving in the report.
If you dont see any movement, then theres something wrong with your index engine. Look for event ID 29057
https://www.veritas.com/support/en_US/article.TECH227713
08-26-2015 09:03 AM
From what I understand Index Volumes Processor internally queues up jobs (or work items) and processes them in a prioritized manner based on archive type and job type. Jobs are either one of two types; synchronization or sub task (i.e. Rebuild, Repair, Verify etc). I think the work items notifiy Index Volumes Processor when it's ready to give up a slot. If there are other work items on the queue, the running item will be suspended and placed back on the queue so that a new work item can be activated in its place.
Maybe somebody can correct me. I am not sure how to check if the slots are "moving" other than constantly dtracing maybe.
08-26-2015 09:56 AM
after restarting indexing, did indexing fully initialize before or after that line on the dtrace?
08-26-2015 11:10 PM
Service initialized fully before showing these entries:
41302 The Indexing Service has completed its initialization. The service is now functioning fully.
10-23-2015 07:51 PM
open a perfmon and add the EV index volume process. You can see the index volumes moving in the report.
If you dont see any movement, then theres something wrong with your index engine. Look for event ID 29057
https://www.veritas.com/support/en_US/article.TECH227713
10-26-2015 12:07 AM
It was related t this post of mine:
https://www-secure.symantec.com/connect/forums/ev11-indexing-running-behind-check
After the fix was applied, it started working again.