[
https://issues.apache.org/jira/browse/GEODE-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Huynh resolved GEODE-2459.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
> When node fails while renaming, new primary node resumes and may delete chunks
> ------------------------------------------------------------------------------
>
> Key: GEODE-2459
> URL: https://issues.apache.org/jira/browse/GEODE-2459
> Project: Geode
> Issue Type: Bug
> Components: lucene
> Affects Versions: 1.0.0-incubating
> Reporter: Jason Huynh
> Assignee: Jason Huynh
> Fix For: 1.2.0
>
>
> Current order of operations of a rename:
> 1.) Copy "old file" to "new file" File object
> 2.) Put into file region new file object
> 3.) Call remove directly on fileRegion for the "old file"
> When a node closes before step 3, the old file still exists in the file
> region.
> The new primary node will start up and when removing this old file (during
> normal lucene operations), it will erase the chunks. However the "new file"
> is still present and expects the chunks to be there.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
