[jira] [Created] (HBASE-23772) Remove deprecated getTimeStampOfLastShippedOp from MetricsSource
Jan Hentschel created HBASE-23772:
-
Summary: Remove deprecated getTimeStampOfLastShippedOp from
MetricsSource
Key: HBASE-23772
URL: https://issues.apache.org/jira/browse/HBASE-23772
Project: HBase
Issue Type: Task
Affects Versions: 3.0.0
Reporter: Jan Hentschel
Assignee: Jan Hentschel
{{MetricsSource}} defines the deprecated method
{{getTimeStampOfLastShippedOp}}, which should be removed for 3.0.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23773) Backport "HBASE-23601 OutputSink.WriterThread exception gets stuck and repeated indefinietly" to branch-2.2
Peter Somogyi created HBASE-23773: - Summary: Backport "HBASE-23601 OutputSink.WriterThread exception gets stuck and repeated indefinietly" to branch-2.2 Key: HBASE-23773 URL: https://issues.apache.org/jira/browse/HBASE-23773 Project: HBase Issue Type: Sub-task Affects Versions: 2.2.4 Reporter: Peter Somogyi Assignee: Peter Somogyi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23773) Backport "HBASE-23601 OutputSink.WriterThread exception gets stuck and repeated indefinietly" to branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi resolved HBASE-23773. --- Fix Version/s: 2.2.4 Resolution: Fixed Pushed to branch-2.2. Thanks for the investigation on this issue [~bszabolcs]! > Backport "HBASE-23601 OutputSink.WriterThread exception gets stuck and > repeated indefinietly" to branch-2.2 > --- > > Key: HBASE-23773 > URL: https://issues.apache.org/jira/browse/HBASE-23773 > Project: HBase > Issue Type: Sub-task >Affects Versions: 2.2.4 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Major > Fix For: 2.2.4 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
FYI 2.1.8 not deployed to maven central
Looks like the 2.1.8 staging repository never got closed and released (no 2.1.8 in maven central). I'm assuming that this is just an oversight? Looking at the archives, I see orgapachehbase-1378 is still closed (not released) which is the repo from the vote. I'll get it published now.
[jira] [Created] (HBASE-23774) Announce user-zh list
Josh Elser created HBASE-23774: -- Summary: Announce user-zh list Key: HBASE-23774 URL: https://issues.apache.org/jira/browse/HBASE-23774 Project: HBase Issue Type: Task Components: website Environment: A Reporter: Josh Elser Assignee: Josh Elser Let folks know about the new user-zh list that is dedicated for user questions in chinese (as opposed to the norm of english on user) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23775) Remove deprecated createLocalHTU(Configuration) from HBaseTestingUtility
Jan Hentschel created HBASE-23775:
-
Summary: Remove deprecated createLocalHTU(Configuration) from
HBaseTestingUtility
Key: HBASE-23775
URL: https://issues.apache.org/jira/browse/HBASE-23775
Project: HBase
Issue Type: Sub-task
Affects Versions: 3.0.0
Reporter: Jan Hentschel
Assignee: Jan Hentschel
{{createLocalHTU(Configuration)}} in {{HBaseTestingUtility}} was deprecated
back in 2.0.0 and should be removed for 3.0.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23776) Remove deprecated createLocalHTU from HBaseTestingUtility
Jan Hentschel created HBASE-23776:
-
Summary: Remove deprecated createLocalHTU from HBaseTestingUtility
Key: HBASE-23776
URL: https://issues.apache.org/jira/browse/HBASE-23776
Project: HBase
Issue Type: Sub-task
Affects Versions: 3.0.0
Reporter: Jan Hentschel
Assignee: Jan Hentschel
{{createLocalHTU()}} in {{HBaseTestingUtility}} was deprecated back in 2.0.0
and should be removed for 3.0.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23777) Remove deprecated createTableDescriptor(String, int, int, int, KeepDeletedCells) from HBaseTestingUtility
Jan Hentschel created HBASE-23777:
-
Summary: Remove deprecated createTableDescriptor(String, int, int,
int, KeepDeletedCells) from HBaseTestingUtility
Key: HBASE-23777
URL: https://issues.apache.org/jira/browse/HBASE-23777
Project: HBase
Issue Type: Sub-task
Affects Versions: 3.0.0
Reporter: Jan Hentschel
Assignee: Jan Hentschel
{{createTableDescriptor(String, int, int, int, KeepDeletedCells)}} in
{{HBaseTestingUtility}} was deprecated back in 2.0.0 and should be removed for
3.0.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23778) Support for 'where ' in shell to get the live and history of region location
Swaroopa Kadam created HBASE-23778:
--
Summary: Support for 'where ' in shell to get the live
and history of region location
Key: HBASE-23778
URL: https://issues.apache.org/jira/browse/HBASE-23778
Project: HBase
Issue Type: Improvement
Reporter: Swaroopa Kadam
Assignee: Swaroopa Kadam
My initial thought is mainly to extend the HBase shell(gradually extend to CLI
and UI) to allow the use of
{code:java}
where {code}
to get the necessary information and allow passing history as an additional
parameter to get the history. We can configure how many transitions we want to
store so that anything (ZK or small data structure in the table region itself
or maybe something else) that is used for state management is not exploded.
As pointed by
[~andrew.purt...@gmail.com] need to be watchful of mistakes done in the past:
HBASE-533
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23779) Up the default fork count; make count relative to CPU count
Michael Stack created HBASE-23779: - Summary: Up the default fork count; make count relative to CPU count Key: HBASE-23779 URL: https://issues.apache.org/jira/browse/HBASE-23779 Project: HBase Issue Type: Bug Components: test Reporter: Michael Stack Tests take a long time. Our fork count running all tests are conservative -- 1 (small) for first part and 5 for second part (medium and large). Rather than hardcoding we should set the fork count to be relative to machine size. Suggestion here is 0.75C where C is CPU count. This ups the CPU use on my box. Looking up at jenkins, it seems like the boxes are 24 cores... at least going by my random survey. The load reported on a few seems low though this not representative (looking at machine/uptime). More parallelism willl probably mean more test failure. Let me take a look see. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23780) Edit of test classifications
Michael Stack created HBASE-23780: - Summary: Edit of test classifications Key: HBASE-23780 URL: https://issues.apache.org/jira/browse/HBASE-23780 Project: HBase Issue Type: Bug Components: test Reporter: Michael Stack Our test classifications have drifted. You can see for yourself running each of the small/medium and large test suites. See test complete times. See how even some large tests should be small and vice versa. The more small tests we can run inside the single JVM, the faster we'll get through the build. Tests that are Medium start their own JVM for each test. Tests that are Medium but only last a second or two are expensive and should be aggregated with other single, short tests to amortize the JVM startup. Anyways, let me edit the test categories and try and clean them up some. -- This message was sent by Atlassian Jira (v8.3.4#803005)
