hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-2304) HTTP status code incorrect for error conditions
Date Sun, 08 Jun 2014 21:57:06 GMT

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

Andrew Purtell resolved HBASE-2304.

    Resolution: Invalid

> HTTP status code incorrect for error conditions
> -----------------------------------------------
>                 Key: HBASE-2304
>                 URL: https://issues.apache.org/jira/browse/HBASE-2304
>             Project: HBase
>          Issue Type: Bug
>            Reporter: K M
>            Priority: Minor
> When there is a error given in the UI/JSPs, the HTTP status code is not set accordingly.
> For example, if the page output for master.jsp is:
> {{HTTP ERROR: 500
> Trying to contact region server null for region , row '', but failed after 3
> attempts.
> Exceptions:
> org.apache.hadoop.hbase.NotServingRegionException:
> org.apache.hadoop.hbase.NotServingRegionException: -ROOT-,,0}}
> The HTTP status code sent with the response is still "HTTP/1.1 200 OK".  This is a red
herring for some types of monitoring, though it is debatable if an HTTP status code of 4xx/5xx
reflect the server state or the state of the system being monitored.  It may well be that
HTTP 200 is OK, since the HTTP UI is responsive and correctly indicating a failed HBase cluster.

This message was sent by Atlassian JIRA

View raw message