[jira] [Resolved] (HBASE-4232) [hbck] Fix should be able to fill info:regioninfo if matching region in fs

2012-04-19 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-4232.
---

Resolution: Duplicate
  Assignee: Jonathan Hsieh

This is the -fixMeta option in the HBASE-5128 hbck improvements.

> [hbck] Fix should be able to fill info:regioninfo if matching region in fs
> --
>
> Key: HBASE-4232
> URL: https://issues.apache.org/jira/browse/HBASE-4232
> Project: HBase
>  Issue Type: Improvement
>Reporter: stack
>Assignee: Jonathan Hsieh
> Attachments: addregion.rb, addregion.rb
>
>
> On Mozilla cluster, hbck reported empty info:regioninfo but then also that 
> there were regions in fs that were not deployed.  At least one of these 
> regions w/ an empty info:regioninfo matches to the region in fs that is not 
> in the .META.  hbck should be able to pick up the region from ms and fix the 
> .META. entry on --fix.
> {code}
> Version: 0.90.1-cdh3u0
> ...
> Number of Tables: 14
> Number of live region servers: 29
> Number of dead region servers: 27
> ..Number of empty REGIONINFO_QUALIFIER rows in .META.: 10
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/10111f37472811e5e86534790bb10e3c
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/1bcaf00897a749ea6a0d0bf1ce709116
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/375913d5c0f5ed4180c0d4506c53fd1d
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/5a1fa81ddf4bac6c7f6483d803d5cc30
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/6240f00ac370c186e44d189d0a52c8e7
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/6bd89ea69b8a4886fed3dfe93ab5e5aa
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/716695118671df66d9d1b883f1aeae56
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/805ce44ef7e6aa7fa1603c422f808a3a
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/8ed41d06b2c8e937cf460ce5e41ecbf9
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/8faa71d5e90aa82570df036515f752e4
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/938f334ca6399ce5a17d33dc1a045d8d
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> ERROR: Region 
> hdfs://hp-admin01.phx1.mozilla.com:8020/hbase/crash_reports/cd673fbac6f8f88f87c81f3bdd3a1ed8
>  on HDFS, b
> ut not listed in META or deployed on any region server.
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-4094) improve hbck tool to fix more hbase problem

2012-04-14 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-4094.
---

  Resolution: Duplicate
