[ANNOUNCE] Apache HBase 2.1.10 is now available for download
The HBase team is happy to announce the immediate availability of Apache HBase 2.1.10. Download from https://hbase.apache.org/downloads.html Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. To learn more about HBase, see https://hbase.apache.org/. HBase 2.1.10 is the latest release of the HBase 2.1 line, continuing on the theme of bringing a stable, reliable database to the Apache Big Data ecosystem and beyond. 2.1.10 includes ~ ~23 bug and improvement fixes done since the 2.1.9. And notice that, 2.1.10 is the last release of the HBase 2.1 line. Thank you for trusting and choosing the 2.1.x release line. In the future, users are encouraged to upgrade to our current stable release line 2.2.x, and please also keep an eye on the up coming 2.3.x release line. For instructions on verifying ASF release downloads, please see https://www.apache.org/dyn/closer.cgi#verify Project member signature keys can be found at https://www.apache.org/dist/hbase/KEYS Thanks to all the contributors who made this release possible! Best, The HBase Dev Team
[jira] [Created] (HBASE-24152) Add ServerSsdLocalityCostFunction to StochasticLoadBalancer
Zheng Wang created HBASE-24152: -- Summary: Add ServerSsdLocalityCostFunction to StochasticLoadBalancer Key: HBASE-24152 URL: https://issues.apache.org/jira/browse/HBASE-24152 Project: HBase Issue Type: New Feature Components: Balancer Reporter: Zheng Wang Assignee: Zheng Wang When use ONE_SSD storagy policy, or ALL_SSD but has not enough SSD, there will be some hdfs blocks on DISK and others on SSD,so it is reasonable to consider the locality of ssd for StochasticLoadBalancer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24121) [Authorization] ServiceAuthorizationManager isn't dynamically updatable. And it should be.
[ https://issues.apache.org/jira/browse/HBASE-24121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan resolved HBASE-24121. --- Resolution: Fixed > [Authorization] ServiceAuthorizationManager isn't dynamically updatable. And > it should be. > -- > > Key: HBASE-24121 > URL: https://issues.apache.org/jira/browse/HBASE-24121 > Project: HBase > Issue Type: Bug >Reporter: Reid Chan >Assignee: Reid Chan >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.7.0, 1.4.14, 2.2.5 > > > Some more background information. > ServiceAuthorizationManager is responsible for the Services access rights > defined in hbase-policy.xml which locates under $hbase_home/conf directory. > Currently, since it doesn't support update dynamically, we need to restart > master/regionservers to make configurations take effect. It is an expensive > and low efficient admin operation. > HDFS has the refreshPolicy to do that, HBase also has update_config command, > we can make use of that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24153) Remove unnecessary super() in MultiVersionConcurrencyControl#MultiVersionConcurrencyControl()
Lisheng Sun created HBASE-24153: --- Summary: Remove unnecessary super() in MultiVersionConcurrencyControl#MultiVersionConcurrencyControl() Key: HBASE-24153 URL: https://issues.apache.org/jira/browse/HBASE-24153 Project: HBase Issue Type: Improvement Reporter: Lisheng Sun -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24154) HdfsFileStatus incompatibility when used with Hadoop 3.1.3 and Hbase version 2.2.4
Mohankumar K H created HBASE-24154: -- Summary: HdfsFileStatus incompatibility when used with Hadoop 3.1.3 and Hbase version 2.2.4 Key: HBASE-24154 URL: https://issues.apache.org/jira/browse/HBASE-24154 Project: HBase Issue Type: Bug Components: hadoop3 Affects Versions: 2.2.4 Environment: cenots 7.6 util.VersionInfo: HBase 2.2.4,/usr/lib/jvm/java-1.8.0-openjdk Reporter: Mohankumar K H Hi, Even after compiling from source I am getting below error message handler.AssignRegionHandler: Fatal error occurred while opening region hbase:meta,,1.1588230740, aborting... java.lang.IncompatibleClassChangeError: Found interface org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:496) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:116) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:576) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:571) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:584) at org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:51) at org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:169) at org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:166) at org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:113) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:643) at org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:126) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:767) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:501) at org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:442) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:156) at org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:61) at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:284) at org.apache.hadoop.hbase.regionserver.HRegionServer.getWAL(HRegionServer.java:2181) at org.apache.hadoop.hbase.regionserver.handler.AssignRegionHandler.process(AssignRegionHandler.java:133) at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24155) When running the tests, a tremendous number of connections are put into TIME_WAIT.
Mark Robert Miller created HBASE-24155: -- Summary: When running the tests, a tremendous number of connections are put into TIME_WAIT. Key: HBASE-24155 URL: https://issues.apache.org/jira/browse/HBASE-24155 Project: HBase Issue Type: Test Components: test Reporter: Mark Robert Miller When you run the test suite and monitor the number of connections in TIME_WAIT, it appears that a very large number of connections do not end up with a proper connection close lifecycle. Given connections can stay in TIME_WAIT from 1-4 minutes depending on OS/Env, running the tests faster or with more tests in parallel increases the TIME_WAIT connection buildup. Some tests spin up a very, very large number of connections and if the wrong ones run at the same time, this can also greatly increase the number of connections put into TIME_WAIT. This can have a dramatic affect on performance (as it can take longer to create a new connection) or flat out fail or timeout. Ideally, a small proportion of connections in a test suite would end up in TIME_WAIT in comparison to the number created. Notes to come in comments below. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24136) Add release branch report to git-jira-release-audit tool
[
https://issues.apache.org/jira/browse/HBASE-24136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24136.
--
Fix Version/s: 3.0.0
Resolution: Fixed
> Add release branch report to git-jira-release-audit tool
>
>
> Key: HBASE-24136
> URL: https://issues.apache.org/jira/browse/HBASE-24136
> Project: HBase
> Issue Type: Improvement
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Minor
> Fix For: 3.0.0
>
>
> Update {{git-jira-release-audit}} to build a "what's new" report for a
> release branch (i.e., {{branch-2.3}}). Currently it only supports building
> such a report from a release line branch (i.e., {{branch-2}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24156) Make ZK registry the default for branch-2 and branch-3
Bharath Vissapragada created HBASE-24156: Summary: Make ZK registry the default for branch-2 and branch-3 Key: HBASE-24156 URL: https://issues.apache.org/jira/browse/HBASE-24156 Project: HBase Issue Type: Task Components: Client Affects Versions: 2.3.0 Reporter: Bharath Vissapragada Assignee: Bharath Vissapragada This is already the case due to [this commit|https://github.com/apache/hbase/commit/558ee079fd04dfab8e61eca10ee98ab5bac89dfa], however it wasn't tagged with a jira ID. I'm creating a new jira so that I can revert and re-apply this commit with this jira ID. Easier to track fix versions this way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24157) RSGroup Aware Export Snapshot
Mallikarjun created HBASE-24157: --- Summary: RSGroup Aware Export Snapshot Key: HBASE-24157 URL: https://issues.apache.org/jira/browse/HBASE-24157 Project: HBase Issue Type: Improvement Components: snapshots Reporter: Mallikarjun Export Snapshot to a destination cluster which is RSGroup aware can lead to data spill outside of destination RSGroup. This improvement aims at ensuring export snapshort to be aware of destination RSGroup nodes and placing the data only in those boxes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24158) [Fl
Michael Stack created HBASE-24158: - Summary: [Fl Key: HBASE-24158 URL: https://issues.apache.org/jira/browse/HBASE-24158 Project: HBase Issue Type: Bug Reporter: Michael Stack -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24159) [flakey test] regionserver.TestRegionMergeTransactionOnCluster
Huaxiang Sun created HBASE-24159: Summary: [flakey test] regionserver.TestRegionMergeTransactionOnCluster Key: HBASE-24159 URL: https://issues.apache.org/jira/browse/HBASE-24159 Project: HBase Issue Type: Test Components: regionserver Affects Versions: 3.0.0, 2.3.0, 2.4.0 Reporter: Huaxiang Sun Assignee: Hua Xiang As reported in [https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2.3/lastSuccessfulBuild/artifact/dashboard.html#job_1,] testCleanMergeReference fails when waiting for merge table in meta table to be cleaned. Debugged a bit, found that this is case that state is polluted from other testing cases. the meta table is polluted from the previous region merge test cases (tables are not deleted after the testing case finishes). While compaction still goes on and janitor kicks in, it will clean up the old table state and breaks the loop (cleaned > 0), so leave the state under test never cleaned up.The solution is to delete tables after each test case. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [ANNOUNCE] Apache HBase 2.1.10 is now available for download
I removed the below user from hbase lists for flagrant violation of our Code of Conduct [1] after chatting w/ the PMC. Pardon the noise, S 1. https://hbase.apache.org/coc.html On Thu, Apr 9, 2020 at 8:46 AM Sean Kennedy wrote: > Zhang, Have you ever conspired in espionage on behalf of the chinese > communist party? Your alma mater has a sordid past in these type of > activities. > > Kindly, > Sean > > On Thu, Apr 9, 2020 at 3:16 AM Duo Zhang wrote: > > > The HBase team is happy to announce the immediate availability of Apache > > HBase 2.1.10. > > > > Download from https://hbase.apache.org/downloads.html > > > > Apache HBase is an open-source, distributed, versioned, non-relational > > database. Apache HBase gives you low latency random access to billions of > > rows with millions of columns atop non-specialized hardware. To learn > more > > about HBase, see https://hbase.apache.org/. > > > > HBase 2.1.10 is the latest release of the HBase 2.1 line, continuing on > the > > theme of bringing a stable, reliable database to the Apache Big Data > > ecosystem and beyond. 2.1.10 includes ~ ~23 bug and improvement fixes > done > > since the 2.1.9. > > > > And notice that, 2.1.10 is the last release of the HBase 2.1 line. Thank > > you for trusting and choosing the 2.1.x release line. In the future, > users > > are encouraged to upgrade to our current stable release line 2.2.x, and > > please also keep an eye on the up coming 2.3.x release line. > > > > For instructions on verifying ASF release downloads, please see > > > > https://www.apache.org/dyn/closer.cgi#verify > > > > Project member signature keys can be found at > > > > https://www.apache.org/dist/hbase/KEYS > > > > Thanks to all the contributors who made this release possible! > > > > Best, > > The HBase Dev Team > > >
[jira] [Created] (HBASE-24160) create-release fails to process x.y.0 version info correctly
Nick Dimiduk created HBASE-24160:
Summary: create-release fails to process x.y.0 version info
correctly
Key: HBASE-24160
URL: https://issues.apache.org/jira/browse/HBASE-24160
Project: HBase
Issue Type: Bug
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
Trying out {{create-release/do-release-docker.sh}}, is has trouble parsing the
2.3.0-SNAPSHOT version. It also builds an invalid tag name for the API check.
{noformat}
Current branch VERSION is 2.3.0-SNAPSHOT.
RELEASE_VERSION [2.3.-1]: 2.3.0
NEXT_VERSION [2.3.0-SNAPSHOT]: 2.3.1-SNAPSHOT
RC_COUNT [0]:
GIT_REF [2.3.0RC0]:
api_diff_tag, [rel/2.2.0)]:
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24156) Make ZK registry the default for branch-2 and branch-2.3
[ https://issues.apache.org/jira/browse/HBASE-24156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharath Vissapragada resolved HBASE-24156. -- Fix Version/s: 2.3.0 Resolution: Fixed > Make ZK registry the default for branch-2 and branch-2.3 > > > Key: HBASE-24156 > URL: https://issues.apache.org/jira/browse/HBASE-24156 > Project: HBase > Issue Type: Task > Components: Client >Affects Versions: 2.3.0 >Reporter: Bharath Vissapragada >Assignee: Bharath Vissapragada >Priority: Major > Fix For: 2.3.0 > > > This is already the case due to [this > commit|https://github.com/apache/hbase/commit/558ee079fd04dfab8e61eca10ee98ab5bac89dfa], > however it wasn't tagged with a jira ID. > I'm creating a new jira so that I can revert and re-apply this commit with > this jira ID. Easier to track fix versions this way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24161) [flakey test] locking.TestEntityLocks.testEntityLockTimeout
Huaxiang Sun created HBASE-24161:
Summary: [flakey test]
locking.TestEntityLocks.testEntityLockTimeout
Key: HBASE-24161
URL: https://issues.apache.org/jira/browse/HBASE-24161
Project: HBase
Issue Type: Test
Components: Client
Affects Versions: 3.0.0, 2.3.0, 2.4.0
Reporter: Huaxiang Sun
Assignee: Hua Xiang
>From 2.3 flakey board,
>[https://builds.apache.org/job/HBase-Flaky-Tests/job/branch-2.3/199/artifact/hbase-server/target/surefire-reports/org.apache.hadoop.hbase.client.locking.TestEntityLocks.txt]
{code:java}
---
Test set: org.apache.hadoop.hbase.client.locking.TestEntityLocks
---
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.917 s <<<
FAILURE! - in org.apache.hadoop.hbase.client.locking.TestEntityLocks
org.apache.hadoop.hbase.client.locking.TestEntityLocks.testEntityLockTimeout
Time elapsed: 2.022 s <<< FAILURE!
java.lang.AssertionError
at
org.apache.hadoop.hbase.client.locking.TestEntityLocks.testEntityLockTimeout(TestEntityLocks.java:178)
Mapping to the code, it complains
assertFalse(lock.getWorker().isAlive());
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24074) ConcurrentModificationException occurred in ReplicationSourceManager while refreshing the peer
[
https://issues.apache.org/jira/browse/HBASE-24074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24074.
---
Fix Version/s: 2.2.5
2.3.0
3.0.0
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to branch-2.2+. Let me know if you disagree [~zghao]
> ConcurrentModificationException occurred in ReplicationSourceManager while
> refreshing the peer
> --
>
> Key: HBASE-24074
> URL: https://issues.apache.org/jira/browse/HBASE-24074
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Reporter: Pankaj Kumar
>Assignee: Pankaj Kumar
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.5
>
>
> Peer update failed with ConcurrentModificationException,
> {noformat}
> 2020-03-28 11:36:49,770 | WARN |
> RpcServer.default.FPBQ.Fifo.handler=49,queue=4,port=hm_port | Refresh peer
> peer1 for UPDATE_CONFIG on rs_host,rs_port,1585228936395 failed |
> org.apache.hadoop.hbase.master.replication.RefreshPeerProcedure.complete(RefreshPeerProcedure.java:114)
> java.util.ConcurrentModificationException via
> szvphispra08478,21302,1585228936395:java.util.ConcurrentModificationException:
>
> at
> org.apache.hadoop.hbase.procedure2.RemoteProcedureException.fromProto(RemoteProcedureException.java:124)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.lambda$reportProcedureDone$4(MasterRpcServices.java:2576)
> at java.util.ArrayList.forEach(ArrayList.java:1257)
> at
> java.util.Collections$UnmodifiableCollection.forEach(Collections.java:1082)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.reportProcedureDone(MasterRpcServices.java:2571)
> at
> org.apache.hadoop.hbase.shaded.protobuf.generated.RegionServerStatusProtos$RegionServerStatusService$2.callBlockingMethod(RegionServerStatusProtos.java:15341)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318)
> Caused by: java.util.ConcurrentModificationException:
> at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
> at java.util.ArrayList$Itr.next(ArrayList.java:859)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSourceManager.refreshSources(ReplicationSourceManager.java:399)
> at
> org.apache.hadoop.hbase.replication.regionserver.PeerProcedureHandlerImpl.updatePeerConfig(PeerProcedureHandlerImpl.java:123)
> at
> org.apache.hadoop.hbase.replication.regionserver.RefreshPeerCallable.call(RefreshPeerCallable.java:68)
> at
> org.apache.hadoop.hbase.replication.regionserver.RefreshPeerCallable.call(RefreshPeerCallable.java:34)
> at
> org.apache.hadoop.hbase.regionserver.handler.RSProcedureHandler.process(RSProcedureHandler.java:47)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24162) Move CHANGES.txt to CHANGES.md. Add RELEASENOTES.md too on branch-2, branch-2.3, and master
Michael Stack created HBASE-24162: - Summary: Move CHANGES.txt to CHANGES.md. Add RELEASENOTES.md too on branch-2, branch-2.3, and master Key: HBASE-24162 URL: https://issues.apache.org/jira/browse/HBASE-24162 Project: HBase Issue Type: Bug Components: build Reporter: Michael Stack Way back on HBASE-18828 for release 2.0.0 we moved to use releasemaker from yetus for generating changes/releasenotes. At that time we moved to *.md files instead of *.txt for CHANGES. Let me make the change on branch-2.3, branch-2 and master, the remaining outposts for *.txt files. Doing it because it confused a coworker (why wouldn't it?). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24163) MOB compactor implementations should use format specifiers when calling String.format
Sean Busbey created HBASE-24163: --- Summary: MOB compactor implementations should use format specifiers when calling String.format Key: HBASE-24163 URL: https://issues.apache.org/jira/browse/HBASE-24163 Project: HBase Issue Type: Bug Components: Compaction, mob Affects Versions: 3.0.0 Reporter: Sean Busbey Assignee: Sean Busbey Fix For: 3.0.0 HBASE-23723 includes a few IOException message constructions that rely on String.format but use slf4j parameters instead of format specifiers. Discovered by nightly failing error-prone. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-24086) Disable output stream capability enforcement when running in standalone mode
[
https://issues.apache.org/jira/browse/HBASE-24086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-24086:
-
I am -1 on this change and intend to revert it and the follow-on docs change so
that we can first have a discussion here or on dev@.
I am concerned that this went in without an in depth reconsideration of the
issues that come with trying to run against LocalFileSystem discussed in
HBASE-20354 (where the docs you changed were added) or HBASE-19289 (where the
check failing on LocalFileSystem first came up) or HBASE-21735 (where this
first showing up for Hadoop 2 came up when it was backported to HBase 1).
Furthermore you didn't ping any of the folks involved in any of those
discussion.
The point of requiring this change is in the config name and emphasizing it is
_unsafe_. A WARN message in a log is too easy to miss. Folks should not be
running a production instance against a local filesystem unless they affirm
they know what they are doing by setting that configuration value.
> Disable output stream capability enforcement when running in standalone mode
>
>
> Key: HBASE-24086
> URL: https://issues.apache.org/jira/browse/HBASE-24086
> Project: HBase
> Issue Type: Task
> Components: master
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.5
>
>
> {noformat}
> $
> JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home
> mvn clean install -DskipTests
> $
> JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home
> ./bin/hbase master start
> {noformat}
> gives
> {noformat}
> 2020-03-30 17:12:43,857 ERROR
> [master/192.168.111.13:16000:becomeActiveMaster] master.HMaster: Failed to
> become active master
>
> java.io.IOException: cannot get log writer
>
>
> at
> org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:118)
>
>
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createAsyncWriter(AsyncFSWAL.java:704)
>
>
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:710)
>
>
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:128)
>
>
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:839)
>
>
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:549)
>
>
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:490)
>
>
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:156)
>
>
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:61)
>
>
> at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:297)
>
>
> at
> org.apache.hadoop.hbase.procedure2.store.region.RegionProcedureStore.createWAL(RegionProcedureStore.java:256)
>
>
> at
> org.apache.hadoop.hbase.procedure2.store.region.RegionProcedureStore.bootstrap(RegionProcedureStore.java:273)
>
>
> at
> org.apache.hadoop.hbase.procedure2.store.region.Re
