[ 
https://issues.apache.org/jira/browse/HDDS-11491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Agrawal updated HDDS-11491:
---------------------------------
    Description: 
Observed certain task of Directory deletion is ignored, and retry same 
directory again.

Issue:

Ratis avoid submit request (considering replay) for condition if "clientId" and 
callID is same.

AbstractKeyDeletingService:
{code:java}
private static ClientId clientId = ClientId.randomId();{code}
This is derived by DirectoryDeletingService, KeyDeletingService, ...

CallId is separate object for each derived class, but if callId update is in 
same/similar pace for all, can cause ignoring of ratis submit (considering 
replay).

This got hit when the service deletion period is made same of 1min each.

As fix, need to make clientId specific to each service.

 

  was:
Observed certain task of Directory deletion is ignored, and retry same 
directory again.

Issue:

Ratis avoid submit request (considering replay) for condition if "clientId" and 
callID is same.

AbstractKeyDeletingService:
{code:java}
private static ClientId clientId = ClientId.randomId();{code}
This is derived by DirectoryDeletingService, KeyDeletingService, ...

CallId is separate object for each derived class, but if callId update is in 
same/similar pace for all, can cause ignoring of ratis submit (considering 
replay).

 

As fix, need to make clientId specific to each service.

 


> DirectoryDeletion task ignored via ratis
> ----------------------------------------
>
>                 Key: HDDS-11491
>                 URL: https://issues.apache.org/jira/browse/HDDS-11491
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: OM
>            Reporter: Sumit Agrawal
>            Assignee: Sumit Agrawal
>            Priority: Major
>
> Observed certain task of Directory deletion is ignored, and retry same 
> directory again.
> Issue:
> Ratis avoid submit request (considering replay) for condition if "clientId" 
> and callID is same.
> AbstractKeyDeletingService:
> {code:java}
> private static ClientId clientId = ClientId.randomId();{code}
> This is derived by DirectoryDeletingService, KeyDeletingService, ...
> CallId is separate object for each derived class, but if callId update is in 
> same/similar pace for all, can cause ignoring of ratis submit (considering 
> replay).
> This got hit when the service deletion period is made same of 1min each.
> As fix, need to make clientId specific to each service.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to