-
Bug
-
Resolution: Fixed
-
Low
-
5.1.3
When the indexing write.lock isn't removed (e.g. if 100% disk usage is reached during indexing) this can create a number of problems including being unable to delete a space or see updates on the dashboard (see CONF-22981).
We should delete this if it's present on startup.
Form Name |
---|
[CONFSERVER-29004] Indexing write.lock remains even after a restart
Workflow | Original: JAC Bug Workflow v3 [ 2890655 ] | New: CONFSERVER Bug Workflow v4 [ 2982928 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2793946 ] | New: JAC Bug Workflow v3 [ 2890655 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2723777 ] | New: JAC Bug Workflow v2 [ 2793946 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2386804 ] | New: JAC Bug Workflow [ 2723777 ] |
Labels | Original: affects-server bugfix loyalty searching/indexing st10 | New: affects-server loyalty searching/indexing st10 |
Labels | Original: affects-server bugfix searching/indexing st10 | New: affects-server bugfix loyalty searching/indexing st10 |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2284032 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2386804 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2224346 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2284032 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2177997 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2224346 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1943454 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2177997 ] |