[jira] [Created] (HBASE-14364) hlog_roll and compact_rs broken in shell
Lars Hofhansl created HBASE-14364: - Summary: hlog_roll and compact_rs broken in shell Key: HBASE-14364 URL: https://issues.apache.org/jira/browse/HBASE-14364 Project: HBase Issue Type: Bug Affects Versions: 0.98.14 Reporter: Lars Hofhansl Assignee: Lars Hofhansl Just noticed that both hlog_roll and compact_rs are broken in shell (at least in 0.98). The hlog_roll broken 3 times: (1) calls admin.rollWALWriter, which no longer exists, and (2) tries to pass a ServerName, but method takes a string, and (3) uses unqualified ServerName to get a server name, which leads to an uninitialized constant error. compact_rs only has the latter problem. Patch upcoming. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14363) Print more details on the row behind an Empty REGIONINFO_QUALIFIER warning
Harsh J created HBASE-14363: --- Summary: Print more details on the row behind an Empty REGIONINFO_QUALIFIER warning Key: HBASE-14363 URL: https://issues.apache.org/jira/browse/HBASE-14363 Project: HBase Issue Type: Bug Components: hbck Affects Versions: 1.0.0 Reporter: Harsh J Priority: Trivial Currently HBCK just prints a vague "Empty REGIONINFO_QUALIFIER found" warning, and does not print the row it found that on. While fixing this is easy thanks to HBCK, some more detail (say the row/region ID) would be good to print, to avoid people manually scanning meta to obtain the very same info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14362) org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS is super duper flaky
Dima Spivak created HBASE-14362: --- Summary: org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS is super duper flaky Key: HBASE-14362 URL: https://issues.apache.org/jira/browse/HBASE-14362 Project: HBase Issue Type: Bug Components: test Affects Versions: 2.0.0 Reporter: Dima Spivak Priority: Critical [As seen in Jenkins|https://builds.apache.org/job/HBase-TRUNK/lastCompletedBuild/testReport/org.apache.hadoop.hbase.master.procedure/TestWALProcedureStoreOnHDFS/history/], this test has been super flaky and we should probably address it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14361) Investigate unused connection objects
Nick Dimiduk created HBASE-14361: Summary: Investigate unused connection objects Key: HBASE-14361 URL: https://issues.apache.org/jira/browse/HBASE-14361 Project: HBase Issue Type: Task Components: Client Reporter: Nick Dimiduk Over on HBASE-12911 I have a patch that registers Connection instances with the metrics system. In both standalone server and tll client applications, I was surprised to see multiple connection objects showing up that are unused. These are pretty heavy objects, including lots of client threads for the batch pool. We should track these down and remove them -- if they're not some kind of phantom artifacts of my WIP patch over there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14360) Client GC log path is not computed
Nick Dimiduk created HBASE-14360:
Summary: Client GC log path is not computed
Key: HBASE-14360
URL: https://issues.apache.org/jira/browse/HBASE-14360
Project: HBase
Issue Type: Bug
Components: scripts
Reporter: Nick Dimiduk
Priority: Minor
Looking for GC logs on the client side, I noticed the nice work from HBASE-7817
that gives us the settings, just uncomment and run. Giving this a try with ltt,
looks like {{}} is not replaced according to the comments. Seems
this work is done by {{bin/hbase-daemon.sh}}, not {{bin/hbase}}. The result is
my ltt produced a file {{.0}} in {{$(pwd)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14359) HTable#close will hang forever if unchecked error/exception thrown in AsyncProcess#sendMultiAction
Yu Li created HBASE-14359: - Summary: HTable#close will hang forever if unchecked error/exception thrown in AsyncProcess#sendMultiAction Key: HBASE-14359 URL: https://issues.apache.org/jira/browse/HBASE-14359 Project: HBase Issue Type: Bug Affects Versions: 1.1.2, 0.98.14 Reporter: Yu Li Assignee: Victor Xu Currently in AsyncProcess#sendMultiAction, we only catch the RejectedExecutionException and let other error/exception go, which will cause decTaskCounter not invoked. Meanwhile, the recommendation for using HTable is to close the table in the finally clause, and HTable#close will call flushCommits and wait until all task done. The problem is when unchecked error/exception like OutOfMemoryError thrown, taskSent will never be equal to taskDone, so AsyncProcess#waitUntilDone will never return. Especially, if autoflush is set thus no data to flush during table close, there would be no rpc call so rpcTimeOut will not break the call, and thread will wait there forever. In our product env, the unchecked error we observed is "java.lang.OutOfMemoryError: unable to create new native thread", and we observed the client thread hang for hours -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14358) Parent region is not removed from regionstates after a successful split
Esteban Gutierrez created HBASE-14358:
-
Summary: Parent region is not removed from regionstates after a
successful split
Key: HBASE-14358
URL: https://issues.apache.org/jira/browse/HBASE-14358
Project: HBase
Issue Type: Bug
Affects Versions: 1.2.1, 1.0.3, 1.1.3
Reporter: Esteban Gutierrez
Priority: Critical
Ran into this while trying to find out why region_mover.rb was not catching an
exception after a region was split. Digging further I found that the problem is
happening in the handling of the region state in the Master since we don't
remove the old state after the split is successful:
{code}
2015-09-03 02:56:49,255 INFO org.apache.hadoop.hbase.master.AssignmentManager:
Ignored moving region not assigned: {ENCODED =>
9a4930ed41dc7013d9956240e6f5c03e, NAME =>
'u,user3605,1432797255754.9a4930ed41dc7013d9956240e6f5c03e.', STARTKEY =>
'user3605', ENDKEY => 'user3723'}, {9a4930ed41dc7013d9956240e6f5c03e
state=SPLIT, ts=1441273152561,
server=a2209.halxg.cloudera.com,22101,1441243232790}
{code}
I don't think the problem is happening in the master branch but at least I've
been able to confirm this is happening on branch-1 and branch-1.2 at least.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
