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

Yingyi Bu updated ASTERIXDB-1948:
---------------------------------
    Description: 
Refer to the rebalance design doc:
https://cwiki.apache.org/confluence/display/ASTERIXDB/Rebalance+API+and+Internal+Implementation

In the event of failures, there could be:

-- leaked source files (from metadata transaction a) which will be reclaimed in 
the next rebalance operation,  

-- or leaked target files (from metadata transaction b) which will not be 
reclaimed,  

-- or leaked node group name (from metadata transaction a) which doesn't 
prevent the success of the next rebalance operation.

  was:
Refer to the rebalance design doc:
https://cwiki.apache.org/confluence/display/ASTERIXDB/Rebalance+API+and+Internal+Implementation

In the event of failures, there could be:

-- leaked source files (from metadata transaction a) which will be reclaimed in 
the next rebalance operation,  

-- or leaked target files (from metadata transaction b) which will not be 
reclaimed,  

-- or leaked node group name (from metadata transaction b) which doesn't 
prevent the success of the next rebalance operation.


> Potential file leaks if crash happens during rebalance
> ------------------------------------------------------
>
>                 Key: ASTERIXDB-1948
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1948
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: CLUS - Cluster management
>            Reporter: Yingyi Bu
>            Assignee: Yingyi Bu
>
> Refer to the rebalance design doc:
> https://cwiki.apache.org/confluence/display/ASTERIXDB/Rebalance+API+and+Internal+Implementation
> In the event of failures, there could be:
> -- leaked source files (from metadata transaction a) which will be reclaimed 
> in the next rebalance operation,  
> -- or leaked target files (from metadata transaction b) which will not be 
> reclaimed,  
> -- or leaked node group name (from metadata transaction a) which doesn't 
> prevent the success of the next rebalance operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to