[
https://issues.apache.org/jira/browse/HBASE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449443#comment-13449443
]
stack commented on HBASE-879:
-----------------------------
I'm fine closing this. The issue Michael talks of in original comment is not
an issue any more; the DFSClient should pick up blocks in new location getting
new block locations list from namenode. Andrew's comment on hbase being able
to survive a dfs restart under it is still to be fixed (we have other issues to
cover this though)
> When dfs restarts or moves blocks around, hbase regionservers don't notice
> --------------------------------------------------------------------------
>
> Key: HBASE-879
> URL: https://issues.apache.org/jira/browse/HBASE-879
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.18.1, 0.19.0
> Reporter: Michael Bieniosek
>
> Since the hbase regionservers use a DFSClient to keep handles open to the
> dfs, if the dfs blocks move around (typically because of a dfs restart, but
> can also happen if datanodes die or blocks get shuffled around), the
> regionserver will be unable to service the region. It would be nice if the
> DFSClient that the regionservers use could notice this case and refresh the
> block list.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
