date:20120913

Gregory Chanan created HBASE-6775:
-

 Summary: Use ZK.multi when available for HBASE-6710 0.92/0.94 
compatibility fix
 Key: HBASE-6775
 URL: https://issues.apache.org/jira/browse/HBASE-6775
 Project: HBase
  Issue Type: Improvement
  Components: zookeeper
Affects Versions: 0.92.2
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.92.3


HBASE-6710 fixed a 0.92/0.94 compatibility issue by writing two znodes in 
different formats.

If a ZK failure occurs between the writing of the two znodes, strange behavior 
can result.

This issue is a reminder to change these two ZK writes to use ZK.multi when we 
require ZK 3.4+. 

--
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

[jira] [Commented] (HBASE-6591) checkAndPut executed/not metrics


[ 
https://issues.apache.org/jira/browse/HBASE-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455223#comment-13455223
 ] 

Lars Hofhansl commented on HBASE-6591:
--

Whatever is more portable :)
If the old syntax is, then let's use that.

 checkAndPut executed/not metrics
 

 Key: HBASE-6591
 URL: https://issues.apache.org/jira/browse/HBASE-6591
 Project: HBase
  Issue Type: Task
  Components: metrics, regionserver
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.96.0


 checkAndPut/checkAndDelete return true if the new put was executed, false 
 otherwise.
 So clients can figure out this metric for themselves, but it would be useful 
 to get a look at what is happening on the cluster as a whole, across all 
 clients.

--
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

[jira] [Commented] (HBASE-6591) checkAndPut executed/not metrics


[ 
https://issues.apache.org/jira/browse/HBASE-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455226#comment-13455226
 ] 

Lars Hofhansl commented on HBASE-6591:
--

Oops... Wrong jira.
If that metric is useful and it's collection is cheap, let's add it.

 checkAndPut executed/not metrics
 

 Key: HBASE-6591
 URL: https://issues.apache.org/jira/browse/HBASE-6591
 Project: HBase
  Issue Type: Task
  Components: metrics, regionserver
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.96.0


 checkAndPut/checkAndDelete return true if the new put was executed, false 
 otherwise.
 So clients can figure out this metric for themselves, but it would be useful 
 to get a look at what is happening on the cluster as a whole, across all 
 clients.

--
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

