[jira] [Resolved] (HBASE-23187) Update parent region state to SPLIT in meta
[ https://issues.apache.org/jira/browse/HBASE-23187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijin Bin resolved HBASE-23187. --- Fix Version/s: 2.2.3 2.3.0 3.0.0 Resolution: Fixed Pushed to master/branch-2/branch-2.2 Thanks Duo Zhang and Guangxu Cheng for reviewing. > Update parent region state to SPLIT in meta > --- > > Key: HBASE-23187 > URL: https://issues.apache.org/jira/browse/HBASE-23187 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 2.2.1 >Reporter: Lijin Bin >Assignee: Lijin Bin >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.3 > > > When split, the parent region set to SPLIT in memory, but the meta do not, so > in some circumstances will bring back the parent region. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23200) incorrect description in SortedCompactionPolicy.getNextMajorCompactTime
[ https://issues.apache.org/jira/browse/HBASE-23200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-23200. --- Resolution: Implemented Implemented by HBASE-23149 > incorrect description in SortedCompactionPolicy.getNextMajorCompactTime > --- > > Key: HBASE-23200 > URL: https://issues.apache.org/jira/browse/HBASE-23200 > Project: HBase > Issue Type: Bug > Components: Compaction >Affects Versions: master >Reporter: jackylau >Assignee: jackylau >Priority: Major > Fix For: 2.2.3 > > > // default = 24hrs > long ret = comConf.getMajorCompactionPeriod(); > but the default value is 7 days in CompactionConfiguration.java -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23199) Error populating Table-Attribute fields
[ https://issues.apache.org/jira/browse/HBASE-23199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-23199. --- Fix Version/s: 2.2.3 2.3.0 3.0.0 Resolution: Fixed Pushed to branch2.2+. Thank [~kpalanisamy] for contributing. > Error populating Table-Attribute fields > --- > > Key: HBASE-23199 > URL: https://issues.apache.org/jira/browse/HBASE-23199 > Project: HBase > Issue Type: Bug > Components: master, UI >Affects Versions: 3.0.0 >Reporter: Karthik Palanisamy >Assignee: Karthik Palanisamy >Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.3 > > Attachments: Screen Shot 2019-10-21 at 3.25.40 PM.png > > > if quota is enabled, then we fetch table and namespace quota info. It is not > necessary both table and namespace will have a quota set. Sometimes, users > only have table level quota or namespace level quota or both un-set. So we > must add Quota "null" check before getting Throttle info(Limit, Type, > TimeUnit, Scope). > > !Screen Shot 2019-10-21 at 3.25.40 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23211) Table UI showed exception message when Quota is enabled
[ https://issues.apache.org/jira/browse/HBASE-23211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangxu Cheng resolved HBASE-23211. --- Resolution: Duplicate > Table UI showed exception message when Quota is enabled > --- > > Key: HBASE-23211 > URL: https://issues.apache.org/jira/browse/HBASE-23211 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 2.2.1 >Reporter: xinxin fan >Priority: Major > Attachments: image-2019-10-24-10-40-45-152.png > > > org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:361)org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1780)org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1391)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1767)org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:513)org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)org.eclipse.jetty.server.Server.handle(Server.java:539)org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333)org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283)org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [ANNOUNCE] Please welcome Sakthi to the Apache HBase PMC
Congratulations and welcome, Sakthi! On Wed, Oct 23, 2019 at 1:14 PM Sean Busbey wrote: > On behalf of the Apache HBase PMC I am pleased to announce that > Sakthi has accepted our invitation to become a PMC member on the > HBase project. We appreciate Sakthi stepping up to take more > responsibility in the HBase project. > > Please join me in welcoming Jan to the HBase PMC! > > > > As a reminder, if anyone would like to nominate another person as a > committer or PMC member, even if you are not currently a committer or > PMC member, you can always drop a note to priv...@hbase.apache.org to > let us know. > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
[jira] [Resolved] (HBASE-23226) Backport HBASE-22460 (Reopen a region if store reader references may have leaked) to branch-1
[ https://issues.apache.org/jira/browse/HBASE-23226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Kyle Purtell resolved HBASE-23226. - Fix Version/s: (was: 1.6.0) Resolution: Duplicate > Backport HBASE-22460 (Reopen a region if store reader references may have > leaked) to branch-1 > - > > Key: HBASE-23226 > URL: https://issues.apache.org/jira/browse/HBASE-23226 > Project: HBase > Issue Type: Sub-task >Affects Versions: 1.5.0, 1.3.6, 1.4.11 >Reporter: Andrew Kyle Purtell >Priority: Major > > Backport parent change to branch-1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23225) Error building shaded-client: duplicate entry: META-INF/.../ObjectCodec
[
https://issues.apache.org/jira/browse/HBASE-23225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-23225.
-
Resolution: Cannot Reproduce
After some other work and builds returning to this to try and repo with -X was
unsuccessful. Whatever may have happened before the Maven black magic voodoo is
working again for me
> Error building shaded-client: duplicate entry: META-INF/.../ObjectCodec
>
>
> Key: HBASE-23225
> URL: https://issues.apache.org/jira/browse/HBASE-23225
> Project: HBase
> Issue Type: Bug
> Environment: $ mvn --version
> Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
> 2019-08-27T08:06:16-07:00)
> Maven home: /usr/local/Cellar/maven/3.6.2/libexec
> Java version: 1.8.0_232, vendor: Azul Systems, Inc., runtime:
> /Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.14.6", arch: "x86_64", family: "mac"
>Reporter: Andrew Kyle Purtell
>Priority: Major
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.1:shade
> (aggregate-into-a-jar-with-relocated-third-parties) on project
> hbase-shaded-client:
> Error creating shaded jar:
> duplicate entry:
> META-INF/services/org.apache.hadoop.hbase.shaded.com.fasterxml.jackson.core.ObjectCodec
>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23226) Backport HBASE-22460 (Reopen a region if store reader references may have leaked) to branch-1
Andrew Kyle Purtell created HBASE-23226: --- Summary: Backport HBASE-22460 (Reopen a region if store reader references may have leaked) to branch-1 Key: HBASE-23226 URL: https://issues.apache.org/jira/browse/HBASE-23226 Project: HBase Issue Type: Sub-task Affects Versions: 1.4.11, 1.3.6, 1.5.0 Reporter: Andrew Kyle Purtell Fix For: 1.6.0 Backport parent change to branch-1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23225) Error building shaded-client: duplicate entry: META-INF/.../ObjectCodec
Andrew Kyle Purtell created HBASE-23225:
---
Summary: Error building shaded-client: duplicate entry:
META-INF/.../ObjectCodec
Key: HBASE-23225
URL: https://issues.apache.org/jira/browse/HBASE-23225
Project: HBase
Issue Type: Bug
Reporter: Andrew Kyle Purtell
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.1.1:shade
(aggregate-into-a-jar-with-relocated-third-parties) on project
hbase-shaded-client:
Error creating shaded jar:
duplicate entry:
META-INF/services/org.apache.hadoop.hbase.shaded.com.fasterxml.jackson.core.ObjectCodec
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23222) Better logging and mitigation for MOB compaction failures
[ https://issues.apache.org/jira/browse/HBASE-23222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-23222. - Fix Version/s: 2.2.3 2.1.8 2.3.0 3.0.0 Release Note: The MOB compaction process in the HBase Master now logs more about its activity. In the event that you run into the problems described in HBASE-22075, there is a new HFileCleanerDelegate that will stop all removal of MOB hfiles from the archive area. It can be configured by adding `org.apache.hadoop.hbase.mob.ManualMobMaintHFileCleaner` to the list configured for `hbase.master.hfilecleaner.plugins`. This new cleaner delegate will cause your archive area to grow unbounded; you will have to manually prune files which may be prohibitively complex. Consider if your use case will allow you to mitigate by disabling mob compactions instead. Caveats: * Be sure the list of cleaner delegates still includes the default cleaners you will likely need: ttl, snapshot, and hlink. * Be mindful that if you enable this cleaner delegate then there will be *no* automated process for removing these mob hfiles. You should see a single region per table in `%hbase_root%/archive` that accumulates files over time. You will have to determine which of these files are safe or not to remove. * You should list this cleaner delegate after the snapshot and hlink delegates so that you can enable sufficient logging to determine when an archived mob hfile is needed by those subsystems. When set to `TRACE` logging, the CleanerChore logger will include archive retention decision justifications. * If your use case creates a large number of uniquely named tables, this new delegate will cause memory pressure on the master. Resolution: Fixed > Better logging and mitigation for MOB compaction failures > - > > Key: HBASE-23222 > URL: https://issues.apache.org/jira/browse/HBASE-23222 > Project: HBase > Issue Type: Bug > Components: mob >Affects Versions: 2.1.0, 2.0.0, 2.2.0 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Critical > Fix For: 3.0.0, 2.3.0, 2.1.8, 2.2.3 > > > Some logging and mitigation options for MOB dataloss issues described in > HBASE-22075. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Request to add Supporting Project
Hi Manu, Thanks for the contribution. You can make the addition yourself: please submit a PR :) The file that manages the page in question is https://github.com/apache/hbase/blob/master/src/site/xdoc/supportingprojects.xml . Thanks, Nick On Sun, Oct 27, 2019 at 3:53 PM Manu M. wrote: > Dear HBase team, > > We at Flipkart are using a light-weight ORM wrapper on top of hbase-client: > https://github.com/flipkart-incubator/hbase-orm (open source, Apache 2.0 > license) > > It helps Java applications interact with HBase in an object-oriented manner > (by encapsulating HBase's Get, Put, Delete, Append and other classes). > > It's published on Maven Central: > > https://search.maven.org/search?q=g:com.flipkart%20AND%20a:hbase-object-mapper&core=gav > > Requesting you to add the above project here: > https://hbase.apache.org/supportingprojects.html > > We believe this will greatly help other software developers using Apache > HBase by expediting their software development. > > -- > Manu M. > Software Architect > https://www.linkedin.com/in/manumanjunath/ > > -- > > > > > *-* > > > *This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they are > addressed. If you have received this email in error, please notify the > system manager. This message contains confidential information and is > intended only for the individual named. If you are not the named > addressee, > you should not disseminate, distribute or copy this email. Please notify > the sender immediately by email if you have received this email by mistake > and delete this email from your system. If you are not the intended > recipient, you are notified that disclosing, copying, distributing or > taking any action in reliance on the contents of this information is > strictly prohibited.* > > > > *Any views or opinions presented in this > email are solely those of the author and do not necessarily represent > those > of the organization. Any information on shares, debentures or similar > instruments, recommended product pricing, valuations and the like are for > information purposes only. It is not meant to be an instruction or > recommendation, as the case may be, to buy or to sell securities, > products, > services nor an offer to buy or sell securities, products or services > unless specifically stated to be so on behalf of the Flipkart group. > Employees of the Flipkart group of companies are expressly required not to > make defamatory statements and not to infringe or authorise any > infringement of copyright or any other legal right by email > communications. > Any such communication is contrary to organizational policy and outside > the > scope of the employment of the individual concerned. The organization will > not accept any liability in respect of such communication, and the > employee > responsible will be personally liable for any damages or other liability > arising.* > > > > *Our organization accepts no liability for the > content of this email, or for the consequences of any actions taken on the > basis of the information *provided,* unless that information is > subsequently confirmed in writing. If you are not the intended recipient, > you are notified that disclosing, copying, distributing or taking any > action in reliance on the contents of this information is strictly > prohibited.* > > > > _-_ > >
[jira] [Reopened] (HBASE-23194) Remove unused methods from TokenUtil
[ https://issues.apache.org/jira/browse/HBASE-23194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey reopened HBASE-23194: - Please revert the removal of methods in TokenUtil that were deprecated in HBASE-22027. TokenUtil is still IA.Public and those deprecation warnings haven't even made it into a HBase 2.y release yet. They shouldn't be removed until HBase 4.0. > Remove unused methods from TokenUtil > > > Key: HBASE-23194 > URL: https://issues.apache.org/jira/browse/HBASE-23194 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Viraj Jasani >Assignee: Viraj Jasani >Priority: Minor > Fix For: 3.0.0 > > > Cleanup TokenUtil: remove unused methods from TokenUtil. For util methods to > obtain Authentication tokens, ClientTokenUtil should be used where possible > (in absence of hbase-server dependency) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-15519) Add per-user metrics
[ https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi resolved HBASE-15519. --- Resolution: Fixed Pushed addendum to branch-2 and master. > Add per-user metrics > - > > Key: HBASE-15519 > URL: https://issues.apache.org/jira/browse/HBASE-15519 > Project: HBase > Issue Type: Sub-task > Components: metrics >Affects Versions: 1.2.0 >Reporter: Enis Soztutar >Assignee: Ankit Singhal >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-15519.master.003.patch, hbase-15519_v0.patch, > hbase-15519_v1.patch, hbase-15519_v1.patch, hbase-15519_v2.patch > > > Per-user metrics will be useful in multi-tenant cases where we can emit > number of requests, operations, num RPCs etc at the per-user aggregate level > per regionserver. We currently have throttles per user, but no way to monitor > resource usage per-user. > Looking at these metrics, operators can adjust throttles, do capacity > planning, etc per-user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-23224) Delete the TODO ("get rid of allocations") tag in the WALProcedureStore class
lixiaobao created HBASE-23224:
-
Summary: Delete the TODO ("get rid of allocations") tag in the
WALProcedureStore class
Key: HBASE-23224
URL: https://issues.apache.org/jira/browse/HBASE-23224
Project: HBase
Issue Type: Improvement
Components: proc-v2
Affects Versions: 2.2.0, 2.1.0, 1.3.0, 1.2.0
Reporter: lixiaobao
Assignee: lixiaobao
Fix For: 3.0.0
{code:java}
// update webui circular buffers (TODO: get rid of allocations)
final SyncMetrics syncMetrics = new SyncMetrics();
syncMetrics.timestamp = currentTs;
syncMetrics.syncWaitMs = syncWaitMs;
syncMetrics.syncedEntries = slotIndex;
syncMetrics.totalSyncedBytes = totalSyncedToStore;
syncMetrics.syncedPerSec = syncedPerSec;
syncMetricsQueue.add(syncMetrics);
{code}
Delete the TODO tag.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-23217) Set version as 2.2.3-SNAPSHOT in branch-2.2
[ https://issues.apache.org/jira/browse/HBASE-23217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi resolved HBASE-23217. --- Assignee: Duo Zhang Resolution: Fixed > Set version as 2.2.3-SNAPSHOT in branch-2.2 > --- > > Key: HBASE-23217 > URL: https://issues.apache.org/jira/browse/HBASE-23217 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-15519) Add per-user metrics
[ https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi reopened HBASE-15519: --- Reopening for error prone issue. > Add per-user metrics > - > > Key: HBASE-15519 > URL: https://issues.apache.org/jira/browse/HBASE-15519 > Project: HBase > Issue Type: Sub-task > Components: metrics >Affects Versions: 1.2.0 >Reporter: Enis Soztutar >Assignee: Ankit Singhal >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-15519.master.003.patch, hbase-15519_v0.patch, > hbase-15519_v1.patch, hbase-15519_v1.patch, hbase-15519_v2.patch > > > Per-user metrics will be useful in multi-tenant cases where we can emit > number of requests, operations, num RPCs etc at the per-user aggregate level > per regionserver. We currently have throttles per user, but no way to monitor > resource usage per-user. > Looking at these metrics, operators can adjust throttles, do capacity > planning, etc per-user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [ANNOUNCE] Please welcome Balazs Meszaros to the Apache HBase PMC
Thank you very much! Balazs On Mon, Oct 28, 2019 at 3:45 AM Reid Chan wrote: > Congratulations and welcome, Balazs! > > > > > -- > > Best regards, > R.C > > > > > From: Sean Busbey > Sent: 24 October 2019 22:35 > To: dev; Hbase-User > Subject: [ANNOUNCE] Please welcome Balazs Meszaros to the Apache HBase PMC > > On behalf of the Apache HBase PMC I am pleased to announce that > Balazs Meszaros has accepted our invitation to become a PMC member on the > HBase project. We appreciate Balazs stepping up to take more > responsibility in the HBase project. > > Please join me in welcoming Balazs to the HBase PMC! > > > > As a reminder, if anyone would like to nominate another person as a > committer or PMC member, even if you are not currently a committer or > PMC member, you can always drop a note to priv...@hbase.apache.org to > let us know. >