Release Note:   (was: The hbck tool(org.apache.hadoop.hbase.util.HBaseFsck) 
can check and repair consistency problem.
some error just be checked but not supply the way to repair, I plan to fix it 
by other tool(close_region...)or by new method.
First, list it and discuss that is it right?

Part A:check meta info
1.errors.reportError(ERROR_CODE.NULL_ROOT_REGION,"Root Region or some of its 
attributes are null."); 
 --> after delete the root table,execute hbck tool to check 
but the tool run error. how to reproduce this error?

2.errors.reportError(ERROR_CODE.NO_META_REGION, ".META. is not found on any 
region.");
 -->after delete the meta table,execute hbck tool to check but the 
tool run error. how to reproduce this error?
 
3.errors.reportError(ERROR_CODE.MULTI_META_REGION, ".META. is found on more 
than one region.");
 ->the logic:scan the root table to get META table 
regioninfo,if META table's regions is more than one,throw the error.
  HBase allow META table has more than 
one region,is it?

Part B:check Consistency
4.ERROR_CODE.NOT_IN_META_HDFS>close it from regionserver.

5.ERROR_CODE.NOT_IN_META_OR_DEPLOYED>do nothing,maybe it will be used to 
fix the chain hole in part C.

6.ERROR_CODE.NOT_IN_META>close it from regionserver.

7.ERROR_CODE.NOT_IN_HDFS_OR_DEPLOYED>delete it from META table,it will make 
a chain hole, when check chain integrity(in part C) to fix it.

8.ERROR_CODE.NOT_IN_HDFS>delete it from META table and close it from 
regionserver,when check chain integrity(in part C) to fix it.

9.ERROR_CODE.NOT_DEPLOYED>assign it.

10.ERROR_CODE.SHOULD_NOT_BE_DEPLOYED>delete if from META table and close it 
from regionserver.

11.ERROR_CODE.MULTI_DEPLOYED--->close all from regionservers,and reassign it.

12.ERROR_CODE.SERVER_DOES_NOT_MATCH_META>close all from regionservers,and 
reassign it.

Part C:check chain Integrity
13.ERROR_CODE.FIRST_REGION_STARTKEY_NOT_EMPTY--->treat it as a hole 
problem(ERROR_CODE.HOLE_IN_REGION_CHAIN).

14.ERROR_CODE.LAST_REGION_ENDKEY_NOT_EMPTY(new add)--->treat it as a hole 
problem(ERROR_CODE.HOLE_IN_REGION_CHAIN).

15.ERROR_CODE.REGION_CYCLE>shut down cluster and merge two region by merge 
tool(org.apache.hadoop.hbase.util.Merge)

16.ERROR_CODE.DUPE_STARTKEYS--->shut down cluster and merge two region by merge 
tool(org.apache.hadoop.hbase.util.Merge)

17.ERROR_CODE.OVERLAP_IN_REGION_CHAIN--->shut down cluster and merge two region 
by merge tool(org.apache.hadoop.hbase.util.Merge)

18.ERROR_CODE.HOLE_IN_REGION_CHAIN--->write a new method to fix it,the logic 
is:for recover the data,collect the regionfo from regionserver and hdfs.if a 
region's key range is overlaping with the hole range,put it in META table and 
assign it,maybe it will create overlapping problem,we can fix it by merge 
tool.if no region be collected,create a new region by the hole key range to fix 
it.)

Changed to duplicate.

> improve hbck tool to fix more hbase problem
> ---
>
> Key: HBASE-4094
> URL: https://issues.apache.org/jira/browse/HBASE-4094
> Project: HBase
>  Issue Type: New Feature
>  Components: master
>Affects Versions: 0.90.3
>Reporter: feng xu
> Fix For: 0.90.7
>
> Attachments: HbaseFsck_TableChain.patch
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-4311) HBaseTestingUtility.createMultiRegions generates table that fails in hbck.

2012-04-12 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-4311.
---

Resolution: Won't Fix

Used other mechanisms to create tables for hbck / HBASE-5128.  Might be better 
to create new issue to remove or deprecate these methods (if this hasn't 
happened yet).

> HBaseTestingUtility.createMultiRegions generates table that fails in hbck.
> --
>
> Key: HBASE-4311
> URL: https://issues.apache.org/jira/browse/HBASE-4311
> Project: HBase
>  Issue Type: Bug
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
>
> When refactoring TestHBaseFsckRepair to add more hbck test cases, I noticed 
> that HBaseTestingUtility.createMultiRegions uses an existing table with empty 
> region, adds more regions, and then attempts to remove the region.  The 
> region remains in meta and is causes hbck to report at inconsistency. Ideally 
> these test table generation utility functions should generate clean tables.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-3354) Add testing of HBCK -fix

2012-04-12 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-3354.
---

Resolution: Duplicate

This was added as part of HBASE-5128.

> Add testing of HBCK -fix
> 
>
> Key: HBASE-3354
> URL: https://issues.apache.org/jira/browse/HBASE-3354
> Project: HBase
>  Issue Type: Test
>Reporter: Jonathan Gray
>Assignee: Jonathan Hsieh
>
> HBASE-3337 adds a new method of HBCK -fix'ing unassignment and dupe 
> assignment.  We should add a unit test which verifies this detects and 
> repairs correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-4122) improve hbck tool to fix .META. hole issue.

2012-04-05 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-4122.
---

   Resolution: Duplicate
Fix Version/s: (was: 0.96.0)
 Assignee: Jonathan Hsieh

This problem this issue tries to fix has been subsumed by HBASE-5128

> improve hbck tool to fix .META. hole issue.
> ---
>
> Key: HBASE-4122
> URL: https://issues.apache.org/jira/browse/HBASE-4122
> Project: HBase
>  Issue Type: Improvement
>  Components: hbck
>Reporter: feng xu
>Assignee: Jonathan Hsieh
> Attachments: HBASE-4122.patch, check_meta.rb
>
>
> hbase hbck tool can check the META hole, but it can not fix this problem by 
> --fix.
> I plan to improve the tool.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-5675) Create table fails if we keep refreshing master's UI for task monitor status

2012-03-29 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-5675.
---

Resolution: Duplicate