[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase from starting in non-distributed mode


[ 
https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455227#comment-13455227
 ] 

Lars Hofhansl commented on HBASE-6504:
--

If head -1 is more portable, let's use that.

 Adding GC details prevents HBase from starting in non-distributed mode
 --

 Key: HBASE-6504
 URL: https://issues.apache.org/jira/browse/HBASE-6504
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Benoit Sigoure
Assignee: Michael Drzal
Priority: Trivial
  Labels: noob
 Attachments: HBASE-6504-output.txt, HBASE-6504.patch


 The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out 
 examples of variables that could be useful, such as adding 
 {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}.  This has 
 the annoying side effect that the JVM prints a summary of memory usage when 
 it exits, and it does so on stdout:
 {code}
 $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool 
 hbase.cluster.distributed
 false
 Heap
  par new generation   total 19136K, used 4908K [0x00073a20, 
 0x00073b6c, 0x00075186)
   eden space 17024K,  28% used [0x00073a20, 0x00073a6cb0a8, 
 0x00073b2a)
   from space 2112K,   0% used [0x00073b2a, 0x00073b2a, 
 0x00073b4b)
   to   space 2112K,   0% used [0x00073b4b, 0x00073b4b, 
 0x00073b6c)
  concurrent mark-sweep generation total 63872K, used 0K [0x00075186, 
 0x0007556c, 0x0007f5a0)
  concurrent-mark-sweep perm gen total 21248K, used 6994K [0x0007f5a0, 
 0x0007f6ec, 0x0008)
 $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool 
 hbase.cluster.distributed /dev/null
 (nothing printed)
 {code}
 And this confuses {{bin/start-hbase.sh}} when it does
 {{distMode=`$bin/hbase --config $HBASE_CONF_DIR 
 org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, 
 because then the {{distMode}} variable is not just set to {{false}}, it also 
 contains all this JVM spam.
 If you don't pay enough attention and realize that 3 processes are getting 
 started (ZK, HM, RS) instead of just one (HM), then you end up with this 
 confusing error message:
 {{Could not start ZK at requested port of 2181.  ZK was started at port: 
 2182.  Aborting as clients (e.g. shell) will not be able to find this ZK 
 quorum.}}, which is even more puzzling because when you run {{netstat}} to 
 see who owns that port, then you won't find any rogue process other than the 
 one you just started.
 I'm wondering if the fix is not to just change the {{if [ $distMode == 
 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work 
 around this annoying JVM misfeature that pollutes stdout.

--
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

[jira] [Commented] (HBASE-6775) Use ZK.multi when available for HBASE-6710 0.92/0.94 compatibility fix


[ 
https://issues.apache.org/jira/browse/HBASE-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455228#comment-13455228
 ] 

Ted Yu commented on HBASE-6775:
---

@Gregory:
Should the Fix Version be 0.94.3 ?

Thanks

 Use ZK.multi when available for HBASE-6710 0.92/0.94 compatibility fix
 --

 Key: HBASE-6775
 URL: https://issues.apache.org/jira/browse/HBASE-6775
 Project: HBase
  Issue Type: Improvement
  Components: zookeeper
Affects Versions: 0.92.2
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.92.3


 HBASE-6710 fixed a 0.92/0.94 compatibility issue by writing two znodes in 
 different formats.
 If a ZK failure occurs between the writing of the two znodes, strange 
 behavior can result.
 This issue is a reminder to change these two ZK writes to use ZK.multi when 
 we require ZK 3.4+. 

--
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

[jira] [Commented] (HBASE-6710) 0.92/0.94 compatibility issues due to HBASE-5206

[
https://issues.apache.org/jira/browse/HBASE-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455231#comment-13455231
]

Ted Yu commented on HBASE-6710:
---

Should this JIRA have a detailed Release Notes ?

0.92/0.94 compatibility issues due to HBASE-5206

Key: HBASE-6710
URL: https://issues.apache.org/jira/browse/HBASE-6710
Project: HBase
Issue Type: Bug
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Critical
Fix For: 0.94.2

Attachments: HBASE-6710-v3.patch

HBASE-5206 introduces some compatibility issues between {0.94,0.94.1} and
{0.92.0,0.92.1}. The release notes of HBASE-5155 describes the issue
(HBASE-5206 is a backport of HBASE-5155).
I think we can make 0.94.2 compatible with both {0.94.0,0.94.1} and
{0.92.0,0.92.1}, although one of those sets will require configuration
changes.
The basic problem is that there is a znode for each table
zookeeper.znode.tableEnableDisable that is handled differently.
On 0.92.0 and 0.92.1 the states for this table are:
[ disabled, disabling, enabling ] or deleted if the table is enabled
On 0.94.1 and 0.94.2 the states for this table are:
[ disabled, disabling, enabling, enabled ]
What saves us is that the location of this znode is configurable. So the
basic idea is to have the 0.94.2 master write two different znodes,
zookeeper.znode.tableEnableDisabled92 and
zookeeper.znode.tableEnableDisabled94 where the 92 node is in 92 format,
the 94 node is in 94 format. And internally, the master would only use the
94 format in order to solve the original bug HBASE-5155 solves.
We can of course make one of these the same default as exists now, so we
don't need to make config changes for one of 0.92 or 0.94 clients. I argue
that 0.92 clients shouldn't have to make config changes for the same reason I
argued above. But that is debatable.
Then, I think the only question left is the question of how to bring along
the {0.94.0, 0.94.1} crew. A {0.94.0, 0.94.1} client would work against a
0.94.2 cluster by just configuring zookeeper.znode.tableEnableDisable in
the client to be whatever zookeeper.znode.tableEnableDisabled94 is in the
cluster. A 0.94.2 client would work against both a {0.94.0, 0.94.1} and
{0.92.0, 0.92.1} cluster if it had HBASE-6268 applied. About rolling upgrade
from {0.94.0, 0.94.1} to 0.94.2 -- I'd have to think about that. Do the
regionservers ever read the tableEnableDisabled znode?
On the mailing list, Lars H suggested the following:
The only input I'd have is that format we'll use going forward will not have
a version attached to it.
So maybe the 92 version would still be called
zookeeper.znode.tableEnableDisable and the new node could have a different
name zookeeper.znode.tableEnableDisableNew (or something).

--
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

[jira] [Updated] (HBASE-6775) Use ZK.multi when available for HBASE-6710 0.92/0.94 compatibility fix


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

Gregory Chanan updated HBASE-6775:
--

Affects Version/s: (was: 0.92.2)
   0.94.2
Fix Version/s: (was: 0.92.3)
   0.94.3

@Ted:

Yes, fixed.

 Use ZK.multi when available for HBASE-6710 0.92/0.94 compatibility fix
 --

 Key: HBASE-6775
 URL: https://issues.apache.org/jira/browse/HBASE-6775
 Project: HBase
  Issue Type: Improvement
  Components: zookeeper
Affects Versions: 0.94.2
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.94.3


 HBASE-6710 fixed a 0.92/0.94 compatibility issue by writing two znodes in 
 different formats.
 If a ZK failure occurs between the writing of the two znodes, strange 
 behavior can result.
 This issue is a reminder to change these two ZK writes to use ZK.multi when 
 we require ZK 3.4+. 

--
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

[jira] [Commented] (HBASE-6710) 0.92/0.94 compatibility issues due to HBASE-5206

2012-09-13 Thread Jonathan Hsieh (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455237#comment-13455237
]

Jonathan Hsieh commented on HBASE-6710:
---

+1 for ted's suggestion.

0.92/0.94 compatibility issues due to HBASE-5206

Key: HBASE-6710
URL: https://issues.apache.org/jira/browse/HBASE-6710
Project: HBase
Issue Type: Bug
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Critical
Fix For: 0.94.2

Attachments: HBASE-6710-v3.patch

[jira] [Commented] (HBASE-6710) 0.92/0.94 compatibility issues due to HBASE-5206

[
https://issues.apache.org/jira/browse/HBASE-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455245#comment-13455245
]

Gregory Chanan commented on HBASE-6710:
---

Yes, I'll work on a Release Note.

0.92/0.94 compatibility issues due to HBASE-5206

Key: HBASE-6710
URL: https://issues.apache.org/jira/browse/HBASE-6710
Project: HBase
Issue Type: Bug
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Critical
Fix For: 0.94.2

Attachments: HBASE-6710-v3.patch

[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase from starting in non-distributed mode


[ 
https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455250#comment-13455250
 ] 

Hadoop QA commented on HBASE-6504:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12545030/HBASE-6504.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+1 hadoop2.0.  The patch compiles against the hadoop 2.0 profile.

+1 javadoc.  The javadoc tool did not generate any warning messages.

-1 javac.  The patch appears to cause mvn compile goal to fail.

-1 findbugs.  The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

 -1 core tests.  The patch failed these unit tests:
   org.apache.hadoop.hbase.client.TestFromClientSide
  
org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2858//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/2858//console

This message is automatically generated.

 Adding GC details prevents HBase from starting in non-distributed mode
 --

 Key: HBASE-6504
 URL: https://issues.apache.org/jira/browse/HBASE-6504
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Benoit Sigoure
Assignee: Michael Drzal
Priority: Trivial
  Labels: noob
 Attachments: HBASE-6504-output.txt, HBASE-6504.patch


 The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out 
 examples of variables that could be useful, such as adding 
 {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}.  This has 
 the annoying side effect that the JVM prints a summary of memory usage when 
 it exits, and it does so on stdout:
 {code}
 $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool 
 hbase.cluster.distributed
 false
 Heap
  par new generation   total 19136K, used 4908K [0x00073a20, 
 0x00073b6c, 0x00075186)
   eden space 17024K,  28% used [0x00073a20, 0x00073a6cb0a8, 
 0x00073b2a)
   from space 2112K,   0% used [0x00073b2a, 0x00073b2a, 
 0x00073b4b)
   to   space 2112K,   0% used [0x00073b4b, 0x00073b4b, 
 0x00073b6c)
  concurrent mark-sweep generation total 63872K, used 0K [0x00075186, 
 0x0007556c, 0x0007f5a0)
  concurrent-mark-sweep perm gen total 21248K, used 6994K [0x0007f5a0, 
 0x0007f6ec, 0x0008)
 $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool 
 hbase.cluster.distributed /dev/null
 (nothing printed)
 {code}
 And this confuses {{bin/start-hbase.sh}} when it does
 {{distMode=`$bin/hbase --config $HBASE_CONF_DIR 
 org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, 
 because then the {{distMode}} variable is not just set to {{false}}, it also 
 contains all this JVM spam.
 If you don't pay enough attention and realize that 3 processes are getting 
 started (ZK, HM, RS) instead of just one (HM), then you end up with this 
 confusing error message:
 {{Could not start ZK at requested port of 2181.  ZK was started at port: 
 2182.  Aborting as clients (e.g. shell) will not be able to find this ZK 
 quorum.}}, which is even more puzzling because when you run {{netstat}} to 
 see who owns that port, then you won't find any rogue process other than the 
 one you just started.
 I'm wondering if the fix is not to just change the {{if [ $distMode == 
 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work 
 around this annoying JVM misfeature that pollutes stdout.

--
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

[jira] [Updated] (HBASE-6260) balancer state should be stored in ZK


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

Gregory Chanan updated HBASE-6260:
--

Attachment: HBASE-6260-v2.patch

* Attached HBASE-6260-v2.patch *

Add PB_MAGIC prefix.

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260.patch, HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Commented] (HBASE-5452) Fixes for HBase shell with protobuf-based data

2012-09-13 Thread Chris Trezzo (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455293#comment-13455293
 ] 

Chris Trezzo commented on HBASE-5452:
-

I can go through and verify some of it. I would hope that our unit tests would 
cover most of it. :-) The shell seems to go through all of the normal client 
interfaces (i.e. HBaseAdmin, ReplicationAdmin, HTable, HRegionInfo, etc. etc.). 
Are there any specific parts that you are especially worried about? Otherwise, 
I am not sure what else to do.

 Fixes for HBase shell with protobuf-based data
 --

 Key: HBASE-5452
 URL: https://issues.apache.org/jira/browse/HBASE-5452
 Project: HBase
  Issue Type: Sub-task
  Components: ipc, master, migration, regionserver
Reporter: Todd Lipcon
Assignee: Chris Trezzo



--
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

[jira] [Commented] (HBASE-5452) Fixes for HBase shell with protobuf-based data


[ 
https://issues.apache.org/jira/browse/HBASE-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455317#comment-13455317
 ] 

Gregory Chanan commented on HBASE-5452:
---

Yes, the shell goes through the normal client interfaces, so I'm not expecting 
a problem.  Our unit tests look pretty sparse in this area, though.

Let me know what you want to do.  I can verify certain commands too if you want.

 Fixes for HBase shell with protobuf-based data
 --

 Key: HBASE-5452
 URL: https://issues.apache.org/jira/browse/HBASE-5452
 Project: HBase
  Issue Type: Sub-task
  Components: ipc, master, migration, regionserver
Reporter: Todd Lipcon
Assignee: Chris Trezzo



--
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

[jira] [Created] (HBASE-6776) Opened region of disabled/enabling table is not added to online region list

Jimmy Xiang created HBASE-6776:
--

 Summary: Opened region of disabled/enabling table is not added to 
online region list
 Key: HBASE-6776
 URL: https://issues.apache.org/jira/browse/HBASE-6776
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang


For opened region of disabled table, it should be added to online region list, 
and then closed.  We should not just ignore them.

For opened region of enabling table, it should be added to online region list, 
so that we don't have to assign it again.  Without adding it to online region 
list, it could be double assigned when assign it again later.


--
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

[jira] [Commented] (HBASE-5452) Fixes for HBase shell with protobuf-based data

2012-09-13 Thread Chris Trezzo (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455337#comment-13455337
 ] 

Chris Trezzo commented on HBASE-5452:
-

Fair enough. I'll take a look now.

 Fixes for HBase shell with protobuf-based data
 --

 Key: HBASE-5452
 URL: https://issues.apache.org/jira/browse/HBASE-5452
 Project: HBase
  Issue Type: Sub-task
  Components: ipc, master, migration, regionserver
Reporter: Todd Lipcon
Assignee: Chris Trezzo



--
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

[jira] [Assigned] (HBASE-6776) Opened region of disabled/enabling table is not added to online region list


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

Jimmy Xiang reassigned HBASE-6776:
--

Assignee: Jimmy Xiang

 Opened region of disabled/enabling table is not added to online region list
 ---

 Key: HBASE-6776
 URL: https://issues.apache.org/jira/browse/HBASE-6776
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang

 For opened region of disabled table, it should be added to online region 
 list, and then closed.  We should not just ignore them.
 For opened region of enabling table, it should be added to online region 
 list, so that we don't have to assign it again.  Without adding it to online 
 region list, it could be double assigned when assign it again later.

--
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

[jira] [Commented] (HBASE-6409) Create histogram class for metrics 2

2012-09-13 Thread Andrew Wang (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455341#comment-13455341
 ] 

Andrew Wang commented on HBASE-6409:


Hi Elliot, sorry about the delay on getting back to you.

I don't think there's an issue with sharing an executor. IIRC, findbugs 
complained since it didn't correctly pick up on synchronizing on the parent 
MutableQuantiles, but it's fine.

The datanode and namenode still seem to shutdown correctly even though the 
threads aren't daemonized. Making them daemonized probably won't hurt though, 
so also LGTM.

 Create histogram class for metrics 2
 

 Key: HBASE-6409
 URL: https://issues.apache.org/jira/browse/HBASE-6409
 Project: HBase
  Issue Type: Sub-task
  Components: metrics
Affects Versions: 0.96.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Priority: Blocker
 Attachments: HBASE-6409-0.patch, HBASE-6409-1.patch, 
 HBASE-6409-2.patch, HBASE-6409-3.patch, HBASE-6409-4.patch


 Create the replacement for MetricsHistogram and PersistantTimeVaryingRate 
 classes.

--
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

[jira] [Commented] (HBASE-6409) Create histogram class for metrics 2


[ 
https://issues.apache.org/jira/browse/HBASE-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455348#comment-13455348
 ] 

Elliott Clark commented on HBASE-6409:
--

Awesome.  Thanks.

 Create histogram class for metrics 2
 

 Key: HBASE-6409
 URL: https://issues.apache.org/jira/browse/HBASE-6409
 Project: HBase
  Issue Type: Sub-task
  Components: metrics
Affects Versions: 0.96.0
Reporter: Elliott Clark
Assignee: Elliott Clark
Priority: Blocker
 Attachments: HBASE-6409-0.patch, HBASE-6409-1.patch, 
 HBASE-6409-2.patch, HBASE-6409-3.patch, HBASE-6409-4.patch


 Create the replacement for MetricsHistogram and PersistantTimeVaryingRate 
 classes.

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK

[
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455350#comment-13455350
]

Hadoop QA commented on HBASE-6260:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545054/HBASE-6260-v2.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

+1 javadoc. The javadoc tool did not generate any warning messages.

-1 javac. The patch appears to cause mvn compile goal to fail.

-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:

org.apache.hadoop.hbase.io.hfile.TestForceCacheImportantBlocks
org.apache.hadoop.hbase.replication.TestReplication

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2859//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2859//console

This message is automatically generated.

balancer state should be stored in ZK
-

Key: HBASE-6260
URL: https://issues.apache.org/jira/browse/HBASE-6260
Project: HBase
Issue Type: Task
Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
Attachments: HBASE-6260.patch, HBASE-6260-v2.patch

See:
https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
And:
https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
In short, we need to move the balancer state to ZK so that it won't have to
be restarted if the master dies.

[jira] [Created] (HBASE-6777) Snapshot Restore interface

2012-09-13 Thread Matteo Bertozzi (JIRA)

Matteo Bertozzi created HBASE-6777:
--

 Summary: Snapshot Restore interface
 Key: HBASE-6777
 URL: https://issues.apache.org/jira/browse/HBASE-6777
 Project: HBase
  Issue Type: New Feature
  Components: client, master, snapshots
Affects Versions: 0.96.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 0.96.0


Add interfaces for restoring a snapshot

--
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

[jira] [Updated] (HBASE-6777) Snapshot Restore interface

2012-09-13 Thread Matteo Bertozzi (JIRA)


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

Matteo Bertozzi updated HBASE-6777:
---

Issue Type: Sub-task  (was: New Feature)
Parent: HBASE-6055

 Snapshot Restore interface
 --

 Key: HBASE-6777
 URL: https://issues.apache.org/jira/browse/HBASE-6777
 Project: HBase
  Issue Type: Sub-task
  Components: client, master, snapshots
Affects Versions: 0.96.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 0.96.0


 Add interfaces for restoring a snapshot

--
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

[jira] [Updated] (HBASE-3801) Backup Master blocked when the HMaster Node Fail.


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

Lars Hofhansl updated HBASE-3801:
-

Resolution: Not A Problem
Status: Resolved  (was: Patch Available)

I think the consensus here is that this works correctly (and nobody else 
reported the problem in a year)... Resolving. Reopen if you disagree.

 Backup Master blocked when the HMaster Node Fail.
 -

 Key: HBASE-3801
 URL: https://issues.apache.org/jira/browse/HBASE-3801
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 0.90.2, 0.90.3
 Environment: 1 HMaster
 1 HMaster -backup
 6 HResignServer
Reporter: Aaron Guo
 Attachments: patch.txt


 When the HMaster crash, the Backup HMaster blocked for waiting the ZK notify.
 The Backup HMaster's thread stack is :
 master-hp1:6 prio=10 tid=0x484c6800 nid=0x4b56 waiting on 
 condition [0x40209000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
 at java.lang.Thread.sleep(Native Method)
 at 
 org.apache.hadoop.hbase.master.HMaster.stallIfBackupMaster(HMaster.java:251)
 at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:279)
Locked ownable synchronizers:
 - None

--
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

[jira] [Updated] (HBASE-6776) Opened region of disabled/enabling table is not added to online region list


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

Jimmy Xiang updated HBASE-6776:
---

Attachment: trunk-6776.patch

 Opened region of disabled/enabling table is not added to online region list
 ---

 Key: HBASE-6776
 URL: https://issues.apache.org/jira/browse/HBASE-6776
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Attachments: trunk-6776.patch


 For opened region of disabled table, it should be added to online region 
 list, and then closed.  We should not just ignore them.
 For opened region of enabling table, it should be added to online region 
 list, so that we don't have to assign it again.  Without adding it to online 
 region list, it could be double assigned when assign it again later.

--
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

[jira] [Updated] (HBASE-6776) Opened region of disabled/enabling table is not added to online region list


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

Jimmy Xiang updated HBASE-6776:
---

Status: Patch Available  (was: Open)

TestMaster* and TestAssign* are green.

For disabled tables, if there are regions still open, changed it to disabling 
state so that disable handler can disable it again.

 Opened region of disabled/enabling table is not added to online region list
 ---

 Key: HBASE-6776
 URL: https://issues.apache.org/jira/browse/HBASE-6776
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Attachments: trunk-6776.patch


 For opened region of disabled table, it should be added to online region 
 list, and then closed.  We should not just ignore them.
 For opened region of enabling table, it should be added to online region 
 list, so that we don't have to assign it again.  Without adding it to online 
 region list, it could be double assigned when assign it again later.

--
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

[jira] [Commented] (HBASE-3799) Provide more accurate check for super underloaded region server in load balancer


[ 
https://issues.apache.org/jira/browse/HBASE-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455353#comment-13455353
 ] 

Lars Hofhansl commented on HBASE-3799:
--

@Ted: Do you still want this?

 Provide more accurate check for super underloaded region server in load 
 balancer
 

 Key: HBASE-3799
 URL: https://issues.apache.org/jira/browse/HBASE-3799
 Project: HBase
  Issue Type: Bug
  Components: mapreduce
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3799.patch


 HBASE-3609 used simple check for region server which recently joined the 
 cluster so that both young and old regions from other region servers are 
 assigned to it.
 The check was too strict.
 1 or more region may be assigned to this server before load balancer performs 
 rebalancing.
 The next time balancer runs, it wouldn't treat this server as seriously 
 underloaded correctly and assign a lot of young regions to it.
 We can use threshold over the number of regions to avoid such issue.

--
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

[jira] [Commented] (HBASE-3792) TableInputFormat leaks ZK connections

[
https://issues.apache.org/jira/browse/HBASE-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455358#comment-13455358
]

Lars Hofhansl commented on HBASE-3792:
--

What should we do with this?

TableInputFormat leaks ZK connections
-

Key: HBASE-3792
URL: https://issues.apache.org/jira/browse/HBASE-3792
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 0.90.1
Environment: Java 1.6.0_24, Mac OS X 10.6.7
Reporter: Bryan Keller
Attachments: patch0.90.4, tableinput.patch

The TableInputFormat creates an HTable using a new Configuration object, and
it never cleans it up. When running a Mapper, the TableInputFormat is
instantiated and the ZK connection is created. While this connection is not
explicitly cleaned up, the Mapper process eventually exits and thus the
connection is closed. Ideally the TableRecordReader would close the
connection in its close() method rather than relying on the process to die
for connection cleanup. This is fairly easy to implement by overriding
TableRecordReader, and also overriding TableInputFormat to specify the new
record reader.
The leak occurs when the JobClient is initializing and needs to retrieves the
splits. To get the splits, it instantiates a TableInputFormat. Doing so
creates a ZK connection that is never cleaned up. Unlike the mapper, however,
my job client process does not die. Thus the ZK connections accumulate.
I was able to fix the problem by writing my own TableInputFormat that does
not initialize the HTable in the getConf() method and does not have an HTable
member variable. Rather, it has a variable for the table name. The HTable is
instantiated where needed and then cleaned up. For example, in the
getSplits() method, I create the HTable, then close the connection once the
splits are retrieved. I also create the HTable when creating the record
reader, and I have a record reader that closes the connection when done.

[jira] [Commented] (HBASE-3791) Display total number of zookeeper connections on master.jsp


[ 
https://issues.apache.org/jira/browse/HBASE-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455359#comment-13455359
 ] 

Lars Hofhansl commented on HBASE-3791:
--

How about this one, Ted?

 Display total number of zookeeper connections on master.jsp
 ---

 Key: HBASE-3791
 URL: https://issues.apache.org/jira/browse/HBASE-3791
 Project: HBase
  Issue Type: Improvement
  Components: zookeeper
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3791.patch


 Quite often, user needs to telnet to Zookeeper and type 'stats' to get the 
 connections, or count the connections on zk.jsp
 We should display the total number of connections beside the link to zk.jsp 
 on master.jsp

--
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

[jira] [Commented] (HBASE-3799) Provide more accurate check for super underloaded region server in load balancer


[ 
https://issues.apache.org/jira/browse/HBASE-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455363#comment-13455363
 ] 

Ted Yu commented on HBASE-3799:
---

The notion of young vs. old regions can be more accurately described with 
various metrics for read / write on regions.
I will close this JIRA for now.

 Provide more accurate check for super underloaded region server in load 
 balancer
 

 Key: HBASE-3799
 URL: https://issues.apache.org/jira/browse/HBASE-3799
 Project: HBase
  Issue Type: Bug
  Components: mapreduce
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3799.patch


 HBASE-3609 used simple check for region server which recently joined the 
 cluster so that both young and old regions from other region servers are 
 assigned to it.
 The check was too strict.
 1 or more region may be assigned to this server before load balancer performs 
 rebalancing.
 The next time balancer runs, it wouldn't treat this server as seriously 
 underloaded correctly and assign a lot of young regions to it.
 We can use threshold over the number of regions to avoid such issue.

--
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

[jira] [Work started] (HBASE-3799) Provide more accurate check for super underloaded region server in load balancer


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

Work on HBASE-3799 started by Ted Yu.

 Provide more accurate check for super underloaded region server in load 
 balancer
 

 Key: HBASE-3799
 URL: https://issues.apache.org/jira/browse/HBASE-3799
 Project: HBase
  Issue Type: Bug
  Components: mapreduce
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3799.patch


 HBASE-3609 used simple check for region server which recently joined the 
 cluster so that both young and old regions from other region servers are 
 assigned to it.
 The check was too strict.
 1 or more region may be assigned to this server before load balancer performs 
 rebalancing.
 The next time balancer runs, it wouldn't treat this server as seriously 
 underloaded correctly and assign a lot of young regions to it.
 We can use threshold over the number of regions to avoid such issue.

--
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

[jira] [Resolved] (HBASE-3799) Provide more accurate check for super underloaded region server in load balancer


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

Ted Yu resolved HBASE-3799.
---

Resolution: Later

 Provide more accurate check for super underloaded region server in load 
 balancer
 

 Key: HBASE-3799
 URL: https://issues.apache.org/jira/browse/HBASE-3799
 Project: HBase
  Issue Type: Bug
  Components: mapreduce
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3799.patch


 HBASE-3609 used simple check for region server which recently joined the 
 cluster so that both young and old regions from other region servers are 
 assigned to it.
 The check was too strict.
 1 or more region may be assigned to this server before load balancer performs 
 rebalancing.
 The next time balancer runs, it wouldn't treat this server as seriously 
 underloaded correctly and assign a lot of young regions to it.
 We can use threshold over the number of regions to avoid such issue.

--
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

[jira] [Commented] (HBASE-3791) Display total number of zookeeper connections on master.jsp


[ 
https://issues.apache.org/jira/browse/HBASE-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455366#comment-13455366
 ] 

Ted Yu commented on HBASE-3791:
---

I think this one would be good to have.

 Display total number of zookeeper connections on master.jsp
 ---

 Key: HBASE-3791
 URL: https://issues.apache.org/jira/browse/HBASE-3791
 Project: HBase
  Issue Type: Improvement
  Components: zookeeper
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3791.patch


 Quite often, user needs to telnet to Zookeeper and type 'stats' to get the 
 connections, or count the connections on zk.jsp
 We should display the total number of connections beside the link to zk.jsp 
 on master.jsp

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK


[ 
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455367#comment-13455367
 ] 

Gregory Chanan commented on HBASE-6260:
---

I ran TestForceCacheImportantBlocks locally and it passed.  TestReplication has 
been failing for a long time.

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260.patch, HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Updated] (HBASE-6759) Forward port ZKReadOnly change from HBASE-6710


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

