[jira] [Created] (HBASE-24222) remove FSUtils.checkAccess , replace with FileSystem.access
niuyulin created HBASE-24222: Summary: remove FSUtils.checkAccess , replace with FileSystem.access Key: HBASE-24222 URL: https://issues.apache.org/jira/browse/HBASE-24222 Project: HBase Issue Type: Improvement Reporter: niuyulin Assignee: niuyulin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24223) The -Phadoop-3.0 option does not work on branch-2 and branch-2.3 with JDK11
Duo Zhang created HBASE-24223: - Summary: The -Phadoop-3.0 option does not work on branch-2 and branch-2.3 with JDK11 Key: HBASE-24223 URL: https://issues.apache.org/jira/browse/HBASE-24223 Project: HBase Issue Type: Bug Components: hadoop3, pom Reporter: Duo Zhang Assignee: Duo Zhang Fix For: 2.3.0 Because we have an enforcer rule which requires the hadoop.profile property to be set to 3.0. I tried to use requireActiveProfile but it failed when building hbase-annotations as in the pom of the module we do not declare a hadoop-3.0 profile(since it does not depend on hadoop...). So we need to find another trick solution. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24198) Skip hadoop2 check for master branch
[ https://issues.apache.org/jira/browse/HBASE-24198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-24198. --- Resolution: Fixed Filed HBASE-24223. > Skip hadoop2 check for master branch > > > Key: HBASE-24198 > URL: https://issues.apache.org/jira/browse/HBASE-24198 > Project: HBase > Issue Type: Sub-task > Components: hadoop2, hadoop3, pom, scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > > Now we will run hadoop2 check on jdk8 and hadoop3 check on jdk11, since the > support of hadoop2 has been dropped, let's make jdk8 check also on hadoop3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-24175) [Flakey Tests] TestSecureExportSnapshot FileNotFoundException
[
https://issues.apache.org/jira/browse/HBASE-24175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack reopened HBASE-24175:
---
Found new tmp reference complaint. Reopen to apply handling.
> [Flakey Tests] TestSecureExportSnapshot FileNotFoundException
> -
>
> Key: HBASE-24175
> URL: https://issues.apache.org/jira/browse/HBASE-24175
> Project: HBase
> Issue Type: Sub-task
> Components: flakies
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.5
>
> Attachments:
> 0001-HBASE-24175-Flakey-Tests-TestSecureExportSnapshot-Fi.addendum.patch,
> 0001-HBASE-24175-Flakey-Tests-TestSecureExportSnapshot-Fi.addendum2.patch,
> 0001-HBASE-24175-Flakey-Tests-TestSecureExportSnapshot-Fi.patch
>
>
> Why we writing '/tmp' dir?
> {code}
> Error Message
> org.apache.hadoop.service.ServiceStateException:
> java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> Stacktrace
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException:
> org.apache.hadoop.service.ServiceStateException:
> java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> at
> org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.setUpBeforeClass(TestSecureExportSnapshot.java:56)
> Caused by: org.apache.hadoop.service.ServiceStateException:
> java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> at
> org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.setUpBeforeClass(TestSecureExportSnapshot.java:56)
> Caused by: java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> at
> org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.setUpBeforeClass(TestSecureExportSnapshot.java:56)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24175) [Flakey Tests] TestSecureExportSnapshot FileNotFoundException
[
https://issues.apache.org/jira/browse/HBASE-24175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24175.
---
Resolution: Fixed
Re-resolving after pushing attached addendum #3.
> [Flakey Tests] TestSecureExportSnapshot FileNotFoundException
> -
>
> Key: HBASE-24175
> URL: https://issues.apache.org/jira/browse/HBASE-24175
> Project: HBase
> Issue Type: Sub-task
> Components: flakies
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.5
>
> Attachments:
> 0001-HBASE-24175-Flakey-Tests-TestSecureExportSnapshot-Fi.addendum.patch,
> 0001-HBASE-24175-Flakey-Tests-TestSecureExportSnapshot-Fi.addendum2.patch,
> 0001-HBASE-24175-Flakey-Tests-TestSecureExportSnapshot-Fi.addendum3.patch,
> 0001-HBASE-24175-Flakey-Tests-TestSecureExportSnapshot-Fi.patch
>
>
> Why we writing '/tmp' dir?
> {code}
> Error Message
> org.apache.hadoop.service.ServiceStateException:
> java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> Stacktrace
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException:
> org.apache.hadoop.service.ServiceStateException:
> java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> at
> org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.setUpBeforeClass(TestSecureExportSnapshot.java:56)
> Caused by: org.apache.hadoop.service.ServiceStateException:
> java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> at
> org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.setUpBeforeClass(TestSecureExportSnapshot.java:56)
> Caused by: java.io.FileNotFoundException: File
> file:/tmp/hadoop-yarn-jenkins/node-attribute/nodeattribute.mirror.writing
> does not exist
> at
> org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot.setUpBeforeClass(TestSecureExportSnapshot.java:56)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24224) Update GC config examples in hbase-env.sh for G1GC
Nick Dimiduk created HBASE-24224:
Summary: Update GC config examples in hbase-env.sh for G1GC
Key: HBASE-24224
URL: https://issues.apache.org/jira/browse/HBASE-24224
Project: HBase
Issue Type: Sub-task
Components: scripts
Affects Versions: 3.0.0, 2.3.0
Reporter: Nick Dimiduk
Anywhere we changed the default collector to G1GC, we should also update
{{hbase-env.sh}} to include GC configuration examples appropriate for that
collector and JVM. This means, where we support both JDK8 and JDK11, we'll have
two sections of examples, one for CMS and the other for G1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24225) Backport HBASE-23833 to branch-2.2
Wei-Chiu Chuang created HBASE-24225: --- Summary: Backport HBASE-23833 to branch-2.2 Key: HBASE-24225 URL: https://issues.apache.org/jira/browse/HBASE-24225 Project: HBase Issue Type: Sub-task Reporter: Wei-Chiu Chuang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24011) HMaster does not restart when rsgroup is enabled and /hbase/WALs is moved
[
https://issues.apache.org/jira/browse/HBASE-24011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad resolved HBASE-24011.
-
Assignee: Mohammad Arshad
Resolution: Won't Fix
> HMaster does not restart when rsgroup is enabled and /hbase/WALs is moved
> -
>
> Key: HBASE-24011
> URL: https://issues.apache.org/jira/browse/HBASE-24011
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
>Affects Versions: 2.2.3
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
>
> HMaster does not restart when rsgroup is enabled and /hbase/WALs is moved
> HMaster restarts properly if rsgroup is not enabled even if /hbase/WALs is
> moved.
> Steps to reproduce:
> # start the cluster
> # create a table do some put, delete
> # kill all the region servers and master
> # move WALs directory for backup (-mv /hbase/WALs /hbase/WALs2)
> # start the cluster
> # Master start fails, initialization keep failing
> {code:java}
> 2020-03-18 11:42:55,369 ERROR
> [ActiveMasterInitializationMonitor-1584511075369] master.HMaster: Master
> failed to complete initialization after 90ms. Please consider submitting
> a bug report including a thread dump of this process.
> {code}
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24226) Address other hard references found in configuration
Michael Stack created HBASE-24226: - Summary: Address other hard references found in configuration Key: HBASE-24226 URL: https://issues.apache.org/jira/browse/HBASE-24226 Project: HBase Issue Type: Bug Reporter: Michael Stack HBASE-24175 started up cleaning hard /tmp references out of Configuration when tests run. I got most of them but then if its hadoop2 or hadoop3 or jenkins or local, the list seems to change. Here are more... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Penzes reopened HBASE-23896:
--
getRandomUUID is static in master branch but not in branch-2.2:
See:
[https://github.com/apache/hbase/blob/branch-2.2/hbase-common/src/test/java/org/apache/hadoop/hbase/HBaseCommonTestingUtility.java#L158]
[https://github.com/apache/hbase/blob/master/hbase-common/src/test/java/org/apache/hadoop/hbase/HBaseCommonTestingUtility.java#L156]
Please fix branch 2.2.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23829) Get `-PrunSmallTests` passing on JDK11
[
https://issues.apache.org/jira/browse/HBASE-23829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-23829.
--
Resolution: Fixed
> Get `-PrunSmallTests` passing on JDK11
> --
>
> Key: HBASE-23829
> URL: https://issues.apache.org/jira/browse/HBASE-23829
> Project: HBase
> Issue Type: Sub-task
> Components: test
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Start with the small tests, shaking out issues identified by the harness. So
> far it seems like {{-Dhadoop.profile=3.0}} and
> {{-Dhadoop-three.version=3.3.0-SNAPSHOT}} maybe be required.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-24227) [JDK11] shell fails to launch
Nick Dimiduk created HBASE-24227:
Summary: [JDK11] shell fails to launch
Key: HBASE-24227
URL: https://issues.apache.org/jira/browse/HBASE-24227
Project: HBase
Issue Type: Sub-task
Components: shell
Affects Versions: 3.0.0
Reporter: Nick Dimiduk
{noformat}
$ JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
./bin/hbase shell
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.hadoop.hbase.util.UnsafeAvailChecker
(file:/Users/ndimiduk/repos/apache/hbase/hbase-common/target/hbase-common-3.0.0-SNAPSHOT.jar)
to method java.nio.Bits.unaligned()
WARNING: Please consider reporting this to the maintainers of
org.apache.hadoop.hbase.util.UnsafeAvailChecker
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
HBase Shell
Use "help" to get list of supported commands.
Use "exit" to quit this interactive shell.
For Reference, please visit: http://hbase.apache.org/book.html#shell
Version 3.0.0-SNAPSHOT, rbcacc4ce939e60fd69891df6315a39aef852b567, Tue Apr 21
15:47:27 PDT 2020
Took 0. seconds
ArgumentError: wrong number of arguments (1 for 0)
` at uri:classloader:/jruby/kernel/jruby/process_manager.rb:32
` at uri:classloader:/jruby/kernel/jruby/process_manager.rb:54
initialize at
/Users/ndimiduk/repos/apache/hbase/hbase-shell/src/main/ruby/irb/hirb.rb:46
start at /Users/ndimiduk/repos/apache/hbase/bin/../bin/hirb.rb:207
at /Users/ndimiduk/repos/apache/hbase/bin/../bin/hirb.rb:219
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (HBASE-24169) Drop hadoop 2 support for hbase 3.x
[ https://issues.apache.org/jira/browse/HBASE-24169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-24169: --- > Drop hadoop 2 support for hbase 3.x > --- > > Key: HBASE-24169 > URL: https://issues.apache.org/jira/browse/HBASE-24169 > Project: HBase > Issue Type: Umbrella > Components: hadoop2, hadoop3, pom >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Blocker > Fix For: 3.0.0 > > > As discussed several times on mailing list, I think it is time to do this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24228) Merge the code in hbase-hadoop2-compat module to hbase-hadoop-compat
Duo Zhang created HBASE-24228: - Summary: Merge the code in hbase-hadoop2-compat module to hbase-hadoop-compat Key: HBASE-24228 URL: https://issues.apache.org/jira/browse/HBASE-24228 Project: HBase Issue Type: Sub-task Reporter: Duo Zhang As now we only depend on hadoop3 and the compatible issues are mostly resolved by reflection, no need to maintain a hadoop2-compat module any more. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24229) [Build] Pin rubocop version <= 0.81
Reid Chan created HBASE-24229: - Summary: [Build] Pin rubocop version <= 0.81 Key: HBASE-24229 URL: https://issues.apache.org/jira/browse/HBASE-24229 Project: HBase Issue Type: Improvement Reporter: Reid Chan rubocop 0.82 has been released, which drops Ruby 2.3 support. We are still using Ruby 2.3 in the Docker, and the docker build will fail (at least in branch-1). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24213) Backport the pre commit changes for HBASE-24169 to all branches
[ https://issues.apache.org/jira/browse/HBASE-24213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-24213. --- Fix Version/s: 2.2.5 1.4.14 1.7.0 1.3.7 2.3.0 3.0.0 Hadoop Flags: Reviewed Resolution: Fixed > Backport the pre commit changes for HBASE-24169 to all branches > --- > > Key: HBASE-24213 > URL: https://issues.apache.org/jira/browse/HBASE-24213 > Project: HBase > Issue Type: Bug > Components: scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.3.7, 1.7.0, 1.4.14, 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24218) Add hadoop 3.2.x in hadoop check
[ https://issues.apache.org/jira/browse/HBASE-24218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-24218. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to all active branches. Thanks all for reviewing. > Add hadoop 3.2.x in hadoop check > > > Key: HBASE-24218 > URL: https://issues.apache.org/jira/browse/HBASE-24218 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.3.7, 1.7.0, 1.4.14, 2.2.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24230) Support user-defined version timestamp when bulk load data
Xiao Zhang created HBASE-24230: -- Summary: Support user-defined version timestamp when bulk load data Key: HBASE-24230 URL: https://issues.apache.org/jira/browse/HBASE-24230 Project: HBase Issue Type: Improvement Components: hbase-connectors Affects Versions: 1.0.0 Reporter: Xiao Zhang Assignee: Xiao Zhang In hbase-connectors-1.0.0, loading data in bulk, only the current system time can be used as the KeyValue version timestamp. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24231) Add hadoop 3.2.x in our support matrix
Duo Zhang created HBASE-24231: - Summary: Add hadoop 3.2.x in our support matrix Key: HBASE-24231 URL: https://issues.apache.org/jira/browse/HBASE-24231 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Duo Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24232) hbase
Rhett.Wang created HBASE-24232: -- Summary: hbase Key: HBASE-24232 URL: https://issues.apache.org/jira/browse/HBASE-24232 Project: HBase Issue Type: Bug Reporter: Rhett.Wang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24232) hbase
[ https://issues.apache.org/jira/browse/HBASE-24232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan resolved HBASE-24232. --- Resolution: Invalid > hbase > - > > Key: HBASE-24232 > URL: https://issues.apache.org/jira/browse/HBASE-24232 > Project: HBase > Issue Type: Bug >Reporter: Rhett.Wang >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24229) [Build] Pin rubocop version <= 0.81
[ https://issues.apache.org/jira/browse/HBASE-24229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan resolved HBASE-24229. --- Hadoop Flags: Reviewed Assignee: Reid Chan Resolution: Fixed > [Build] Pin rubocop version <= 0.81 > --- > > Key: HBASE-24229 > URL: https://issues.apache.org/jira/browse/HBASE-24229 > Project: HBase > Issue Type: Improvement > Components: build >Affects Versions: 1.4.13 >Reporter: Reid Chan >Assignee: Reid Chan >Priority: Major > Fix For: 1.7.0, 1.4.14 > > > rubocop 0.82 has been released, which drops Ruby 2.3 support. > We are still using Ruby 2.3 in the Docker, and the docker build will fail (at > least in branch-1). > Similar to AVRO-2807 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24233) Client getting stuck infinitely while connecting to thrift2 server in Secure mode
Ashok shetty created HBASE-24233: Summary: Client getting stuck infinitely while connecting to thrift2 server in Secure mode Key: HBASE-24233 URL: https://issues.apache.org/jira/browse/HBASE-24233 Project: HBase Issue Type: Bug Components: Thrift Affects Versions: 2.2.3 Reporter: Ashok shetty Tried connecting thrift2 server to test PUT operation from a secure client to 1.3.x server . It works fine , But when same operation is performed in 2.2.3 server, client is getting stuck infinitely. it's unable to connect to server . Exception in thread "main" java.security.PrivilegedActionException: org.apache.thrift.transport.TTransportException: java.net.SocketTimeoutException: Read timed out at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.hbase.thrift2.GitDemoClient.main(GitDemoClient.java:80) Caused by: org.apache.thrift.transport.TTransportException: java.net.SocketTimeoutException: Read timed out at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:129) at org.apache.thrift.transport.TTransport.readAll(TTransport.java:86) at org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:178) at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:277) at org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:38) at org.apache.hadoop.hbase.thrift2.GitDemoClient.run(GitDemoClient.java:117) at org.apache.hadoop.hbase.thrift2.GitDemoClient$1.run(GitDemoClient.java:84) at org.apache.hadoop.hbase.thrift2.GitDemoClient$1.run(GitDemoClient.java:1) ... 3 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127) ... 10 more Getting above exception when timeout has been set at client side. *References* https://github.com/apache/hbase/blob/master/hbase-examples/src/main/java/org/apache/hadoop/hbase/thrift2/DemoClient.java https://hbase.apache.org/book.html#hbase.secure.configuration (section 60.4) Client-side Configuration for Secure operation- Thrift Gateway -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24139) Balancer should avoid leaving idle region servers
[
https://issues.apache.org/jira/browse/HBASE-24139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani resolved HBASE-24139.
--
Fix Version/s: 1.7.0
2.3.0
3.0.0
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to master, branch-2, 2.3 and branch-1. Thanks for the contribution
[~bea0113]
> Balancer should avoid leaving idle region servers
> -
>
> Key: HBASE-24139
> URL: https://issues.apache.org/jira/browse/HBASE-24139
> Project: HBase
> Issue Type: Improvement
> Components: Balancer, Operability
>Reporter: Sean Busbey
>Assignee: Beata Sudi
>Priority: Critical
> Labels: beginner
> Fix For: 3.0.0, 2.3.0, 1.7.0
>
>
> After HBASE-15529 the StochasticLoadBalancer makes the decision to run based
> on its internal cost functions rather than the simple region count skew of
> BaseLoadBalancer.
> Given the default weights for those cost functions, the default minimum cost
> to indicate a need to rebalance, and a regions per region server density of
> ~90 we are not very responsive to adding additional region servers for
> non-trivial cluster sizes:
> * For clusters ~10 nodes, the defaults think a single RS at 0 regions means
> we need to balance
> * For clusters >20 nodes, the defaults will not consider a single RS at 0
> regions to mean we need to balance. 2 RS at 0 will cause it to balance.
> * For clusters ~100 nodes, having 6 RS with no regions will still not meet
> the threshold to cause a balance.
> Note that this is the decision to look at balancer plans at all. The
> calculation is severely dominated by the region count skew (it has weight 500
> and all other weights are ~105), so barring a very significant change in all
> other cost functions this condition will persist indefinitely.
> Two possible approaches:
> * add a new cost function that's essentially "don't have RS with 0 regions"
> that an operator can tune
> * add a short circuit condition for the {{needsBalance}} method that checks
> for empty RS similar to the check we do for colocated region replicas
> For those currently hitting this an easy work around is to set
> {{hbase.master.balancer.stochastic.minCostNeedBalance}} to {{0.01}}. This
> will mean that a single RS having 0 regions will cause the balancer to run
> for clusters of up to ~90 region servers. It's essentially the same as the
> default slop of 0.01 used by the BaseLoadBalancer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24196) [Shell] Add rename rsgroup command in hbase shell
[ https://issues.apache.org/jira/browse/HBASE-24196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan resolved HBASE-24196. --- Hadoop Flags: Reviewed Resolution: Fixed > [Shell] Add rename rsgroup command in hbase shell > - > > Key: HBASE-24196 > URL: https://issues.apache.org/jira/browse/HBASE-24196 > Project: HBase > Issue Type: Improvement > Components: rsgroup, shell >Reporter: Reid Chan >Assignee: Reid Chan >Priority: Major > Fix For: 3.0.0, 2.3.0, 1.7.0, 2.2.5 > > > HBASE-24112 supports renaming rsgroup. So here we add shell command support. -- This message was sent by Atlassian Jira (v8.3.4#803005)
