[jira] [Created] (HBASE-26622) Update to error-prone 2.10
Mike Drob created HBASE-26622: - Summary: Update to error-prone 2.10 Key: HBASE-26622 URL: https://issues.apache.org/jira/browse/HBASE-26622 Project: HBase Issue Type: Task Reporter: Mike Drob -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (HBASE-26399) branch-2 modules dependencies are confused
Mike Drob created HBASE-26399:
-
Summary: branch-2 modules dependencies are confused
Key: HBASE-26399
URL: https://issues.apache.org/jira/browse/HBASE-26399
Project: HBase
Issue Type: Task
Components: build
Affects Versions: 2.5.0
Environment: branch-2
Java version: 11.0.12
Apache Maven 3.8.3
Reporter: Mike Drob
When trying to build branch-2, I get several dependency resolution issues.
Different issues based on what approach I try.
{{mvn -e -B --no-transfer-progress -Dhadoop.profile=3.0
-Dhadoop-three.version=3.0.0-cdh6.3.2 clean install -Dmaven.test.skip=true}}
will fail with:
{noformat}
231.4 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce
(hadoop-profile-min-maven-min-java-banned-xerces) on project
hbase-build-configuration: Execution
hadoop-profile-min-maven-min-java-banned-xerces of goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M3:enforce failed:
org.apache.maven.shared.dependency.graph.DependencyGraphBuilderException: Could
not resolve following dependencies:
[org.apache.hbase:hbase-annotations:jar:tests:2.5.0-SNAPSHOT (test)]: Could not
resolve dependencies for project
org.apache.hbase:hbase-build-configuration:pom:2.5.0-SNAPSHOT: Could not find
artifact org.apache.hbase:hbase-annotations:jar:tests:2.5.0-SNAPSHOT in
snapshots{noformat}
Note that I'm running this behind a corporate firewall, so if there is a
snapshot available upstream in apache snapshots repo, then I'm not able to
access it. I would have thought that it can use the locally built and installed
one instead, since build-configuration does correctly come after annotations.
If I change to {{-DskipTests}} then this target succeeds, but later {{mvn
site}} fails with
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site) on project
hbase: Error generating maven-javadoc-plugin:3.2.0:aggregate-no-fork report:
[ERROR] Exit code: 1 -
/home/jenkins-agent/hbase/hbase-testing-util/src/main/java/org/apache/hadoop/hbase/testing/TestingHBaseClusterOption.java:24:
error: cannot find symbol
[ERROR] import org.apache.hadoop.hbase.StartMiniClusterOption;
[ERROR] ^
[ERROR] symbol: class StartMiniClusterOption
[ERROR] location: package org.apache.hadoop.hbase {noformat}
Again, I'm missing testing packages, this time for javadocs.
I believe I was getting similar errors on main branch, although I don't have
logs for that anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-21306) website should have 1.4.x release docs
[ https://issues.apache.org/jira/browse/HBASE-21306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-21306. --- Assignee: (was: Andrew Kyle Purtell) Resolution: Duplicate The website has this, it was fixed at some point it the past. > website should have 1.4.x release docs > -- > > Key: HBASE-21306 > URL: https://issues.apache.org/jira/browse/HBASE-21306 > Project: HBase > Issue Type: Task > Components: community, documentation, website >Reporter: Mike Drob >Priority: Major > > Since 1.4 is the stable line now, we should include the API docs on the > website instead of (in addition to?) the 1.2 docs we have now. > See also HBASE-21114 and HBASE-21119 for the process. > FYI: [~busbey], [~apurtell] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-19168) Considering Java 10
[ https://issues.apache.org/jira/browse/HBASE-19168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-19168. --- Fix Version/s: (was: 3.0.0) Resolution: Won't Fix > Considering Java 10 > --- > > Key: HBASE-19168 > URL: https://issues.apache.org/jira/browse/HBASE-19168 > Project: HBase > Issue Type: New Feature > Components: dependencies, java >Reporter: Mike Drob >Priority: Critical > > JDK 10 Early Access builds are now available at: - jdk.java.net/10/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-17814) Move hbasecon site to hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-17814. --- Assignee: Michael Stack Resolution: Fixed This looks like it was done. > Move hbasecon site to hbase.apache.org > -- > > Key: HBASE-17814 > URL: https://issues.apache.org/jira/browse/HBASE-17814 > Project: HBase > Issue Type: Bug >Reporter: Michael Stack >Assignee: Michael Stack >Priority: Major > > Moving our hbasecon pages from a site that Cloudera sponsored. > We want to be able to point hbasecon our new hosts for this year (and keep > around links to the old content which while it is all up on youtube and > slideshare, the hbasecon archive pages have the pointers). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-21374) Backport HBASE-21342 to branch-1
Mike Drob created HBASE-21374: - Summary: Backport HBASE-21342 to branch-1 Key: HBASE-21374 URL: https://issues.apache.org/jira/browse/HBASE-21374 Project: HBase Issue Type: Task Reporter: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21306) website should have 1.4.x release docs
Mike Drob created HBASE-21306: - Summary: website should have 1.4.x release docs Key: HBASE-21306 URL: https://issues.apache.org/jira/browse/HBASE-21306 Project: HBase Issue Type: Task Components: community, documentation, website Affects Versions: 1.4.7 Reporter: Mike Drob Since 1.4 is the stable line now, we should include the API docs on the website instead of (in addition to?) the 1.2 docs we have now. See also HBASE-21114 and HBASE-21119 for the process. FYI: [~busbey], [~apurtell] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21305) TestHRegionInfo failing because descriptive strings have different times
Mike Drob created HBASE-21305: - Summary: TestHRegionInfo failing because descriptive strings have different times Key: HBASE-21305 URL: https://issues.apache.org/jira/browse/HBASE-21305 Project: HBase Issue Type: Task Components: test Reporter: Mike Drob Assignee: Mike Drob We see TestHRegionInfo.testRegionDetailsForDisplay failing because the strings now show timestamps as created at differing points in the past. Can use EnvironmentEdge to fix this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21287) JVMClusterUtil Master initialization wait time not configurable
Mike Drob created HBASE-21287: - Summary: JVMClusterUtil Master initialization wait time not configurable Key: HBASE-21287 URL: https://issues.apache.org/jira/browse/HBASE-21287 Project: HBase Issue Type: Task Components: test Reporter: Mike Drob Assignee: Mike Drob We can configure how long the local cluster threads will wait for master to come up and become active, but not how long we allow initialization to take. Being able to tune this would improve my test loop on some experiment I am running. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21273) Move classes out of org.apache.spark namespace
Mike Drob created HBASE-21273: - Summary: Move classes out of org.apache.spark namespace Key: HBASE-21273 URL: https://issues.apache.org/jira/browse/HBASE-21273 Project: HBase Issue Type: Task Components: spark Affects Versions: 3.0.0 Reporter: Mike Drob Assignee: Mike Drob Fix For: 3.0.0 We currently have classes in the org.apache.spark space, I expect the Spark PMC would be upset with us if we started releasing those. Let's see if we can move them out. There's an ancient (2016) comment saying we need them there for access restriction reasons, if that's the case then we'll have to work through that issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-14707) NPE spew getting metrics via jmx
[
https://issues.apache.org/jira/browse/HBASE-14707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-14707.
---
Resolution: Cannot Reproduce
Not seen in a while and not enough info to reproduce. The JVM used for the
original report seems to have stack trace optimization turned on, where it
discards the rest of the NPE after printing it the first few times. If this
comes up again, then we'll try to address it.
> NPE spew getting metrics via jmx
>
>
> Key: HBASE-14707
> URL: https://issues.apache.org/jira/browse/HBASE-14707
> Project: HBase
> Issue Type: Bug
> Components: metrics
>Reporter: stack
>Priority: Major
>
> See this in branch-1 tip:
> {code}
> 2015-10-27 08:01:08,954 INFO [main-EventThread]
> replication.ReplicationTrackerZKImpl:
> /hbase/rs/e1101.halxg.cloudera.com,16020,1445958006576 znode expired,
> triggering replicatorRemoved event
> 2015-10-27 08:01:20,645 ERROR [685943200@qtp-893835279-134] util.JSONBean:
> getting attribute Value of
> "org.apache.hadoop.hbase.client":type="MetricsConnection",scope="hconnection-0x33abd9d3",name="executorPoolActiveThreads"
> threw an exception
> javax.management.RuntimeMBeanException: java.lang.NullPointerException
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:839)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:852)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:651)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
> at
> org.apache.hadoop.hbase.util.JSONBean.writeAttribute(JSONBean.java:235)
> at org.apache.hadoop.hbase.util.JSONBean.write(JSONBean.java:209)
> at org.apache.hadoop.hbase.util.JSONBean.access$000(JSONBean.java:53)
> at org.apache.hadoop.hbase.util.JSONBean$1.write(JSONBean.java:96)
> at
> org.apache.hadoop.hbase.http.jmx.JMXJsonServlet.doGet(JMXJsonServlet.java:202)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
> at
> org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:113)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1354)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
>
[jira] [Resolved] (HBASE-14950) Create table with AC fails when quota is enabled
[
https://issues.apache.org/jira/browse/HBASE-14950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-14950.
---
Resolution: Cannot Reproduce
> Create table with AC fails when quota is enabled
>
>
> Key: HBASE-14950
> URL: https://issues.apache.org/jira/browse/HBASE-14950
> Project: HBase
> Issue Type: Bug
> Components: proc-v2
>Affects Versions: 1.1.2
>Reporter: Ashish Singhi
>Priority: Critical
>
> Scenario:
> 1. Set hbase.quota.enabled to true
> 2. As per the [ACL matrix |
> http://hbase.apache.org/book.html#appendix_acl_matrix] for create table,
> grant '@group1', 'C', '@ns1'
> 3. From a user of group1, create 't1', 'd' -- *Failed*
> {noformat}
> ERROR: java.io.IOException: Namespace Descriptor found null for ns1 This is
> unexpected.
> at
> org.apache.hadoop.hbase.namespace.NamespaceStateManager.checkAndUpdateNamespaceTableCount(NamespaceStateManager.java:170)
> at
> org.apache.hadoop.hbase.namespace.NamespaceAuditor.checkQuotaToCreateTable(NamespaceAuditor.java:76)
> at
> org.apache.hadoop.hbase.quotas.MasterQuotaManager.checkNamespaceTableAndRegionQuota(MasterQuotaManager.java:312)
> at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1445)
> at
> org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:428)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:49404)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2136)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:107)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:133)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> When quota is enabled, then as part of createTable we internally also call
> getNamespaceDescriptor which needs 'A' privilege.
> So when quota is enabled we need both C and A permission to create a table.
> ACL Matrix needs to be updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-15020) Remove DistributedLogReplay (a.k.a DLR)
[ https://issues.apache.org/jira/browse/HBASE-15020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15020. --- Resolution: Duplicate Fix Version/s: 2.0.0 > Remove DistributedLogReplay (a.k.a DLR) > --- > > Key: HBASE-15020 > URL: https://issues.apache.org/jira/browse/HBASE-15020 > Project: HBase > Issue Type: Bug >Reporter: Elliott Clark >Priority: Major > Fix For: 2.0.0 > > > It's time has come. The tests are being disabled no one trusts the code not > to lose large chunks of data. We shouldn't have code reviewers worry about it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21168) BloomFilterUtil uses hardcoded randomness
Mike Drob created HBASE-21168: - Summary: BloomFilterUtil uses hardcoded randomness Key: HBASE-21168 URL: https://issues.apache.org/jira/browse/HBASE-21168 Project: HBase Issue Type: Task Affects Versions: 2.0.0 Reporter: Mike Drob Assignee: Mike Drob This was flagged by a Fortify scan and while it doesn't appear to be a real issue, it's pretty easy to take care of anyway. The hard coded rand can be moved to the test class that actually needs it to make the static analysis happy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21110) Issues with Unsafe and JDK 11
Mike Drob created HBASE-21110:
-
Summary: Issues with Unsafe and JDK 11
Key: HBASE-21110
URL: https://issues.apache.org/jira/browse/HBASE-21110
Project: HBase
Issue Type: Task
Reporter: Mike Drob
Using Java 11 RC 1, I get the following warning, probably need to add the
suggested flag to our scripts?
{noformat}
mdrob@mdrob-MBP:~/IdeaProjects/hbase$ java -version
java version "11" 2018-09-25
Java(TM) SE Runtime Environment 18.9 (build 11+28)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
mdrob@mdrob-MBP:~/IdeaProjects/hbase$ bin/start-hbase.sh
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.hadoop.hbase.util.UnsafeAvailChecker
(file:/Users/mdrob/IdeaProjects/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
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-21027) Inconsistent synchronization in CacheableDeserializerIdManager
Mike Drob created HBASE-21027: - Summary: Inconsistent synchronization in CacheableDeserializerIdManager Key: HBASE-21027 URL: https://issues.apache.org/jira/browse/HBASE-21027 Project: HBase Issue Type: Task Affects Versions: 3.0.0 Reporter: Mike Drob Assignee: Mike Drob Fix For: 3.0.0 There is some inconsistent synchronization going on in CDIM, we should switch it to using ConcurrentHashMap and simplify our code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20942) Make RpcServer trace log length configurable
Mike Drob created HBASE-20942: - Summary: Make RpcServer trace log length configurable Key: HBASE-20942 URL: https://issues.apache.org/jira/browse/HBASE-20942 Project: HBase Issue Type: Task Reporter: Esteban Gutierrez We truncate RpcServer output to 1000 characters for trace logging. Would be better if that value was configurable. Esteban mentioned this to me earlier, so I'm crediting him as the reporter. cc: [~elserj] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20905) branch-1 docker build fails
Mike Drob created HBASE-20905:
-
Summary: branch-1 docker build fails
Key: HBASE-20905
URL: https://issues.apache.org/jira/browse/HBASE-20905
Project: HBase
Issue Type: Task
Components: build
Affects Versions: 1.5.0
Reporter: Jingyun Tian
Assignee: Mike Drob
Fix For: 1.5.0
Docker build for precommit fails:
{quote}
19:08:29 Cleaning up...19:08:29 Command python setup.py egg_info failed with
error code 1 in /tmp/pip_build_root/pylint*19:08:29* Storing debug log for
failure in /root/.pip/pip.log*19:08:29* The command '/bin/sh -c pip install
pylint' returned a non-zero code: 1*19:08:29* 19:08:29 Total Elapsed time: 0m
3s*19:08:29* 19:08:29 ERROR: Docker failed to build image.
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20894) Move BucketCache from java serialization to protobuf
Mike Drob created HBASE-20894: - Summary: Move BucketCache from java serialization to protobuf Key: HBASE-20894 URL: https://issues.apache.org/jira/browse/HBASE-20894 Project: HBase Issue Type: Task Components: BucketCache Affects Versions: 2.0.0 Reporter: Mike Drob Fix For: 3.0.0 We should use a better serialization format instead of Java Serialization for the BucketCache entry persistence. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20884) Replace usage of our Base64 implementation with java.util.Base64
Mike Drob created HBASE-20884: - Summary: Replace usage of our Base64 implementation with java.util.Base64 Key: HBASE-20884 URL: https://issues.apache.org/jira/browse/HBASE-20884 Project: HBase Issue Type: Task Reporter: Mike Drob Fix For: 3.0.0 We have a public domain implementation of Base64 that is copied into our code base and infrequently receives updates. We should replace usage of that with the new Java 8 java.util.Base64 where possible. For the migration, I propose a phased approach. * Deprecate on 1.x and 2.x to signal to users that this is going away. * Replace usages on branch-2 and master with j.u.Base64 * Delete our implementation of Base64 on master. Does this seem in line with our API compatibility requirements? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-20833) Modify pre-upgrade coprocessor validator to support table level coprocessors
[ https://issues.apache.org/jira/browse/HBASE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-20833. --- Resolution: Fixed > Modify pre-upgrade coprocessor validator to support table level coprocessors > > > Key: HBASE-20833 > URL: https://issues.apache.org/jira/browse/HBASE-20833 > Project: HBase > Issue Type: New Feature >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Major > Fix For: 3.0.0, 2.0.2, 2.2.0, 2.1.1 > > Attachments: HBASE-20833.master.001.patch, > HBASE-20833.master.003.patch, HBASE-20833.master.004.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (HBASE-20833) Modify pre-upgrade coprocessor validator to support table level coprocessors
[ https://issues.apache.org/jira/browse/HBASE-20833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reopened HBASE-20833: --- > Modify pre-upgrade coprocessor validator to support table level coprocessors > > > Key: HBASE-20833 > URL: https://issues.apache.org/jira/browse/HBASE-20833 > Project: HBase > Issue Type: New Feature >Reporter: Balazs Meszaros >Assignee: Balazs Meszaros >Priority: Major > Fix For: 3.0.0, 2.2.0 > > Attachments: HBASE-20833.master.001.patch, > HBASE-20833.master.003.patch, HBASE-20833.master.004.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20862) Address 2.1.0 Compatibility Report Issues
Mike Drob created HBASE-20862: - Summary: Address 2.1.0 Compatibility Report Issues Key: HBASE-20862 URL: https://issues.apache.org/jira/browse/HBASE-20862 Project: HBase Issue Type: Task Components: compatibility Affects Versions: 2.1.0 Reporter: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20835) Document how to get replication reporting
Mike Drob created HBASE-20835: - Summary: Document how to get replication reporting Key: HBASE-20835 URL: https://issues.apache.org/jira/browse/HBASE-20835 Project: HBase Issue Type: Task Components: Replication Affects Versions: 2.1.0 Reporter: Mike Drob Assignee: Duo Zhang Fix For: 2.1.0 Based on my questions at the tail end of HBASE-19543 bq. We have some tooling that checks on replication queues and reads the znode as the source of truth. When replication is disabled, it's expected that the node was still there, but just empty. Is there a better way to get this same information? I understand that with table based replication it doesn't make sense to check ZK for status. However, losing the ability to inspect the data and get information is a tough hit for operators. Do we have APIs that expose the same sort of metrics? bq. how many peers/queues, queue size, position in the queue, and age of last op Assigning to you for now, Duo, since you were both primary implementor and RM for 2.1.0 and I'm not sure who else would know the answers. If the docs already exist, then nothing to do but we should include them in the RN. Maybe this will need additional code, but I hope it's already there and is something we can write a workaround for. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20814) fix error prone assertion failure ignored warnings
Mike Drob created HBASE-20814: - Summary: fix error prone assertion failure ignored warnings Key: HBASE-20814 URL: https://issues.apache.org/jira/browse/HBASE-20814 Project: HBase Issue Type: Sub-task Components: build, test Reporter: Mike Drob Assignee: Mike Drob when we have assertion failures ignored, that likely means we're missing a test case, let's make sure our tests are actually running and covering what we think they are. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-20762) precommit should archive generated LICENSE file
[
https://issues.apache.org/jira/browse/HBASE-20762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-20762.
---
Resolution: Not A Problem
> precommit should archive generated LICENSE file
> ---
>
> Key: HBASE-20762
> URL: https://issues.apache.org/jira/browse/HBASE-20762
> Project: HBase
> Issue Type: Bug
> Components: build, community
>Reporter: Mike Drob
>Priority: Major
>
> When a precommit run fails due to license issues, we get pointed to a file in
> our maven logs:
> {noformat}
> /testptch/hbase/hbase-assembly/target/maven-shared-archive-resources/META-INF/LICENSE
> {noformat}
> But we don't have that file saved, so we don't know what the actual failure
> was. So we should save that in our build artifacts. Or maybe we can print a
> snippet from that file directly into the maven log. Both would be acceptable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20764) build broken when latest commit is gpg signed
Mike Drob created HBASE-20764:
-
Summary: build broken when latest commit is gpg signed
Key: HBASE-20764
URL: https://issues.apache.org/jira/browse/HBASE-20764
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 3.0.0
Reporter: Mike Drob
Assignee: Mike Drob
Fix For: 3.0.0
I broke the build by digitally signing a commit:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile (default-compile)
on project hbase-common: Compilation failure: Compilation failure:
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[11,41]
unclosed string literal
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[12,4]
expected
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[12,30]
';' expected
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[12,35]
malformed floating point literal
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[13,4]
';' expected
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[13,20]
';' expected
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[13,25]
expected
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[13,76]
illegal start of type
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[13,85]
';' expected
[ERROR]
/Users/mdrob/IdeaProjects/hbase/hbase-common/target/generated-sources/java/org/apache/hadoop/hbase/Version.java:[14,41]
unclosed string literal
{noformat}
Which complains because:
{code}
public static final String revision = "gpg: Signature made Wed Jun 20
09:42:38 2018 PDT
gpg:using RSA key 86EDB9C33B8517228E88A8F93E48C0C6EF362B9E
gpg: Good signature from "Mike Drob (CODE SIGNING KEY) "
[ultimate]
d1cad1a25432ffcd75cd654e9bf68233ca7e1957";
{code}
And this comes from {{src/saveVersion.sh}} where it does:
{noformat}
revision=`git log -1 --pretty=format:"%H"`
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20762) precommit should archive generated LICENSE file
Mike Drob created HBASE-20762:
-
Summary: precommit should archive generated LICENSE file
Key: HBASE-20762
URL: https://issues.apache.org/jira/browse/HBASE-20762
Project: HBase
Issue Type: Bug
Components: build, community
Reporter: Mike Drob
When a precommit run fails due to license issues, we get pointed to a file in
our maven logs:
{noformat}
/testptch/hbase/hbase-assembly/target/maven-shared-archive-resources/META-INF/LICENSE
{noformat}
But we don't have that file saved, so we don't know what the actual failure
was. So we should save that in our build artifacts. Or maybe we can print a
snippet from that file directly into the maven log. Both would be acceptable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20736) Fix smattering of error-prone warnings
Mike Drob created HBASE-20736: - Summary: Fix smattering of error-prone warnings Key: HBASE-20736 URL: https://issues.apache.org/jira/browse/HBASE-20736 Project: HBase Issue Type: Bug Reporter: Mike Drob Assignee: Mike Drob I wanted some coding on cruise control for a few hours tonight, so I deiced to fix error-prone warnings. I only fixed ones that were straight-forward, easy to do, and could defensibly have value in the fix. I skipped a lot, and won't claim to have any particular reason. Got as far as hbase-server in the output before deciding to move on with my life (didn't cover the tests at all). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20707) Move MissingSwitchDefault check from checkstyle to error-prone
Mike Drob created HBASE-20707: - Summary: Move MissingSwitchDefault check from checkstyle to error-prone Key: HBASE-20707 URL: https://issues.apache.org/jira/browse/HBASE-20707 Project: HBase Issue Type: Bug Components: build Reporter: Mike Drob Both checkstyle and error-prone can alert when a switch statement is missing a default. However, because checkstyle does it via static analysis and error-prone does it during compilation, e-p can detect when all cases of an enum have been covered, and will _not_ warn about the needed default case. In fact, checkstyle explicitly mentions in their docs that even if you cover all enum cases now, you should still have a default label because the enum could change in the future. Which seems silly to me, because your analysis tools should still be running in the future and would catch it then. Se we should migrate the check from checkstyle to a slightly smarter error-prone check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20674) clean up short circuit read logic and docs
Mike Drob created HBASE-20674: - Summary: clean up short circuit read logic and docs Key: HBASE-20674 URL: https://issues.apache.org/jira/browse/HBASE-20674 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 2.0.0 Reporter: Mike Drob Assignee: Mike Drob Mailing list discussion at https://lists.apache.org/thread.html/f6f73df0ceae29f762f9b9088e3ffd0bf8f109d3dd692df100bf4fd6@%3Cdev.hbase.apache.org%3E There are several inconsistencies between how our docs claim we do things and how we actually do things. There are two docs sections that attempt to address how SCR should work. dfs.client.read.shortcircuit.skip.checksum is advised to set to true, but our code in separate places ignores it and then later sets it to true anyway. CommonFSUtils and FSUtils duplicate code related to SCR setup. There is a workaround in HFileSystem for a bug that's been fixed in all versions of hadoop that we support. (HADOOP-9307) We suggest setting dfs.client.read.shortcircuit.buffer.size to a value that is very close to what we'd set it to anyway, without clearly explaining why this is important. There are other properties that we claim are important, but we don't offer any suggestions or explanations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20663) duplicate anchor id in hbase book
Mike Drob created HBASE-20663:
-
Summary: duplicate anchor id in hbase book
Key: HBASE-20663
URL: https://issues.apache.org/jira/browse/HBASE-20663
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Mike Drob
"upgrade2.0.coprocessors" section title is reused in upgrading.adoc resulting
in an unlinkable section.
Also the section that is
{noformat}
This would be a good place to link to a coprocessor migration guide
{noformat}
should actually link to the guide (which is currently hidden behind the second
instance of the section title).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (HBASE-20646) TestWALProcedureStoreOnHDFS failing on branch-1
[
https://issues.apache.org/jira/browse/HBASE-20646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob reopened HBASE-20646:
---
This breaks error-prone compilation in the nightly build.
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:testCompile
(default-testCompile) on project hbase-server: Compilation failure
[ERROR]
/testptch/hbase/hbase-server/src/test/java/org/apache/hadoop/hbase/master/procedure/TestWALProcedureStoreOnHDFS.java:[109,15]
[JUnit4TearDownNotRun] tearDown() method will not be run; Please add an @After
annotation
[ERROR] (see http://errorprone.info/bugpattern/JUnit4TearDownNotRun)
[ERROR] Did you mean '@After'?
{noformat}
Can you add a suppression for it?
> TestWALProcedureStoreOnHDFS failing on branch-1
> ---
>
> Key: HBASE-20646
> URL: https://issues.apache.org/jira/browse/HBASE-20646
> Project: HBase
> Issue Type: Test
>Affects Versions: 1.4.4
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Trivial
> Fix For: 1.5.0, 1.4.5
>
> Attachments: HBASE-20646-branch-1.patch
>
>
> TestWALProcedureStoreOnHDFS fails sometimes on branch-1 depending on junit
> particulars. An @After decoration was improperly added. Remove to fix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-13862) TestRegionRebalancing is flaky avain
[
https://issues.apache.org/jira/browse/HBASE-13862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-13862.
---
Resolution: Cannot Reproduce
Not on flaky dashboard, cleaning up old issues.
> TestRegionRebalancing is flaky avain
>
>
> Key: HBASE-13862
> URL: https://issues.apache.org/jira/browse/HBASE-13862
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 2.0.0
>Reporter: Mikhail Antonov
>Assignee: Sergey Soldatov
>Priority: Major
>
> I can reproduce it by running mvn test -Dtest=TestRegionRebalancing on fresh
> master about 1 out of 3-4 runs.
> {code}
> unning org.apache.hadoop.hbase.TestRegionRebalancing
> 2015-06-08 12:00:52.125 java[45610:5873722] Unable to load realm info from
> SCDynamicStore
> Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 26.743 sec
> <<< FAILURE! - in org.apache.hadoop.hbase.TestRegionRebalancing
> testRebalanceOnRegionServerNumberChange[0](org.apache.hadoop.hbase.TestRegionRebalancing)
> Time elapsed: 15.599 sec <<< FAILURE!
> java.lang.AssertionError: null
> at
> org.apache.hadoop.hbase.TestRegionRebalancing.testRebalanceOnRegionServerNumberChange(TestRegionRebalancing.java:144)
> testRebalanceOnRegionServerNumberChange[1](org.apache.hadoop.hbase.TestRegionRebalancing)
> Time elapsed: 10.671 sec <<< FAILURE!
> java.lang.AssertionError: null
> at
> org.apache.hadoop.hbase.TestRegionRebalancing.testRebalanceOnRegionServerNumberChange(TestRegionRebalancing.java:144)
> Results :
> Failed tests:
> TestRegionRebalancing.testRebalanceOnRegionServerNumberChange:144 null
> TestRegionRebalancing.testRebalanceOnRegionServerNumberChange:144 null
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-14242) TestAccessController#testMergeRegions is flaky in branch-1.0
[
https://issues.apache.org/jira/browse/HBASE-14242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-14242.
---
Resolution: Cannot Reproduce
Not on flaky dashboard, cleaning up old issues.
> TestAccessController#testMergeRegions is flaky in branch-1.0
>
>
> Key: HBASE-14242
> URL: https://issues.apache.org/jira/browse/HBASE-14242
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.0.2
>Reporter: Andrew Purtell
>Priority: Minor
> Fix For: 1.0.4
>
>
> Flaked tests:
> org.apache.hadoop.hbase.security.access.TestAccessController.testMergeRegions(org.apache.hadoop.hbase.security.access.TestAccessController)
> Run 1:
> TestAccessController.testMergeRegions:687->SecureTestUtil.verifyAllowed:176->SecureTestUtil.verifyAllowed:168
> Expected action to pass for user 'owner' but was denied
> Run 2: PASS
> {noformat}
> java.lang.AssertionError: Expected action to pass for user 'owner' but was
> denied
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.hadoop.hbase.security.access.SecureTestUtil.verifyAllowed(SecureTestUtil.java:168)
> at
> org.apache.hadoop.hbase.security.access.SecureTestUtil.verifyAllowed(SecureTestUtil.java:176)
> at
> org.apache.hadoop.hbase.security.access.TestAccessController.testMergeRegions(TestAccessController.java:687)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-13405) TestHBaseFsck is flaky
[
https://issues.apache.org/jira/browse/HBASE-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-13405.
---
Resolution: Cannot Reproduce
Not on flaky dashboard, cleaning up old issues.
> TestHBaseFsck is flaky
> --
>
> Key: HBASE-13405
> URL: https://issues.apache.org/jira/browse/HBASE-13405
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 2.0.0
>Reporter: Mikhail Antonov
>Priority: Major
>
> Once in a while I'm seeing the following, running #testContainedRegionOverlap
> test in IDE after clean install (mac osx, hbase master):
> {code}
> regionserver.HRegionServer(1863): Post open deploy tasks for
> tableContainedRegionOverlap,A,1428099123733.03a139b02119e99ef08149addd9a7996.
> 2015-04-03 15:12:11,695 INFO
> [PostOpenDeployTasks:03a139b02119e99ef08149addd9a7996]
> regionserver.HRegionServer(1956): Failed to report region transition, will
> retry
> java.io.InterruptedIOException: Origin: InterruptedException
> at
> org.apache.hadoop.hbase.util.ExceptionUtil.asInterrupt(ExceptionUtil.java:65)
> at
> org.apache.hadoop.hbase.protobuf.ProtobufUtil.getRemoteException(ProtobufUtil.java:313)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.reportRegionStateTransition(HRegionServer.java:1955)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.postOpenDeployTasks(HRegionServer.java:1882)
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler$PostOpenDeployTasksThread.run(OpenRegionHandler.java:241)
> Caused by: java.lang.InterruptedException: callId: 158 methodName:
> ReportRegionStateTransition param {TODO: class
> org.apache.hadoop.hbase.protobuf.generated.RegionServerStatusProtos$ReportRegionStateTransitionRequest}
> at
> io.netty.util.concurrent.DefaultPromise.await0(DefaultPromise.java:333)
> at
> io.netty.util.concurrent.DefaultPromise.await(DefaultPromise.java:266)
> at io.netty.util.concurrent.AbstractFuture.get(AbstractFuture.java:42)
> at
> org.apache.hadoop.hbase.ipc.AsyncRpcClient.call(AsyncRpcClient.java:226)
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient.callBlockingMethod(AbstractRpcClient.java:213)
> at
> org.apache.hadoop.hbase.ipc.AbstractRpcClient$BlockingRpcChannelImplementation.callBlockingMethod(AbstractRpcClient.java:287)
> at
> org.apache.hadoop.hbase.protobuf.generated.RegionServerStatusProtos$RegionServerStatusService$BlockingStub.reportRegionStateTransition(RegionServerStatusProtos.java:9030)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.reportRegionStateTransition(HRegionServer.java:1946)
> ... 2 more
> 2015-04-03 15:12:11,696 INFO
> [B.defaultRpcServer.handler=1,queue=0,port=51217]
> master.MasterRpcServices(237): Client=mantonov//10.1.4.219 set
> balanceSwitch=false
> 2015-04-03 15:12:11,696 DEBUG [main-EventThread]
> zookeeper.ZooKeeperWatcher(388): maste
> {code}
> and then:
> {code}
> 015-04-03 15:12:11,796 INFO [Thread-3019] client.HBaseAdmin$10(981): Started
> disable of tableContainedRegionOverlap
> 2015-04-03 15:12:21,641 INFO
> [B.defaultRpcServer.handler=1,queue=0,port=51217] master.HMaster(1645):
> Client=mantonov//10.1.4.219 disable tableContainedRegionOverlap
> java.lang.AssertionError:
> Expected :[]
> Actual :[NOT_DEPLOYED, HOLE_IN_REGION_CHAIN]
>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.hadoop.hbase.util.hbck.HbckTestingUtil.assertNoErrors(HbckTestingUtil.java:92)
> at
> org.apache.hadoop.hbase.util.TestHBaseFsck.testContainedRegionOverlap(TestHBaseFsck.java:941)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-15012) Flakies: Umbrella issue to hang current set of flakies from
[ https://issues.apache.org/jira/browse/HBASE-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15012. --- Resolution: Done All subtasks resolved, cleaning up old issues. > Flakies: Umbrella issue to hang current set of flakies from > --- > > Key: HBASE-15012 > URL: https://issues.apache.org/jira/browse/HBASE-15012 > Project: HBase > Issue Type: Umbrella >Reporter: stack >Priority: Major > > Flakies are tests that have failed a few times in the last set of test runs. > Hang any flaky issues off here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-14814) HDFS UI port clashes cause test fails
[ https://issues.apache.org/jira/browse/HBASE-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-14814. --- Resolution: Cannot Reproduce Agree w/ you, Peter. Cleaning up. > HDFS UI port clashes cause test fails > - > > Key: HBASE-14814 > URL: https://issues.apache.org/jira/browse/HBASE-14814 > Project: HBase > Issue Type: Sub-task > Components: flakey, test >Reporter: stack >Assignee: stack >Priority: Major > > In test runs, HDFS UI can clash when concurrent test runs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-14335) TestAssignmentManagerOnCluster#testSSHWhenDisablingTableRegionsInOpeningOrPendingOpenState occasionally timing out during cleanup
[
https://issues.apache.org/jira/browse/HBASE-14335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-14335.
---
Resolution: Cannot Reproduce
Old issue, cleaning up, this was fixed somewhere along the way. Please file new
issue against currently supported release lines if still a problem.
> TestAssignmentManagerOnCluster#testSSHWhenDisablingTableRegionsInOpeningOrPendingOpenState
> occasionally timing out during cleanup
> -
>
> Key: HBASE-14335
> URL: https://issues.apache.org/jira/browse/HBASE-14335
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.98.14
>Reporter: Andrew Purtell
>Priority: Major
>
> TestAssignmentManagerOnCluster#testSSHWhenDisablingTableRegionsInOpeningOrPendingOpenState
> is occasionally timing out when cleaning up after a test. Depends on
> environment. Given the right timing we get a timeout. One one test host,
> fails with 7u79. On another, passes with 7u79, fails with 8u45.
> {noformat}
> Running org.apache.hadoop.hbase.master.TestAssignmentManagerOnCluster
> Tests run: 17, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 85.924 sec
> <<<
> FAILURE! - in org.apache.hadoop.hbase.master.TestAssignmentManagerOnCluster
> testSSHWhenDisablingTableRegionsInOpeningOrPendingOpenState(org.apache.hadoop.hb
> ase.master.TestAssignmentManagerOnCluster) Time elapsed: 60.036 sec <<<
> ERROR!
> java.lang.Exception: test timed out after 6 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.deleteTable(HBaseAdmin.java
> :724)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.deleteTable(HBaseTestingU
> tility.java:1581)
> at
> org.apache.hadoop.hbase.master.TestAssignmentManagerOnCluster.testSSH
> WhenDisablingTableRegionsInOpeningOrPendingOpenState(TestAssignmentManagerOnClus
> ter.java:676)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-14319) TestAtomicOperation.testMultiRowMutationMultiThreads is flaky
[ https://issues.apache.org/jira/browse/HBASE-14319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-14319. --- Resolution: Cannot Reproduce No longer on the flaky dashboard, was fixed somewhere along the way. > TestAtomicOperation.testMultiRowMutationMultiThreads is flaky > - > > Key: HBASE-14319 > URL: https://issues.apache.org/jira/browse/HBASE-14319 > Project: HBase > Issue Type: Bug > Components: test >Affects Versions: 2.0.0 >Reporter: Dima Spivak >Priority: Critical > > org.apache.hadoop.hbase.regionserver.TestAtomicOperation.testMultiRowMutationMultiThreads > has been failing sporadically for a while on at least trunk. This might also > be reproducible on other branches, but it's hard to tell the state since our > b.a.o Jenkins matrix for different Java versions that we test against hasn't > been set up to display test results in a pretty way (separate JIRA > forthcoming). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20594) provide utility to compare old and new descriptors
Mike Drob created HBASE-20594: - Summary: provide utility to compare old and new descriptors Key: HBASE-20594 URL: https://issues.apache.org/jira/browse/HBASE-20594 Project: HBase Issue Type: Improvement Reporter: Mike Drob HBASE-20567 gives us hooks that give both the old and new descriptor in pre/postModify* events, but comparing them is still cumbersome. We should provide users some kind of utility for this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-20570) CLONE - Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-20570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-20570. --- Resolution: Duplicate This looks like a duplicate of HBASE-13992, which is currently on track to be included in HBase 3.0 (the next major release). > CLONE - Integrate SparkOnHBase into HBase > - > > Key: HBASE-20570 > URL: https://issues.apache.org/jira/browse/HBASE-20570 > Project: HBase > Issue Type: New Feature > Components: spark >Reporter: ujjawal kumar >Assignee: Theodore michael Malaska >Priority: Major > Fix For: 3.0.0 > > > This Jira is to ask if SparkOnHBase can find a home in side HBase core. > Here is the github: > https://github.com/cloudera-labs/SparkOnHBase > I am the core author of this project and the license is Apache 2.0 > A blog explaining this project is here > http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ > A spark Streaming example is here > http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ > A real customer using this in produce is blogged here > http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ > Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-20534) need docs on downstream projects required to set random local port assignment for tests
[ https://issues.apache.org/jira/browse/HBASE-20534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-20534. --- Resolution: Not A Problem I think HBASE-20544 is going to remove the need for docs by addressing the root issue. > need docs on downstream projects required to set random local port assignment > for tests > --- > > Key: HBASE-20534 > URL: https://issues.apache.org/jira/browse/HBASE-20534 > Project: HBase > Issue Type: Bug > Components: documentation, test >Affects Versions: 2.0.0 >Reporter: Mike Drob >Priority: Critical > > We need better user facing text to explain that they need to set > hbase.localcluster.assign.random.ports to true. See HBASE-20224. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20534) need docs on downstream projects required to set random local port assignment for tests
Mike Drob created HBASE-20534: - Summary: need docs on downstream projects required to set random local port assignment for tests Key: HBASE-20534 URL: https://issues.apache.org/jira/browse/HBASE-20534 Project: HBase Issue Type: Bug Components: documentation, test Affects Versions: 2.0.0 Reporter: Mike Drob We need better user facing text to explain that they need to set hbase.localcluster.assign.random.ports to true. See HBASE-20224. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190
Mike Drob created HBASE-20502: - Summary: Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190 Key: HBASE-20502 URL: https://issues.apache.org/jira/browse/HBASE-20502 Project: HBase Issue Type: Bug Components: dependencies, documentation Reporter: Mike Drob Fix For: 3.0.0 We need to call out hadoop-yarn 2.9.0 and the entire 3.0.x line as explicitly unsupported due to needing YARN-7190 fixed in versions that have ATS available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (HBASE-20459) Majority of scan CPU time in HBase-1 spent in size estimation
[ https://issues.apache.org/jira/browse/HBASE-20459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reopened HBASE-20459: --- reopening to mark that this patch needs to go to branch-2 and branch-2.0 > Majority of scan CPU time in HBase-1 spent in size estimation > - > > Key: HBASE-20459 > URL: https://issues.apache.org/jira/browse/HBASE-20459 > Project: HBase > Issue Type: Improvement > Components: Performance, scan >Affects Versions: 1.4.3 >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Critical > Fix For: 1.5.0, 1.4.4, 2.0.1 > > Attachments: 20459-v2.txt, 20459.2.0.txt, 20459.txt, > HBASE-20459.branch-2.0.001.patch, Screenshot_20180419_162559.png > > > See attached screenshot. Will look into a fix later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20410) upgrade protoc compiler to 3.5.1-1
Mike Drob created HBASE-20410: - Summary: upgrade protoc compiler to 3.5.1-1 Key: HBASE-20410 URL: https://issues.apache.org/jira/browse/HBASE-20410 Project: HBase Issue Type: Bug Components: build, dependencies, Protobufs Reporter: Mike Drob Assignee: Mike Drob See HBASE-20356 After doing the cleanup there, I was informed that there's a 3.5.1-1 version of the compiler binaries that work on rhel6, so let's just go to that. Wish I knew about it beforehand. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (HBASE-20351) Shell dumps netty properties on startup
[
https://issues.apache.org/jira/browse/HBASE-20351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob reopened HBASE-20351:
---
Assignee: stack
> Shell dumps netty properties on startup
> ---
>
> Key: HBASE-20351
> URL: https://issues.apache.org/jira/browse/HBASE-20351
> Project: HBase
> Issue Type: Bug
> Components: documentation, shell
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: HBASE-20351.master.001.patch
>
>
> {code}
> stack@ve0524:~$ ./hbase/bin/hbase --config conf_hbase shell
> 2018-04-04 19:58:02,187 DEBUG [main] logging.InternalLoggerFactory: Using
> SLF4J as the default logging framework
> 2018-04-04 19:58:02,191 DEBUG [main] util.ResourceLeakDetector:
> -Dorg.apache.hbase.thirdparty.io.netty.leakDetection.level: simple
> 2018-04-04 19:58:02,192 DEBUG [main] util.ResourceLeakDetector:
> -Dorg.apache.hbase.thirdparty.io.netty.leakDetection.targetRecords: 4
> 2018-04-04 19:58:02,214 DEBUG [main] internal.PlatformDependent0:
> -Dio.netty.noUnsafe: false
> 2018-04-04 19:58:02,215 DEBUG [main] internal.PlatformDependent0: Java
> version: 8
> 2018-04-04 19:58:02,216 DEBUG [main] internal.PlatformDependent0:
> sun.misc.Unsafe.theUnsafe: available
> 2018-04-04 19:58:02,216 DEBUG [main] internal.PlatformDependent0:
> sun.misc.Unsafe.copyMemory: available
> 2018-04-04 19:58:02,217 DEBUG [main] internal.PlatformDependent0:
> java.nio.Buffer.address: available
> 2018-04-04 19:58:02,217 DEBUG [main] internal.PlatformDependent0: direct
> buffer constructor: available
> 2018-04-04 19:58:02,218 DEBUG [main] internal.PlatformDependent0:
> java.nio.Bits.unaligned: available, true
> 2018-04-04 19:58:02,218 DEBUG [main] internal.PlatformDependent0:
> jdk.internal.misc.Unsafe.allocateUninitializedArray(int): unavailable prior
> to Java9
> 2018-04-04 19:58:02,218 DEBUG [main] internal.PlatformDependent0:
> java.nio.DirectByteBuffer.(long, int): available
> 2018-04-04 19:58:02,218 DEBUG [main] internal.PlatformDependent:
> sun.misc.Unsafe: available
> 2018-04-04 19:58:02,218 DEBUG [main] internal.PlatformDependent:
> -Dio.netty.tmpdir: /tmp (java.io.tmpdir)
> 2018-04-04 19:58:02,218 DEBUG [main] internal.PlatformDependent:
> -Dio.netty.bitMode: 64 (sun.arch.data.model)
> 2018-04-04 19:58:02,219 DEBUG [main] internal.PlatformDependent:
> -Dio.netty.noPreferDirect: false
> 2018-04-04 19:58:02,219 DEBUG [main] internal.PlatformDependent:
> -Dio.netty.maxDirectMemory: 1073741824 bytes
> 2018-04-04 19:58:02,219 DEBUG [main] internal.PlatformDependent:
> -Dio.netty.uninitializedArrayAllocationThreshold: -1
> 2018-04-04 19:58:02,220 DEBUG [main] internal.CleanerJava6:
> java.nio.ByteBuffer.cleaner(): available
> 2018-04-04 19:58:02,220 DEBUG [main] util.ResourceLeakDetectorFactory: Loaded
> default ResourceLeakDetector:
> org.apache.hbase.thirdparty.io.netty.util.ResourceLeakDetector@7dbae40
> 2018-04-04 19:58:02,229 DEBUG [main] internal.PlatformDependent:
> org.jctools-core.MpscChunkedArrayQueue: available
> 2018-04-04 19:58:02,260 DEBUG [main] channel.MultithreadEventLoopGroup:
> -Dio.netty.eventLoopThreads: 96
> 2018-04-04 19:58:02,282 DEBUG [main] nio.NioEventLoop:
> -Dio.netty.noKeySetOptimization: false
> 2018-04-04 19:58:02,282 DEBUG [main] nio.NioEventLoop:
> -Dio.netty.selectorAutoRebuildThreshold: 512
> HBase Shell
> Use "help" to get list of supported commands.
> Use "exit" to quit this interactive shell.
> Version 2.0.0, r0db342d312784a6663b406fdb0f7b3b3c1fa928d, Mon Apr 2 22:54:56
> PDT 2018
> Took 0.0028 seconds
> hbase(main):001:0>
> {code}
> Does it each time I run a command
> {code}
> hbase(main):001:0> describe 'ycsb'
> 2018-04-04 19:59:00,084 DEBUG [main] buffer.AbstractByteBuf:
> -Dorg.apache.hbase.thirdparty.io.netty.buffer.bytebuf.checkAccessible: true
> 2018-04-04 19:59:00,084 DEBUG [main] util.ResourceLeakDetectorFactory: Loaded
> default ResourceLeakDetector:
> org.apache.hbase.thirdparty.io.netty.util.ResourceLeakDetector@66ab924
> 2018-04-04 19:59:00,121 DEBUG [main] channel.DefaultChannelId:
> -Dio.netty.processId: 697 (auto-detected)
> 2018-04-04 19:59:00,123 DEBUG [main] util.NetUtil:
> -Djava.net.preferIPv4Stack: true
> 2018-04-04 19:59:00,123 DEBUG [main] util.NetUtil:
> -Djava.net.preferIPv6Addresses: false
> 2018-04-04 19:59:00,124 DEBUG [main] util.NetUtil: Loopback interface: lo
> (lo, 127.0.0.1)
> 2018-04-04 19:59:00,125 DEBUG [main] util.NetUtil:
> /proc/sys/net/core/somaxconn: 128
> 2018-04-04 19:59:00,125 DEBUG [main] channel.DefaultChannelId:
> -Dio.netty.machineId: 00:1e:67:ff:fe:c5:54:b4 (auto-detected)
> 2018-04-04 19:59:00,130 DEBUG [main] internal.InternalThreadLocalMap:
> -Dio.netty.threadLocalMap.stringBuilder.initialSize: 1024
> 2018-04-04 19:59:00,131 DEBUG [main]
[jira] [Created] (HBASE-20382) If RSGroups not enabled, rsgroup.jsp prints stack trace
Mike Drob created HBASE-20382:
-
Summary: If RSGroups not enabled, rsgroup.jsp prints stack trace
Key: HBASE-20382
URL: https://issues.apache.org/jira/browse/HBASE-20382
Project: HBase
Issue Type: Bug
Components: rsgroup, UI
Reporter: Mike Drob
Fix For: 2.0.0
Going to {{rsgroup.jsp?name=foo}} I get the following stack trace:
{noformat}
org.apache.hadoop.hbase.TableNotFoundException: hbase:rsgroup
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegionInMeta(ConnectionImplementation.java:842)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:733)
at
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:719)
at
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:690)
at
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
at
org.apache.hadoop.hbase.client.ConnectionImplementation.getRegionLocation(ConnectionImplementation.java:571)
at
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.getRegionLocation(ConnectionUtils.java:131)
at
org.apache.hadoop.hbase.client.HRegionLocator.getRegionLocation(HRegionLocator.java:73)
at
org.apache.hadoop.hbase.client.RegionServerCallable.prepare(RegionServerCallable.java:223)
at
org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:105)
at org.apache.hadoop.hbase.client.HTable.get(HTable.java:385)
at org.apache.hadoop.hbase.client.HTable.get(HTable.java:359)
at
org.apache.hadoop.hbase.RSGroupTableAccessor.getRSGroupInfo(RSGroupTableAccessor.java:75)
at
org.apache.hadoop.hbase.generated.master.rsgroup_jsp._jspService(rsgroup_jsp.java:78)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
at
org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at
org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at
org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1374)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at
org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at
org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:534)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
at
[jira] [Reopened] (HBASE-20159) Support using separate ZK quorums for client
[
https://issues.apache.org/jira/browse/HBASE-20159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob reopened HBASE-20159:
---
> Support using separate ZK quorums for client
>
>
> Key: HBASE-20159
> URL: https://issues.apache.org/jira/browse/HBASE-20159
> Project: HBase
> Issue Type: New Feature
> Components: Client, Operability, Zookeeper
>Reporter: Yu Li
>Assignee: Yu Li
>Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: 20159.addendum, 20159.addendum2.patch,
> HBASE-20159.branch-2.patch, HBASE-20159.patch, HBASE-20159.v2.patch,
> HBASE-20159.v3.patch
>
>
> Currently we are using the same zookeeper quorums for client and server,
> which makes us under risk that if some client connection boost exhausted
> zookeeper, RegionServer might abort due to zookeeper session loss. Actually
> we have suffered from this many times in production.
> Here we propose to allow client to use different ZK quorums, through below
> settings:
> {noformat}
> hbase.client.zookeeper.quorum
> hbase.client.zookeeper.property.clientPort
> hbase.client.zookeeper.observer.mode
> {noformat}
> The first two are for specifying client zookeeper properties, and the third
> one indicating whether the client ZK nodes are in observer mode. If the
> client ZK are not observer nodes, HMaster will take responsibility to
> synchronize necessary meta information (such as meta location and master
> address, etc.) from server to client ZK
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20307) LoadTestTool prints too much zookeeper logging
Mike Drob created HBASE-20307: - Summary: LoadTestTool prints too much zookeeper logging Key: HBASE-20307 URL: https://issues.apache.org/jira/browse/HBASE-20307 Project: HBase Issue Type: Bug Components: tooling Reporter: Mike Drob When running ltt there is a ton of ZK related cruft that I probably don't care about. Hide it behind -verbose flag or point people at log4j configuration but don't print it by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20306) LoadTestTool does not print summary at end of run
Mike Drob created HBASE-20306: - Summary: LoadTestTool does not print summary at end of run Key: HBASE-20306 URL: https://issues.apache.org/jira/browse/HBASE-20306 Project: HBase Issue Type: Bug Components: tooling Reporter: Mike Drob ltt currently prints status as it goes, but doesn't give a nice summary of what happened so users have to infer it from the last status line printed. Would be nice to print a real summary with statistics about what was run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-13696) cleanup references to EOM releases across the reference guide
[ https://issues.apache.org/jira/browse/HBASE-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-13696. --- Resolution: Duplicate > cleanup references to EOM releases across the reference guide > - > > Key: HBASE-13696 > URL: https://issues.apache.org/jira/browse/HBASE-13696 > Project: HBase > Issue Type: Task >Reporter: Sean Busbey >Assignee: Chia-Ping Tsai >Priority: Major > Labels: beginner > Attachments: HBASE-13696.1.patch, HBASE-13696.2.patch, > HBASE-13696.v3.patch > > > the java table still contains HBase 0.96, and the Hadoop table still has > HBase 0.92 and 0.96. We should remove these. Their details can still be found > in their last release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20283) update documentation around default compaction schedule
Mike Drob created HBASE-20283:
-
Summary: update documentation around default compaction schedule
Key: HBASE-20283
URL: https://issues.apache.org/jira/browse/HBASE-20283
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Mike Drob
Our documentation currently states that compactions default to once a week.
>From [~stack]'s comments:
{quote}
We should file an issue to update the compactions section: "By default, major
compactions are scheduled to run once in a 7-day period." Should talk about how
dumb our default is, that operators should run them themselves..., the tooling
available, etc.
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20260) Purge old content from the book for branch-2/master
Mike Drob created HBASE-20260: - Summary: Purge old content from the book for branch-2/master Key: HBASE-20260 URL: https://issues.apache.org/jira/browse/HBASE-20260 Project: HBase Issue Type: Bug Components: documentation Affects Versions: 2.0.0-beta-2 Reporter: Mike Drob Assignee: Mike Drob Fix For: 2.0.0 Attachments: HBASE-20260.patch there's lots of old content that we should clean up to make room for new content. old warnings that don't matter any more, properties that don't exist, etc... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-13840) Server UIs should rename column labels from KVs to Cell
[ https://issues.apache.org/jira/browse/HBASE-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-13840. --- Resolution: Duplicate Fix Version/s: (was: 1.5.0) (was: 2.0.0) Closing as dup of HBASE-20132 > Server UIs should rename column labels from KVs to Cell > --- > > Key: HBASE-13840 > URL: https://issues.apache.org/jira/browse/HBASE-13840 > Project: HBase > Issue Type: Bug > Components: master, regionserver, UI >Affects Versions: 1.1.0 >Reporter: Lars George >Priority: Major > > Currently the master UI still refers to KVs in some of the tables. We should > do a sweep and rename to Cell. > Also do for RS templates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20198) ReplicationSource::initialize shouldn't always retry
Mike Drob created HBASE-20198: - Summary: ReplicationSource::initialize shouldn't always retry Key: HBASE-20198 URL: https://issues.apache.org/jira/browse/HBASE-20198 Project: HBase Issue Type: Bug Components: Replication Reporter: Mike Drob ReplicationSource::initialize will always retry on failure to create the replication endpoint. However, the failure could be caused by something like ClassNotFoundException (see ReplicationSource::createReplicationEndpoint) where a retry has no chance to make things better and will instead clutter the logs. Let's make this logic a bit more w.r.t. failure modes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20180) Avoid Class::newInstance
Mike Drob created HBASE-20180:
-
Summary: Avoid Class::newInstance
Key: HBASE-20180
URL: https://issues.apache.org/jira/browse/HBASE-20180
Project: HBase
Issue Type: Sub-task
Reporter: Mike Drob
Assignee: Mike Drob
Class::newInstance is deprecated starting in Java 9 -
https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw
undeclared checked exceptions. The suggested replacement is
{{getDeclaredConstructor().newInstance()}}, which will wrap the checked
exceptions in InvocationException.
There's even an error-prone warning about it, we should promote that to error
while we're fixing this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20175) hbase-spark needs scala dependency convergance
Mike Drob created HBASE-20175:
-
Summary: hbase-spark needs scala dependency convergance
Key: HBASE-20175
URL: https://issues.apache.org/jira/browse/HBASE-20175
Project: HBase
Issue Type: Bug
Components: dependencies, spark
Reporter: Mike Drob
This is a follow-on to HBASE-16179 - I think we might need to specify an
exclude in the dependency management.
{noformat}
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ hbase-spark
---
[WARNING] Expected all dependencies to require Scala version: 2.11.8
[WARNING] org.apache.hbase:hbase-spark:3.0.0-SNAPSHOT requires scala version:
2.11.8
[WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala version:
2.11.8
[WARNING] org.apache.spark:spark-streaming_2.11:2.1.1 requires scala version:
2.11.8
[WARNING] org.scalatest:scalatest_2.11:2.2.4 requires scala version: 2.11.2
{noformat}
[~tedyu] - since you're already fiddling in this area, do you want to take a
look?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20164) failed hadoopcheck should add footer link
Mike Drob created HBASE-20164: - Summary: failed hadoopcheck should add footer link Key: HBASE-20164 URL: https://issues.apache.org/jira/browse/HBASE-20164 Project: HBase Issue Type: Bug Components: community Reporter: Mike Drob Assignee: Mike Drob thought for sure this already had an issue, [~busbey], but I can't find it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20153) enable error-prone analysis in precommit
Mike Drob created HBASE-20153:
-
Summary: enable error-prone analysis in precommit
Key: HBASE-20153
URL: https://issues.apache.org/jira/browse/HBASE-20153
Project: HBase
Issue Type: Bug
Components: community
Reporter: Mike Drob
We've done a lot of work to get rid of the error-prone errors, we should make
sure they stay out. Let's enable errorProne profile and analysis in precommit.
[~busbey] - I tried figuring out how to pass flags ({{-PerrorProne}} to the mvn
compile precommit check but was unable to unravel that thread. Any help is
appreciated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-16795) Revisit 'in project Maven repo' checked in as part of HBASE-14785
[
https://issues.apache.org/jira/browse/HBASE-16795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-16795.
---
Resolution: Won't Fix
Branch 1.1 is EOL
> Revisit 'in project Maven repo' checked in as part of HBASE-14785
> -
>
> Key: HBASE-16795
> URL: https://issues.apache.org/jira/browse/HBASE-16795
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.1.13
>Reporter: Andrew Purtell
>Priority: Major
>
> I did a naive update of docs on branch-1.1 from master like so:
> {noformat}
> $ git co master src
> ...
> {noformat}
> and the result failed a RAT check. Looking at rat.txt I noticed we are
> including binaries in our source tarball, checked in as part of HBASE-14785.
> {noformat}
> HBASE-14785 Addendum: Add an in-project Maven repo
> src/main/site/resources/css/site.css | 1 -
> .../maven-fluido-skin/1.5-HBASE/maven-fluido-skin-1.5-HBASE.jar | Bin 0 ->
> 344936 bytes
> .../maven-fluido-skin/1.5-HBASE/maven-fluido-skin-1.5-HBASE.pom | 718
>
> .../maven/skins/maven-fluido-skin/maven-metadata-local.xml | 12 +
> 4 files changed, 730 insertions(+), 1 deletion(-)
> {noformat}
> I'm not sure why RAT flagged this in that 1.1 build when I see that
> previously we have copied back docs from master into the branch. Perhaps
> previous copies have been more selective.
> This change has been committed for over a year. Let's make sure we have
> discussed this and determined it is appropriate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-15168) Zombie stomping branch-1.1 edition
[ https://issues.apache.org/jira/browse/HBASE-15168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15168. --- Resolution: Won't Fix Branch 1.1 is EOL > Zombie stomping branch-1.1 edition > -- > > Key: HBASE-15168 > URL: https://issues.apache.org/jira/browse/HBASE-15168 > Project: HBase > Issue Type: Umbrella > Components: test >Affects Versions: 1.1.0 >Reporter: Nick Dimiduk >Priority: Critical > Fix For: 1.1.7 > > > Let's bring back the work done on HBASE-14420 for branch-1.1, stabilize our > [builds|https://builds.apache.org/job/HBase-1.1-JDK7/]. Hang tickets here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-15308) Flakey TestSplitWalDataLoss on branch-1.1
[ https://issues.apache.org/jira/browse/HBASE-15308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15308. --- Resolution: Won't Fix Branch 1.1 is EOL > Flakey TestSplitWalDataLoss on branch-1.1 > - > > Key: HBASE-15308 > URL: https://issues.apache.org/jira/browse/HBASE-15308 > Project: HBase > Issue Type: Sub-task > Components: test >Reporter: Heng Chen >Priority: Major > Fix For: 1.1.7 > > > It happens during HBASE-15169 QA test, see > https://builds.apache.org/job/PreCommit-HBASE-Build/628/artifact/patchprocess/patch-unit-hbase-server-jdk1.8.0_72.txt > https://builds.apache.org/job/PreCommit-HBASE-Build/547/artifact/patchprocess/patch-unit-hbase-server-jdk1.8.0_72.txt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-15185) Fix jdk8 javadoc warnings for branch-1.1
[ https://issues.apache.org/jira/browse/HBASE-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-15185. --- Resolution: Won't Fix Branch 1.1 is EOL > Fix jdk8 javadoc warnings for branch-1.1 > > > Key: HBASE-15185 > URL: https://issues.apache.org/jira/browse/HBASE-15185 > Project: HBase > Issue Type: Task >Affects Versions: 1.1.3 >Reporter: Yu Li >Assignee: Zheng Hu >Priority: Major > Attachments: HBASE-15185.branch-1.1.patch, > HBASE-15185.branch-1.1.v2.patch, HBASE-15185.branch-1.1.v3.patch > > > [This > link|https://builds.apache.org/job/PreCommit-HBASE-Build/340/artifact/patchprocess/patch-javadoc-hbase-server-jdk1.8.0_66.txt] > shows jdk8 javadoc warnings for current branch-1.1 code base. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-14341) branch-1.1 source assembly contains spurious hbase-shaded-client and hbase-shaded-server modules
[
https://issues.apache.org/jira/browse/HBASE-14341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-14341.
---
Resolution: Won't Fix
branch-1.1 is EOL
> branch-1.1 source assembly contains spurious hbase-shaded-client and
> hbase-shaded-server modules
>
>
> Key: HBASE-14341
> URL: https://issues.apache.org/jira/browse/HBASE-14341
> Project: HBase
> Issue Type: Bug
> Components: build
>Affects Versions: 1.1.2
>Reporter: Sean Busbey
>Priority: Major
>
> if you build a source assembly according to the book:
> {quote}
> mvn clean install -DskipTests assembly:single
> -Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
> {quote}
> Then the resultant artifact has an extra set of the shaded modules at the top
> level (in addition to the ones in the hbase-shaded module)
> {code}
> $ ls -lah hbase-1.1.2/
> total 608
> drwxr-xr-x 32 busbey staff 1.1K Aug 30 17:14 .
> drwxr-xr-x 3 busbey staff 102B Aug 30 17:14 ..
> -rw-r--r-- 1 busbey staff 162K Aug 30 16:42 CHANGES.txt
> -rw-r--r-- 1 busbey staff36K Aug 30 16:15 LICENSE.txt
> -rw-r--r-- 1 busbey staff 1.5K Aug 30 16:15 NOTICE.txt
> -rw-r--r-- 1 busbey staff 1.4K Aug 30 16:15 README.txt
> drwxr-xr-x 31 busbey staff 1.0K Aug 30 16:42 bin
> drwxr-xr-x 9 busbey staff 306B Aug 30 16:42 conf
> drwxr-xr-x 24 busbey staff 816B Aug 30 16:42 dev-support
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:56 hbase-annotations
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:58 hbase-assembly
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:56 hbase-checkstyle
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:57 hbase-client
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:56 hbase-common
> drwxr-xr-x 5 busbey staff 170B Aug 30 16:58 hbase-examples
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:57 hbase-hadoop-compat
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:57 hbase-hadoop2-compat
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:58 hbase-it
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:57 hbase-prefix-tree
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:56 hbase-procedure
> drwxr-xr-x 5 busbey staff 170B Aug 30 16:56 hbase-protocol
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:56 hbase-resource-bundle
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:57 hbase-rest
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:57 hbase-server
> drwxr-xr-x 5 busbey staff 170B Aug 30 16:42 hbase-shaded
> drwxr-xr-x 3 busbey staff 102B Aug 30 16:42 hbase-shaded-client
> drwxr-xr-x 3 busbey staff 102B Aug 30 16:42 hbase-shaded-server
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:58 hbase-shell
> drwxr-xr-x 3 busbey staff 102B Aug 30 16:57 hbase-testing-util
> drwxr-xr-x 4 busbey staff 136B Aug 30 16:57 hbase-thrift
> -rw-r--r-- 1 busbey staff94K Aug 30 16:42 pom.xml
> drwxr-xr-x 3 busbey staff 102B Aug 30 16:15 src
> $ diff -r hbase-1.1.2/hbase-shaded-client
> hbase-1.1.2/hbase-shaded/hbase-shaded-client
> Only in hbase-1.1.2/hbase-shaded/hbase-shaded-client: target
> $ diff -r hbase-1.1.2/hbase-shaded-server
> hbase-1.1.2/hbase-shaded/hbase-shaded-server
> Only in hbase-1.1.2/hbase-shaded/hbase-shaded-server: target
> {code}
> they're the same as the correct ones and they don't build by default since
> the top level pom doesn't mention them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20134) website generation uses hard-coded /tmp
Mike Drob created HBASE-20134:
-
Summary: website generation uses hard-coded /tmp
Key: HBASE-20134
URL: https://issues.apache.org/jira/browse/HBASE-20134
Project: HBase
Issue Type: Bug
Components: website
Reporter: Mike Drob
Assignee: Sean Busbey
{code}
if [ -z "${working_dir}" ]; then
echo "[DEBUG] defaulting to creating a directory in /tmp"
working_dir=/tmp
while [[ -e ${working_dir} ]]; do
working_dir=/tmp/hbase-generate-website-${RANDOM}.${RANDOM}
done
mkdir "${working_dir}"
else
{code}
This should likely use {{$TMPDIR}} or {{mktemp -d}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-20062) findbugs is not running on precommit checks
[
https://issues.apache.org/jira/browse/HBASE-20062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-20062.
---
Resolution: Fixed
I've seen findbugs running now. Closing.
> findbugs is not running on precommit checks
> ---
>
> Key: HBASE-20062
> URL: https://issues.apache.org/jira/browse/HBASE-20062
> Project: HBase
> Issue Type: Bug
> Components: community, test
>Reporter: Sean Busbey
>Assignee: Mike Drob
>Priority: Blocker
> Fix For: 1.3.2, 1.5.0, 1.2.7, 2.0.0-beta-2, 1.4.3
>
>
> as of build #11638 ~3 hours ago precommit isn't using findbugs:
> {quote}
> 0 findbugs0m 0s Findbugs executables are not available.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20058) improper quoting in presplitting command docs
Mike Drob created HBASE-20058:
-
Summary: improper quoting in presplitting command docs
Key: HBASE-20058
URL: https://issues.apache.org/jira/browse/HBASE-20058
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Mike Drob
http://hbase.apache.org/book.html#tricks.pre-split
{code}
hbase>create 't1','f',SPLITS => ['10','20',30']
{code}
Missing a quote before the 30./
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20043) ITBLL fails against hadoop3
Mike Drob created HBASE-20043:
-
Summary: ITBLL fails against hadoop3
Key: HBASE-20043
URL: https://issues.apache.org/jira/browse/HBASE-20043
Project: HBase
Issue Type: Bug
Components: integration tests
Reporter: Mike Drob
Fix For: 2.0.0-beta-2
This has been failing for a while, I haven't tried to bisec but it was before
my changes for HBASE-19991 at least.
{code}
mvn clean verify -pl hbase-it -Dhadoop.profile=3.0
-Dit.test=IntegrationTestBigLinkedList -Dtest=none -am
{code}
{code}
2018-02-21 16:43:13,265 ERROR
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=60450] ipc.RpcServer(464):
Unexpected throwable object
java.lang.AssertionError:
hri=IntegrationTestBigLinkedList,\x8E8\xE3\x8E8\xE3\x8E5,1519252895022.236bbedde32e4549691c108a1a7005a8.,
source=, destination=mdrob-mbp.hsd1.tx.comcast.net,60456,1519252856027
at org.apache.hadoop.hbase.master.HMaster.move(HMaster.java:1691)
at
org.apache.hadoop.hbase.master.MasterRpcServices.moveRegion(MasterRpcServices.java:1348)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:406)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
2018-02-21 16:43:13,276 DEBUG
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=60450] ipc.CallRunner(141):
callId: 49 service: MasterService methodName: MoveRegion size: 106 connection:
192.168.1.134:60743 deadline: 1519253053263
java.io.IOException:
hri=IntegrationTestBigLinkedList,\x8E8\xE3\x8E8\xE3\x8E5,1519252895022.236bbedde32e4549691c108a1a7005a8.,
source=, destination=mdrob-mbp.hsd1.tx.comcast.net,60456,1519252856027
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:465)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)
at
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
Caused by: java.lang.AssertionError:
hri=IntegrationTestBigLinkedList,\x8E8\xE3\x8E8\xE3\x8E5,1519252895022.236bbedde32e4549691c108a1a7005a8.,
source=, destination=mdrob-mbp.hsd1.tx.comcast.net,60456,1519252856027
at org.apache.hadoop.hbase.master.HMaster.move(HMaster.java:1691)
at
org.apache.hadoop.hbase.master.MasterRpcServices.moveRegion(MasterRpcServices.java:1348)
at
org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java)
at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:406)
... 3 more
{code}
The assertion that it trips is:
{code}
// Now we can do the move
RegionPlan rp = new RegionPlan(hri, regionState.getServerName(), dest);
assert rp.getDestination() != null: rp.toString() + " " + dest;
assert rp.getSource() != null: rp.toString();
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-20041) cannot start mini mapreduce cluster for ITs
Mike Drob created HBASE-20041: - Summary: cannot start mini mapreduce cluster for ITs Key: HBASE-20041 URL: https://issues.apache.org/jira/browse/HBASE-20041 Project: HBase Issue Type: Sub-task Reporter: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-20039) move testhbasetestingutility mr tests to hbase-mapreduce
[ https://issues.apache.org/jira/browse/HBASE-20039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-20039. --- Resolution: Fixed Fix Version/s: 2.0.0-beta-2 > move testhbasetestingutility mr tests to hbase-mapreduce > > > Key: HBASE-20039 > URL: https://issues.apache.org/jira/browse/HBASE-20039 > Project: HBase > Issue Type: Sub-task >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Major > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-20039.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20039) move testhbasetestingutility mr tests to hbase-mapreduce
Mike Drob created HBASE-20039: - Summary: move testhbasetestingutility mr tests to hbase-mapreduce Key: HBASE-20039 URL: https://issues.apache.org/jira/browse/HBASE-20039 Project: HBase Issue Type: Sub-task Reporter: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-19991) lots of hbase-rest test failures against hadoop 3
[ https://issues.apache.org/jira/browse/HBASE-19991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-19991. --- Resolution: Fixed easier to handle in follow on issues > lots of hbase-rest test failures against hadoop 3 > - > > Key: HBASE-19991 > URL: https://issues.apache.org/jira/browse/HBASE-19991 > Project: HBase > Issue Type: Bug > Components: REST, test >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Major > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-19991.WIP.patch, HBASE-19991.v1.patch, > HBASE-19991.v2.patch > > > mvn clean test -pl hbase-rest -Dhadoop.profile=3.0 > [ERROR] Tests run: 106, Failures: 95, Errors: 8, Skipped: 1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (HBASE-19991) lots of hbase-rest test failures against hadoop 3
[ https://issues.apache.org/jira/browse/HBASE-19991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reopened HBASE-19991: --- > lots of hbase-rest test failures against hadoop 3 > - > > Key: HBASE-19991 > URL: https://issues.apache.org/jira/browse/HBASE-19991 > Project: HBase > Issue Type: Bug > Components: REST, test >Reporter: Mike Drob >Assignee: Mike Drob >Priority: Major > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-19991.WIP.patch, HBASE-19991.v1.patch, > HBASE-19991.v2.patch > > > mvn clean test -pl hbase-rest -Dhadoop.profile=3.0 > [ERROR] Tests run: 106, Failures: 95, Errors: 8, Skipped: 1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-20007) rest server doesn't start against hadoop-3
Mike Drob created HBASE-20007:
-
Summary: rest server doesn't start against hadoop-3
Key: HBASE-20007
URL: https://issues.apache.org/jira/browse/HBASE-20007
Project: HBase
Issue Type: Bug
Components: REST
Reporter: Mike Drob
While fixing HBASE-19991 I discovered that this command fails:
{noformat}
mvn clean package -Dhadoop.profile=3.0 -DskipTests && bin/hbase-daemon.sh start
rest
{noformat}
The command itself actually succeeds, but the rest server fails to start with
{noformat}
Exception in thread "main" java.lang.NoClassDefFoundError:
com/sun/jersey/core/spi/factory/AbstractRuntimeDelegate
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:107)
at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:166)
at
javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135)
at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120)
at javax.ws.rs.core.MediaType.valueOf(MediaType.java:179)
at
org.glassfish.jersey.server.model.IntrospectionModeller.extractMediaTypes(IntrospectionModeller.java:297)
at
org.glassfish.jersey.server.model.IntrospectionModeller.extractMediaTypes(IntrospectionModeller.java:282)
at
org.glassfish.jersey.server.model.IntrospectionModeller.doCreateResourceBuilder(IntrospectionModeller.java:129)
at
org.glassfish.jersey.server.model.IntrospectionModeller.access$000(IntrospectionModeller.java:80)
at
org.glassfish.jersey.server.model.IntrospectionModeller$1.call(IntrospectionModeller.java:112)
at
org.glassfish.jersey.server.model.IntrospectionModeller$1.call(IntrospectionModeller.java:109)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at
org.glassfish.jersey.internal.Errors.processWithException(Errors.java:255)
at
org.glassfish.jersey.server.model.IntrospectionModeller.createResourceBuilder(IntrospectionModeller.java:109)
at org.glassfish.jersey.server.model.Resource.from(Resource.java:797)
at
org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:465)
at
org.glassfish.jersey.server.ApplicationHandler.access$500(ApplicationHandler.java:184)
at
org.glassfish.jersey.server.ApplicationHandler$3.call(ApplicationHandler.java:350)
at
org.glassfish.jersey.server.ApplicationHandler$3.call(ApplicationHandler.java:347)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at
org.glassfish.jersey.internal.Errors.processWithException(Errors.java:255)
at
org.glassfish.jersey.server.ApplicationHandler.(ApplicationHandler.java:347)
at
org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:392)
at
org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:177)
at
org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:369)
at javax.servlet.GenericServlet.init(GenericServlet.java:244)
at
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:643)
at
org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:422)
at
org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:892)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:349)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:778)
at
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
at
[jira] [Reopened] (HBASE-19920) TokenUtil.obtainToken unnecessarily creates a local directory
[
https://issues.apache.org/jira/browse/HBASE-19920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob reopened HBASE-19920:
---
Reopen because I think we want this on branch-1 as well. [~apurtell]
> TokenUtil.obtainToken unnecessarily creates a local directory
> -
>
> Key: HBASE-19920
> URL: https://issues.apache.org/jira/browse/HBASE-19920
> Project: HBase
> Issue Type: Bug
>Reporter: Rohini Palaniswamy
>Assignee: Mike Drob
>Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19920.patch, HBASE-19920.v2.patch,
> HBASE-19920.v3.patch, HBASE-19920.v4.patch, HBASE-19920.v5.patch,
> HBASE-19920.v6.patch, HBASE-19920.v7.patch, HBASE-19920.v8.patch,
> HBASE-19920.v9.patch
>
>
> On client code, when one calls TokenUtil.obtainToken it loads ProtobufUtil
> which in its static block initializes DynamicClassLoader and that creates the
> directory ${hbase.local.dir}/jars/ and also instantiates a filesystem class
> to access hbase.dynamic.jars.dir.
> https://github.com/apache/hbase/blob/master/hbase-common/src/main/java/org/apache/hadoop/hbase/util/DynamicClassLoader.java#L109-L127
> Since this is region server specific code, not expecting this to happen when
> one accesses hbase as a client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-19991) lots of hbase-rest test failures against hadoop 3
Mike Drob created HBASE-19991: - Summary: lots of hbase-rest test failures against hadoop 3 Key: HBASE-19991 URL: https://issues.apache.org/jira/browse/HBASE-19991 Project: HBase Issue Type: Bug Components: REST, test Reporter: Mike Drob Assignee: Mike Drob Fix For: 2.0.0 mvn clean test -pl hbase-rest -Dhadoop.profile=3.0 [ERROR] Tests run: 106, Failures: 95, Errors: 8, Skipped: 1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19987) update error-prone to 2.2.0
Mike Drob created HBASE-19987: - Summary: update error-prone to 2.2.0 Key: HBASE-19987 URL: https://issues.apache.org/jira/browse/HBASE-19987 Project: HBase Issue Type: Bug Reporter: Mike Drob keep ourselves healthy and up to date -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19984) Add hadoop 2.8 and 2.9 to precommit
Mike Drob created HBASE-19984: - Summary: Add hadoop 2.8 and 2.9 to precommit Key: HBASE-19984 URL: https://issues.apache.org/jira/browse/HBASE-19984 Project: HBase Issue Type: Sub-task Reporter: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19983) Update ref guide for hadoop versions to include 2.8 and 2.9
Mike Drob created HBASE-19983: - Summary: Update ref guide for hadoop versions to include 2.8 and 2.9 Key: HBASE-19983 URL: https://issues.apache.org/jira/browse/HBASE-19983 Project: HBase Issue Type: Sub-task Reporter: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19982) Hadoop 2.8 and 2.9 Compatability
Mike Drob created HBASE-19982: - Summary: Hadoop 2.8 and 2.9 Compatability Key: HBASE-19982 URL: https://issues.apache.org/jira/browse/HBASE-19982 Project: HBase Issue Type: Improvement Reporter: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19963) TestFSHDFSUtils assumes wrong default port for Hadoop 3.0.1+
Mike Drob created HBASE-19963:
-
Summary: TestFSHDFSUtils assumes wrong default port for Hadoop
3.0.1+
Key: HBASE-19963
URL: https://issues.apache.org/jira/browse/HBASE-19963
Project: HBase
Issue Type: Task
Components: test
Reporter: Mike Drob
We try to accommodate HDFS changing ports when testing if it is the same FS in
our tests:
https://github.com/apache/hbase/blob/master/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestFSHDFSUtils.java#L156-L162
{code}
if (isHadoop3) {
// Hadoop 3.0.0 alpha1+ change default nn port to 9820. See HDFS-9427
testIsSameHdfs(9820);
} else {
// pre hadoop 3.0.0 defaults to port 8020
testIsSameHdfs(8020);
}
{code}
But in Hadoop 3.0.1, they decided to go back to the old port - see HDFS-12990.
So our tests will fail against the snapshot and against future releases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-19947) MR jobs using ITU use wrong filesystem
[ https://issues.apache.org/jira/browse/HBASE-19947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-19947. --- Resolution: Fixed removed extra conf line and pushed to branch-2 and master. thanks for review, stack. > MR jobs using ITU use wrong filesystem > -- > > Key: HBASE-19947 > URL: https://issues.apache.org/jira/browse/HBASE-19947 > Project: HBase > Issue Type: Task > Components: integration tests >Reporter: stack >Assignee: Mike Drob >Priority: Critical > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-19947.patch > > > Discovered by [~stack] as a result of HBASE-19841 > IntegrationTestUtil subclasses HBasteTestUtility which new sets local FS as > the default. When ITU is run against a mini cluster we reset it to the newly > created DFS, but when it runs against an already existing distributed > cluster, we forget to point our conf at the right place. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19947) MR jobs using ITU use wrong filesystem
Mike Drob created HBASE-19947: - Summary: MR jobs using ITU use wrong filesystem Key: HBASE-19947 URL: https://issues.apache.org/jira/browse/HBASE-19947 Project: HBase Issue Type: Task Components: integration tests Reporter: stack Assignee: Mike Drob Fix For: 2.0.0-beta-2 Discovered by [~stack] as a result of HBASE-19841 IntegrationTestUtil subclasses HBasteTestUtility which new sets local FS as the default. When ITU is run against a mini cluster we reset it to the newly created DFS, but when it runs against an already existing distributed cluster, we forget to point our conf at the right place. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (HBASE-19841) Tests against hadoop3 fail with StreamLacksCapabilityException
[
https://issues.apache.org/jira/browse/HBASE-19841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-19841.
---
Resolution: Fixed
> Tests against hadoop3 fail with StreamLacksCapabilityException
> --
>
> Key: HBASE-19841
> URL: https://issues.apache.org/jira/browse/HBASE-19841
> Project: HBase
> Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Mike Drob
>Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: 19841.007.patch, 19841.06.patch, 19841.v0.txt,
> 19841.v1.txt, HBASE-19841.v10.patch, HBASE-19841.v11.patch,
> HBASE-19841.v11.patch, HBASE-19841.v2.patch, HBASE-19841.v3.patch,
> HBASE-19841.v4.patch, HBASE-19841.v5.patch, HBASE-19841.v7.patch,
> HBASE-19841.v8.patch, HBASE-19841.v8.patch, HBASE-19841.v8.patch,
> HBASE-19841.v9.patch
>
>
> The following can be observed running against hadoop3:
> {code}
> java.io.IOException: cannot get log writer
> at
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.compactingSetUp(TestCompactingMemStore.java:107)
> at
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.setUp(TestCompactingMemStore.java:89)
> Caused by:
> org.apache.hadoop.hbase.util.CommonFSUtils$StreamLacksCapabilityException:
> hflush and hsync
> at
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.compactingSetUp(TestCompactingMemStore.java:107)
> at
> org.apache.hadoop.hbase.regionserver.TestCompactingMemStore.setUp(TestCompactingMemStore.java:89)
> {code}
> This was due to hbase-server/src/test/resources/hbase-site.xml not being
> picked up by Configuration object. Among the configs from this file, the
> value for "hbase.unsafe.stream.capability.enforce" relaxes check for presence
> of hflush and hsync. Without this config entry,
> StreamLacksCapabilityException is thrown.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-19946) TestPerColumnFamilyFlush and TestWalAndCompactingMemStoreFlush fail against h3
Mike Drob created HBASE-19946: - Summary: TestPerColumnFamilyFlush and TestWalAndCompactingMemStoreFlush fail against h3 Key: HBASE-19946 URL: https://issues.apache.org/jira/browse/HBASE-19946 Project: HBase Issue Type: Task Components: test Reporter: Mike Drob Assignee: Mike Drob Fix For: 2.0.0-beta-2 These tests started failing against hadoop 3 after HBASE-19841 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19922) ProtobufUtils::PRIMITIVES is unused
Mike Drob created HBASE-19922: - Summary: ProtobufUtils::PRIMITIVES is unused Key: HBASE-19922 URL: https://issues.apache.org/jira/browse/HBASE-19922 Project: HBase Issue Type: Task Components: Protobufs Reporter: Mike Drob It looks like ProtobufUtils::PRIMITIVES is never read in both the shaded and non-shaded versions of the class. Is it safe to remove? https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java#L128 We populate the map in a static initializer but never read any values from it... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19859) Update download page header for 1.1 EOL
Mike Drob created HBASE-19859: - Summary: Update download page header for 1.1 EOL Key: HBASE-19859 URL: https://issues.apache.org/jira/browse/HBASE-19859 Project: HBase Issue Type: Task Reporter: Mike Drob See example mirror: http://mirrors.ocf.berkeley.edu/apache/hbase/ They still claim that 1.1 is under active development. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19853) duplicate slf4j declaration in mapreduce pom
Mike Drob created HBASE-19853: - Summary: duplicate slf4j declaration in mapreduce pom Key: HBASE-19853 URL: https://issues.apache.org/jira/browse/HBASE-19853 Project: HBase Issue Type: Bug Components: dependencies Reporter: Mike Drob Assignee: Mike Drob -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-19784) stop-hbase gives unfriendly message when local hbase isn't running
Mike Drob created HBASE-19784:
-
Summary: stop-hbase gives unfriendly message when local hbase
isn't running
Key: HBASE-19784
URL: https://issues.apache.org/jira/browse/HBASE-19784
Project: HBase
Issue Type: Bug
Components: scripts
Reporter: Mike Drob
Assignee: Mike Drob
Fix For: 2.0.0-beta-2
{noformat}
$ bin/stop-hbase.sh
stopping hbasecat: /tmp/hbase-mdrob-master.pid: No such file or directory
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (HBASE-19776) shell gives unfriendly errors for nonexistant table
[
https://issues.apache.org/jira/browse/HBASE-19776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-19776.
---
Resolution: Duplicate
Fix Version/s: (was: 2.0.0-beta-2)
Beat to the punch by [~romil.choksi] on HBASE-19775
> shell gives unfriendly errors for nonexistant table
> ---
>
> Key: HBASE-19776
> URL: https://issues.apache.org/jira/browse/HBASE-19776
> Project: HBase
> Issue Type: Bug
>Reporter: Mike Drob
>
> When attempting operations against a non-existent table, some of the errors
> that we get are very unintuitive.
> {noformat}
> $ bin/hbase shell -n <<< "count 'no_such_table'"
> 2018-01-11 16:22:54,499 WARN [main] util.NativeCodeLoader: Unable to load
> native-hadoop library for your platform... using builtin-java classes where
> applicable
> Took 0.4709 seconds
>
>
> java exception
> ERROR Java::OrgApacheHadoopHbase::TableNotFoundException: Region of
> 'hbase:namespace,,1515709347596.af9aaa132e8baa3dcf2874ce6d93.' is
> expected in the table of 'no_such_table', but hbase:meta says it is in the
> table of 'hbase:namespace'. hbase:meta might be damaged.
> {noformat}
> Similar errors from scan, and from interactive shell instead on
> noninteractive mode.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19776) shell gives unfriendly errors for nonexistant table
Mike Drob created HBASE-19776:
-
Summary: shell gives unfriendly errors for nonexistant table
Key: HBASE-19776
URL: https://issues.apache.org/jira/browse/HBASE-19776
Project: HBase
Issue Type: Bug
Reporter: Mike Drob
Fix For: 2.0.0-beta-2
When attempting operations against a non-existent table, some of the errors
that we get are very unintuitive.
{noformat}
$ bin/hbase shell -n <<< "count 'no_such_table'"
2018-01-11 16:22:54,499 WARN [main] util.NativeCodeLoader: Unable to load
native-hadoop library for your platform... using builtin-java classes where
applicable
Took 0.4709 seconds
java exception
ERROR Java::OrgApacheHadoopHbase::TableNotFoundException: Region of
'hbase:namespace,,1515709347596.af9aaa132e8baa3dcf2874ce6d93.' is expected
in the table of 'no_such_table', but hbase:meta says it is in the table of
'hbase:namespace'. hbase:meta might be damaged.
{noformat}
Similar errors from scan, and from interactive shell instead on noninteractive
mode.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19721) Unnecessary stubbings detected in test class: TestReversedScannerCallable
Mike Drob created HBASE-19721:
-
Summary: Unnecessary stubbings detected in test class:
TestReversedScannerCallable
Key: HBASE-19721
URL: https://issues.apache.org/jira/browse/HBASE-19721
Project: HBase
Issue Type: Bug
Components: test
Reporter: Jean-Marc Spaggiari
Assignee: Mike Drob
Fix For: 2.0.0-beta-2
Found by JMS on the mailing list:
{noformat}
---
Test set: org.apache.hadoop.hbase.client.TestReversedScannerCallable
---
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.515 s <<<
FAILURE! - in org.apache.hadoop.hbase.client.TestReversedScannerCallable
unnecessary Mockito
stubbings(org.apache.hadoop.hbase.client.TestReversedScannerCallable) Time
elapsed: 0.014 s <<< ERROR!
org.mockito.exceptions.misusing.UnnecessaryStubbingException:
Unnecessary stubbings detected in test class: TestReversedScannerCallable
Clean & maintainable test code requires zero unnecessary code.
Following stubbings are unnecessary (click to navigate to relevant line of
code):
1. -> at
org.apache.hadoop.hbase.client.TestReversedScannerCallable.setUp(TestReversedScannerCallable.java:66)
2. -> at
org.apache.hadoop.hbase.client.TestReversedScannerCallable.setUp(TestReversedScannerCallable.java:68)
Please remove unnecessary stubbings. More info: javadoc for
UnnecessaryStubbingException class.
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (HBASE-19552) update hbase to use new thirdparty libs
[ https://issues.apache.org/jira/browse/HBASE-19552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved HBASE-19552. --- Resolution: Fixed > update hbase to use new thirdparty libs > --- > > Key: HBASE-19552 > URL: https://issues.apache.org/jira/browse/HBASE-19552 > Project: HBase > Issue Type: Task > Components: dependencies, thirdparty >Reporter: Mike Drob >Assignee: Mike Drob > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19552.ADDENDUM.patch, HBASE-19552.patch, > HBASE-19552.v2.patch, HBASE-19552.v3.patch, HBASE-19552.v4.BASE.patch, > HBASE-19552.v4.FULL.patch > > > When we release hbase-thirdparty next release, we will need to update our > code for the packaging change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-18722) Replace copied guava code w/ pointer to the (shaded) lib
[
https://issues.apache.org/jira/browse/HBASE-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-18722.
---
Resolution: Duplicate
> Replace copied guava code w/ pointer to the (shaded) lib
>
>
> Key: HBASE-18722
> URL: https://issues.apache.org/jira/browse/HBASE-18722
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Priority: Minor
> Labels: beginner
>
> I found a few bits of code copied from guava src:
> {code}
> ./src/main/java/org/apache/hadoop/hbase/io/LimitInputStream.java: * Copied
> from guava source code v15 (LimitedInputStream)
> ./src/main/java/org/apache/hadoop/hbase/io/LimitInputStream.java: * allows to
> be compatible with guava 11 to 15+.
> ./src/main/java/org/apache/hadoop/hbase/util/ByteBufferUtils.java: *
> from guava v21
> ./src/main/java/org/apache/hadoop/hbase/util/Bytes.java: *
> comparator from guava v21
> {code}
> We can instead point back at guava implementations now we use shaded guava
> internally. No point having it in our code base when latest guava is on
> latest CLASSPATH (This wasn't always the case; this is why the code was
> copied into hbase).
> Also, there are other copies other than the above.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (HBASE-19552) update hbase to use new thirdparty libs
[ https://issues.apache.org/jira/browse/HBASE-19552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reopened HBASE-19552: --- > update hbase to use new thirdparty libs > --- > > Key: HBASE-19552 > URL: https://issues.apache.org/jira/browse/HBASE-19552 > Project: HBase > Issue Type: Task > Components: dependencies, thirdparty >Reporter: Mike Drob >Assignee: Mike Drob > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-19552.patch, HBASE-19552.v2.patch, > HBASE-19552.v3.patch, HBASE-19552.v4.BASE.patch, HBASE-19552.v4.FULL.patch > > > When we release hbase-thirdparty next release, we will need to update our > code for the packaging change. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19655) Consider import order (shaded, thirdparty)
Mike Drob created HBASE-19655: - Summary: Consider import order (shaded, thirdparty) Key: HBASE-19655 URL: https://issues.apache.org/jira/browse/HBASE-19655 Project: HBase Issue Type: Task Reporter: Mike Drob In HBASE-19552 we insert the thirdparty imports before the shaded imports to minimize changes in a single patch. Maybe we need to have it after to preserve alphabetical order. cc: [~chia7712], [~Jan Hentschel] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19584) hbase-thirdparty L refer to items not actually in the src release
Mike Drob created HBASE-19584:
-
Summary: hbase-thirdparty L refer to items not actually in the
src release
Key: HBASE-19584
URL: https://issues.apache.org/jira/browse/HBASE-19584
Project: HBase
Issue Type: Bug
Reporter: Mike Drob
>From [~elserj]'s vote on 2.0-RC0:
{quote}
* L not entirely accurate, IMO. They state that things are included in the
src release which are not. I think it would be more appropriate to push the
relevant information down into src/main/apppended-resources for each module
(e.g. hbase-shaded-protobuf would have
src/main/appended-resources/{LICENSE,NOTICE}) which have the relevant L
content for the products being bundled. Thus, we'd have nothing in the 3rdparty
L which reflects the src release.
{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19560) create make-rc.sh for hbase-thirdparty
Mike Drob created HBASE-19560:
-
Summary: create make-rc.sh for hbase-thirdparty
Key: HBASE-19560
URL: https://issues.apache.org/jira/browse/HBASE-19560
Project: HBase
Issue Type: Task
Components: hbase-thirdparty
Reporter: Mike Drob
Make it easier to automate the process...
Some notes, may not correspond to exact commands I ran...
{noformat}
mvn clean deploy -Papache-release
git tag -s HEAD
git archive HEAD -o release.tar.gz
gpg --sign release.tar.gz
gpg --print-mds
gpg --print-md MD5
gpg --print-md SHA512
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