Gregory Chanan updated HBASE-6759:
--

Attachment: HBASE-6759.patch

* Attached HBASE-6759.patch *

 Forward port ZKReadOnly change from HBASE-6710
 --

 Key: HBASE-6759
 URL: https://issues.apache.org/jira/browse/HBASE-6759
 Project: HBase
  Issue Type: Task
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.96.0

 Attachments: HBASE-6759.patch


 In HBASE-6710 (0.94 only), ZKTable was split into ZKTable and 
 ZKTableReadOnly.  We should do that in trunk as well to make the code clearer 
 and closer to 0.94.

--
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

[jira] [Updated] (HBASE-6759) Forward port ZKReadOnly change from HBASE-6710


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

Gregory Chanan updated HBASE-6759:
--

Status: Patch Available  (was: Open)

 Forward port ZKReadOnly change from HBASE-6710
 --

 Key: HBASE-6759
 URL: https://issues.apache.org/jira/browse/HBASE-6759
 Project: HBase
  Issue Type: Task
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.96.0

 Attachments: HBASE-6759.patch


 In HBASE-6710 (0.94 only), ZKTable was split into ZKTable and 
 ZKTableReadOnly.  We should do that in trunk as well to make the code clearer 
 and closer to 0.94.

--
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

[jira] [Commented] (HBASE-3787) Increment is non-idempotent but client retries RPC


[ 
https://issues.apache.org/jira/browse/HBASE-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455384#comment-13455384
 ] 

Lars Hofhansl commented on HBASE-3787:
--

This is an interesting one.
To me the main goal of retries is to ride over a split or region move. If we 
can isolate that condition and avoid retrying for all undecided conditions 
(the various timeouts) we should be OK.


 Increment is non-idempotent but client retries RPC
 --

 Key: HBASE-3787
 URL: https://issues.apache.org/jira/browse/HBASE-3787
 Project: HBase
  Issue Type: Bug
  Components: client
Reporter: dhruba borthakur
Assignee: dhruba borthakur

 The HTable.increment() operation is non-idempotent. The client retries the 
 increment RPC a few times (as specified by configuration) before throwing an 
 error to the application. This makes it possible that the same increment call 
 be applied twice at the server.
 For increment operations, is it better to use 
 HConnectionManager.getRegionServerWithoutRetries()? Another  option would be 
 to enhance the IPC module to make the RPC server correctly identify if the 
 RPC is a retry attempt and handle accordingly.

--
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

[jira] [Commented] (HBASE-3786) Enhance MasterCoprocessorHost to include notification of balancing of each region


[ 
https://issues.apache.org/jira/browse/HBASE-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455389#comment-13455389
 ] 

Lars Hofhansl commented on HBASE-3786:
--

I'm a bit fuzzy as to what the current state is. In MasterObserver I find 
{pre|post}Balance, but those are not per region, so I guess they do not provide 
what is being asked here...?

 Enhance MasterCoprocessorHost to include notification of balancing of each 
 region
 -

 Key: HBASE-3786
 URL: https://issues.apache.org/jira/browse/HBASE-3786
 Project: HBase
  Issue Type: Improvement
  Components: coprocessors
Affects Versions: 0.90.2
Reporter: Ted Yu



--
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

[jira] [Commented] (HBASE-6759) Forward port ZKReadOnly change from HBASE-6710


[ 
https://issues.apache.org/jira/browse/HBASE-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455391#comment-13455391
 ] 

stack commented on HBASE-6759:
--

+1

 Forward port ZKReadOnly change from HBASE-6710
 --

 Key: HBASE-6759
 URL: https://issues.apache.org/jira/browse/HBASE-6759
 Project: HBase
  Issue Type: Task
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.96.0

 Attachments: HBASE-6759.patch


 In HBASE-6710 (0.94 only), ZKTable was split into ZKTable and 
 ZKTableReadOnly.  We should do that in trunk as well to make the code clearer 
 and closer to 0.94.

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK


[ 
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455394#comment-13455394
 ] 

stack commented on HBASE-6260:
--

+1

Checked PB_MAGIC is included serializing and managed deserializing.  Looks good.

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260.patch, HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Updated] (HBASE-6055) Snapshots in HBase 0.96

2012-09-13 Thread Jonathan Hsieh (JIRA)


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

Jonathan Hsieh updated HBASE-6055:
--

Component/s: snapshots

 Snapshots in HBase 0.96
 ---

 Key: HBASE-6055
 URL: https://issues.apache.org/jira/browse/HBASE-6055
 Project: HBase
  Issue Type: New Feature
  Components: client, master, regionserver, snapshots, zookeeper
Reporter: Jesse Yates
Assignee: Jesse Yates
 Fix For: 0.96.0

 Attachments: Snapshots in HBase.docx


 Continuation of HBASE-50 for the current trunk. Since the implementation has 
 drastically changed, opening as a new ticket.

