Description
While investigating MB-44446 "could not open pindex: PINDEX_META: no such file or directory" multiple issues were found.
Changes associated with MB-44446 are limited to attempting to reduce lock contention, believe to contribute to loadDataDir taking excessive time (hours).
However, regardless of exactly how long loadDataDir takes, it's behavior is asynchronous, and can overlap with operations of the janitor. This has at least two problems:
1. Both loadDataDir and the janitor start pindexes methods often attempt to do the same work, around the same time. Increasing resource and lock contention unnecessarily.
2. The janitor mutates state operated on by loadDataDir (files/dirs on disk), which can lead to unexpected errors (no such file or directory as seen in MB-44446).
Changes related to this issue will attempt to address this deeper design issue.
Attachments
Issue Links
- relates to
-
MB-60313 [System Test][FTS] manager: could not open pindex path, pindex: could not open indexType: fulltext-index, err: error parsing mapping JSON: unexpected end of JSON input and couple of other 500 errors
- Closed
-
MB-22494 [FTS] Indexing is stuck while a restarted node is loading its dataDir
- Closed
-
MB-44446 [System Test][ERRO] manager: could not open pindex: PINDEX_META: no such file or directory
- Closed
Gerrit Reviews
For Gerrit Dashboard: MB-45375 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
152226,1 | MB-45375 - loadDataDir short wait at start | master | cbgt | Status: NEW | 0 | -1 |
161371,3 | MB-44446 - could not open pindex: no such file or directory | master | cbgt | Status: MERGED | +2 | +1 |