You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Amrit Verma (Jira)" <ji...@apache.org> on 2021/03/05 08:13:00 UTC
[jira] [Commented] (OAK-9375) Remote elastic index deletion job
incorrectly deletes indices
[ https://issues.apache.org/jira/browse/OAK-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295855#comment-17295855 ]
Amrit Verma commented on OAK-9375:
----------------------------------
This happened in case of large indices because of non existence of {{:nameSeed }}property on the index definition while indexing is running. Since the indexing of large index takes more time and during that time the remote index deletion task could run and delete the remote index since remote index name won't be found due to non existence of {{:nameSeed }}property.
Fix would be to not delete the remote index if remote index name is not found for an elastic index. Also we should increase the deletion threshold to 1 day since indexing should have finished by that time.
PR link - https://github.com/oak-indexing/jackrabbit-oak/pull/430/files
> Remote elastic index deletion job incorrectly deletes indices
> -------------------------------------------------------------
>
> Key: OAK-9375
> URL: https://issues.apache.org/jira/browse/OAK-9375
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
> Affects Versions: 1.38.0
> Reporter: Amrit Verma
> Assignee: Amrit Verma
> Priority: Major
> Fix For: 1.40.0
>
>
> The remote index deletion job introduced in OAK-9169 deletes remote indexes even when local indices exist.
> This is not often reproducible. I think this only happens when the index involved is somewhat big (few GBs).
> We need to investigate why this happens and then fix/disable this job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)