--
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

[jira] [Commented] (HBASE-6777) Snapshot Restore interface

2012-09-13 Thread Matteo Bertozzi (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455403#comment-13455403
 ] 

Matteo Bertozzi commented on HBASE-6777:


code on review board https://reviews.apache.org/r/7096

 Snapshot Restore interface
 --

 Key: HBASE-6777
 URL: https://issues.apache.org/jira/browse/HBASE-6777
 Project: HBase
  Issue Type: Sub-task
  Components: client, master, snapshots
Affects Versions: 0.96.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 0.96.0


 Add interfaces for restoring a snapshot

--
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

[jira] [Updated] (HBASE-6241) HBaseCluster interface for interacting with the cluster from system tests


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

Enis Soztutar updated HBASE-6241:
-

Status: Open  (was: Patch Available)

 HBaseCluster interface for interacting with the cluster from system tests 
 --

 Key: HBASE-6241
 URL: https://issues.apache.org/jira/browse/HBASE-6241
 Project: HBase
  Issue Type: Sub-task
Reporter: Enis Soztutar
Assignee: Enis Soztutar
 Attachments: HBASE-6241_v0.2.patch, HBASE-6241_v1.patch, 
 HBASE-6241_v4.patch


 We need to abstract away the cluster interactions for system tests running on 
 actual clusters. 
 MiniHBaseCluster and RealHBaseCluster should both implement this interface, 
 and system tests should work with both.
 I'll split Devaraj's patch in HBASE-6053 for the initial version. 

--
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

[jira] [Updated] (HBASE-6241) HBaseCluster interface for interacting with the cluster from system tests


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

Enis Soztutar updated HBASE-6241:
-

Attachment: HBASE-6241_v4.patch

Attaching patch from RB. 

 HBaseCluster interface for interacting with the cluster from system tests 
 --

 Key: HBASE-6241
 URL: https://issues.apache.org/jira/browse/HBASE-6241
 Project: HBase
  Issue Type: Sub-task
Reporter: Enis Soztutar
Assignee: Enis Soztutar
 Attachments: HBASE-6241_v0.2.patch, HBASE-6241_v1.patch, 
 HBASE-6241_v4.patch


 We need to abstract away the cluster interactions for system tests running on 
 actual clusters. 
 MiniHBaseCluster and RealHBaseCluster should both implement this interface, 
 and system tests should work with both.
 I'll split Devaraj's patch in HBASE-6053 for the initial version. 

--
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

[jira] [Updated] (HBASE-6241) HBaseCluster interface for interacting with the cluster from system tests


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

Enis Soztutar updated HBASE-6241:
-

Status: Patch Available  (was: Open)

 HBaseCluster interface for interacting with the cluster from system tests 
 --

 Key: HBASE-6241
 URL: https://issues.apache.org/jira/browse/HBASE-6241
 Project: HBase
  Issue Type: Sub-task
Reporter: Enis Soztutar
Assignee: Enis Soztutar
 Attachments: HBASE-6241_v0.2.patch, HBASE-6241_v1.patch, 
 HBASE-6241_v4.patch


 We need to abstract away the cluster interactions for system tests running on 
 actual clusters. 
 MiniHBaseCluster and RealHBaseCluster should both implement this interface, 
 and system tests should work with both.
 I'll split Devaraj's patch in HBASE-6053 for the initial version. 

--
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

[jira] [Updated] (HBASE-6260) balancer state should be stored in ZK


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

Gregory Chanan updated HBASE-6260:
--

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Thanks for the review, stack.  Committed to trunk.

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260.patch, HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK


[ 
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455414#comment-13455414
 ] 

Ted Yu commented on HBASE-6260:
---

{code}
+ * Tracks the load balancer switch up in ZK
{code}
Probably you should make the above comment more general - LoadBalancerTracker 
may cover more than switch status.
{code}
+  // is data in ZK is null, use default of on.
{code}
Typo: 'is' - 'if'

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260.patch, HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Updated] (HBASE-6260) balancer state should be stored in ZK


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

Gregory Chanan updated HBASE-6260:
--

Attachment: HBASE-6260-addendum.patch

@Ted:

attached an addendum.  Let me know what you think.

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260-addendum.patch, HBASE-6260.patch, 
 HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Commented] (HBASE-6759) Forward port ZKReadOnly change from HBASE-6710

[
https://issues.apache.org/jira/browse/HBASE-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455429#comment-13455429
]

Hadoop QA commented on HBASE-6759:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545069/HBASE-6759.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 3 new or modified tests.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

+1 javadoc. The javadoc tool did not generate any warning messages.

-1 javac. The patch appears to cause mvn compile goal to fail.

-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.TestFullLogReconstruction
org.apache.hadoop.hbase.client.TestFromClientSide
org.apache.hadoop.hbase.io.hfile.TestForceCacheImportantBlocks

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2860//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2860//console

This message is automatically generated.

Forward port ZKReadOnly change from HBASE-6710
--

Key: HBASE-6759
URL: https://issues.apache.org/jira/browse/HBASE-6759
Project: HBase
Issue Type: Task
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
Fix For: 0.96.0

Attachments: HBASE-6759.patch

In HBASE-6710 (0.94 only), ZKTable was split into ZKTable and
ZKTableReadOnly. We should do that in trunk as well to make the code clearer
and closer to 0.94.

[jira] [Created] (HBASE-6778) Deprecate Chore; its a thread per task when we should have one thread to do all tasks

stack created HBASE-6778:


 Summary: Deprecate Chore; its a thread per task when we should 
have one thread to do all tasks
 Key: HBASE-6778
 URL: https://issues.apache.org/jira/browse/HBASE-6778
 Project: HBase
  Issue Type: Bug
Reporter: stack


Should use something like ScheduledThreadPoolExecutor instead (Elliott said 
this first I think; J-D said something similar just now).

--
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

[jira] [Commented] (HBASE-6778) Deprecate Chore; its a thread per task when we should have one thread to do all tasks


[ 
https://issues.apache.org/jira/browse/HBASE-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455432#comment-13455432
 ] 

Elliott Clark commented on HBASE-6778:
--

Last time I counted we have ~150 threads on a totally un-loaded region server. 
The number of context switches that represents is a pretty serious perf impact.

 Deprecate Chore; its a thread per task when we should have one thread to do 
 all tasks
 -

 Key: HBASE-6778
 URL: https://issues.apache.org/jira/browse/HBASE-6778
 Project: HBase
  Issue Type: Bug
Reporter: stack

 Should use something like ScheduledThreadPoolExecutor instead (Elliott said 
 this first I think; J-D said something similar just now).

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK


[ 
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455435#comment-13455435
 ] 

stack commented on HBASE-6260:
--

Just commit G.

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260-addendum.patch, HBASE-6260.patch, 
 HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Commented] (HBASE-3782) Multi-Family support for bulk upload tools causes File Not Found Exception


[ 
https://issues.apache.org/jira/browse/HBASE-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455436#comment-13455436
 ] 

Lars Hofhansl commented on HBASE-3782:
--

This is no longer an issue it seems. HFileOutputFormat is now 
HFile.Writer.appendFileInfo.
Still... Hard to verify.

 Multi-Family support for bulk upload tools causes File Not Found Exception
 --

 Key: HBASE-3782
 URL: https://issues.apache.org/jira/browse/HBASE-3782
 Project: HBase
  Issue Type: Bug
  Components: mapreduce
Affects Versions: 0.90.3
Reporter: Nichole Treadway
 Attachments: HBASE-3782.patch


 I've been testing HBASE-1861 in 0.90.2, which adds multi-family support for 
 bulk upload tools.
 I found that when running the importtsv program, some reduce tasks fail with 
 a File Not Found exception if there are no keys in the input data which fall 
 into the region assigned to that reduce task.  From what I can determine, it 
 seems that an output directory is created in the write() method and expected 
 to exist in the writeMetaData() method...if there are no keys to be written 
 for that reduce task, the write method is never called and the output 
 directory is never created, but writeMetaData is expecting the output 
 directory to exist...thus the FnF exception:
 2011-03-17 11:52:48,095 WARN org.apache.hadoop.mapred.TaskTracker: Error 
 running child
 java.io.FileNotFoundException: File does not exist: 
 hdfs://master:9000/awardsData/_temporary/_attempt_201103151859_0066_r_00_0
   at 
 org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:468)
   at 
 org.apache.hadoop.hbase.regionserver.StoreFile.getUniqueFile(StoreFile.java:580)
   at 
 org.apache.hadoop.hbase.mapreduce.HFileOutputFormat$1.writeMetaData(HFileOutputFormat.java:186)
   at 
 org.apache.hadoop.hbase.mapreduce.HFileOutputFormat$1.close(HFileOutputFormat.java:247)
   at 
 org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:567)
   at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:408)
   at org.apache.hadoop.mapred.Child.main(Child.java:170)
 Simply checking if the file exists should fix the issue. 

--
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

[jira] [Commented] (HBASE-6778) Deprecate Chore; its a thread per task when we should have one thread to do all tasks


[ 
https://issues.apache.org/jira/browse/HBASE-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455437#comment-13455437
 ] 

Enis Soztutar commented on HBASE-6778:
--

I was thinking along the same lines when I first encountered Chore. +1 

 Deprecate Chore; its a thread per task when we should have one thread to do 
 all tasks
 -

 Key: HBASE-6778
 URL: https://issues.apache.org/jira/browse/HBASE-6778
 Project: HBase
  Issue Type: Bug
Reporter: stack

 Should use something like ScheduledThreadPoolExecutor instead (Elliott said 
 this first I think; J-D said something similar just now).

--
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

[jira] [Commented] (HBASE-6710) 0.92/0.94 compatibility issues due to HBASE-5206

[
https://issues.apache.org/jira/browse/HBASE-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455439#comment-13455439
]

Gregory Chanan commented on HBASE-6710:
---

Here's a first cut. Let me know what you think.

This issue introduces a compatibility mode on the HMaster for 0.92.0 and 0.92.1
clients that requires a configuration change on those client to turn on.
Without the compatibility mode, 0.92.0 and 0.92.1 clients will hang on calls to
enableTable and is_enabled will always return false, even for enabled
tables. To use the compatibility mode, 0.92.0 and 0.92.1 clients should make
the following configuration change:
namezookeeper.znode.tableEnableDisable/name
valuetable92/value

In rare failure cases, even with the compatibility mode on, the client may
report inaccurate results for is_enabled and is_disabled. This issue can
be corrected by calling enable or disable again to return the table to the
desired state.

0.92/0.94 compatibility issues due to HBASE-5206

Key: HBASE-6710
URL: https://issues.apache.org/jira/browse/HBASE-6710
Project: HBase
Issue Type: Bug
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Critical
Fix For: 0.94.2

Attachments: HBASE-6710-v3.patch

[jira] [Commented] (HBASE-6776) Opened region of disabled/enabling table is not added to online region list

[
https://issues.apache.org/jira/browse/HBASE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455451#comment-13455451
]

stack commented on HBASE-6776:
--

bq. For opened region of disabled table, it should be added to online region
list, and then closed. We should not just ignore them.

So, I see you add all to online regions in your patch. If we do this inside in
the rebuild of user regions, where do we do the close you suggest above?

I see you do this: getZKTable().setDisablingTable(tableName);

What is going on here? The table was Disabled but you are setting the set back
to Disabling because you came across a region that is still open?

bq. For opened region of enabling table, it should be added to online region
list, so that we don't have to assign it again. Without adding it to online
region list, it could be double assigned when assign it again later.

This seems right.

Opened region of disabled/enabling table is not added to online region list
---

Key: HBASE-6776
URL: https://issues.apache.org/jira/browse/HBASE-6776
Project: HBase
Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Attachments: trunk-6776.patch

