The dump below was taken from the Verity status.log file.
Running CFMX 7.0.2 in a Windows environment. We have a scheduled
task that processes a queue of directories that need indexing.
These directories are processed into one collection. I noticed in
the log file that the last set of files appear to have been queued
up for some "Async slot".
Subsequent updates to this collection with documents that
have new category and categorytree values do not appear when
performing a <cfcollection action="list">. The only way to
get these items to return from a search is to call then out with a
"cf_url <contains> {directorypath}" type query. Any search of
the category or categorytree with the new values results in no data
found.
Has anyone else experienced this kind of behavior, and come
up with a solution?
2007-01-25 13:04:02 Status: [VDKCB ws=cf_jrpp-18_workspace]
Bulk insert operation into E:/JRun4/verity/collections/sspmeetings
(946) from
E:/JRun4/verity/Data/services/ColdFusionK2_indexserver1/tmp/cf_jrpp-18_workspace_BIFDIR_sspmeetings/bif.txt
(0, 0)
2007-01-25 13:04:02 Status: [VDKCB ws=cf_jrpp-18_workspace]
Initializing dataset 00000946.ddd, index 00000946.did
2007-01-25 13:06:44 Status: [VDKCB ws=cf_jrpp-18_workspace]
Totals (1173 documents): 8805 para 29285 sent 1036702 word (18544
Kb used)
2007-01-25 13:06:45 Status: [VDKCB ws=cf_jrpp-18_workspace]
Optimizing database layout
2007-01-25 13:06:45 Status: [VDKCB ws=cf_jrpp-18_workspace]
(162797 ms) Indexed 1173 docs into
E:/JRun4/verity/collections/sspmeetings/parts/00000946
2007-01-25 13:06:47 Status: [VDKCB ws=cf_jrpp-18_workspace]
Writing partition index data
2007-01-25 13:06:48 Status: OdkWrk4 service worker thread [0]
executing request K2IdxCollOperate
2007-01-25 13:13:00 Status: OdkWrk5 service worker thread [0]
executing request K2OdkWSOpen
2007-01-25 13:13:00 Status: K2Index WorkSpace Open:
[WorkSpace=cf_jrpp-19_workspace, Owner=anonymous]
2007-01-25 13:13:00 Status: OdkWrk5 service worker thread [0]
executing request K2IdxCollOpen
2007-01-25 13:13:00 Status: K2 Index Server: Waiting for
available Async slot
2007-01-25 13:22:00 Status: OdkWrk6 service worker thread [0]
executing request K2OdkWSOpen
2007-01-25 13:22:00 Status: K2Index WorkSpace Open:
[WorkSpace=cf_jrpp-20_workspace, Owner=anonymous]
2007-01-25 13:22:00 Status: OdkWrk6 service worker thread [0]
executing request K2IdxCollOpen
2007-01-25 13:22:01 Status: K2 Index Server: Waiting for
available Async slot
2007-01-25 13:44:01 Status: OdkWrk7 service worker thread [0]
executing request K2OdkWSOpen
2007-01-25 13:44:01 Status: K2Index WorkSpace Open:
[WorkSpace=cf_jrpp-23_workspace, Owner=anonymous]
2007-01-25 13:44:01 Status: OdkWrk7 service worker thread [0]
executing request K2IdxCollOpen
2007-01-25 13:44:01 Status: K2 Index Server: Waiting for
available Async slot
2007-01-25 13:53:00 Status: OdkWrk8 service worker thread [0]
executing request K2OdkWSOpen
2007-01-25 13:53:00 Status: K2Index WorkSpace Open:
[WorkSpace=cf_jrpp-25_workspace, Owner=anonymous]
2007-01-25 13:53:00 Status: OdkWrk8 service worker thread [0]
executing request K2IdxCollOpen
2007-01-25 13:53:00 Status: K2 Index Server: Waiting for
available Async slot
2007-01-25 14:02:01 Status: OdkWrk9 service worker thread [0]
executing request K2OdkWSOpen
2007-01-25 14:02:01 Status: OdkWrk9 service worker thread [0]
executing request K2OdkWSOpen
2007-01-25 14:02:01 Status: K2Index WorkSpace Open:
[WorkSpace=cf_jrpp-28_workspace, Owner=anonymous]
2007-01-25 14:02:01 Status: OdkWrk9 service worker thread [0]
executing request K2IdxCollOpen
2007-01-25 14:02:01 Status: K2 Index Server: Waiting for
available Async slot
1
Reply
AdChoices