FoxTrot Search Forum
FoxTrot Search for macOS Forum
Home » Public Forums » FoxTrot Search User Forum » Indexing is stuck with HIERARCHICAL EXCEPTION CAUGHT (Indexing cannot continue)
Indexing is stuck with HIERARCHICAL EXCEPTION CAUGHT [message #1505] Fri, 05 August 2022 21:54 Go to next message
Kyle
Messages: 6
Registered: August 2021
Junior Member
I have an index that repeatedly gets stuck with the code from the logs shown below. I have tried rebuilding the index as well as creating a brand new index, but with the Indexed Data custom folder source. That folder is 85 TB. What is the source of this error? How might I troubleshoot or work around the issue?

2022/08/04, 19:01:05 -0700: ...Periodic commit done in 0 seconds!
2022/08/04, 19:11:07 -0700: Periodic commit started...
2022/08/04, 19:11:08 -0700: ...Periodic commit done in 1 seconds!
2022/08/04, 19:21:11 -0700: Periodic commit started...
2022/08/04, 19:21:11 -0700: ### HIERARCHICAL EXCEPTION CAUGHT HandleNextActionByPriority ###
    class=FoxT, what=12, when=33, err=0, name=Index
    class=FoxT, what=100, when=36, err=0, name=Index
    class=FoxT, what=100, when=35, err=0, name=Index
    class=FoxT, what=100, when=8, err=0, name=Index
2022/08/04, 19:21:22 -0700: Periodic commit started...
2022/08/04, 19:21:22 -0700: ### HIERARCHICAL EXCEPTION CAUGHT HandleNextActionByPriority ###
    class=FoxT, what=12, when=33, err=0, name=Index
    class=FoxT, what=100, when=36, err=0, name=Index
    class=FoxT, what=100, when=35, err=0, name=Index
    class=FoxT, what=100, when=8, err=0, name=Index
2022/08/04, 19:21:22 -0700: Periodic commit started...

Report message to a moderator

Re: Indexing is stuck with HIERARCHICAL EXCEPTION CAUGHT [message #1511 is a reply to message #1505] Thu, 18 August 2022 17:16 Go to previous messageGo to next message
Kyle
Messages: 6
Registered: August 2021
Junior Member
Has anyone had issues like the above, where an index is no longer able to update or rebuild?

Report message to a moderator

Re: Indexing is stuck with HIERARCHICAL EXCEPTION CAUGHT [message #1548 is a reply to message #1511] Mon, 31 October 2022 16:33 Go to previous message
Kyle
Messages: 6
Registered: August 2021
Junior Member
I worked around this issue by splitting the 89 TB folder into 5 indices. The data stayed in the same place, I just built more indices to capture it. In the end, this worked better because only a small amount of the 89 TB changes; the parts that don't change don't get re-indexed.

Report message to a moderator

Previous Topic: Preview shows only plain text for pdf
Next Topic: Is it advisable to index html files as txt?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Tue Dec 03 18:50:49 GMT+1 2024
FoxTrot Search Home