For opened region of disabled table, it should be added to online region
list, and then closed. We should not just ignore them.
For opened region of enabling table, it should be added to online region
list, so that we don't have to assign it again. Without adding it to online
region list, it could be double assigned when assign it again later.

[jira] [Created] (HBASE-6779) Fix issues analysis.apache.org raises about StochasticLoadBalancer

Elliott Clark created HBASE-6779:


 Summary: Fix issues analysis.apache.org raises about 
StochasticLoadBalancer
 Key: HBASE-6779
 URL: https://issues.apache.org/jira/browse/HBASE-6779
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark




--
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

[jira] [Updated] (HBASE-6779) Fix issues analysis.apache.org raises about StochasticLoadBalancer


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

Elliott Clark updated HBASE-6779:
-

Attachment: HBASE-6779-0.patch

Removes an if statement that has always been skipped and uses entrySet rather 
than keySet + a get.

 Fix issues analysis.apache.org raises about StochasticLoadBalancer
 --

 Key: HBASE-6779
 URL: https://issues.apache.org/jira/browse/HBASE-6779
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
 Attachments: HBASE-6779-0.patch




--
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

[jira] [Updated] (HBASE-6779) Fix issues analysis.apache.org raises about StochasticLoadBalancer


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

Elliott Clark updated HBASE-6779:
-

Assignee: Elliott Clark
  Status: Patch Available  (was: Open)

 Fix issues analysis.apache.org raises about StochasticLoadBalancer
 --

 Key: HBASE-6779
 URL: https://issues.apache.org/jira/browse/HBASE-6779
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
Assignee: Elliott Clark
 Attachments: HBASE-6779-0.patch




--
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

[jira] [Commented] (HBASE-6241) HBaseCluster interface for interacting with the cluster from system tests


[ 
https://issues.apache.org/jira/browse/HBASE-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455460#comment-13455460
 ] 

stack commented on HBASE-6241:
--

I was trying to run tests locally but seems to fail w/ this Enis:

{code}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) on project hbase-server: Compilation failure
[ERROR] 
/Users/Stack/checkouts/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java:[1053,50]
 unreported exception java.io.IOException; must be caught or declared to be 
thrown
{code}

Do you have same issue?

 HBaseCluster interface for interacting with the cluster from system tests 
 --

 Key: HBASE-6241
 URL: https://issues.apache.org/jira/browse/HBASE-6241
 Project: HBase
  Issue Type: Sub-task
Reporter: Enis Soztutar
Assignee: Enis Soztutar
 Attachments: HBASE-6241_v0.2.patch, HBASE-6241_v1.patch, 
 HBASE-6241_v4.patch


 We need to abstract away the cluster interactions for system tests running on 
 actual clusters. 
 MiniHBaseCluster and RealHBaseCluster should both implement this interface, 
 and system tests should work with both.
 I'll split Devaraj's patch in HBASE-6053 for the initial version. 

--
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

[jira] [Commented] (HBASE-6776) Opened region of disabled/enabling table is not added to online region list

[
https://issues.apache.org/jira/browse/HBASE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455464#comment-13455464
]

Hadoop QA commented on HBASE-6776:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545063/trunk-6776.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

+1 javadoc. The javadoc tool did not generate any warning messages.

-1 javac. The patch appears to cause mvn compile goal to fail.

-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2861//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2861//console

This message is automatically generated.

Opened region of disabled/enabling table is not added to online region list
---

Key: HBASE-6776
URL: https://issues.apache.org/jira/browse/HBASE-6776
Project: HBase
Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Attachments: trunk-6776.patch

[jira] [Commented] (HBASE-3779) Allow split regions to be placed on different region servers


[ 
https://issues.apache.org/jira/browse/HBASE-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455463#comment-13455463
 ] 

Lars Hofhansl commented on HBASE-3779:
--

@Ted: Do you want to keep this open?

 Allow split regions to be placed on different region servers
 

 Key: HBASE-3779
 URL: https://issues.apache.org/jira/browse/HBASE-3779
 Project: HBase
  Issue Type: Improvement
  Components: master
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3779-v2.patch


 Currently daughter regions are placed on the same region server where the 
 parent region was.
 Stanislav Barton mentioned the idea that load information should be 
 considered when placing the daughter regions.
 The rationale is that the daughter regions tend to receive more writes. So it 
 would be beneficial to place at least one daughter region on a different 
 region server.

--
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

[jira] [Commented] (HBASE-6759) Forward port ZKReadOnly change from HBASE-6710


[ 
https://issues.apache.org/jira/browse/HBASE-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455466#comment-13455466
 ] 

Gregory Chanan commented on HBASE-6759:
---

Ran failed unit tests locally, they all passed.

 Forward port ZKReadOnly change from HBASE-6710
 --

 Key: HBASE-6759
 URL: https://issues.apache.org/jira/browse/HBASE-6759
 Project: HBase
  Issue Type: Task
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Minor
 Fix For: 0.96.0

 Attachments: HBASE-6759.patch


 In HBASE-6710 (0.94 only), ZKTable was split into ZKTable and 
 ZKTableReadOnly.  We should do that in trunk as well to make the code clearer 
 and closer to 0.94.

--
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

[jira] [Commented] (HBASE-3775) Unique transient names for processes

[
https://issues.apache.org/jira/browse/HBASE-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455474#comment-13455474
]

Lars Hofhansl commented on HBASE-3775:
--

It seems this is no longer an issue. Agreed?

Unique transient names for processes

Key: HBASE-3775
URL: https://issues.apache.org/jira/browse/HBASE-3775
Project: HBase
Issue Type: Brainstorming
Reporter: Andrew Purtell

HBASE-3772 is the latest of several incidents where regionservers and master
map their identities to hostnames yet hostname resolution is inconsistent
cluster wide. With HBase 0.20 we have seen this lead conditions like META
being hosted on 11 servers at once. The situation with HBase 0.90 is better
but it concerns me a lot. Confusion about identity cannot be anything but bad.
Why don't we have the processes generate for themselves a random UUID upon
startup, or similar, and have all processes on the cluster map these UUIDs to
identities? Critically, region assignment state should hold the UUID of the
current assignee. This would not remove the need to resolve region locations
to network addresses, nor determine liveness of assignments, but will prevent
the specific double assignment scenarios we have seen if hostname resolution
is flaky.

[jira] [Updated] (HBASE-4962) Optimize time range scans using a delete Bloom filter

2012-09-13 Thread Kannan Muthukkaruppan (JIRA)


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

Kannan Muthukkaruppan updated HBASE-4962:
-

Assignee: Pritam Damania  (was: Liyin Tang)

 Optimize time range scans using a delete Bloom filter
 -

 Key: HBASE-4962
 URL: https://issues.apache.org/jira/browse/HBASE-4962
 Project: HBase
  Issue Type: Improvement
Reporter: Mikhail Bautin
Assignee: Pritam Damania
Priority: Minor

 To speed up time range scans we need to seek to the maximum timestamp of the 
 requested range,instead of going to the first KV of the (row, column) pair 
 and iterating from there. If we don't know the (row, column), e.g. if it is 
 not specified in the query, we need to go to end of the current row/column 
 pair first, get a KV from there, and do another seek to (row', column', 
 timerange_max) from there. We can only skip over to the timerange_max 
 timestamp when we know that there are no DeleteColumn records at the top of 
 that row/column with a higher timestamp. We can utilize another Bloom filter 
 keyed on (row, column) to quickly find that out.

--
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

[jira] [Resolved] (HBASE-3752) Tool to replay moved-aside WAL logs


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

Lars Hofhansl resolved HBASE-3752.
--

Resolution: Duplicate

Resolving as DUP of HBASE-5604

 Tool to replay moved-aside WAL logs
 ---

 Key: HBASE-3752
 URL: https://issues.apache.org/jira/browse/HBASE-3752
 Project: HBase
  Issue Type: Task
Reporter: stack
Priority: Critical
 Attachments: walplayer.rb, walplayer.rb


 We need this.

--
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

[jira] [Created] (HBASE-6780) On the master status page the Number of Requests per second is incorrect for RegionServer's

Elliott Clark created HBASE-6780:


 Summary: On the master status page the Number of Requests per 
second is incorrect for RegionServer's
 Key: HBASE-6780
 URL: https://issues.apache.org/jira/browse/HBASE-6780
 Project: HBase
  Issue Type: Bug
  Components: master
Reporter: Elliott Clark
Assignee: Elliott Clark


The number of requests per second is getting divided when it shouldn't be.

--
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

[jira] [Commented] (HBASE-3779) Allow split regions to be placed on different region servers


[ 
https://issues.apache.org/jira/browse/HBASE-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455478#comment-13455478
 ] 

Ted Yu commented on HBASE-3779:
---

Please keep this open.
We just need to find a good approach for this issue.

 Allow split regions to be placed on different region servers
 

 Key: HBASE-3779
 URL: https://issues.apache.org/jira/browse/HBASE-3779
 Project: HBase
  Issue Type: Improvement
  Components: master
Affects Versions: 0.90.2
Reporter: Ted Yu
Assignee: Ted Yu
 Attachments: 3779-v2.patch


 Currently daughter regions are placed on the same region server where the 
 parent region was.
 Stanislav Barton mentioned the idea that load information should be 
 considered when placing the daughter regions.
 The rationale is that the daughter regions tend to receive more writes. So it 
 would be beneficial to place at least one daughter region on a different 
 region server.

--
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

[jira] [Resolved] (HBASE-3760) Package info docs missing from org.apache.hadoop.hbase.rest


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

Lars Hofhansl resolved HBASE-3760.
--

Resolution: Invalid

Closing as invalid for the reason that Jean-Marc cites.

 Package info docs missing from org.apache.hadoop.hbase.rest
 ---

 Key: HBASE-3760
 URL: https://issues.apache.org/jira/browse/HBASE-3760
 Project: HBase
  Issue Type: Task
  Components: documentation, rest
Reporter: Gary Helmling
Priority: Trivial

 It looks like the old stargate package-info javadocs somehow got dropped when 
 it replaced the REST code in 0.90.  Was pointed out on IRC that the package 
 docs existed here:
 http://hbase.apache.org/docs/r0.20.6/api/org/apache/hadoop/hbase/stargate/package-summary.html
 We should pull them out of 0.20 into 0.90 and make whatever updates 
 necessary.  Seems to be causing some confusion with users getting started.

--
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

[jira] [Commented] (HBASE-6776) Opened region of disabled/enabling table is not added to online region list


[ 
https://issues.apache.org/jira/browse/HBASE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455483#comment-13455483
 ] 

Jimmy Xiang commented on HBASE-6776:


Right, the table is Disabled.  Somehow, there is still a region opened 
somewhere.

 Opened region of disabled/enabling table is not added to online region list
 ---

 Key: HBASE-6776
 URL: https://issues.apache.org/jira/browse/HBASE-6776
 Project: HBase
  Issue Type: Bug
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Attachments: trunk-6776.patch


 For opened region of disabled table, it should be added to online region 
 list, and then closed.  We should not just ignore them.
 For opened region of enabling table, it should be added to online region 
 list, so that we don't have to assign it again.  Without adding it to online 
 region list, it could be double assigned when assign it again later.

--
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

[jira] [Resolved] (HBASE-3745) Add the ability to restrict major-compactible files by timestamp

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

Lars Hofhansl resolved HBASE-3745.
--

Resolution: Duplicate

Let me mark this as DUP of HBASE-6371

Add the ability to restrict major-compactible files by timestamp

Key: HBASE-3745
URL: https://issues.apache.org/jira/browse/HBASE-3745
Project: HBase
Issue Type: Improvement
Affects Versions: 0.92.0
Reporter: Todd Lipcon

