"Number of Files in directory indexer/err is consistently above threshold" is reported under the indexer node
Article ID: 100033579
Updated On:
Description
Error Message
Index Threshold limit exceeded - 714=Directory threshold for {0.EN_US} exceeds; current count is {1.EN_US}
Cause
Resolution
Note the MSU ID of the files in the
The MSU ID is the INDEX:
1. On the Indexer Node, check the idxcheck.0.log.
Example:
[ERR] FILER: zebra
[ERR] SHARE: HoHome
[ERR] HELPER: 845
[ERR] INDEXDB: -1 (4.37 GB)
[ERR] DHASH: 163281264 (155.72 MB)
[ERR] FSSIZE: 25206521764772 bytes (22.93 TB)
[ERR] DIREVENTS: 88746 (create=97, read=88534, write=96, mkdir=19)
[ERR] OPEVENTS: 88746 (create=97, read=88534, write=96, mkdir=19)
[ERR] dentry: 3401692
[ERR] extension: 236
[ERR] segment_file: 2
[ERR] uentry: 5309
[ERR] ipentry: 62
[ERR] segment_batch: 71
[ERR] fentry: 30371869
[ERR] sentry: 1
[ERR] acl: 5772
[ERR] user_acl: 3906
[ERR] ace_search: 56655
[ERR] permdelta: 132029
[ERR] SEGMENTS: 2
[ERR] SEGSIZE: 6103040 (5.82 MB)
[ERR] INTEGRITY: ok
[ERR] STALE INDEXDB: 0 (0.00 Bytes), 0 file(s)
[ERR] STALE DIRHASH: 0 (0.00 Bytes), 0 file(s)
[ERR] STALE FILEHASH: 0 (0.00 Bytes), 0 file(s)
[ERR] STALE ACTINDEX: 0 (0.00 Bytes), 0 file(s)
2. If the Integrity is ok move the sqlite files from the
NOTE: If the Intergrity is not reported as ok, please open a support case with Veritas Technical Support for remedial actions.
3. From the Data Insight console: Settings > Data Insight Servers > Select and click the Indexer in question > Jobs > run the IndexWriterJob.
4. After the IndexWriterJob is completed, click on the Data Insight servers and check the status of the Health of the Indexer in question. It should be successful.
Issue/Introduction