> Create table fails if we keep refreshing master's UI for task monitor status
> 
>
> Key: HBASE-5675
> URL: https://issues.apache.org/jira/browse/HBASE-5675
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Affects Versions: 0.90.4, 0.92.0
>Reporter: Mubarak Seyed
>Assignee: Mubarak Seyed
>  Labels: noob
>
> I tried to create a table with 2K pre-split regions, region assignment was in 
> middle and i was keep refreshing master's web UI to find the status of the 
> task using task monitor, table creation was failed and {{META}} was showing 
> 2K regions with server location value is {{null}} and regions weren't 
> deployed onto region-servers.
> {code}
> table_ACreating table table_A
> java.io.IOException: java.io.IOException: 
> java.util.ConcurrentModificationException
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>   at 
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:95)
>   at 
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:79)
>   at 
> org.apache.hadoop.hbase.client.HBaseAdmin.createTableAsync(HBaseAdmin.java:384)
>   at 
> org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:294)
>   at com.test.tools.hbase.schema.createIfNotExists(schema.java:520)
>   at com.test.tools.hbase.schema.main(schema.java:627)
> Caused by: org.apache.hadoop.ipc.RemoteException: java.io.IOException: 
> java.util.ConcurrentModificationException
>   at java.util.SubList.checkForComodification(AbstractList.java:752)
>   at java.util.SubList.add(AbstractList.java:632)
>   at java.util.SubList.add(AbstractList.java:633)
>   at java.util.SubList.add(AbstractList.java:633)
>   ..
>   ..
>   at java.util.SubList.add(AbstractList.java:633)
>   at java.util.AbstractList.add(AbstractList.java:91)
>   at 
> org.apache.hadoop.hbase.monitoring.TaskMonitor.createStatus(TaskMonitor.java:76)
>   at org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:510)
>   at org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:490)
>   at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:853)
>   at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:813)
>   at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:780)
>   at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:570)
>   at 
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1039)
>   at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:771)
>   at 
> org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:257)
>   at $Proxy5.createTable(Unknown Source)
>   at 
> org.apache.hadoop.hbase.client.HBaseAdmin.createTableAsync(HBaseAdmin.java:382)
>   
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-5603) rolling-restart.sh script hangs when attempting to detect expiration of /hbase/master znode.

2012-03-20 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-5603.
---

   Resolution: Fixed
Fix Version/s: 0.96.0
   0.94.0
   0.92.2
 Hadoop Flags: Reviewed

Commited.  Thanks Lars and Ted.

> rolling-restart.sh script hangs when attempting to detect expiration of 
> /hbase/master znode.
> 
>
> Key: HBASE-5603
> URL: https://issues.apache.org/jira/browse/HBASE-5603
> Project: HBase
>  Issue Type: Bug
>  Components: zookeeper
>Affects Versions: 0.92.0, 0.94.0, 0.96.0
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
>Priority: Blocker
> Fix For: 0.92.2, 0.94.0, 0.96.0
>
> Attachments: HBASE-5603.patch
>
>
> Due to bugfix ZOOKEEPER-1059 (ZK 3.4.0+), the rolling-restart.sh script will 
> hang when attempting to make sure the /hbase/master znode is deleted.
> Here's the code
> {code}
> # make sure the master znode has been deleted before continuing
> zparent=`$bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool 
> zookeeper.znode.parent`
> if [ "$zparent" == "null" ]; then zparent="/hbase"; fi
> zmaster=`$bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool 
> zookeeper.znode.master`
> if [ "$zmaster" == "null" ]; then zmaster="master"; fi
> zmaster=$zparent/$zmaster
> echo -n "Waiting for Master ZNode ${zmaster} to expire"
> while bin/hbase zkcli stat $zmaster >/dev/null 2>&1; do
>   echo -n "."
>   sleep 1
> done
> echo #force a newline
> {code}
> Prior to ZOOKEEPER-1059, stat on a null znode would NPE and cause zkcli to 
> exit with retcode 1.  Afterwards, the null is caught, zkcli will exit with 0 
> in the case where the znode is present and in the case where it does not 
> exist.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-5410) Deprecate check_meta.rb

2012-03-07 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-5410.
---

Resolution: Duplicate
  Assignee: Jonathan Hsieh

