[jira] [Assigned] (HBASE-5798) NPE running hbck on 0.94 out of reportTablesInFlux
[
https://issues.apache.org/jira/browse/HBASE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-5798:
-
Assignee: Anoop Sam John (was: Jonathan Hsieh)
Anoop -- go for it. :)
> NPE running hbck on 0.94 out of reportTablesInFlux
> --
>
> Key: HBASE-5798
> URL: https://issues.apache.org/jira/browse/HBASE-5798
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Affects Versions: 0.94.0, 0.96.0
>Reporter: stack
>Assignee: Anoop Sam John
>
> Got this playing w/ hbck going against the 0.94RC:
> {code}
> 12/04/16 17:03:14 INFO util.HBaseFsck: getHTableDescriptors == tableNames =>
> []
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.util.HBaseFsck.reportTablesInFlux(HBaseFsck.java:553)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:344)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:380)
> at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3033)
> {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] [Assigned] (HBASE-5798) NPE running hbck on 0.94 out of reportTablesInFlux
[
https://issues.apache.org/jira/browse/HBASE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-5798:
-
Assignee: Jonathan Hsieh
> NPE running hbck on 0.94 out of reportTablesInFlux
> --
>
> Key: HBASE-5798
> URL: https://issues.apache.org/jira/browse/HBASE-5798
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Assignee: Jonathan Hsieh
>
> Got this playing w/ hbck going against the 0.94RC:
> {code}
> 12/04/16 17:03:14 INFO util.HBaseFsck: getHTableDescriptors == tableNames =>
> []
> Exception in thread "main" java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.util.HBaseFsck.reportTablesInFlux(HBaseFsck.java:553)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:344)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:380)
> at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3033)
> {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] [Assigned] (HBASE-5793) TestHBaseFsck#TestNoHdfsTable test hangs after HBASE-5747
[ https://issues.apache.org/jira/browse/HBASE-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5793: - Assignee: Jonathan Hsieh > TestHBaseFsck#TestNoHdfsTable test hangs after HBASE-5747 > - > > Key: HBASE-5793 > URL: https://issues.apache.org/jira/browse/HBASE-5793 > Project: HBase > Issue Type: Bug >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > After the HBSAE-5747 modification, this one particular case hangs. -- 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] [Assigned] (HBASE-5781) Zookeeper session got closed while trying to assign the region to RS using hbck -fix
[
https://issues.apache.org/jira/browse/HBASE-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-5781:
-
Assignee: Jonathan Hsieh
> Zookeeper session got closed while trying to assign the region to RS using
> hbck -fix
>
>
> Key: HBASE-5781
> URL: https://issues.apache.org/jira/browse/HBASE-5781
> Project: HBase
> Issue Type: Bug
> Components: hbck
>Reporter: Kristam Subba Swathi
>Assignee: Jonathan Hsieh
>
> After running the hbck in the cluster ,it is found that one region is not
> assigned
> So the hbck -fix is used to fix this
> But the assignment didnt happen since the zookeeper session is closed
> Please find the attached trace for more details
> -
> Trying to fix unassigned region...
> 12/04/03 11:02:57 INFO util.HBaseFsckRepair: Region still in transition,
> waiting for it to become assigned: {NAME =>
> 'ufdr,002300,179123498.00871fbd7583512e12c4eb38e900be8d.', STARTKEY =>
> '002300', ENDKEY => '002311', ENCODED => 00871fbd7583512e12c4eb38e900be8d,}
> 12/04/03 11:02:58 INFO client.HConnectionManager$HConnectionImplementation:
> Closed zookeeper sessionid=0x236738a263a
> 12/04/03 11:02:58 INFO zookeeper.ZooKeeper: Session: 0x236738a263a closed
> ERROR: Region { meta =>
> ufdr,010444,179123857.01594219211d0035b9586f98954462e1., hdfs =>
> hdfs://10.18.40.25:9000/hbase/ufdr/01594219211d0035b9586f98954462e1, deployed
> => } not deployed on any region server.
> Trying to fix unassigned region...
> 12/04/03 11:02:58 INFO zookeeper.ClientCnxn: EventThread shut down
> 12/04/03 11:02:58 WARN zookeeper.ZKUtil: hconnection-0x236738a263a Unable
> to set watcher on znode (/hbase)
> org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode
> = Session expired for /hbase
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:127)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1021)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:150)
> at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:263)
> at
> org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.checkIfBaseNodeAvailable(ZooKeeperNodeTracker.java:208)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.checkIfBaseNodeAvailable(HConnectionManager.java:695)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getMaster(HConnectionManager.java:626)
> at org.apache.hadoop.hbase.client.HBaseAdmin.getMaster(HBaseAdmin.java:211)
> at org.apache.hadoop.hbase.client.HBaseAdmin.assign(HBaseAdmin.java:1325)
> at
> org.apache.hadoop.hbase.util.HBaseFsckRepair.forceOfflineInZK(HBaseFsckRepair.java:109)
> at
> org.apache.hadoop.hbase.util.HBaseFsckRepair.fixUnassigned(HBaseFsckRepair.java:92)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.tryAssignmentRepair(HBaseFsck.java:1235)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.checkRegionConsistency(HBaseFsck.java:1351)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.checkAndFixConsistency(HBaseFsck.java:1114)
> at
> org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:356)
> at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:375)
> at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:2894)
> 12/04/03 11:02:58 ERROR zookeeper.ZooKeeperWatcher:
> hconnection-0x236738a263a Received unexpected KeeperException,
> re-throwing exception
> org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode
> = Session expired for /hbase
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:127)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1021)
> at
> org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.exists(RecoverableZooKeeper.java:150)
> at org.apache.hadoop.hbase.zookeeper.ZKUtil.checkExists(ZKUtil.java:263)
> at
> org.apache.hadoop.hbase.zookeeper.ZooKeeperNodeTracker.checkIfBaseNodeAvailable(ZooKeeperNodeTracker.java:208)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.checkIfBaseNodeAvailable(HConnectionManager.java:695)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getMaster(HConnectionManager.java:626)
> at org.apache.hadoop.hbase.client.HBaseAdmin.getMaster(HBaseAdmin.java:211)
> at org.apache.hadoop.hbase.client.HBaseAdmin.assign(HBaseAdmin.java:1325)
> at
> org.apache.hadoop.hbase.util.HBaseFsckRepair.forceOfflineInZK(HBaseFsckRepair.java:109)
> at
> org.apache.hadoop.hbase.util.H
[jira] [Assigned] (HBASE-5680) Hbase94 and Hbase 92.2 is not compatible with the Hadoop 23.1
[ https://issues.apache.org/jira/browse/HBASE-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5680: - Assignee: Jonathan Hsieh > Hbase94 and Hbase 92.2 is not compatible with the Hadoop 23.1 > -- > > Key: HBASE-5680 > URL: https://issues.apache.org/jira/browse/HBASE-5680 > Project: HBase > Issue Type: Bug > Components: master >Reporter: Kristam Subba Swathi >Assignee: Jonathan Hsieh > > Hmaster is not able to start because of the following error > Please find the following error > > 2012-03-30 11:12:19,487 FATAL org.apache.hadoop.hbase.master.HMaster: > Unhandled exception. Starting shutdown. > java.lang.NoClassDefFoundError: > org/apache/hadoop/hdfs/protocol/FSConstants$SafeModeAction > at org.apache.hadoop.hbase.util.FSUtils.waitOnSafeMode(FSUtils.java:524) > at > org.apache.hadoop.hbase.master.MasterFileSystem.checkRootDir(MasterFileSystem.java:324) > at > org.apache.hadoop.hbase.master.MasterFileSystem.createInitialFileSystemLayout(MasterFileSystem.java:127) > at > org.apache.hadoop.hbase.master.MasterFileSystem.(MasterFileSystem.java:112) > at > org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:496) > at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:363) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.ClassNotFoundException: > org.apache.hadoop.hdfs.protocol.FSConstants$SafeModeAction > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 7 more > There is a change in the FSConstants -- 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] [Assigned] (HBASE-5712) Parallelize load of .regioninfo files in diagnostic/repair portion of hbck.
[ https://issues.apache.org/jira/browse/HBASE-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5712: - Assignee: Jonathan Hsieh > Parallelize load of .regioninfo files in diagnostic/repair portion of hbck. > --- > > Key: HBASE-5712 > URL: https://issues.apache.org/jira/browse/HBASE-5712 > Project: HBase > Issue Type: Sub-task > Components: hbck >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > On heavily loaded hdfs's some dfs nodes may not respond quickly and backs off > for 60s before attempting to read data from another datanode. Portions of > the information gathered from hdfs (.regioninfo files) are loaded serially. > With HBase with clusters with 100's, or 1000's, or 1's regions > encountering these 60s delay blocks progress and can be very painful. > There is already some parallelization of portions of the hdfs information > load operations and the goal here is move the reading of .regioninfos into > the parallelized sections.. -- 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] [Assigned] (HBASE-4393) Implement a canary monitoring program
[ https://issues.apache.org/jira/browse/HBASE-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4393: - Assignee: Matteo Bertozzi (was: Amandeep Khurana) > Implement a canary monitoring program > - > > Key: HBASE-4393 > URL: https://issues.apache.org/jira/browse/HBASE-4393 > Project: HBase > Issue Type: New Feature > Components: monitoring >Affects Versions: 0.92.0 >Reporter: Todd Lipcon >Assignee: Matteo Bertozzi > Attachments: Canary-v0.java, HBaseCanary.java > > > This JIRA is to implement a standalone program that can be used to do "canary > monitoring" of a running HBase cluster. This program would gather a list of > the regions in the cluster, then iterate over them doing lightweight > operations (eg short scans) to provide metrics about latency as well as alert > on availability issues. -- 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] [Assigned] (HBASE-5314) Gracefully rolling restart region servers in rolling-restart.sh
[ https://issues.apache.org/jira/browse/HBASE-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5314: - Assignee: Yifeng Jiang Set Yifeng as assignee. > Gracefully rolling restart region servers in rolling-restart.sh > --- > > Key: HBASE-5314 > URL: https://issues.apache.org/jira/browse/HBASE-5314 > Project: HBase > Issue Type: Improvement > Components: scripts >Reporter: Yifeng Jiang >Assignee: Yifeng Jiang >Priority: Minor > Fix For: 0.96.0 > > Attachments: HBASE-5314.patch, HBASE-5314.patch.2 > > > The rolling-restart.sh has a --rs-only option which simply restarts all > region servers in the cluster. > Consider improve it to gracefully restart region servers to avoid the offline > time of the regions deployed on that server, and keep the region > distributions same as what it was before the restarting. -- 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] [Assigned] (HBASE-5603) rolling-restart.sh script hangs when attempting to detect expiration of /hbase/master znode.
[
https://issues.apache.org/jira/browse/HBASE-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-5603:
-
Assignee: Jonathan Hsieh
> 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
> 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] [Assigned] (HBASE-5588) Deprecate/remove AssignmentManager#clearRegionFromTransition
[ https://issues.apache.org/jira/browse/HBASE-5588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5588: - Assignee: Jonathan Hsieh > Deprecate/remove AssignmentManager#clearRegionFromTransition > > > Key: HBASE-5588 > URL: https://issues.apache.org/jira/browse/HBASE-5588 > Project: HBase > Issue Type: Sub-task > Components: hbck >Affects Versions: 0.90.5, 0.92.0, 0.94.0, 0.96.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > This method is essentially a dupe of Assignment#regionOffline. As suggested > in early review of HBASE-5128 - deprecate up to 0.94 and remove from > 0.96/trunk. -- 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] [Assigned] (HBASE-5589) Add of the offline call to the Master Interface
[ https://issues.apache.org/jira/browse/HBASE-5589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5589: - Assignee: Jonathan Hsieh > Add of the offline call to the Master Interface > --- > > Key: HBASE-5589 > URL: https://issues.apache.org/jira/browse/HBASE-5589 > Project: HBase > Issue Type: Sub-task > Components: hbck >Affects Versions: 0.90.6, 0.92.0, 0.94.0, 0.96.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > Hbck from HBASE-5128 requires an offline method on the master to properly > cleanup state during certain assignment repair operations. This will this > method will be added to recent and older versions of HBase. -- 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] [Assigned] (HBASE-5364) Fix source files missing licenses in 0.92 and trunk
[ https://issues.apache.org/jira/browse/HBASE-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5364: - Assignee: Elliott Clark > 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 > Attachments: HBASE-5364-1.patch, hbase-5364-0.92.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] [Assigned] (HBASE-5377) Fix licenses on the 0.90 branch.
[ https://issues.apache.org/jira/browse/HBASE-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5377: - Assignee: Jonathan Hsieh > Fix licenses on the 0.90 branch. > > > Key: HBASE-5377 > URL: https://issues.apache.org/jira/browse/HBASE-5377 > Project: HBase > Issue Type: Bug >Affects Versions: 0.90.6 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Attachments: hbase-5377.patch > > > There are a handful of empty files and several files missing apache licenses > on the 0.90 branch. This patch will fixes all of them and in conjunction > with HBASE-5363 will allow it to pass RAT tests. -- 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] [Assigned] (HBASE-5288) Security source code dirs missing from 0.92.0 release tarballs.
[ https://issues.apache.org/jira/browse/HBASE-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5288: - Assignee: Jonathan Hsieh (was: Gary Helmling) > Security source code dirs missing from 0.92.0 release tarballs. > --- > > Key: HBASE-5288 > URL: https://issues.apache.org/jira/browse/HBASE-5288 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 0.94.0, 0.92.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh >Priority: Blocker > Fix For: 0.94.0, 0.92.1 > > Attachments: hbase-5288.patch > > > The release tarballs have a compiled version of the hbase jars and the > security tarball seems to have the compiled security bits. However, the > source code and resources for security implementation are missing from the > release tarballs in both distributions. They should be included in both. -- 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] [Assigned] (HBASE-5363) Add rat check to run automatically on mvn build.
[ https://issues.apache.org/jira/browse/HBASE-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5363: - Assignee: Jonathan Hsieh > Add rat check to run automatically on mvn build. > > > Key: HBASE-5363 > URL: https://issues.apache.org/jira/browse/HBASE-5363 > Project: HBase > Issue Type: Improvement > Components: build >Affects Versions: 0.90.5, 0.92.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > Some of the recent hbase release failed rat checks (mvn rat:check). We > should add checks likely in the mvn package phase so that this becomes a > non-issue in the future. > Here's an example from Whirr: > https://github.com/apache/whirr/blob/trunk/pom.xml line 388 for an example. -- 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] [Assigned] (HBASE-5356) region_mover.rb can hang if table region it belongs to is deleted.
[
https://issues.apache.org/jira/browse/HBASE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-5356:
-
Assignee: Jonathan Hsieh
> region_mover.rb can hang if table region it belongs to is deleted.
> --
>
> Key: HBASE-5356
> URL: https://issues.apache.org/jira/browse/HBASE-5356
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.3, 0.94.0, 0.92.0
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
>Priority: Minor
>
> I was testing the region_mover.rb script on a loaded hbase and noticed that
> it can hang (thus hanging graceful shutdown) if a region that it is
> attempting to move gets deleted (by a table delete operation).
> Here's the start of the relevent stack dump
> {code}
> 12/02/08 13:27:13 WARN client.HConnectionManager$HConnectionImplementation:
> Encountered problems when prefetch META table:
> org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for
> table: TestLoadAndVerify_1328735001040, row=TestLoadAnd\
> Verify_1328735001040,yC^P\xD7\x945\xD4,99
> at
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:136)
> at
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:95)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:64\
> 9)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:703\
> )
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:594)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.relocateRegion(HConnectionManager.java:565)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionLocation(HConnectionManager.java:416)
> at
> org.apache.hadoop.hbase.client.ServerCallable.instantiateServer(ServerCallable.java:57)
> at
> org.apache.hadoop.hbase.client.ScannerCallable.instantiateServer(ScannerCallable.java:63)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithRetries(HConnectionManager.\
> java:1018)
> at
> org.apache.hadoop.hbase.client.HTable$ClientScanner.nextScanner(HTable.java:1104)
> at
> org.apache.hadoop.hbase.client.HTable$ClientScanner.initialize(HTable.java:1027)
> at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:535)
> at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:525)
> at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:380)
> at
> org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:58)
> at
> org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:137)
> at
> usr.lib.hbase.bin.region_mover.method__7$RUBY$isSuccessfulScan(/usr/lib/hbase/bin/region_mover.rb:133)
> at
> usr$lib$hbase$bin$region_mover#method__7$RUBY$isSuccessfulScan.call(usr$lib$hbase$bin$region_mover#method__7$RUBY$isSucces\
> sfulScan:65535)
> at
> usr$lib$hbase$bin$region_mover#method__7$RUBY$isSuccessfulScan.call(usr$lib$hbase$bin$region_mover#method__7$RUBY$isSucces\
> sfulScan:65535)
> at
> org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:171)
> at
> usr.lib.hbase.bin.region_mover.block_4$RUBY$__for__(/usr/lib/hbase/bin/region_mover.rb:326)
> at
> usr$lib$hbase$bin$region_mover#block_4$RUBY$__for__.call(usr$lib$hbase$bin$region_mover#block_4$RUBY$__for__:65535)
> at org.jruby.runtime.CompiledBlock.yield(CompiledBlock.java:133)
> at org.jruby.runtime.BlockBody.call(BlockBody.java:73)
> at org.jruby.runtime.Block.call(Block.java:89)
> at org.jruby.RubyProc.call(RubyProc.java:268)
> at org.jruby.RubyProc.call(RubyProc.java:228)
> at org.jruby.RubyProc$i$0$0$call.call(RubyProc$i$0$0$call.gen:65535)
> at
> org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:209)
> at
> org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:205)
> at
> org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:137)
> at org.jruby.ast.CallOneArgNode.interpret(CallOneArgNode.java:57)
> at org.jruby.ast.NewlineNode.interpret(NewlineNode.java:103)
>
[jira] [Assigned] (HBASE-5083) Backup HMaster should have http infoport open with link to the active master
[ https://issues.apache.org/jira/browse/HBASE-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5083: - Assignee: Jonathan Hsieh > Backup HMaster should have http infoport open with link to the active master > > > Key: HBASE-5083 > URL: https://issues.apache.org/jira/browse/HBASE-5083 > Project: HBase > Issue Type: Improvement > Components: master >Affects Versions: 0.92.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > Without ssh'ing and jps/ps'ing, it is difficult to see if a backup hmaster is > up. It seems like it would be good for a backup hmaster to have a basic web > page up on the info port so that users could see that it is up. Also it > should probably either provide a link to the active master or automatically > forward to the active master. -- 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] [Assigned] (HBASE-5063) RegionServers fail to report to backup HMaster after primary goes down.
[ https://issues.apache.org/jira/browse/HBASE-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-5063: - Assignee: Jonathan Hsieh > RegionServers fail to report to backup HMaster after primary goes down. > --- > > Key: HBASE-5063 > URL: https://issues.apache.org/jira/browse/HBASE-5063 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.0 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh >Priority: Critical > Attachments: HBASE-5063.patch > > > # Setup cluster with two HMasters > # Observe that HM1 is up and that all RS's are in the RegionServer list on > web page. > # Kill (not even -9) the active HMaster > # Wait for ZK to time out (default 3 minutes). > # Observe that HM2 is now active. Tables may show up but RegionServers never > report on web page. Existing connections are fine. New connections cannot > find regionservers. > Note: > * If we replace a new HM1 in the same place and kill HM2, the cluster > functions normally again after recovery. This sees to indicate that > regionservers are stuck trying to talk to the old HM1. -- 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] [Assigned] (HBASE-4934) Display Master server and Regionserver start time on respective info servers.
[ https://issues.apache.org/jira/browse/HBASE-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4934: - Assignee: Jonathan Hsieh > Display Master server and Regionserver start time on respective info servers. > - > > Key: HBASE-4934 > URL: https://issues.apache.org/jira/browse/HBASE-4934 > Project: HBase > Issue Type: Improvement >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh >Priority: Minor > > With operations like rolling restart or master failovers, it is difficult to > tell if a server is the "old" instance or the "new" restarted instance. > Adding a start date stamp on the info web pages would be helpful for > determining this. -- 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] [Assigned] (HBASE-4677) Remove old single bulkLoadHFile method
[ https://issues.apache.org/jira/browse/HBASE-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4677: - Assignee: Jonathan Hsieh > Remove old single bulkLoadHFile method > -- > > Key: HBASE-4677 > URL: https://issues.apache.org/jira/browse/HBASE-4677 > Project: HBase > Issue Type: Sub-task > Components: regionserver >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.92.0 > > > In review for HBASE-4649, there is some debate as whether to remove, > deprecate, or leave the HRegionServer.bulkLoadHFile method. > https://reviews.apache.org/r/2545/ . This jira will take care of that for > the 0.92 and trunk releases, and allow the same patch to remain for an > optional 0.90.x patch. -- 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] [Assigned] (HBASE-4650) Update LoadIncrementalHFiles to use atomic bulk load RS mechanism
[ https://issues.apache.org/jira/browse/HBASE-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4650: - Assignee: Jonathan Hsieh > Update LoadIncrementalHFiles to use atomic bulk load RS mechanism > - > > Key: HBASE-4650 > URL: https://issues.apache.org/jira/browse/HBASE-4650 > Project: HBase > Issue Type: Sub-task > Components: regionserver >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.92.0 > > Attachments: > 0001-HBASE-4650-Update-LoadIncrementalHFiles-to-use-atomi.patch, > 0001-HBASE-4650-Update-LoadIncrementalHFiles-to-use-atomi.prelim.patch > > > MR jobs and command line bulk load execution runs use the > LoadIncrementalHFile.doBulkLoad. This needs to be updated to group HFiles by > row/region so that rows can be atomically loaded multiple column families. -- 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] [Assigned] (HBASE-4649) Add atomic bulk load function to region server
[ https://issues.apache.org/jira/browse/HBASE-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4649: - Assignee: Jonathan Hsieh > Add atomic bulk load function to region server > -- > > Key: HBASE-4649 > URL: https://issues.apache.org/jira/browse/HBASE-4649 > Project: HBase > Issue Type: Sub-task > Components: regionserver >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.92.0 > > > Add a method that atomically bulk load multiple hfiles. Row atomicity > guarantees for multi-column family rows require this functionality. -- 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] [Assigned] (HBASE-4552) multi-CF bulk load is not atomic across column families
[ https://issues.apache.org/jira/browse/HBASE-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4552: - Assignee: Jonathan Hsieh > multi-CF bulk load is not atomic across column families > --- > > Key: HBASE-4552 > URL: https://issues.apache.org/jira/browse/HBASE-4552 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.92.0 >Reporter: Todd Lipcon >Assignee: Jonathan Hsieh > Fix For: 0.92.0 > > > Currently the bulk load API simply imports one HFile at a time. With > multi-column-family support, this is inappropriate, since different CFs show > up separately. Instead, the IPC endpoint should take a of CF -> HFiles, so we > can online them all under a single region-wide lock. -- 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] [Assigned] (HBASE-4378) [hbck] Does not complain about regions with startkey==endkey.
[ https://issues.apache.org/jira/browse/HBASE-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4378: - Assignee: Jonathan Hsieh > [hbck] Does not complain about regions with startkey==endkey. > - > > Key: HBASE-4378 > URL: https://issues.apache.org/jira/browse/HBASE-4378 > Project: HBase > Issue Type: Bug > Components: hbck >Affects Versions: 0.90.4 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.92.0, 0.90.5 > > Attachments: > 0001-HBASE-4378-hbck-Does-not-complain-about-regions-with.patch > > > hbck doesn't seem to complain or have an error condition if there is a region > where startkey==endkey. -- 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] [Assigned] (HBASE-4623) Remove @deprecated Scan methods in 0.90 from TRUNK and 0.92
[ https://issues.apache.org/jira/browse/HBASE-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4623: - Assignee: Jonathan Hsieh > Remove @deprecated Scan methods in 0.90 from TRUNK and 0.92 > --- > > Key: HBASE-4623 > URL: https://issues.apache.org/jira/browse/HBASE-4623 > Project: HBase > Issue Type: Sub-task >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.92.0 > > -- 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] [Assigned] (HBASE-4436) Remove methods deprecated in 0.90 from TRUNK and 0.92
[ https://issues.apache.org/jira/browse/HBASE-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4436: - Assignee: Jonathan Hsieh > Remove methods deprecated in 0.90 from TRUNK and 0.92 > - > > Key: HBASE-4436 > URL: https://issues.apache.org/jira/browse/HBASE-4436 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: Jonathan Hsieh >Priority: Critical > Labels: noob > Fix For: 0.92.0 > > > Remove methods deprecated in 0.90 from codebase. i took a quick look. The > messy bit is thrift referring to old stuff; will take a little work to do the > convertion over to the new methods. -- 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] [Assigned] (HBASE-4515) User.getCurrent() can cause NPE.
[
https://issues.apache.org/jira/browse/HBASE-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-4515:
-
Assignee: Gary Helmling (was: Jonathan Hsieh)
> User.getCurrent() can cause NPE.
>
>
> Key: HBASE-4515
> URL: https://issues.apache.org/jira/browse/HBASE-4515
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.0, 0.94.0
>Reporter: Jonathan Hsieh
>Assignee: Gary Helmling
> Attachments: 0001-HBASE-4515-User.getCurrent-can-cause-NPE.patch,
> HBASE-4515_trunk.patch
>
>
> When testing with miniclusters that shutdown and are restarted, sometimes a
> call to User.getCurrent().getName() NPEs when attempting to restart hbase.
> Oddly this happens consistently on particular branches and not on others. I
> don't know or understand why this happens but it has something to do with the
> getCurrentUGI call in o.a.h.h.security.User.HadoopUser sometimes returning
> null and sometimes returning data.
> {code}
>private HadoopUser() {
> try {
> ugi = (UserGroupInformation) callStatic("getCurrentUGI");
> if (ugi == null) {
> LOG.warn("Although successfully retrieved UserGroupInformation"
> + " it was null!");
> }
> } catch (RuntimeException re) {
> {code}
> This patch essentially is a workaround -- it propagates the null so that
> clients can check and avoid the NPE.
--
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] [Assigned] (HBASE-4515) User.getCurrent() can cause NPE.
[
https://issues.apache.org/jira/browse/HBASE-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh reassigned HBASE-4515:
-
Assignee: Jonathan Hsieh
> User.getCurrent() can cause NPE.
>
>
> Key: HBASE-4515
> URL: https://issues.apache.org/jira/browse/HBASE-4515
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.0, 0.94.0
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
>
> When testing with miniclusters that shutdown and are restarted, sometimes a
> call to User.getCurrent().getName() NPEs when attempting to restart hbase.
> Oddly this happens consistently on particular branches and not on others. I
> don't know or understand why this happens but it has something to do with the
> getCurrentUGI call in o.a.h.h.security.User.HadoopUser sometimes returning
> null and sometimes returning data.
> {code}
>private HadoopUser() {
> try {
> ugi = (UserGroupInformation) callStatic("getCurrentUGI");
> if (ugi == null) {
> LOG.warn("Although successfully retrieved UserGroupInformation"
> + " it was null!");
> }
> } catch (RuntimeException re) {
> {code}
> This patch essentially is a workaround -- it propagates the null so that
> clients can check and avoid the NPE.
--
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] [Assigned] (HBASE-4509) [hbck] Improve region map output
[ https://issues.apache.org/jira/browse/HBASE-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4509: - Assignee: Jonathan Hsieh > [hbck] Improve region map output > > > Key: HBASE-4509 > URL: https://issues.apache.org/jira/browse/HBASE-4509 > Project: HBase > Issue Type: Improvement >Affects Versions: 0.92.0, 0.94.0, 0.90.5 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > HBASE-4375 added a region coverage visualization to hbck in details mode. > When users have binary row keys the output is difficult to parse (awk/sed) or > pull into programs (numeric, excel) capable of handling tsv formatted data. > This patch > * improves output by using Bytes.toStringBinary (which escapes binary) > instead of Bytes.toString when printing keys, > * suggests some repair actions, and > * collects "problem group" that groups regions that are overlapping. -- 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] [Assigned] (HBASE-4377) [hbck] Offline rebuild .META. from fs data only.
[ https://issues.apache.org/jira/browse/HBASE-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh reassigned HBASE-4377: - Assignee: Jonathan Hsieh > [hbck] Offline rebuild .META. from fs data only. > > > Key: HBASE-4377 > URL: https://issues.apache.org/jira/browse/HBASE-4377 > Project: HBase > Issue Type: New Feature >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > > In a worst case situation, it may be helpful to have an offline .META. > rebuilder that just looks at the file system's .regioninfos and rebuilds meta > from scratch. Users could move bad regions out until there is a clean > rebuild. > It would likely fill in region split holes. Follow on work could given > options to merge or select regions that overlap, or do online rebuilds. -- 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