In some applications, a common access pattern is to frequently scan tables
with a time range predicate restricted to a fairly recent time window. For
example, you may want to do an incremental aggregation or indexing step only
on rows that have changed in the last hour. We do this efficiently by
tracking min and max timestamp on an HFile level, so that old HFiles don't
have to be read.
After a major compaction, however, the entire dataset will need to be read,
which can hurt performance of this access pattern.
We should add a column family attribute that can specify a policy like: When
major compacting, never include an HFile that contains data with a timestamp
in the last 4 hours. This, recently flushed HFiles will always be uncompacted
and provide the good scan performance required for these applications.

[jira] [Commented] (HBASE-6780) On the master status page the Number of Requests per second is incorrect for RegionServer's


[ 
https://issues.apache.org/jira/browse/HBASE-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455487#comment-13455487
 ] 

Lars Hofhansl commented on HBASE-6780:
--

What is it divided by?

 On the master status page the Number of Requests per second is incorrect for 
 RegionServer's
 ---

 Key: HBASE-6780
 URL: https://issues.apache.org/jira/browse/HBASE-6780
 Project: HBase
  Issue Type: Bug
  Components: master
Reporter: Elliott Clark
Assignee: Elliott Clark

 The number of requests per second is getting divided when it shouldn't be.

--
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

[jira] [Commented] (HBASE-6780) On the master status page the Number of Requests per second is incorrect for RegionServer's


[ 
https://issues.apache.org/jira/browse/HBASE-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455499#comment-13455499
 ] 

Elliott Clark commented on HBASE-6780:
--

It's divided by the metrics reporting time (which seems like it should work 
assuming that the period is in seconds).

Producing: http://imgur.com/nnoKC

 On the master status page the Number of Requests per second is incorrect for 
 RegionServer's
 ---

 Key: HBASE-6780
 URL: https://issues.apache.org/jira/browse/HBASE-6780
 Project: HBase
  Issue Type: Bug
  Components: master
Reporter: Elliott Clark
Assignee: Elliott Clark

 The number of requests per second is getting divided when it shouldn't be.

--
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

[jira] [Commented] (HBASE-6779) Fix issues analysis.apache.org raises about StochasticLoadBalancer

[
https://issues.apache.org/jira/browse/HBASE-6779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455506#comment-13455506
]

Hadoop QA commented on HBASE-6779:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545082/HBASE-6779-0.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

+1 javadoc. The javadoc tool did not generate any warning messages.

-1 javac. The patch appears to cause mvn compile goal to fail.

-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2863//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2863//console

This message is automatically generated.

Fix issues analysis.apache.org raises about StochasticLoadBalancer
--

Key: HBASE-6779
URL: https://issues.apache.org/jira/browse/HBASE-6779
Project: HBase
Issue Type: Bug
Reporter: Elliott Clark
Assignee: Elliott Clark
Attachments: HBASE-6779-0.patch

[jira] [Commented] (HBASE-6592) [shell] Add means of custom formatting output by column

2012-09-13 Thread Jie Huang (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455507#comment-13455507
 ] 

Jie Huang commented on HBASE-6592:
--

Thanks Stack. 'c(CLASSNAME).METHOD' is much better. What I mean is that the 
user can define their own converter function in the CONVERTER definition.  :)

For that Exception, it is caused by the converter itself. We also met the 
similar problem while running java code. 

The current Bytes.toXXX needs to check the length of the byte array in advance. 
For example, if you want to encode *1*(Int) to a byte array, the array will 
contain 4 bytes (something like \000\000\000\001). And then you are able to 
convert that byte array to an Int object.  You can find the corresponding code 
in *org.apache.hadoop.hbase.util.Bytes.java*. In order to get rid of those 
'\000' in the ruby shell result, here we allow the end user to provide a 
converter to print out the proper output format as they like.
{code}
  public static int toInt(byte[] bytes, int offset, final int length) {
if (length != SIZEOF_INT || offset + length  bytes.length) {  //check the 
length here.
  throw explainWrongLengthOrOffset(bytes, offset, length, SIZEOF_INT);
}
int n = 0;
for(int i = offset; i  (offset + length); i++) {
  n = 8;
  n ^= bytes[i]  0xFF;
}
return n;
  }
{code}
Meanwhile, we also allow the end user to provide their own converter for the 
case as you pointed out. They can define a converter as  'c(CLASSNAME).METHOD' 
as you mentioned. 

 [shell] Add means of custom formatting output by column
 ---

 Key: HBASE-6592
 URL: https://issues.apache.org/jira/browse/HBASE-6592
 Project: HBase
  Issue Type: New Feature
  Components: shell
Reporter: stack
Priority: Minor
  Labels: noob
 Attachments: hbase-6592.patch, hbase-6592-v2.patch, 
 hbase-6952-v1.patch


 See Jacques suggestion toward end of this thread for how we should allow 
 adding a custom formatter per column to use outputting column content in 
 shell: 
 http://search-hadoop.com/m/2WxUB1fuxL11/Printing+integers+in+the+Hbase+shellsubj=Printing+integers+in+the+Hbase+shell

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK

2012-09-13 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455510#comment-13455510
 ] 

Hudson commented on HBASE-6260:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #172 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/172/])
HBASE-6260 balancer state should be stored in ZK (Revision 1384593)

 Result = FAILURE
gchanan : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/generated/LoadBalancerProtos.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/LoadBalancerTracker.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java
* /hbase/trunk/hbase-server/src/main/protobuf/LoadBalancer.proto
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java


 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260-addendum.patch, HBASE-6260.patch, 
 HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Commented] (HBASE-6769) HRS.multi eats NoSuchColumnFamilyException since HBASE-5021

2012-09-13 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455511#comment-13455511
 ] 

Hudson commented on HBASE-6769:
---

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #172 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/172/])
HBASE-6769 HRS.multi eats NoSuchColumnFamilyException (Elliott Clark) 
(Revision 1384377)

 Result = FAILURE
larsh : 
Files : 
* 
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/FailedSanityCheckException.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java


 HRS.multi eats NoSuchColumnFamilyException since HBASE-5021
 ---

 Key: HBASE-6769
 URL: https://issues.apache.org/jira/browse/HBASE-6769
 Project: HBase
  Issue Type: Bug
Affects Versions: 0.94.0, 0.94.1
Reporter: Jean-Daniel Cryans
Assignee: Elliott Clark
Priority: Critical
 Fix For: 0.96.0, 0.94.2

 Attachments: HBASE-6769-0.94-0.patch, HBASE-6769-0.94-1.patch, 
 HBASE-6769-0.patch


 I think this is a pretty major usability regression, since HBASE-5021 this is 
 what you get in the client when using a wrong family:
 {noformat}
 2012-09-11 09:45:29,634 WARN 
 org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 
 action: DoNotRetryIOException: 1 time, servers with issues: sfor3s44:10304, 
   at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchCallback(HConnectionManager.java:1601)
   at 
 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1377)
   at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:916)
   at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:772)
   at org.apache.hadoop.hbase.client.HTable.put(HTable.java:747)
 {noformat}
 Then you have to log on the server to understand what failed.
 Since everything is now a multi call, even single puts in the shell fail like 
 this.
 This is present since 0.94.0
 Assigning to Elliott because he asked.

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK

2012-09-13 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455516#comment-13455516
 ] 

Hudson commented on HBASE-6260:
---

Integrated in HBase-TRUNK #3329 (See 
[https://builds.apache.org/job/HBase-TRUNK/3329/])
HBASE-6260 balancer state should be stored in ZK (Revision 1384593)

 Result = FAILURE
gchanan : 
Files : 
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/protobuf/generated/LoadBalancerProtos.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/LoadBalancerTracker.java
* 
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/ZooKeeperWatcher.java
* /hbase/trunk/hbase-server/src/main/protobuf/LoadBalancer.proto
* 
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterFailover.java


 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260-addendum.patch, HBASE-6260.patch, 
 HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Commented] (HBASE-6416) hbck dies on NPE when a region folder exists but the table does not

2012-09-13 Thread Jie Huang (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455521#comment-13455521
 ] 

Jie Huang commented on HBASE-6416:
--

Sorry for my late response. 

My concern is that now we try to fix .tableinfo file during the online phase, 
which only happens after the offline phase. However, the fixHdfsOrphan does 
happen during the offline phase. I wonder if it is possible to recover those 
missing files respectively. And then, re-run the hbck for a better status.


 hbck dies on NPE when a region folder exists but the table does not
 ---

 Key: HBASE-6416
 URL: https://issues.apache.org/jira/browse/HBASE-6416
 Project: HBase
  Issue Type: Bug
Reporter: Jean-Daniel Cryans
 Fix For: 0.96.0, 0.94.3

 Attachments: hbase-6416.patch, hbase-6416-v1.patch


 This is what I'm getting for leftover data that has no .regioninfo
 First:
 {quote}
 12/07/17 23:13:37 WARN util.HBaseFsck: Failed to read .regioninfo file for 
 region null
 java.io.FileNotFoundException: File does not exist: 
 /hbase/stumble_info_urlid_user/bd5f6cfed674389b4d7b8c1be227cb46/.regioninfo
   at 
 org.apache.hadoop.hdfs.DFSClient$DFSInputStream.openInfo(DFSClient.java:1822)
   at 
 org.apache.hadoop.hdfs.DFSClient$DFSInputStream.init(DFSClient.java:1813)
   at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:544)
   at 
 org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:187)
   at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:456)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck.loadHdfsRegioninfo(HBaseFsck.java:611)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck.access$2200(HBaseFsck.java:140)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck$WorkItemHdfsRegionInfo.call(HBaseFsck.java:2882)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck$WorkItemHdfsRegionInfo.call(HBaseFsck.java:2866)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
   at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 {quote}
 Then it hangs on:
 {quote}
 12/07/17 23:13:39 INFO util.HBaseFsck: Attempting to handle orphan hdfs dir: 
 hdfs://sfor3s24:10101/hbase/stumble_info_urlid_user/bd5f6cfed674389b4d7b8c1be227cb46
 12/07/17 23:13:39 INFO util.HBaseFsck: checking orphan for table null
 Exception in thread main java.lang.NullPointerException
   at 
 org.apache.hadoop.hbase.util.HBaseFsck$TableInfo.access$100(HBaseFsck.java:1634)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck.adoptHdfsOrphan(HBaseFsck.java:435)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck.adoptHdfsOrphans(HBaseFsck.java:408)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck.restoreHdfsIntegrity(HBaseFsck.java:529)
   at 
 org.apache.hadoop.hbase.util.HBaseFsck.offlineHdfsIntegrityRepair(HBaseFsck.java:313)
   at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:386)
   at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3227)
 {quote}
 The NPE is sent by:
 {code}
 Preconditions.checkNotNull(Table  + tableName + ' not present!, 
 tableInfo);
 {code}
 I wonder why the condition checking was added if we don't handle it... In any 
 case hbck dies but it hangs because there are some non-daemon hanging around.

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK


[ 
https://issues.apache.org/jira/browse/HBASE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455530#comment-13455530
 ] 

Ted Yu commented on HBASE-6260:
---

Addendum looks good.

I saw the following in both trunk builds, including HBase-TRUNK-on-Hadoop-2.0.0:
{code}
Failed tests:   
testRegionTransitionOperations(org.apache.hadoop.hbase.coprocessor.TestMasterObserver):
 Coprocessor should be called on region rebalancing
{code}

Please fix the above.

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260-addendum.patch, HBASE-6260.patch, 
 HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Created] (HBASE-6781) .archive directory should be added to HConstants.HBASE_NON_USER_TABLE_DIRS

Ted Yu created HBASE-6781:
-

 Summary: .archive directory should be added to 
HConstants.HBASE_NON_USER_TABLE_DIRS
 Key: HBASE-6781
 URL: https://issues.apache.org/jira/browse/HBASE-6781
 Project: HBase
  Issue Type: Bug
Reporter: Ted Yu
 Fix For: 0.96.0


