[
https://issues.apache.org/jira/browse/HADOOP-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565969#action_12565969
]
Konstantin Shvachko commented on HADOOP-1188:
---------------------------------------------
I actually found a way to write the test on Windows.
If I lock fsedits from the outside using FileChannel.lock() or tryLock() the
name-node
would not be able to log name-space operations and will stop using this
directory.
The real problem is to model this behavior on Unix.
Locking is advisory in Unix and the name-node will have to explicitely check
for the lock in order to
fail while synching fsedits. File.delete() or rename() does not help either
because once opened the file
is still accessible via its inode even though the link to the file is removed
from the containing directory.
We should open a separate jira if want such a test.
> processIOError() should update fstime file
> ------------------------------------------
>
> Key: HADOOP-1188
> URL: https://issues.apache.org/jira/browse/HADOOP-1188
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.10.1, 0.11.2, 0.12.2
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Priority: Blocker
> Fix For: 0.16.1
>
> Attachments: hadoop-1188.patch
>
>
> Name-node can have multiple directories to store the name space image and
> edits.
> During startup the name-node selects the latest image and reads it in memory.
> fstime stores the time of the latest checkpoint.
> If one of the directories becomes inaccessible during normal operation the
> name-node
> excludes it from the list, and never writes anything into it until restarted.
> Now if the the name-node restarts after excluding one of the directories, and
> if that
> excluded directory contained the latest image, then all modifications of the
> name space
> recorded in edits files in other directories starting from the moment the
> directory was
> excluded will be lost.
> We should update fstime in all remaining good directories after the exclusion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