> Deprecate check_meta.rb
> ---
>
> Key: HBASE-5410
> URL: https://issues.apache.org/jira/browse/HBASE-5410
> Project: HBase
>  Issue Type: Task
>Reporter: Jimmy Xiang
>Assignee: Jonathan Hsieh
>Priority: Trivial
>
> We should depreate check_meta.rb and suggest users to use hbck instead.
> hbck should give more accurate region hole information.
> Should we remove check_meta.rb from both 92 and 94?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-5364) Fix source files missing licenses in 0.92 and trunk

2012-02-10 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-5364.
---

   Resolution: Fixed
Fix Version/s: 0.92.1
   0.94.0
 Hadoop Flags: Reviewed

> Fix source files missing licenses in 0.92 and trunk
> ---
>
> Key: HBASE-5364
> URL: https://issues.apache.org/jira/browse/HBASE-5364
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.94.0, 0.92.0
>Reporter: Jonathan Hsieh
>Assignee: Elliott Clark
>Priority: Blocker
> Fix For: 0.94.0, 0.92.1
>
> Attachments: HBASE-5364-1.patch, hbase-5364-0.92.patch, 
> hbase-5364-v2.patch
>
>
> running 'mvn rat:check' shows that a few files have snuck in that do not have 
> proper apache licenses.  Ideally we should fix these before we cut another 
> release/release candidate.
> This is a blocker for 0.94, and probably should be for the other branches as 
> well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-5276) PerformanceEvaluation does not set the correct classpath for MR because it lives in the test jar

2012-01-26 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-5276.
---

Resolution: Duplicate

> PerformanceEvaluation does not set the correct classpath for MR because it 
> lives in the test jar
> 
>
> Key: HBASE-5276
> URL: https://issues.apache.org/jira/browse/HBASE-5276
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 0.90.4
>Reporter: Tim Robertson
>Assignee: Jonathan Hsieh
>Priority: Minor
>
> Note: This was discovered running the CDH version hbase-0.90.4-cdh3u2
> Running the PerformanceEvaluation as follows:
>   $HADOOP_HOME/bin/hadoop org.apache.hadoop.hbase.PerformanceEvaluation scan 5
> fails because the MR tasks do not get the HBase jar on the CP, and thus hit 
> ClassNotFoundExceptions.
> The job gets the following only:
>   file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/hbase-0.90.4-cdh3u2-tests.jar
>   
> file:/Users/tim/dev/hadoop/hadoop-0.20.2-cdh3u2/hadoop-core-0.20.2-cdh3u2.jar
>   
> file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/lib/zookeeper-3.3.3-cdh3u2.jar
> The RowCounter etc all work because they live in the HBase jar, not the test 
> jar, and they get the following 
>   file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/lib/guava-r06.jar
>   
> file:/Users/tim/dev/hadoop/hadoop-0.20.2-cdh3u2/hadoop-core-0.20.2-cdh3u2.jar
>   file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/hbase-0.90.4-cdh3u2.jar
>   
> file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/lib/zookeeper-3.3.3-cdh3u2.jar
> Presumably this relates to 
>   job.setJarByClass(PerformanceEvaluation.class);
>   ...
>   TableMapReduceUtil.addDependencyJars(job);
> A (cowboy) workaround to run PE is to unpack the jars, and copy the 
> PerformanceEvaluation* classes building a patched jar.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-5276) PerformanceEvaluation does not set the correct classpath for MR because it lives in the test jar

2012-01-26 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-5276.
---

   Resolution: Won't Fix
Fix Version/s: (was: 0.92.1)

This is essentially a dupe for HBASE-4688 which is fixed for Apache HBase 0.92. 
 A new backport request issue specific to CDH is filed here:  
https://issues.cloudera.org/browse/DISTRO-369