We can see the following in test output:
{code}
2012-09-14 00:50:43,500 DEBUG [IPC Server handler 0 on 51461] 
util.FSTableDescriptors(175): Exception during readTableDecriptor. Current 
table name = .archive
org.apache.hadoop.hbase.TableInfoMissingException: No .tableinfo file under 
hdfs://localhost:35107/user/jenkins/hbase/.archive
at 
org.apache.hadoop.hbase.util.FSTableDescriptors.getTableDescriptor(FSTableDescriptors.java:417)
at 
org.apache.hadoop.hbase.util.FSTableDescriptors.getTableDescriptor(FSTableDescriptors.java:408)
at 
org.apache.hadoop.hbase.util.FSTableDescriptors.get(FSTableDescriptors.java:170)
at 
org.apache.hadoop.hbase.util.FSTableDescriptors.getAll(FSTableDescriptors.java:201)
at 
org.apache.hadoop.hbase.master.HMaster.getTableDescriptors(HMaster.java:2199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Server.call(ProtobufRpcEngine.java:357)
at 
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1816)
{code}
.archive directory should be added to HConstants.HBASE_NON_USER_TABLE_DIRS

--
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

[jira] [Commented] (HBASE-6592) [shell] Add means of custom formatting output by column

2012-09-13 Thread Jie Huang (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455537#comment-13455537
 ] 

Jie Huang commented on HBASE-6592:
--

here list the examples in the unit test case:
{code}
+
+define_test get should support COLUMNS with value CONVERTER information 
do
+@test_table.put(1, x:c, [1024].pack('N'))
+@test_table.put(1, x:d, [98].pack('N'))
+begin
+  res = @test_table._get_internal('1', ['x:c:toInt'], 
['x:d:c(org.apache.hadoop.hbase.util.Bytes).toInt'])
+  assert_not_nil(res)
+  assert_kind_of(Hash, res)
+  assert_not_nil(/value=1024/.match(res['x:c']))
+  assert_not_nil(/value=98/.match(res['x:d']))
+ensure
+  # clean up newly added columns for this test only.
+  @test_table.delete(1, x:c)
+  @test_table.delete(1, x:d)
+end
+end

+
+define_test scan should support COLUMNS with value CONVERTER information 
do
+  @test_table.put(1, x:c, [1024].pack('N'))
+  @test_table.put(1, x:d, [98].pack('N'))
+  begin
+res = @test_table._scan_internal COLUMNS = ['x:c:toInt', 
'x:d:c(org.apache.hadoop.hbase.util.Bytes).toInt']
+assert_not_nil(res)
+assert_kind_of(Hash, res)
+assert_not_nil(/value=1024/.match(res['1']['x:c']))
+assert_not_nil(/value=98/.match(res['1']['x:d']))
+  ensure
+# clean up newly added columns for this test only.
+@test_table.delete(1, x:c)
+@test_table.delete(1, x:d)
+end
+end
{code}

 [shell] Add means of custom formatting output by column
 ---

 Key: HBASE-6592
 URL: https://issues.apache.org/jira/browse/HBASE-6592
 Project: HBase
  Issue Type: New Feature
  Components: shell
Reporter: stack
Priority: Minor
  Labels: noob
 Attachments: hbase-6592.patch, hbase-6592-v2.patch, 
 hbase-6952-v1.patch


 See Jacques suggestion toward end of this thread for how we should allow 
 adding a custom formatter per column to use outputting column content in 
 shell: 
 http://search-hadoop.com/m/2WxUB1fuxL11/Printing+integers+in+the+Hbase+shellsubj=Printing+integers+in+the+Hbase+shell

--
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

[jira] [Updated] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

2012-09-13 Thread Maryann Xue (JIRA)


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

Maryann Xue updated HBASE-6299:
---

Attachment: (was: HBASE-6299-v3.patch)

 RS starts region open while fails ack to HMaster.sendRegionOpen() causes 
 inconsistency in HMaster's region state and a series of successive problems.
 -

 Key: HBASE-6299
 URL: https://issues.apache.org/jira/browse/HBASE-6299
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 0.90.6, 0.94.0
Reporter: Maryann Xue
Assignee: Maryann Xue
Priority: Critical
 Fix For: 0.96.0, 0.92.3, 0.94.3

 Attachments: HBASE-6299.patch, HBASE-6299-v2.patch


 1. HMaster tries to assign a region to an RS.
 2. HMaster creates a RegionState for this region and puts it into 
 regionsInTransition.
 3. In the first assign attempt, HMaster calls RS.openRegion(). The RS 
 receives the open region request and starts to proceed, with success 
 eventually. However, due to network problems, HMaster fails to receive the 
 response for the openRegion() call, and the call times out.
 4. HMaster attemps to assign for a second time, choosing another RS. 
 5. But since the HMaster's OpenedRegionHandler has been triggered by the 
 region open of the previous RS, and the RegionState has already been removed 
 from regionsInTransition, HMaster finds invalid and ignores the unassigned ZK 
 node RS_ZK_REGION_OPENING updated by the second attempt.
 6. The unassigned ZK node stays and a later unassign fails coz 
 RS_ZK_REGION_CLOSING cannot be created.
 {code}
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Using pre-existing plan for 
 region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.;
  
 plan=hri=CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.,
  src=swbss-hadoop-004,60020,1340890123243, 
 dest=swbss-hadoop-006,60020,1340890678078
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Assigning region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  to swbss-hadoop-006,60020,1340890678078
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=M_ZK_REGION_OFFLINE, server=swbss-hadoop-002:6, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:28,882 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,291 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,299 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENED, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,299 DEBUG 
 org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: Handling OPENED 
 event for 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  from serverName=swbss-hadoop-006,60020,1340890678078, load=(requests=518945, 
 regions=575, usedHeap=15282, maxHeap=31301); deleting unassigned node
 2012-06-29 07:06:32,299 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 master:6-0x2377fee2ae80007 Deleting existing unassigned node for 
 b713fd655fa02395496c5a6e39ddf568 that is in expected state RS_ZK_REGION_OPENED
 2012-06-29 07:06:32,301 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 master:6-0x2377fee2ae80007 Successfully deleted unassigned node for 
 region b713fd655fa02395496c5a6e39ddf568 in expected state RS_ZK_REGION_OPENED
 2012-06-29 07:06:32,301 DEBUG 
 org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: The master has 
 opened the region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  that was online on serverName=swbss-hadoop-006,60020,1340890678078, 
 load=(requests=518945, regions=575, usedHeap=15282, maxHeap=31301)
 2012-06-29 07:07:41,140 WARN 
 org.apache.hadoop.hbase.master.AssignmentManager: Failed assignment of 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  to serverName=swbss-hadoop-006,60020,1340890678078, load=(requests=0, 
 regions=575, usedHeap=0, maxHeap=0), trying to assign elsewhere instead; 
 retry=0
 java.net.SocketTimeoutException: Call to

[jira] [Updated] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

2012-09-13 Thread Maryann Xue (JIRA)


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

Maryann Xue updated HBASE-6299:
---

Attachment: HBASE-6299-v3.patch

@Lars the original unwrap should not work.
@Ted please review the patch.
@ramkrishna How about we apply this fix first and then update the patch for 
HBASE-6438? for as i can see HBASE-6438 is about another problem but the patch 
includes my old fix.

 RS starts region open while fails ack to HMaster.sendRegionOpen() causes 
 inconsistency in HMaster's region state and a series of successive problems.
 -

 Key: HBASE-6299
 URL: https://issues.apache.org/jira/browse/HBASE-6299
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 0.90.6, 0.94.0
Reporter: Maryann Xue
Assignee: Maryann Xue
Priority: Critical
 Fix For: 0.96.0, 0.92.3, 0.94.3

 Attachments: HBASE-6299.patch, HBASE-6299-v2.patch, 
 HBASE-6299-v3.patch


 1. HMaster tries to assign a region to an RS.
 2. HMaster creates a RegionState for this region and puts it into 
 regionsInTransition.
 3. In the first assign attempt, HMaster calls RS.openRegion(). The RS 
 receives the open region request and starts to proceed, with success 
 eventually. However, due to network problems, HMaster fails to receive the 
 response for the openRegion() call, and the call times out.
 4. HMaster attemps to assign for a second time, choosing another RS. 
 5. But since the HMaster's OpenedRegionHandler has been triggered by the 
 region open of the previous RS, and the RegionState has already been removed 
 from regionsInTransition, HMaster finds invalid and ignores the unassigned ZK 
 node RS_ZK_REGION_OPENING updated by the second attempt.
 6. The unassigned ZK node stays and a later unassign fails coz 
 RS_ZK_REGION_CLOSING cannot be created.
 {code}
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Using pre-existing plan for 
 region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.;
  
 plan=hri=CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.,
  src=swbss-hadoop-004,60020,1340890123243, 
 dest=swbss-hadoop-006,60020,1340890678078
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Assigning region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  to swbss-hadoop-006,60020,1340890678078
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=M_ZK_REGION_OFFLINE, server=swbss-hadoop-002:6, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:28,882 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,291 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,299 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENED, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,299 DEBUG 
 org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: Handling OPENED 
 event for 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  from serverName=swbss-hadoop-006,60020,1340890678078, load=(requests=518945, 
 regions=575, usedHeap=15282, maxHeap=31301); deleting unassigned node
 2012-06-29 07:06:32,299 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 master:6-0x2377fee2ae80007 Deleting existing unassigned node for 
 b713fd655fa02395496c5a6e39ddf568 that is in expected state RS_ZK_REGION_OPENED
 2012-06-29 07:06:32,301 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 master:6-0x2377fee2ae80007 Successfully deleted unassigned node for 
 region b713fd655fa02395496c5a6e39ddf568 in expected state RS_ZK_REGION_OPENED
 2012-06-29 07:06:32,301 DEBUG 
 org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: The master has 
 opened the region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  that was online on serverName=swbss-hadoop-006,60020,1340890678078, 
 load=(requests=518945, regions=575, usedHeap=15282, maxHeap=31301)
 2012-06-29 07:07:41,140 WARN 
 org.apache.hadoop.hbase.master.AssignmentManager: Failed assignment of

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

[
https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1348#comment-1348
]

Hadoop QA commented on HBASE-6299:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545092/HBASE-6299-v3.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

+1 javadoc. The javadoc tool did not generate any warning messages.

-1 javac. The patch appears to cause mvn compile goal to fail.

-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

-1 core tests. The patch failed these unit tests:

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2864//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2864//console

This message is automatically generated.

RS starts region open while fails ack to HMaster.sendRegionOpen() causes
inconsistency in HMaster's region state and a series of successive problems.
-

Key: HBASE-6299
URL: https://issues.apache.org/jira/browse/HBASE-6299
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.90.6, 0.94.0
Reporter: Maryann Xue
Assignee: Maryann Xue
Priority: Critical
Fix For: 0.96.0, 0.92.3, 0.94.3

Attachments: HBASE-6299.patch, HBASE-6299-v2.patch,
HBASE-6299-v3.patch

1. HMaster tries to assign a region to an RS.
2. HMaster creates a RegionState for this region and puts it into
regionsInTransition.
3. In the first assign attempt, HMaster calls RS.openRegion(). The RS
receives the open region request and starts to proceed, with success
eventually. However, due to network problems, HMaster fails to receive the
response for the openRegion() call, and the call times out.
4. HMaster attemps to assign for a second time, choosing another RS.
5. But since the HMaster's OpenedRegionHandler has been triggered by the
region open of the previous RS, and the RegionState has already been removed
from regionsInTransition, HMaster finds invalid and ignores the unassigned ZK
node RS_ZK_REGION_OPENING updated by the second attempt.
6. The unassigned ZK node stays and a later unassign fails coz
RS_ZK_REGION_CLOSING cannot be created.
{code}
2012-06-29 07:03:38,870 DEBUG
org.apache.hadoop.hbase.master.AssignmentManager: Using pre-existing plan for
region
CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.;

