[jira] [Created] (HBASE-27315) Add timeout to JavaRegexEngine
Minwoo Kang created HBASE-27315: --- Summary: Add timeout to JavaRegexEngine Key: HBASE-27315 URL: https://issues.apache.org/jira/browse/HBASE-27315 Project: HBase Issue Type: New Feature Reporter: Minwoo Kang Assignee: Minwoo Kang Java regular expression engine is based on backtracking. Thus, a malicious regular expression may result in a ReDoS. When ReDoS occurs in the HBase, the region server's handler is occupied as a result it cannot process the user's request. It would be nice to have a timeout for system protection. The engine does not have timeout. The charAt method is called during pattern matching, and the charAt method checks if it is timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: How to store keystore/truststore password securely?
In real production deployment, usually we will store an encrypted password in the configuration file, and then decrypt it after loading, to actually use it. And how to get the decryption will depend on the environment. On cloud VMs, usually you can use an encryption service to decrypt the password. On K8s, you can mount the key using secret. So maybe we should abstract a decryption interface, so users could implement it on their own to find a suitable way to decrypt the encrypted password? Andor Molnar 于2022年8月23日周二 05:55写道： > > Hi team, > > Netty TLS support is now merged into master and branch-2 branches. > Currently keystore/truststore passwords can only be stored in hbase- > site.xml which is not the best approach from security perspective. > > In the docs review Sergey Soldatov mentioned ( > https://github.com/apache/hbase/pull/4717/files#r951768699) an approach > in HDFS where password can be stored in special files or in environment > variables. > > Sergey, would you please point me to the details of that > implementation? Sounds like it would be acceptable for HBase too. > > Is there any other idea that folks could recommend? > > Thanks, > Andor > > >
[jira] [Created] (HBASE-27314) Make index block be customized and configured
Lijin Bin created HBASE-27314: - Summary: Make index block be customized and configured Key: HBASE-27314 URL: https://issues.apache.org/jira/browse/HBASE-27314 Project: HBase Issue Type: New Feature Reporter: Lijin Bin Current the index block use a flat structure and can not support other format, we can explore other structure to use it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] HBase 2.4.14 release candidate (RC0) is available
Sorry but -1. I replied on HBASE-27301 that the issue should be included in 2.4.14 but got no response. And I checked the CHANGES.md, there is no HBASE-27301 in it, neither in 2.4.13 nor 2.4.14. Please fix this issue and publish an RC again. Thanks. Huaxiang Sun 于2022年8月23日周二 07:15写道： > > Please vote on this Apache hbase release candidate, > > hbase-2.4.14RC0 > > > The VOTE will remain open for at least 72 hours. > > > [ ] +1 Release this package as Apache hbase 2.4.14 > > [ ] -1 Do not release this package because ... > > > The tag to be voted on is 2.4.14RC0: > > > https://github.com/apache/hbase/tree/2.4.14RC0 > > > This tag currently points to git reference > > > f507fb71c6724ed44eb4ac25bbdd3e35b2441a1a > > > The release files, including signatures, digests, as well as CHANGES.md > > and RELEASENOTES.md included in this RC can be found at: > > > https://dist.apache.org/repos/dist/dev/hbase/2.4.14RC0/ > > > Maven artifacts are available in a staging repository at: > > > https://repository.apache.org/content/repositories/orgapachehbase-1493/ > > > Artifacts were signed with the 0x117C835E key which can be found in: > > > https://downloads.apache.org/hbase/KEYS > > > To learn more about Apache hbase, please see > > > http://hbase.apache.org/ > > > Thanks, > > Your HBase Release Manager
Re: Request to join the HBase Slack channel
Sent On Mon, Aug 22, 2022 at 8:44 PM Henry Sowell wrote: > Good evening, > > Following-up here, can I join the Hbase slack channel? I'm excited to > participate. > > Thank you! > > Henry > > On Wed, Aug 17, 2022 at 5:03 PM Henry Sowell > wrote: > > > Hello! > > > > Can I please have access to the HBase slack channel? > > > > Thank you, > > > > Henry > > >
Re: Request to join the HBase Slack channel
Good evening, Following-up here, can I join the Hbase slack channel? I'm excited to participate. Thank you! Henry On Wed, Aug 17, 2022 at 5:03 PM Henry Sowell wrote: > Hello! > > Can I please have access to the HBase slack channel? > > Thank you, > > Henry >
[VOTE] HBase 2.4.14 release candidate (RC0) is available
Please vote on this Apache hbase release candidate, hbase-2.4.14RC0 The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache hbase 2.4.14 [ ] -1 Do not release this package because ... The tag to be voted on is 2.4.14RC0: https://github.com/apache/hbase/tree/2.4.14RC0 This tag currently points to git reference f507fb71c6724ed44eb4ac25bbdd3e35b2441a1a The release files, including signatures, digests, as well as CHANGES.md and RELEASENOTES.md included in this RC can be found at: https://dist.apache.org/repos/dist/dev/hbase/2.4.14RC0/ Maven artifacts are available in a staging repository at: https://repository.apache.org/content/repositories/orgapachehbase-1493/ Artifacts were signed with the 0x117C835E key which can be found in: https://downloads.apache.org/hbase/KEYS To learn more about Apache hbase, please see http://hbase.apache.org/ Thanks, Your HBase Release Manager
How to store keystore/truststore password securely?
Hi team, Netty TLS support is now merged into master and branch-2 branches. Currently keystore/truststore passwords can only be stored in hbase- site.xml which is not the best approach from security perspective. In the docs review Sergey Soldatov mentioned ( https://github.com/apache/hbase/pull/4717/files#r951768699) an approach in HDFS where password can be stored in special files or in environment variables. Sergey, would you please point me to the details of that implementation? Sounds like it would be acceptable for HBase too. Is there any other idea that folks could recommend? Thanks, Andor
[jira] [Created] (HBASE-27313) Persist list of Hfiles names for which prefetch is done
Shanmukha Haripriya Kota created HBASE-27313: Summary: Persist list of Hfiles names for which prefetch is done Key: HBASE-27313 URL: https://issues.apache.org/jira/browse/HBASE-27313 Project: HBase Issue Type: Improvement Components: BucketCache Reporter: Shanmukha Haripriya Kota Persist list of Hfiles names for which prefetch is completed when persist for in-memory bucket cache mapping state is enabled. We need to persist the Set, which contains a list of all the HFiles for which the prefetch has completed along with the In-memory state of the bucket cache so that when we restart and if any prefetch is scheduled again for the same HFile and we already have the in-memory state retrieved, we can skip the prefetch for it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Aiming for 2.5.0RC1 this Friday
So I think there's a permissions issue. https://issues.apache.org/jira/browse/HBASE-27312 On Mon, Aug 22, 2022 at 5:28 PM Andrew Purtell wrote: > I spent a significant amount of time fiddling with gpg-agent until my > build VM could reliably run the build script. Any usability improvements we > can make there will be helpful to new RMs. > > Great to see the progress here. > (Hello from Nassau!) > > > On Aug 22, 2022, at 6:07 AM, Nick Dimiduk wrote: > > > > On Mon, Aug 22, 2022 at 3:57 AM 张铎(Duo Zhang) > wrote: > > > >> I've merged all the error prone PRs opened by Andrew. > >> > > > > Great! > > > > And for HBASE-27297, I suggest we just reopen HBASE-26882 and use that > >> issue to land the change on branch-2.5. No need to open a new issue. > >> > > > > +1 > > > > FYI, I've been having issues with gpg-agent and signing the release > > candidate. Stack and Huaxiang are helping me out, I have some new > > suggestions to try today. > > > > It has not been my intention to be opaque to the community -- I merely > > assumed it was some issue on my machine and I'd find a version mismatch > or > > something. That was most of last week. If I'm still unsuccessful at the > end > > of day today, I'll file a JIRA with the details of the issue. > > > > Yours, > > Nick > > > > Tak Lon (Stephen) Wu 于2022年8月13日周六 03:05写道： > >>> > >>> if we can still accept commits before the next RC vote, I'd like to > have > >>> HBASE-27297 (backporting HBASE-26810) to be part of the release. > >>> > >>> Thanks, > >>> Stephen > >>> > >>> On Fri, Aug 12, 2022 at 9:35 AM Nick Dimiduk > >> wrote: > >>> > Hi team, > > Let's get some more eyes on the open ErrorProne issues, try to land > the > ones that have patches available. Looks like the MOB fixes are close > >> too. > > I'll dust off my signing keys and find some hardware. Maybe we can > have > another RC on Monday or Tuesday. > > Thanks, > Nick > > On Thu, Aug 11, 2022 at 4:35 PM Peter Somogyi > >> wrote: > > > I'd like to include HBASE-27281 if I'm not too late. This is to keep > >> API > > compatibility. > > > > On Thu, Aug 11, 2022 at 5:26 AM 张铎(Duo Zhang) >>> > > wrote: > > > >> OK, no problem :) > >> > >> Andrew Purtell 于2022年8月11日周四 10:48写道： > >>> > >>> Also I only got about halfway through the modules. hbase-server > >> may > > have > >> many findings. Will get to it when back. > >>> > On Aug 10, 2022, at 7:46 PM, Andrew Purtell < > > andrew.purt...@gmail.com> > >> wrote: > > Those error prone cleanups don’t change functionality so I > >> think > > they > >> can go in any time. 2.5.1? Etc > > > On Aug 10, 2022, at 7:16 PM, 张铎 > >> wrote: > > > > This is still some error prone cleanup PR pending. > > > > I think the hbase-http and hbase-it are good to go, I could > >> help > > merging them. The hbase-common and hbase-examples still need > >> more > > reviews. > > > > But maybe this could done after the 2.5.0 is out? Since they > >> are > not > > likely to touch the public API or introduce big refactoring. > > > > > > Andrew Purtell 于2022年8月11日周四 05:32写道： > > > >> > >> Please, do. > >> > >>> On Wed, Aug 10, 2022 at 2:20 PM Nick Dimiduk < > ndimi...@apache.org > >> > >> wrote: > >>> > >>> I can give it a go, if you’d like. No problem from my > perspective. > >> I’m also > >>> happy to help along someone new who’d have a go at it, if > there’s > >> another > >>> volunteer. Thanks for pushing, Andrew. > >>> > >>> -n > >>> > >>> On Wed, Aug 10, 2022 at 19:28 Andrew Purtell < > >> andrew.purt...@gmail.com> > >>> wrote: > >>> > By fixVersion is what I use. > > We got heads down on something time critical at my > >> employer. I > >> also am > going on vacation next week for two weeks. Does someone > >> want to > >> volunteer > to spin the next RC? Otherwise I can pick this back up at > >> the > end > >> of the > month. There would be no reason for such a delay at this > >> point > >> other than > RM availability. > > > > On Aug 10, 2022, at 9:12 AM, Bryan Beaudreault < > >>> bbeaudrea...@hubspot.com.invalid> > wrote: > > > > Are there any remaining blockers for 2.5.0? Also if > >> there's > an > >> easy > >>> way > to > > view this in JIRA (beyond a custom search for > fixVersion=2.5.0) > >> please > let > > me know. > > > >> On Thu, Jul 14, 2022 at 9:40
[jira] [Created] (HBASE-27312) Update create-release to work with maven-gpg-plugin-3.0.1 and gnupg >= 2.1.x
Nick Dimiduk created HBASE-27312: Summary: Update create-release to work with maven-gpg-plugin-3.0.1 and gnupg >= 2.1.x Key: HBASE-27312 URL: https://issues.apache.org/jira/browse/HBASE-27312 Project: HBase Issue Type: Task Components: build Reporter: Nick Dimiduk Fix For: 3.0.0-alpha-4 I've run into some trouble with `create-release`. The issue seems to come down to changes to maven-release-plugin via MGPG-79 and working with the `agent-extra-socket`. After MGPG-79, maven-release-plugin uses `--pinentry-mode error` in a non-interactive setting, which is not permissible over the restricted permissions exposed via `agent-extra-socket`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Aiming for 2.5.0RC1 this Friday
I spent a significant amount of time fiddling with gpg-agent until my build VM could reliably run the build script. Any usability improvements we can make there will be helpful to new RMs. Great to see the progress here. (Hello from Nassau!) > On Aug 22, 2022, at 6:07 AM, Nick Dimiduk wrote: > > On Mon, Aug 22, 2022 at 3:57 AM 张铎(Duo Zhang) wrote: > >> I've merged all the error prone PRs opened by Andrew. >> > > Great! > > And for HBASE-27297, I suggest we just reopen HBASE-26882 and use that >> issue to land the change on branch-2.5. No need to open a new issue. >> > > +1 > > FYI, I've been having issues with gpg-agent and signing the release > candidate. Stack and Huaxiang are helping me out, I have some new > suggestions to try today. > > It has not been my intention to be opaque to the community -- I merely > assumed it was some issue on my machine and I'd find a version mismatch or > something. That was most of last week. If I'm still unsuccessful at the end > of day today, I'll file a JIRA with the details of the issue. > > Yours, > Nick > > Tak Lon (Stephen) Wu 于2022年8月13日周六 03:05写道： >>> >>> if we can still accept commits before the next RC vote, I'd like to have >>> HBASE-27297 (backporting HBASE-26810) to be part of the release. >>> >>> Thanks, >>> Stephen >>> >>> On Fri, Aug 12, 2022 at 9:35 AM Nick Dimiduk >> wrote: >>> Hi team, Let's get some more eyes on the open ErrorProne issues, try to land the ones that have patches available. Looks like the MOB fixes are close >> too. I'll dust off my signing keys and find some hardware. Maybe we can have another RC on Monday or Tuesday. Thanks, Nick On Thu, Aug 11, 2022 at 4:35 PM Peter Somogyi >> wrote: > I'd like to include HBASE-27281 if I'm not too late. This is to keep >> API > compatibility. > > On Thu, Aug 11, 2022 at 5:26 AM 张铎(Duo Zhang) >> > wrote: > >> OK, no problem :) >> >> Andrew Purtell 于2022年8月11日周四 10:48写道： >>> >>> Also I only got about halfway through the modules. hbase-server >> may > have >> many findings. Will get to it when back. >>> On Aug 10, 2022, at 7:46 PM, Andrew Purtell < > andrew.purt...@gmail.com> >> wrote: Those error prone cleanups don’t change functionality so I >> think > they >> can go in any time. 2.5.1? Etc > On Aug 10, 2022, at 7:16 PM, 张铎 >> wrote: > > This is still some error prone cleanup PR pending. > > I think the hbase-http and hbase-it are good to go, I could >> help > merging them. The hbase-common and hbase-examples still need >> more > reviews. > > But maybe this could done after the 2.5.0 is out? Since they >> are not > likely to touch the public API or introduce big refactoring. > > > Andrew Purtell 于2022年8月11日周四 05:32写道： > >> >> Please, do. >> >>> On Wed, Aug 10, 2022 at 2:20 PM Nick Dimiduk < ndimi...@apache.org >> >> wrote: >>> >>> I can give it a go, if you’d like. No problem from my perspective. >> I’m also >>> happy to help along someone new who’d have a go at it, if there’s >> another >>> volunteer. Thanks for pushing, Andrew. >>> >>> -n >>> >>> On Wed, Aug 10, 2022 at 19:28 Andrew Purtell < >> andrew.purt...@gmail.com> >>> wrote: >>> By fixVersion is what I use. We got heads down on something time critical at my >> employer. I >> also am going on vacation next week for two weeks. Does someone >> want to >> volunteer to spin the next RC? Otherwise I can pick this back up at >> the end >> of the month. There would be no reason for such a delay at this >> point >> other than RM availability. > On Aug 10, 2022, at 9:12 AM, Bryan Beaudreault < >>> bbeaudrea...@hubspot.com.invalid> wrote: > > Are there any remaining blockers for 2.5.0? Also if >> there's an >> easy >>> way to > view this in JIRA (beyond a custom search for fixVersion=2.5.0) >> please let > me know. > >> On Thu, Jul 14, 2022 at 9:40 PM Bryan Beaudreault < bbeaudrea...@hubspot.com> >> wrote: >> >> Sounds good. Thanks all for the consideration. >> >> On Thu, Jul 14, 2022 at 7:39 PM Andrew Purtell < >> apurt...@apache.org> >> wrote: >> >>> HBASE-27204 was filed because we are pushing on RPC. >> This is >> good >>> progress.
[jira] [Created] (HBASE-27311) The implementation of syncReplicationPeerLock is incomplete
Duo Zhang created HBASE-27311: - Summary: The implementation of syncReplicationPeerLock is incomplete Key: HBASE-27311 URL: https://issues.apache.org/jira/browse/HBASE-27311 Project: HBase Issue Type: Bug Components: proc-v2, Replication Reporter: Duo Zhang Assignee: Duo Zhang We also need to restore the state after loading the procedure after master restarts. And we'd better not just let the PEWorker hand there on waiting the semaphore, better to let the procedure suspend and retry later. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27305) add an option to skip file splitting when bulkload hfiles
[ https://issues.apache.org/jira/browse/HBASE-27305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27305. --- Fix Version/s: 2.5.0 Hadoop Flags: Reviewed Release Note: Add a 'hbase.loadincremental.fail.if.need.split.hfile' configuration. If set to true, th bulk load operation will fail immediately if we need to split the hfiles. This can be used to prevent unexpected time consuming bulk load operation. Resolution: Fixed Pushed to branch-2.5+. Thanks [~frostruan] for contributing! > add an option to skip file splitting when bulkload hfiles > - > > Key: HBASE-27305 > URL: https://issues.apache.org/jira/browse/HBASE-27305 > Project: HBase > Issue Type: Improvement > Components: tooling >Affects Versions: 3.0.0-alpha-3 >Reporter: ruanhui >Assignee: ruanhui >Priority: Minor > Fix For: 2.5.0, 3.0.0-alpha-4 > > > When bulkload hfiles, if the key range of the hfile does not match the key > range of the region, the BulkLoadHFilesTool will split hfile to fit make the > key range of the new file match the key range of the region. If there are > many files to be split, the load on the BulkLoadHFilesTool will be very high. > Sometimes we want to avoid this situation, just directly fail and regenerate > new hfiles. Here we try to introduce a new option, When the above problem is > encountered, an exception will be thrown and let the upper client handle it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (HBASE-27104) Add a tool command list_unknownservers
[ https://issues.apache.org/jira/browse/HBASE-27104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-27104. --- Fix Version/s: 2.5.0 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.5+. Thanks [~heliangjun] for contributing! > Add a tool command list_unknownservers > -- > > Key: HBASE-27104 > URL: https://issues.apache.org/jira/browse/HBASE-27104 > Project: HBase > Issue Type: New Feature > Components: master >Affects Versions: 3.0.0-alpha-3 >Reporter: LiangJun He >Assignee: LiangJun He >Priority: Major > Fix For: 2.5.0, 3.0.0-alpha-4 > > Attachments: image-2022-06-10-15-49-33-178.png > > > Sometimes, RegionServer will become an unknown server. It is necessary to add > a tool command to list unknown servers. > !image-2022-06-10-15-49-33-178.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Aiming for 2.5.0RC1 this Friday
On Mon, Aug 22, 2022 at 3:57 AM 张铎(Duo Zhang) wrote: > I've merged all the error prone PRs opened by Andrew. > Great! And for HBASE-27297, I suggest we just reopen HBASE-26882 and use that > issue to land the change on branch-2.5. No need to open a new issue. > +1 FYI, I've been having issues with gpg-agent and signing the release candidate. Stack and Huaxiang are helping me out, I have some new suggestions to try today. It has not been my intention to be opaque to the community -- I merely assumed it was some issue on my machine and I'd find a version mismatch or something. That was most of last week. If I'm still unsuccessful at the end of day today, I'll file a JIRA with the details of the issue. Yours, Nick Tak Lon (Stephen) Wu 于2022年8月13日周六 03:05写道： > > > > if we can still accept commits before the next RC vote, I'd like to have > > HBASE-27297 (backporting HBASE-26810) to be part of the release. > > > > Thanks, > > Stephen > > > > On Fri, Aug 12, 2022 at 9:35 AM Nick Dimiduk > wrote: > > > > > Hi team, > > > > > > Let's get some more eyes on the open ErrorProne issues, try to land the > > > ones that have patches available. Looks like the MOB fixes are close > too. > > > > > > I'll dust off my signing keys and find some hardware. Maybe we can have > > > another RC on Monday or Tuesday. > > > > > > Thanks, > > > Nick > > > > > > On Thu, Aug 11, 2022 at 4:35 PM Peter Somogyi > wrote: > > > > > > > I'd like to include HBASE-27281 if I'm not too late. This is to keep > API > > > > compatibility. > > > > > > > > On Thu, Aug 11, 2022 at 5:26 AM 张铎(Duo Zhang) > > > > > wrote: > > > > > > > > > OK, no problem :) > > > > > > > > > > Andrew Purtell 于2022年8月11日周四 10:48写道： > > > > > > > > > > > > Also I only got about halfway through the modules. hbase-server > may > > > > have > > > > > many findings. Will get to it when back. > > > > > > > > > > > > > On Aug 10, 2022, at 7:46 PM, Andrew Purtell < > > > > andrew.purt...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > Those error prone cleanups don’t change functionality so I > think > > > > they > > > > > can go in any time. 2.5.1? Etc > > > > > > > > > > > > > >> On Aug 10, 2022, at 7:16 PM, 张铎 > wrote: > > > > > > >> > > > > > > >> This is still some error prone cleanup PR pending. > > > > > > >> > > > > > > >> I think the hbase-http and hbase-it are good to go, I could > help > > > > > > >> merging them. The hbase-common and hbase-examples still need > more > > > > > > >> reviews. > > > > > > >> > > > > > > >> But maybe this could done after the 2.5.0 is out? Since they > are > > > not > > > > > > >> likely to touch the public API or introduce big refactoring. > > > > > > >> > > > > > > >> > > > > > > >> Andrew Purtell 于2022年8月11日周四 05:32写道： > > > > > > >> > > > > > > >>> > > > > > > >>> Please, do. > > > > > > >>> > > > > > > On Wed, Aug 10, 2022 at 2:20 PM Nick Dimiduk < > > > ndimi...@apache.org > > > > > > > > > > wrote: > > > > > > > > > > > > I can give it a go, if you’d like. No problem from my > > > perspective. > > > > > I’m also > > > > > > happy to help along someone new who’d have a go at it, if > > > there’s > > > > > another > > > > > > volunteer. Thanks for pushing, Andrew. > > > > > > > > > > > > -n > > > > > > > > > > > > On Wed, Aug 10, 2022 at 19:28 Andrew Purtell < > > > > > andrew.purt...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > By fixVersion is what I use. > > > > > > > > > > > > > > We got heads down on something time critical at my > employer. I > > > > > also am > > > > > > > going on vacation next week for two weeks. Does someone > want to > > > > > volunteer > > > > > > > to spin the next RC? Otherwise I can pick this back up at > the > > > end > > > > > of the > > > > > > > month. There would be no reason for such a delay at this > point > > > > > other than > > > > > > > RM availability. > > > > > > > > > > > > > > > > > > > > >> On Aug 10, 2022, at 9:12 AM, Bryan Beaudreault < > > > > > > bbeaudrea...@hubspot.com.invalid> > > > > > > > wrote: > > > > > > >> > > > > > > >> Are there any remaining blockers for 2.5.0? Also if > there's > > > an > > > > > easy > > > > > > way > > > > > > > to > > > > > > >> view this in JIRA (beyond a custom search for > > > fixVersion=2.5.0) > > > > > please > > > > > > > let > > > > > > >> me know. > > > > > > >> > > > > > > >>> On Thu, Jul 14, 2022 at 9:40 PM Bryan Beaudreault < > > > > > > > bbeaudrea...@hubspot.com> > > > > > > >>> wrote: > > > > > > >>> > > > > > > >>> Sounds good. Thanks all for the consideration. > > > > > > >>> > > > > > > >>> On Thu, Jul 14, 2022 at 7:39 PM Andrew Purtell < > > > > > apurt...@apache.org> > > > > > > >>> wrote: > > > > > > >>> > > > > > > HBASE-27204 was filed because we are pushing on RPC. > This is > > > > > good > > > > > >
[jira] [Reopened] (HBASE-26882) Backport "HBASE-26810 Add dynamic configuration support for system coprocessors" to branch-2
[ https://issues.apache.org/jira/browse/HBASE-26882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk reopened HBASE-26882: -- > Backport "HBASE-26810 Add dynamic configuration support for system > coprocessors" to branch-2 > > > Key: HBASE-26882 > URL: https://issues.apache.org/jira/browse/HBASE-26882 > Project: HBase > Issue Type: Task > Components: Coprocessors, master, regionserver >Affects Versions: 2.5.0, 2.6.0, 2.4.12 >Reporter: Tak-Lon (Stephen) Wu >Assignee: Tak-Lon (Stephen) Wu >Priority: Major > Fix For: 2.6.0, 2.4.12 > > > Backport HBASE-26810 to streams of branch-2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
