[jira] [Resolved] (HBASE-21169) Initiate hbck2 tool in hbase-operator-tools repo
[ https://issues.apache.org/jira/browse/HBASE-21169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21169. --- Resolution: Fixed Fix Version/s: 2.1.1 2.2.0 3.0.0 I think its fair to say this has been well-started so resovling. I moved the 'design' from here up to the parent project. Its ongoing and it may get more eyeballs in the umbrella issue. > Initiate hbck2 tool in hbase-operator-tools repo > > > Key: HBASE-21169 > URL: https://issues.apache.org/jira/browse/HBASE-21169 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Affects Versions: 2.1.0 >Reporter: Umesh Agashe >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.1.1 > > Attachments: hbase-21169.master.001.patch > > > Create hbck2 tool in hbase-operator-tools > (https://github.com/apache/hbase-operator-tools.git) repo. This is not > intended to be complete tool but initial changes with usage, ability to > connect to server, logging, and using newly added HbckService etc. Code > changes to address specific use cases can be added later and tool will evolve. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-21209) Add HBaseInterfaceAudience HBCK to indicate that this tool is used by HBCK2?
[ https://issues.apache.org/jira/browse/HBASE-21209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21209. --- Resolution: Duplicate HBASE-20941 already did this ([~uagashe]) > Add HBaseInterfaceAudience HBCK to indicate that this tool is used by HBCK2? > > > Key: HBASE-21209 > URL: https://issues.apache.org/jira/browse/HBASE-21209 > Project: HBase > Issue Type: Sub-task > Components: hbck2 >Reporter: stack >Priority: Major > > We have a new hbck Service and we are adding Procedures that hbck2 can use. > Lets add a new audience designation hbck2 so can mark them apart (From > [~Apache9] over in HBASE-21169) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21209) Add HBaseInterfaceAudience HBCK to indicate that this tool is used by HBCK2?
stack created HBASE-21209: - Summary: Add HBaseInterfaceAudience HBCK to indicate that this tool is used by HBCK2? Key: HBASE-21209 URL: https://issues.apache.org/jira/browse/HBASE-21209 Project: HBase Issue Type: Sub-task Components: hbck2 Reporter: stack We have a new hbck Service and we are adding Procedures that hbck2 can use. Lets add a new audience designation hbck2 so can mark them apart (From [~Apache9] over in HBASE-21169) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21208) Bytes#toShort doesn't work without unsafe
Chia-Ping Tsai created HBASE-21208:
--
Summary: Bytes#toShort doesn't work without unsafe
Key: HBASE-21208
URL: https://issues.apache.org/jira/browse/HBASE-21208
Project: HBase
Issue Type: Bug
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai
Fix For: 2.2.0, 2.1.1, 2.0.3
seems we put the brackets in the wrong place :)
{code}
short n = 0;
n = (short) ((n ^ bytes[offset]) & 0xFF);
n = (short) (n << 8);
n = (short) ((n ^ bytes[offset+1]) & 0xFF); // this one
return n;
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-21207) Add client side sorting functionality in master web UI for table and region server details.
Archana Katiyar created HBASE-21207: --- Summary: Add client side sorting functionality in master web UI for table and region server details. Key: HBASE-21207 URL: https://issues.apache.org/jira/browse/HBASE-21207 Project: HBase Issue Type: Improvement Components: master, monitoring, UI, Usability Reporter: Archana Katiyar In Master UI, we can see region server details like requests per seconds and number of regions etc. Similarly, for tables also we can see online regions , offline regions. It will help ops people in determining hot spotting if we can provide sort functionality in the UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21206) Scan with batch size may return incomplete cells
Zheng Hu created HBASE-21206: Summary: Scan with batch size may return incomplete cells Key: HBASE-21206 URL: https://issues.apache.org/jira/browse/HBASE-21206 Project: HBase Issue Type: Bug Reporter: Zheng Hu Assignee: Zheng Hu Attachments: ut.patch See the attached UT. the table has 5 columns and each column has at least one cell in it, but when we scan the table with batchSize=3, we only got 3 cells returned , the other 2 cells got lost ... It's a critial bug and should be fixed.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-21205) 对时序数据的支持
[ https://issues.apache.org/jira/browse/HBASE-21205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-21205. --- Resolution: Invalid > 对时序数据的支持 > > > Key: HBASE-21205 > URL: https://issues.apache.org/jira/browse/HBASE-21205 > Project: HBase > Issue Type: New Feature >Reporter: lixiaobao >Priority: Minor > > 目前对于物联网的时序数据来说，每秒采集的数据点有几百万个点，每一行数据有几千列，数据写入hbase的时候比较缓慢，有没有计划以后添加对时序数据的支持？ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21205) 对时序数据的支持
lixiaobao created HBASE-21205: - Summary: 对时序数据的支持 Key: HBASE-21205 URL: https://issues.apache.org/jira/browse/HBASE-21205 Project: HBase Issue Type: New Feature Components: HFile Reporter: lixiaobao 目前对于物联网的时序数据来说，每秒采集的数据点有几百万个点，每一行数据有几千列，数据写入hbase的时候比较缓慢，有没有计划以后添加对时序数据的支持？ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Making flakey tests run again
Thanks for the information Sean. I will then commit the changes and watch the flaky tests build. Regards Ram On Tue, Sep 18, 2018 at 11:20 AM Sean Busbey wrote: > Unfortunately there is not currently a way to have tests that are in > the flaky list run in the automated precommit tests[1]. > > I suggest you test the change locally and then commit. When the test > no longer fails in the flaky test runner and ages out of what the > flaky detector looks at[2], it'll start showing up in precommit again. > > [1]: > > https://issues.apache.org/jira/browse/HBASE-19265 > > [2]: > > > https://builds.apache.org/job/HBase-Find-Flaky-Tests/job/master/lastSuccessfulBuild/artifact/dashboard.html > On Mon, Sep 17, 2018 at 11:59 PM ramkrishna vasudevan > wrote: > > > > Hi > > > > As part of HBASE-21102 the test case that was added was reported as Flaky > > test. I had fixed the code such that the test case is not flaky any more. > > > > But when we submit the patch for precommit - it still avoids that test > case > > since it is marked flaky. > > > > I can see in the console output that > > DOCKER_EXTRAARGS=--env=EXCLUDE_TESTS_URL= > > > https://builds.apache.org/job/HBase-Find-Flaky-Tests/job/master/lastSuccessfulBuild/artifact/excludes/ > > > > The test TestServerCrashProcedureWithReplicas has been marked in the > > excludes file and hence it is getting skipped. Is there a way to make it > > run again? > > > > I tried asking the question in the JIRA but thought this is the best > place > > to ask. I did check the dev-support folder and the hbase-personality.sh > > file but was not sure if there was a way to include that flaky test back > > again to ensure it starts running again. > > > > Regards > > Ram >