plan=hri=CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.,
src=swbss-hadoop-004,60020,1340890123243,
dest=swbss-hadoop-006,60020,1340890678078
2012-06-29 07:03:38,870 DEBUG
org.apache.hadoop.hbase.master.AssignmentManager: Assigning region
CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
to swbss-hadoop-006,60020,1340890678078
2012-06-29 07:03:38,870 DEBUG
org.apache.hadoop.hbase.master.AssignmentManager: Handling
transition=M_ZK_REGION_OFFLINE, server=swbss-hadoop-002:6,
region=b713fd655fa02395496c5a6e39ddf568
2012-06-29 07:06:28,882 DEBUG
org.apache.hadoop.hbase.master.AssignmentManager: Handling
transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078,
region=b713fd655fa02395496c5a6e39ddf568
2012-06-29 07:06:32,291 DEBUG
org.apache.hadoop.hbase.master.AssignmentManager: Handling
transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078,
region=b713fd655fa02395496c5a6e39ddf568
2012-06-29 07:06:32,299 DEBUG
org.apache.hadoop.hbase.master.AssignmentManager: Handling
transition=RS_ZK_REGION_OPENED, server=swbss-hadoop-006,60020,1340890678078,
region=b713fd655fa02395496c5a6e39ddf568
2012-06-29 07:06:32,299 DEBUG
org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: Handling OPENED
event for
CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
from serverName=swbss-hadoop-006,60020,1340890678078, load=(requests=518945,
regions=575, usedHeap=15282, maxHeap=31301); deleting unassigned node
2012-06-29

[jira] [Updated] (HBASE-6780) On the master status page the Number of Requests per second is incorrect for RegionServer's


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

Elliott Clark updated HBASE-6780:
-

Fix Version/s: 0.96.0
   Status: Patch Available  (was: Open)

 On the master status page the Number of Requests per second is incorrect for 
 RegionServer's
 ---

 Key: HBASE-6780
 URL: https://issues.apache.org/jira/browse/HBASE-6780
 Project: HBase
  Issue Type: Bug
  Components: master
Reporter: Elliott Clark
Assignee: Elliott Clark
 Fix For: 0.96.0

 Attachments: HBASE-6780-0.patch


 The number of requests per second is getting divided when it shouldn't be.

--
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

[jira] [Updated] (HBASE-6780) On the master status page the Number of Requests per second is incorrect for RegionServer's


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

Elliott Clark updated HBASE-6780:
-

Attachment: HBASE-6780-0.patch

Patch to remove the divide.  The Protobuf that transfers NumberOfRequests gets 
the number from a rate, so there's no need to divide by metrics reporting 
period anymore.

 On the master status page the Number of Requests per second is incorrect for 
 RegionServer's
 ---

 Key: HBASE-6780
 URL: https://issues.apache.org/jira/browse/HBASE-6780
 Project: HBase
  Issue Type: Bug
  Components: master
Reporter: Elliott Clark
Assignee: Elliott Clark
 Fix For: 0.96.0

 Attachments: HBASE-6780-0.patch


 The number of requests per second is getting divided when it shouldn't be.

--
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

[jira] [Commented] (HBASE-6592) [shell] Add means of custom formatting output by column


[ 
https://issues.apache.org/jira/browse/HBASE-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455571#comment-13455571
 ] 

stack commented on HBASE-6592:
--

Understood.  Makes sense.  Let me play around some more  And I'll get back 
to you.  I think all the pieces are here for commit.  I might adjust the doc 
some after playing with it.  Its a nice addition to shell Jie so lets get it in.

 [shell] Add means of custom formatting output by column
 ---

 Key: HBASE-6592
 URL: https://issues.apache.org/jira/browse/HBASE-6592
 Project: HBase
  Issue Type: New Feature
  Components: shell
Reporter: stack
Priority: Minor
  Labels: noob
 Attachments: hbase-6592.patch, hbase-6592-v2.patch, 
 hbase-6952-v1.patch


 See Jacques suggestion toward end of this thread for how we should allow 
 adding a custom formatter per column to use outputting column content in 
 shell: 
 http://search-hadoop.com/m/2WxUB1fuxL11/Printing+integers+in+the+Hbase+shellsubj=Printing+integers+in+the+Hbase+shell

--
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

[jira] [Updated] (HBASE-6780) On the master status page the Number of Requests per second is incorrect for RegionServer's


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

stack updated HBASE-6780:
-

  Resolution: Fixed
Hadoop Flags: Reviewed
  Status: Resolved  (was: Patch Available)

Committed to trunk.  Thanks Elliott.

 On the master status page the Number of Requests per second is incorrect for 
 RegionServer's
 ---

 Key: HBASE-6780
 URL: https://issues.apache.org/jira/browse/HBASE-6780
 Project: HBase
  Issue Type: Bug
  Components: master
Reporter: Elliott Clark
Assignee: Elliott Clark
 Fix For: 0.96.0

 Attachments: HBASE-6780-0.patch


 The number of requests per second is getting divided when it shouldn't be.

--
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

[jira] [Commented] (HBASE-6780) On the master status page the Number of Requests per second is incorrect for RegionServer's

[
https://issues.apache.org/jira/browse/HBASE-6780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455578#comment-13455578
]

Hadoop QA commented on HBASE-6780:
--

-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545097/HBASE-6780-0.patch
against trunk revision .

+1 @author. The patch does not contain any @author tags.

+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.

+1 javadoc. The javadoc tool did not generate any warning messages.

-1 javac. The patch appears to cause mvn compile goal to fail.

-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.

+1 release audit. The applied patch does not increase the total number of
release audit warnings.

+1 core tests. The patch passed unit tests in .

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2865//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2865//console

This message is automatically generated.

On the master status page the Number of Requests per second is incorrect for
RegionServer's
---

Key: HBASE-6780
URL: https://issues.apache.org/jira/browse/HBASE-6780
Project: HBase
Issue Type: Bug
Components: master
Reporter: Elliott Clark
Assignee: Elliott Clark
Fix For: 0.96.0

Attachments: HBASE-6780-0.patch

The number of requests per second is getting divided when it shouldn't be.

[jira] [Commented] (HBASE-6299) RS starts region open while fails ack to HMaster.sendRegionOpen() causes inconsistency in HMaster's region state and a series of successive problems.

2012-09-13 Thread ramkrishna.s.vasudevan (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13455581#comment-13455581
 ] 

ramkrishna.s.vasudevan commented on HBASE-6299:
---

@Maryann
For Sockettimeout unwrap is not needed.  But for RITExcepiton we may need that. 
 As far as i have seen we need to unwrap the remote exception to know the 
actual exception. But SocketTimeOut does not come under that.  (Reason for this 
i have not digged in).:)

 RS starts region open while fails ack to HMaster.sendRegionOpen() causes 
 inconsistency in HMaster's region state and a series of successive problems.
 -

 Key: HBASE-6299
 URL: https://issues.apache.org/jira/browse/HBASE-6299
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 0.90.6, 0.94.0
Reporter: Maryann Xue
Assignee: Maryann Xue
Priority: Critical
 Fix For: 0.96.0, 0.92.3, 0.94.3

 Attachments: HBASE-6299.patch, HBASE-6299-v2.patch, 
 HBASE-6299-v3.patch


 1. HMaster tries to assign a region to an RS.
 2. HMaster creates a RegionState for this region and puts it into 
 regionsInTransition.
 3. In the first assign attempt, HMaster calls RS.openRegion(). The RS 
 receives the open region request and starts to proceed, with success 
 eventually. However, due to network problems, HMaster fails to receive the 
 response for the openRegion() call, and the call times out.
 4. HMaster attemps to assign for a second time, choosing another RS. 
 5. But since the HMaster's OpenedRegionHandler has been triggered by the 
 region open of the previous RS, and the RegionState has already been removed 
 from regionsInTransition, HMaster finds invalid and ignores the unassigned ZK 
 node RS_ZK_REGION_OPENING updated by the second attempt.
 6. The unassigned ZK node stays and a later unassign fails coz 
 RS_ZK_REGION_CLOSING cannot be created.
 {code}
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Using pre-existing plan for 
 region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.;
  
 plan=hri=CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.,
  src=swbss-hadoop-004,60020,1340890123243, 
 dest=swbss-hadoop-006,60020,1340890678078
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Assigning region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  to swbss-hadoop-006,60020,1340890678078
 2012-06-29 07:03:38,870 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=M_ZK_REGION_OFFLINE, server=swbss-hadoop-002:6, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:28,882 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,291 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENING, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,299 DEBUG 
 org.apache.hadoop.hbase.master.AssignmentManager: Handling 
 transition=RS_ZK_REGION_OPENED, server=swbss-hadoop-006,60020,1340890678078, 
 region=b713fd655fa02395496c5a6e39ddf568
 2012-06-29 07:06:32,299 DEBUG 
 org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: Handling OPENED 
 event for 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  from serverName=swbss-hadoop-006,60020,1340890678078, load=(requests=518945, 
 regions=575, usedHeap=15282, maxHeap=31301); deleting unassigned node
 2012-06-29 07:06:32,299 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 master:6-0x2377fee2ae80007 Deleting existing unassigned node for 
 b713fd655fa02395496c5a6e39ddf568 that is in expected state RS_ZK_REGION_OPENED
 2012-06-29 07:06:32,301 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: 
 master:6-0x2377fee2ae80007 Successfully deleted unassigned node for 
 region b713fd655fa02395496c5a6e39ddf568 in expected state RS_ZK_REGION_OPENED
 2012-06-29 07:06:32,301 DEBUG 
 org.apache.hadoop.hbase.master.handler.OpenedRegionHandler: The master has 
 opened the region 
 CDR_STATS_TRAFFIC,13184390567|20120508|17||2|3|913,1337256975556.b713fd655fa02395496c5a6e39ddf568.
  that was online on serverName=swbss-hadoop-006,60020,1340890678078, 
 load=(requests=518945, regions=575, usedHeap=15282, maxHeap=31301)
 2012-06-29 07:07:41,140 WARN 
 org.apache.hadoop.hbase.master.AssignmentManager:

[jira] [Created] (HBASE-6782) HBase shell's 'status 'detailed'' should escape the printed keys

2012-09-13 Thread Viji (JIRA)

Viji created HBASE-6782:
---

 Summary: HBase shell's 'status 'detailed'' should escape the 
printed keys
 Key: HBASE-6782
 URL: https://issues.apache.org/jira/browse/HBASE-6782
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 0.90.1
Reporter: Viji
Priority: Minor


Currently the HBase shell's status command prints unescaped keys on the 
terminal causing the terminal to print garbage characters. We should escape the 
printed keys.

--
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

[jira] [Updated] (HBASE-6260) balancer state should be stored in ZK


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

Gregory Chanan updated HBASE-6260:
--

Attachment: HBASE-6260-addendum2.patch

 balancer state should be stored in ZK
 -

 Key: HBASE-6260
 URL: https://issues.apache.org/jira/browse/HBASE-6260
 Project: HBase
  Issue Type: Task
  Components: master, zookeeper
Affects Versions: 0.96.0
Reporter: Gregory Chanan
Assignee: Gregory Chanan
Priority: Blocker
 Attachments: HBASE-6260-addendum2.patch, HBASE-6260-addendum.patch, 
 HBASE-6260.patch, HBASE-6260-v2.patch


 See: 
 https://issues.apache.org/jira/browse/HBASE-5953?focusedCommentId=13270200page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13270200
 And: 
 https://issues.apache.org/jira/browse/HBASE-5630?focusedCommentId=13399225page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13399225
 In short, we need to move the balancer state to ZK so that it won't have to 
 be restarted if the master dies.

--
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

[jira] [Commented] (HBASE-6260) balancer state should be stored in ZK