> PerformanceEvaluation does not set the correct classpath for MR because it 
> lives in the test jar
> 
>
> Key: HBASE-5276
> URL: https://issues.apache.org/jira/browse/HBASE-5276
> Project: HBase
>  Issue Type: Bug
>  Components: test
>Affects Versions: 0.90.4
>Reporter: Tim Robertson
>Assignee: Jonathan Hsieh
>Priority: Minor
>
> Note: This was discovered running the CDH version hbase-0.90.4-cdh3u2
> Running the PerformanceEvaluation as follows:
>   $HADOOP_HOME/bin/hadoop org.apache.hadoop.hbase.PerformanceEvaluation scan 5
> fails because the MR tasks do not get the HBase jar on the CP, and thus hit 
> ClassNotFoundExceptions.
> The job gets the following only:
>   file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/hbase-0.90.4-cdh3u2-tests.jar
>   
> file:/Users/tim/dev/hadoop/hadoop-0.20.2-cdh3u2/hadoop-core-0.20.2-cdh3u2.jar
>   
> file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/lib/zookeeper-3.3.3-cdh3u2.jar
> The RowCounter etc all work because they live in the HBase jar, not the test 
> jar, and they get the following 
>   file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/lib/guava-r06.jar
>   
> file:/Users/tim/dev/hadoop/hadoop-0.20.2-cdh3u2/hadoop-core-0.20.2-cdh3u2.jar
>   file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/hbase-0.90.4-cdh3u2.jar
>   
> file:/Users/tim/dev/hadoop/hbase-0.90.4-cdh3u2/lib/zookeeper-3.3.3-cdh3u2.jar
> Presumably this relates to 
>   job.setJarByClass(PerformanceEvaluation.class);
>   ...
>   TableMapReduceUtil.addDependencyJars(job);
> A (cowboy) workaround to run PE is to unpack the jars, and copy the 
> PerformanceEvaluation* classes building a patched jar.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-5101) Add a max number of regions per regionserver limit

2011-12-29 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-5101.
---

Resolution: Duplicate
  Assignee: Jonathan Hsieh

This is a dupe of HBASE-2844, and later discussion lead to something similar to 
HBASE-2956.  

> Add a max number of regions per regionserver limit
> --
>
> Key: HBASE-5101
> URL: https://issues.apache.org/jira/browse/HBASE-5101
> Project: HBase
>  Issue Type: Improvement
>  Components: regionserver
>Affects Versions: 0.92.0
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
>
> In a testing environment, a cluster got to a state with more than 1500 
> regions per region server, and essentially became stuck and unavailable.  We 
> could add a limit to the number of regions that a region server can serve to 
> prevent this from happening.  This looks like it could be implemented in the 
> core or as a coprocessor.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-4972) Investigate and port patches on 0.90 branch that are not on 0.92/trunk branch.

2011-12-07 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-4972.
---

Resolution: Not A Problem

> Investigate and port patches on 0.90 branch that are not on 0.92/trunk branch.
> --
>
> Key: HBASE-4972
> URL: https://issues.apache.org/jira/browse/HBASE-4972
> Project: HBase
>  Issue Type: Task
>Affects Versions: 0.92.0
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
>Priority: Critical
> Fix For: 0.92.0
>
>
> There are several issues that have been committed in the 0.90 branch but were 
> not in trunk/0.92 branch.   These regressions should be "forward" ported.
> HBASE-3320  ! 
> HBASE-3380  ! -> HBASE-4610 is a jira to backports this, but it is not done.
> HBASE-3410  ! 
> HBASE-3501  !
> HBASE-3714  ! 
> HBASE-3729  !! Marked in 0.92 but not committed there, committed in 0.90 
> branch.
> HBASE-3848  !
> HBASE-3892  ! * Comments say trunk does not need.
> HBASE-3906  !
> HBASE-3989  !
> HBASE-4109  !
> HBASE-4160  !! Marked resolved 0.90.5, but no corresponding commit in either 
> 0.90 or 0.92
> HBASE-4423  ! 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (HBASE-4548) Client should not look on HDFS to list tables

2011-10-06 Thread Jonathan Hsieh (Resolved) (JIRA) 

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

Jonathan Hsieh resolved HBASE-4548.
---

Resolution: Not A Problem

> Client should not look on HDFS to list tables
> -
>
> Key: HBASE-4548
> URL: https://issues.apache.org/jira/browse/HBASE-4548
> Project: HBase
>  Issue Type: Bug
>  Components: client
>Affects Versions: 0.92.0
>Reporter: Todd Lipcon
>Priority: Critical
> Fix For: 0.92.0
>
>
> In HBASE-4377, Jon noticed that HConnectionManager.listTable now looks on 
> HDFS for the table list. This seems incorrect, since the client may not have 
> access to the hbase directory on HDFS (eg in a secure cluster). At the least, 
> it should RPC to the master to find a table list, and have the master do the 
> list on HDFS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira