[
https://issues.apache.org/jira/browse/HBASE-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856990#action_12856990
]
Lars George commented on HBASE-2117:
------------------------------------
I think we can close this issue as it is superseded by recent efforts to add
this sort of info to ZooKeeper. I recall this being discussed on IRC or the
Mailing List, this was also important to detect write failures during bulk
import if a region server is lost (it shuts itself down because it "loses"
contact to the DFS and panics) and does not flush its MemStores and *no* WAL is
used. Is there an issue for it already?
Or this issue could be postponed until that info is available (make it
dependent) in ZooKeeper and then adding the info is trivial?
> Simple check on the master overview page if the number of currently running
> regionservers is unchanged.
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-2117
> URL: https://issues.apache.org/jira/browse/HBASE-2117
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: master, regionserver
> Affects Versions: 0.20.2
> Reporter: Ferdy
> Attachments: HBASE-2117-v2.patch, HBASE-2117.patch
>
>
> Incidentally, it happens that some of our regionservers just stop working.
> The regionserver logs show some sort of termination and the affected
> regionserver is just removed from the master page. Besides the actual problem
> of the termination, what I was missing was some sort of warning (from either
> running client code or the master page) that some regionservers are having
> trouble.
> It seems like the Master is ok with the fact that a regionserver suddenly
> decides to stop. The result is that the clients depending on the data in
> Hbase will be presented an incomplete data set, at least as long as the
> failing regions are not re-assigned yet. In order to have this monitored, I
> decided to create a patch that exposes an extra piece of information on the
> master page. An 'OK:' is presented if the current number of regionservers is
> unchanged since the start of the processes. An 'ERROR:' is shown whenever the
> current number is not the same. What the master page does is reading the
> 'regionservers' file once, and remember the number of slaves so that is can
> be used in the check. (So afterwards changes to this file are not supported).
> Perhaps this is not the right way of doing things. Please let me know if
> there are any existing solutions for these issues.
> I will attach a patch right away.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
