[jira] [Created] (HBASE-19918) Promote TestAsyncClusterAdminApi to LargeTests
Guanghao Zhang created HBASE-19918: -- Summary: Promote TestAsyncClusterAdminApi to LargeTests Key: HBASE-19918 URL: https://issues.apache.org/jira/browse/HBASE-19918 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 2.0.0-beta-1 Reporter: Guanghao Zhang Assignee: Guanghao Zhang org.junit.runners.model.TestTimedOutException: test timed out after 180 seconds Found this timeout in our branch-2 nightly jobs. And this test run more than 110 seconds on my local computer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-19896) Fix ScanInfo.customize() to update only the requested options
[ https://issues.apache.org/jira/browse/HBASE-19896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Singhal resolved HBASE-19896. --- Resolution: Fixed Fix Version/s: 2.0.0-beta-2 > Fix ScanInfo.customize() to update only the requested options > - > > Key: HBASE-19896 > URL: https://issues.apache.org/jira/browse/HBASE-19896 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Ankit Singhal >Assignee: Ankit Singhal >Priority: Major > Fix For: 2.0.0-beta-2 > > > It seems that ScanInfo.customize() is changing > options(timeToPurgeDeletes,tableMaxRowSize,cellsPerTimeoutCheck,preadMaxBytes) > along with requested one's (maxVersions,ttl) > FYI [~tedyu] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Going to roll 1.3.2 RC in next few weeks
Francis, Do you still have an interest in running a 1.3.2 release? On Fri, Jan 5, 2018 at 9:37 AM, Andrew Purtell wrote: > Ok. Great! > > Will revisit this next month. > > On Jan 5, 2018, at 9:35 AM, Francis Christopher Liu > wrote: > > I'm interested in picking it up if that's ok. Tho I'm out till mid next > week. > > Thanks, > Francis > > On Thu, Jan 4, 2018 at 12:00 PM Andrew Purtell > wrote: > >> Ok, I’ll start work on a 1.3.2 RC >> >> >> >> > On Jan 3, 2018, at 12:13 PM, Andrew Purtell >> wrote: >> > >> > I volunteer, if nobody else would like to pick it up. I think we should >> at least have one more 1.3 release. Thanks for running the first two 1.3 >> releases Mikhail. >> > >> > >> >> On Wed, Jan 3, 2018 at 6:01 AM, Mikhail Antonov >> wrote: >> >> Sorry, I have been mostly away since Christmas and catching up on >> emails.. >> >> >> >> So I was going to come up with 1.3.2 RC for some time but never really >> got >> >> to it, life and work intervened.. As I don't expect that to change >> soon, I >> >> suppose it might be better if someone who may have more bandwidth >> picked it >> >> up :( Any volunteers? >> >> >> >> Since we never moved stable pointer to 1.3 line, I think we can discuss >> >> separately how many releases out of this line we want. >> >> >> >> Thanks, >> >> Mikhail >> >> >> >> On Tue, Dec 26, 2017 at 3:24 PM, 김영우 (YoungWoo Kim) >> >> wrote: >> >> >> >> > Hi Mikhail, >> >> > >> >> > Any progress on 1.3.2? Just curious If there is a plan for >> continuing 1.3 >> >> > line. >> >> > >> >> > Thanks, >> >> > - Youngwoo >> >> > >> >> > On Tue, Oct 10, 2017 at 12:52 PM, Mikhail Antonov < >> anto...@apache.org> >> >> > wrote: >> >> > >> >> > > This week I'm planning to go through the hanging jiras >> >> > > and see where we are on it. >> >> > > >> >> > > Please speak up if you have open jiras targeted to 1.3.2 that you'd >> >> > > like to get to 1.3.2 or backport in there, also if you have any >> concerns >> >> > > regarding the jiras that already went in or are about to, or have >> any >> >> > > findings or doubts. >> >> > > >> >> > > Thanks! >> >> > > Mikhail >> >> > > >> >> > >> >> >> >> >> >> >> >> -- >> >> Thanks, >> >> Michael Antonov >> > >> > >> > >> > -- >> > Best regards, >> > Andrew >> > >> > Words like orphans lost among the crosstalk, meaning torn from truth's >> decrepit hands >> >- A23, Crosstalk >> > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
[jira] [Created] (HBASE-19917) Improve RSGroupBasedLoadBalancer#filterServers() to be more efficient
Xiang Li created HBASE-19917:
Summary: Improve RSGroupBasedLoadBalancer#filterServers() to be
more efficient
Key: HBASE-19917
URL: https://issues.apache.org/jira/browse/HBASE-19917
Project: HBase
Issue Type: Improvement
Components: rsgroup
Reporter: Xiang Li
Assignee: Xiang Li
private List filterServers(Collection servers,
Collection onlineServers) {
ArrayList finalList = new ArrayList();
for (Address server : servers) {
for(ServerName curr: onlineServers) {
if(curr.getAddress().equals(server)) {
finalList.add(curr);
}
}
}
return finalList;
}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)
All seems to have settled now. Hadoopqa is running 'normally' again with yetus 0.7.0 and some new configs (Thanks to Allen Wittenhauer for the help/input...). That said, we need to work on curbing resources used during test runs St.Ack On Wed, Jan 31, 2018 at 9:01 AM, Stack wrote: > I just set hadoopqa to be 0.7.0 again with an upped proclimit to see if > this fixes our OOME failures.. HadoopQA builds numbered 11295 and later > will have this change. > Thanks > S > > On Wed, Jan 31, 2018 at 6:46 AM, Stack wrote: > >> Note that I reverted our yetus version last night. It discombobulated our >> builds (OOMEs). Meantime, you'll have to do the patch naming trick for >> another day or so. Our test runs seem to use an ungodly number of file >> descriptors Stay tuned. >> S >> >> On Mon, Jan 29, 2018 at 10:56 PM, Stack wrote: >> >>> Our brothers and sisters over in yetus-land made a release that deals w/ >>> the changed JIRA behavior regards ordering attached-patches. No need of >>> deleting all but the intended patch going forward nor gymnastics with >>> prefixes when naming. It seems to be working properly. The one-liner >>> change that moves us from yetus 0.6.0 to 0.7.0 has been pushed to all >>> active branches and our hadoopqa up on jenkins has been configured to use >>> it going forward. >>> >>> FYI, >>> S >>> >>> On Fri, Dec 8, 2017 at 12:13 PM, Stack wrote: >>> Thanks Andrew. I disabled the job. Use the nightly going forward. The jdk7 builds seem to run fine. The jdk8 has some timeout going on. Need to dig in. You can see here: https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Ni ghtly/job/branch-1.4/ Thanks, M On Fri, Dec 8, 2017 at 11:29 AM, Andrew Purtell wrote: > Ok with me, Stack. Thanks for asking. > > > On Thu, Nov 30, 2017 at 5:33 PM, Stack wrote: > > > On the move over to nightly test runs: > > > > 1.2 nightly had a successful build last night after the branch-1 > > stabilization effort (HBASE-19204) and fixing a few unit test > failures. See > > build 150 > > https://builds.apache.org/view/H-L/view/HBase/job/HBase% > > 20Nightly/job/branch-1.2/ > > It then failed, 151, because of timed out test. Need to dig in. > Clean up a > > few more unit tests and branch-1.2 is probably ready for a > release-cutting. > > > > 1.3 has a few flakies. The last build failed because of: > > > > Test Result (1 failure / ±0) > > org.apache.hadoop.hbase.regionserver.TestEncryptionKeyRotation. > > testCFKeyRotation > > > > Just a little effort should turn 1.3 green. > > > > I was going to disable the 1.4 job, > > https://builds.apache.org/view/H-L/view/HBase/job/HBase-1.4/, in > favor of > > the 1.4 nightly, > > https://builds.apache.org/view/H-L/view/HBase/job/HBase% > > 20Nightly/job/branch-1.4/, > > if ok w/ you Andrew Purtell... And move over the branch-1, branch-2, > and > > master too. > > > > Thanks, > > S > > > > > > > > On Wed, Nov 29, 2017 at 8:06 AM, Stack wrote: > > > > > Example of the new nice reporting: vhttps://builds.apache.org/ > > > view/H-L/view/HBase/job/HBase%20Nightly/job/branch-1.2/ > > > S > > > > > > On Wed, Nov 29, 2017 at 8:06 AM, Stack wrote: > > > > > >> Note that I have disabled the HBase-1.2-JDK7, HBase-1.2-JDK8, > > >> HBase-1.3-JDK7, and HBase-1.3-JDK8 jobs. They have been broken > for a > > good > > >> while now. In their place, refer to an ongoing Sean "Nightly" > project, > > an > > >> effort he has been at for a while. It does more checking with > pretty > > >> reports that will help figuring general stability over time. See > under > > >> https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Ni > ghtly/ > > >> See the nightly builds for 1.2 and 1.3. They have some teething > issues > > >> still but are almost there. See the 1.2 build from last night. In > recent > > >> days, the 1.2 branch went from trash-can fire to stable. See how > all > > tests > > >> passed in the last build but then we failed generating the src > bundle on > > >> the end (this is what I mean by 'teething' issue). Will work on > fixing > > this > > >> last step and moving over 1.4, etc., in the next few days. > > >> > > >> FYI, > > >> St.Ack > > >> > > >> > > >> On Tue, Nov 7, 2017 at 7:45 AM, Stack wrote: > > >> > > >>> On Tue, Nov 7, 2017 at 6:10 AM, Sean Busbey > wrote: > > >>> > > > Should I be able to see the machine dir when I look at > nightlies > > output? > > > (Was trying to see what else is running). > > > > Ah. we don't have the same machine sampling on nightly as we do > in > > precommit. I am 80% on a
[jira] [Created] (HBASE-19916) TestCacheOnWrite Times Out
stack created HBASE-19916: - Summary: TestCacheOnWrite Times Out Key: HBASE-19916 URL: https://issues.apache.org/jira/browse/HBASE-19916 Project: HBase Issue Type: Sub-task Reporter: stack All day it has been timing out. Its a medium test. There is a bit in the middle where we are hung up for a minute or more: 2018-02-01 23:01:02,471 DEBUG [Time-limited test] hfile.HFile$WriterFactory(336): Unable to set drop behind on /testptch/hbase/hbase-server/target/test-data/6a153924-7f81-4008-ac7e-d0e69384655e/data/default/CompactionCacheOnWrite/6dd6ed35f3b6090bd8d04ed21d687424/.tmp/myCF/c0387b09f82840ab9e636faf5cf02d2d 2018-02-01 23:01:03,059 DEBUG [Time-limited test] regionserver.HRegionFileSystem(463): Committing store file /testptch/hbase/hbase-server/target/test-data/6a153924-7f81-4008-ac7e-d0e69384655e/data/default/CompactionCacheOnWrite/6dd6ed35f3b6090bd8d04ed21d687424/.tmp/myCF/c0387b09f82840ab9e63 ...[truncated 1865657 bytes]... b663/myCF/61386855036d4facb75ce7eca2059661, entries=15000, sequenceid=1005, filesize=85.3 K 2018-02-01 23:03:50,591 INFO [Time-limited test] regionserver.HRegion(2713): Finished memstore flush of ~1.73 MB/1814000, currentsize=0 B/0 for region CompactionCacheOnWrite,,1517526229883.3b579f93f196a847ed1489e71585b663. in 175ms, sequenceid=1005, compaction requested=false 2018-02-01 23:03:50,799 INFO [Time-limited test] regionserver.HRegion(2517): Flushing 1/1 column families, memstore=1.80 MB ... I've seen this a few times. The test takes 100seconds locally. Let me try changing it to type. If that doesn't work, will be back. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19915) From SplitTableRegionProcedure daughter regions get created in OFFLINE state
Umesh Agashe created HBASE-19915: Summary: From SplitTableRegionProcedure daughter regions get created in OFFLINE state Key: HBASE-19915 URL: https://issues.apache.org/jira/browse/HBASE-19915 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0-beta-1 Reporter: Umesh Agashe Assignee: Umesh Agashe Fix For: 2.0.0-beta-2 See HBASE-19530. When regions are created initial state should be CLOSED. Bug was discovered while debugging flaky test TestSplitTableRegionProcedure#testRollbackAndDoubleExecution numOfSteps set to 4. After updating daughter regions in meta when master is restarted, startup sequence of master assigns all OFFLINE regions. As daughter regions are stored with OFFLINE state, daughter regions are assigned. This is followed by re-assignment of daughter regions from resumed SplitTableRegionProcedure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Need one more binding vote on 1.4.1 RC0, please
Thank you, Ted. On Thu, Feb 1, 2018 at 2:36 PM, Andrew Purtell wrote: > There are currently 7 nonbinding +1s, one nonbinding -0 and two binding > +1s on the 1.4.1 RC0. > > I need one more binding vote from the PC, please. > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands >- A23, Crosstalk > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
Re: [VOTE] The first HBase 1.4.1 release candidate (RC0) is available
+1 Ran test suite with Java 1.8 - passed Checked signature Ran LTT with 1M row - passed Checked basic WebUI Exercised shell commands On Tue, Jan 30, 2018 at 1:11 PM, Andrew Purtell wrote: > You should follow the build instructions on our online manual (look for > the #maven.release anchor). Please file a JIRA and maybe someone suitably > motivated will look at it but I dont see this as a veto-able concern unless > the build fails following our release procedures. That didn't happen. Or > we'd not have a release candidate. :-) > > > > On Jan 30, 2018, at 1:00 PM, Zach York > wrote: > > > > -0 (non-binding) > > > > It still looks like mvn clean site fails (Also fails for 1.4.0, hence > not a > > -1): > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on > > project hbase: Error generating maven-javadoc-plugin:2.10.3:aggregate: > > [ERROR] Exit code: 1 - warning: unknown enum constant When.MAYBE > > [ERROR] reason: class file for javax.annotation.meta.When not found > > [ERROR] warning: unknown enum constant When.ALWAYS > > [ERROR] warning: unknown enum constant When.UNKNOWN > > [ERROR] javadoc: error - > > com.sun.tools.doclets.internal.toolkit.util.DocletAbortException: > > com.sun.tools.javac.code.Symbol$CompletionFailure: class file for > > javax.annotation.concurrent.Immutable not found > > > > There was some initial investigation/discussion in > > https://issues.apache.org/jira/browse/HBASE-19663 and > > https://issues.apache.org/jira/browse/HBASE-19780 but that was for > branch-2. > > Probably not a blocker for the release, but I still wanted to call this > out. > > > > Zach > > > > > > > >> On Tue, Jan 30, 2018 at 4:26 AM, Yu Li wrote: > >> > >> +1 > >> > >> Checked sums and signatures: ok > >> Built from source: ok (7u79) > >> RAT check: ok (7u79) > >> Compatibility check: ok (7u79) > >> Unit tests pass: ok (7u79) > >> Shell commands: ok (8u101), ran DDL/flush/compact/split commands, > >> everything looks good > >> Loaded 1M rows with LTT: ok (8u101), all keys verified, latency and logs > >> looks good > >> > >> Best Regards, > >> Yu > >> > >>> On 30 January 2018 at 02:28, Andrew Purtell > wrote: > >>> > >>> Thanks Peter, much appreciated. > >>> > >>> On Mon, Jan 29, 2018 at 9:35 AM, Peter Somogyi > >>> wrote: > >>> > The tests failed in localhost mode when executed from maven. I've just > checked some integration tests now on 1.4.0 and it fails there as > well, > >>> so > it not a regression. I'm OK with a +1 on this RC. > > Peter > > On Mon, Jan 29, 2018 at 5:52 PM, Andrew Purtell < > >>> andrew.purt...@gmail.com> > wrote: > > > Are the integration test failures from when it runs in localhost > >> mode? > >>> I > > think these are long term test issues present since 1.3. Or, is this > >>> new > in > > 1.4.1? If these also have the same result with 1.4.0, indicating no > >> new > > regression, would you consider changing your vote? > > > >> On Jan 29, 2018, at 6:54 AM, Peter Somogyi > > wrote: > >> > >> 0 > >> > >> - RAT check: OK > >> - Signatures, checksums: OK > >> - Build from src: OK > >> - Start standalone from src and bin, run shell commands: OK > >> - LTT 1M rows: OK > >> - Web UI, logs: OK > >> - Ran full test suite: passes except integration tests > >> > >> I had failures in IntegrationTestRpcClient, IntegrationTestMTTR, > >> IntegrationTestBigLinkedListWithVisibility and > >> IntegrationTestWithCellVisibilityLoadAndVerify. All other tests > >>> passed > > for > >> me. > >> > >>> On Thu, Jan 25, 2018 at 3:45 AM, Andrew Purtell < > >>> apurt...@apache.org> > > wrote: > >>> > >>> The first HBase 1.4.1 release candidate (RC0) is available for > download > > at > >>> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.1RC0/ and > Maven > >>> artifacts are available in the temporary repository > >>> https://repository.apache.org/content/repositories/ > orgapachehbase-1194 > > . > >>> > >>> The git tag corresponding to the candidate is '1.4.1RC0' > >>> (4b25debc83). > >>> > >>> A detailed source and binary compatibility report for this release > >>> is > >>> available for your review at > >>> https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.1RC0/ > >>> compat-check-report.html > >>> . > >>> > >>> A list of the 38 issues resolved in this release can be found at > >>> https://s.apache.org/tx1w . > >>> > >>> Please try out the candidate and vote +1/0/-1. > >>> > >>> This vote will be open for at least 72 hours. Unless objection I > >>> will > > try > >>> to close it Friday February 2, 2018 if we have sufficient votes. > >>> > >>> Prior to making this announcement I made the following preflight > checks: > >>> > >>> - RAT check passes (7u80)
Re: [VOTE] The first HBase 1.4.1 release candidate (RC0) is available
Considering the site issue isn't a sinkable offense I'm changing my vote to a +1. On Wed, Jan 31, 2018 at 3:50 PM, Umesh Agashe wrote: > +1 non-binding > > download src & bin tar ball - OK > signatures & sums- OK > build from source (openjdk version "1.8.0_151") - OK > rat check - > OK > unit tests - > OK > start local instance from bin & CRUD from shell - OK > LTT write, read1 million rows, 2 cols/row - OK > check logs - OK > > > > On Wed, Jan 31, 2018 at 11:54 AM, Andrew Purtell > wrote: > > > > could not compile against hadoop3 (several issues, will file jira > later) > > > > Thanks, that would be helpful. > > > > We need to discuss it of course but I don't think we should consider > > ticking the Hadoop 3 is supported box on 1.x until the next minor > release, > > 1.5, at which time we could do this work. > > > > > > On Wed, Jan 31, 2018 at 10:20 AM, Mike Drob wrote: > > > > > +1 non-binding > > > > > > sigs/sums good > > > compiles against hadoop2 (7u80) > > > ran hbase-downstreamer tests against staging repo > > > verified upgrade from 1.4.1 to 2.0.0-beta1 > > > > > > could not compile against hadoop3 (several issues, will file jira > later) > > > > > > On Wed, Jan 31, 2018 at 8:52 AM, Ashish Singhi < > ashishsin...@apache.org> > > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > Downloaded the binary and checked the following, > > > > > > > > - Checked LICENSE and NOTICE files, looks ok > > > > - Apache RAT check, looks good > > > > > > > > Verified the following in a non-secure setup, > > > > > > > > - Exercised basic shell commands > > > > - Ran LTT with 1M row, checked read and write operations > > > > - Poked around webUI > > > > - Started Rest server and executed some commands > > > > - Checked logs > > > > - Browsed book > > > > > > > > Regards, > > > > Ashish > > > > > > > > On Thu, Jan 25, 2018 at 8:15 AM, Andrew Purtell > > > > > wrote: > > > > > > > > > The first HBase 1.4.1 release candidate (RC0) is available for > > download > > > > at > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.1RC0/ and > > Maven > > > > > artifacts are available in the temporary repository > > > > > https://repository.apache.org/content/repositories/ > > orgapachehbase-1194 > > > . > > > > > > > > > > The git tag corresponding to the candidate is '1.4.1RC0' > > (4b25debc83). > > > > > > > > > > A detailed source and binary compatibility report for this release > is > > > > > available for your review at > > > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.1RC0/ > > > > > compat-check-report.html > > > > > . > > > > > > > > > > A list of the 38 issues resolved in this release can be found at > > > > > https://s.apache.org/tx1w . > > > > > > > > > > Please try out the candidate and vote +1/0/-1. > > > > > > > > > > This vote will be open for at least 72 hours. Unless objection I > will > > > try > > > > > to close it Friday February 2, 2018 if we have sufficient votes. > > > > > > > > > > Prior to making this announcement I made the following preflight > > > checks: > > > > > > > > > >- RAT check passes (7u80) > > > > >- Unit test suite passes 10 of 10 iterations (8u131) > > > > >- LTT load 1M rows with 100% verification and 20% updates > (8u131) > > > > >- PE sequentialWrite, sequentialRead, randomWrite, randomRead, > > > > >scanRange100 (8u131) > > > > > > > > > > > > > > > -- > > > > > Best regards, > > > > > Andrew > > > > > > > > > > Words like orphans lost among the crosstalk, meaning torn from > > truth's > > > > > decrepit hands > > > > >- A23, Crosstalk > > > > > > > > > > > > > > > > > > > > -- > > Best regards, > > Andrew > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > decrepit hands > >- A23, Crosstalk > > >
Need one more binding vote on 1.4.1 RC0, please
There are currently 7 nonbinding +1s, one nonbinding -0 and two binding +1s on the 1.4.1 RC0. I need one more binding vote from the PC, please. -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
[jira] [Resolved] (HBASE-19911) Convert some tests from small to medium because they are timing out: TestNettyRpcServer, TestClientClusterStatus, TestCheckTestClasses
[ https://issues.apache.org/jira/browse/HBASE-19911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-19911. --- Resolution: Fixed Release Note: Changed a few tests so they are medium sized rather than small size. Also, upped the time we wait on small tests to 60seconds from 30seconds. Small tests are tests that run in 15seconds or less. What we changed was the timeout watcher. It is now more lax, more tolerant of dodgy infrastructure that might be running tests slowly. > Convert some tests from small to medium because they are timing out: > TestNettyRpcServer, TestClientClusterStatus, TestCheckTestClasses > -- > > Key: HBASE-19911 > URL: https://issues.apache.org/jira/browse/HBASE-19911 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.0-beta-2 > > Attachments: > HBASE-19911.addendum2.up_small_timeout_from_30_to_60_seconds.patch, > HBASE-19911.branch-2.001.patch > > > Found some more timeouts of small tests. > TestNettyRpcServer > https://builds.apache.org/view/H-L/view/HBase/job/PreCommit-HBASE-Build/11307/testReport/junit/org.apache.hadoop.hbase.ipc/TestNettyRpcServer/org_apache_hadoop_hbase_ipc_TestNettyRpcServer/ > On local machine takes 14 seconds to run 1 test. In the above failure..., the > test needs another second or so to complete It has been running 30 > seconds. > Starts a minihbasecluster, creates a table, then shuts down. Shouldn't even > take 3 seconds but thats another story. > TestClientClusterStatus is a small test that starts 5 regionservers and 3 > masters. Then does some stopping of servers, etc. > .. in same test run... > https://builds.apache.org/view/H-L/view/HBase/job/PreCommit-HBASE-Build/11307/testReport/junit/org.apache.hadoop.hbase/TestClientClusterStatus/org_apache_hadoop_hbase_TestClientClusterStatus/ > ... it timed out after 30 seconds. Its almost done w/ shutdown but not quite. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Please invite me slack
Hello, dev users. I want to join the slack channel. Please invite me slack. Best regards, Minwoo Kang
[jira] [Created] (HBASE-19914) TestVisibilityLabelsOnNewVersionBehaviorTable does not have Category annotation
Duo Zhang created HBASE-19914: - Summary: TestVisibilityLabelsOnNewVersionBehaviorTable does not have Category annotation Key: HBASE-19914 URL: https://issues.apache.org/jira/browse/HBASE-19914 Project: HBase Issue Type: Sub-task Components: test Reporter: Duo Zhang Fix For: 2.0.0-beta-2 And both TestVisibilityLabelsOnNewVersionBehaviorTable and its parent class run about 2 minutes, which is not safe to declared as MediumTests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
