[HBASE-7276] Fix TestRegionServerMetrics failing test one more time

Author: adela

Summary:
Can't see how we get negative numbers there. I am putting the
test case in a separate class let's see if that will fix the problem

Test Plan: tested on my machine

Reviewers: liyintang, rshroff, manukranthk

Reviewed By: rshroff

CC: hbase-eng@

Differential Revision: https://phabricator.fb.com/D695499

Task ID: 1981461

git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.89-fb@1459459 13f79535-47bb-0310-9956-ffa450edef68
[89-fb] [HBASE-7509] Export quorum metrics from HRegionServer

Author: aaiyer

Summary:
DFSClient metrics are disbled to save CPU usage.
This diff will expoet the required quorum Read Metrics
from HRegionServer

Test Plan:
deploy to dev cluster and ensure that the
metrics are seen via ODS counter

part of the output from hbasedev131.ash3:
"hadoop.regionserver_quorumreadsdone": 23,
"hadoop.regionserver_quorumreadsexecutedincurthread": 0,
"hadoop.regionserver_quorumreadwins": 0,

Reviewers: liyintang, rshroff

Reviewed By: rshroff

CC: hbase-eng@

Differential Revision: https://phabricator.fb.com/D697700

git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.89-fb@1459460 13f79535-47bb-0310-9956-ffa450edef68
[0.89-fb] [master] Fix the order of handling MSG_REPORT_EXITING

Author: aaiyer

Summary:
Before this fix, we process all the region closes, before marking
the RS as dead. This causes an issue where all the transient region
assignments are placed on the exiting server (if it happens to be the
    primary). This would not happen, if the server were in the list
of dead servers.

But, because we add the server to the list of dead servers, after
processing the region closes, the server seems "alive and active"
during the assignment process. Fixing the order, so that the
region will be assigned to a different RS, (considering the exiting
    RS as dead.)

Test Plan:
test suite. only failure TestHRegionCloseRetry, also fails
without the diff

Push to TSH025 master and make sure that the regions are not assigned
back to the exiting server.

4 /tmp/2013-02-06_14_39_23_hbase-trunk_fixRSExitingOrder-mrFailures  Failed on
MR:  TestHRegionClose TestHRegionCloseRetry TestRegionServerMetrics
TestThriftServer
1 /tmp/2013-02-06_14_39_23_hbase-trunk_fixRSExitingOrder-localFailures  Failed
on Local:  TestHRegionCloseRetry
mv target/surefire-reports
mr_unit/2013-02-06_14_39_23_hbase-trunk_fixRSExitingOrder

Reviewers: liyintang

Reviewed By: liyintang

CC: hbase-eng@

Differential Revision: https://phabricator.fb.com/D701100

git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.89-fb@1459461 13f79535-47bb-0310-9956-ffa450edef68
[HBASE-7532] Enable the FavoredNodes for the HFileOutputFormat

Author: manukranthk

Summary: HFileOutputFormat has a writer embedded but it is not configured to use the FavoredNodes. This revision is to add that support to the HFileOutputFormat while it is used as an OutputFormat either the Mapper or the Reducer for a MapReduce task.

Test Plan: Unit Testing.

Reviewers: liyintang, kannan

Reviewed By: liyintang

CC: hbase-eng@, astewart

Differential Revision: https://phabricator.fb.com/D675950

Task ID: 1964673

git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.89-fb@1459462 13f79535-47bb-0310-9956-ffa450edef68
[master] Fast fail META and ROOT during rack reboots. Do not wait for 10 mins

Author: aaiyer

Summary:
Having .META. unavailable during rack failures can block the
client threads trying to fetch information from meta.

In case of a rack reboot. we will not wait for 10 minutes for these
servers.

Test Plan:
MR unit tests.
Deploy to dev cluster, and kill the rack with .META. or ROOT.
  - verify that the recovery takes off immediately
kill a normal rack.
  - verify that we do still wait for 10 mins.

Reviewers: kannan, kranganathan, liyintang

Reviewed By: liyintang

CC: hbase-eng@

Differential Revision: https://phabricator.fb.com/D544346

git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.89-fb@1459463 13f79535-47bb-0310-9956-ffa450edef68
[0.89-fb] [HBASE-7517] Improve the PFFE mechanism such that (i) Ensure that if a thread gets the AtomicBoolean for a single server, it will not be stopped to get the AtomicBoolean for a different server. (ii) PFFE is only thrown for threads that are not a

Author: aaiyer

Summary:
Improvements to the PFFE mechanism, so as to let the
retrying threads to handle errors as if they were not in PFFE mode.

Threads that are allowed to go through (1 per server) will follow the
same logic as normal threads -- when not in fast fail mode. (The only
    exception being that all errors will be logged as LOG.error).
These threads will never throw a PFFE.

Threads that are not allowed to go through, will throw PFFE Exception.

Test Plan:
Add unit test to debug.
Test it out on tsh025.

Reviewers: liyintang, kannan, kranganathan, adela

Reviewed By: liyintang

CC: hbase-eng@

Differential Revision: https://phabricator.fb.com/D690778

git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.89-fb@1459464 13f79535-47bb-0310-9956-ffa450edef68
[0.89-fb] [HBASE-7852] Ensure that the command line options are respected.

Author: aaiyer

Summary:
LoadIncrementalHFiles should extract the config options after
Tool.run() is called, to ensure that the command line overrides
are respected.

Test Plan:
Test out on the dev cluster, with command line overrides.
Ensure that the command line override for configuration settings is
respected

Reviewers: adela, liyintang

Reviewed By: liyintang

CC: hbase-eng@, ryandm

Differential Revision: https://phabricator.fb.com/D693206

git-svn-id: https://svn.apache.org/repos/asf/hbase/branches/0.89-fb@1459465 13f79535-47bb-0310-9956-ffa450edef68