Regarding a tool, I’ve already committed one that I used for 2.3.0. IIRC,
Busbey suggested on its original PR the idea of using it during our
nightlies as well. I’m pretty sure I’ve mentioned it explicit already to
Viraj, Andrew, and Huaxiang. Check dev-support/git-jira-release-audit on
master.
Hi Andrew,
I had a conversation on this same topic yesterday with Huaxiang and, I
believe, came to a similar conclusion. I was advocating that git be the
source of truth and Jira follow, and there be no CHANGES file in the
repository at all.
I’m on mobile at the moment. Let me spend some time
[
https://issues.apache.org/jira/browse/HBASE-25375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25375.
--
Release Note:
Adds a Vagrant project for running releases under `dev-support/release-vm
[
https://issues.apache.org/jira/browse/HBASE-25489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25489.
--
Resolution: Fixed
> [git-jira-audit] improve performance of --parse-release-t
[
https://issues.apache.org/jira/browse/HBASE-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-15073.
--
Resolution: Won't Fix
Closing old, reverted normalizer issue as "Won't Fix".
>
Nick Dimiduk created HBASE-25489:
Summary: [git-jira-audit] improve performance of
--parse-release-tags
Key: HBASE-25489
URL: https://issues.apache.org/jira/browse/HBASE-25489
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-25468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25468.
--
Resolution: Fixed
> Update git-jira-audit fallback_actions file with recent excepti
Nick Dimiduk created HBASE-25468:
Summary: Update git-jira-audit fallback_actions file with recent
exceptions
Key: HBASE-25468
URL: https://issues.apache.org/jira/browse/HBASE-25468
Project: HBase
in 2.3.4, please
> wrap them up in couple of days.
>
> Thanks,
> Huaxiang
>
> On Fri, Dec 4, 2020 at 8:38 AM Nick Dimiduk wrote:
>
> > Heya,
> >
> > It's past time to start the 2.3.4 release process. I plan to let the
> 2.4.0
> > release run i
Good plan, +1 !
On Tue, Dec 15, 2020 at 17:08 Guanghao Zhang wrote:
> Hi folks!
>
> Now we cut new branch-2.4 and the 2.4.0 will be released. We can EOM for
> branch-2.2 to reduce the maintenance work. Meanwhile, I thought branch-2.3
> is more stable than branch-2.2 because you guys take great
On Tue, Dec 15, 2020 at 11:26 AM Andrew Purtell wrote:
> With six (6) binding +1 votes including my own, and one (1) nonbinding +1
> vote, and no 0 or -1 votes, this vote passes.
>
> Thanks to all who voted on the release candidate.
>
Thank you for taking this on, Andrew!
On Thu, Dec 3,
On Tue, Dec 1, 2020 at 6:45 AM 张铎(Duo Zhang) wrote:
>
> If no other objections tomorrow, will follow what Sean proposed above, to
> include the patch in 3.0.0 and mark the issue as incompatible change.
Belated +1.
> 张铎(Duo Zhang) 于2020年11月30日周一 上午11:04写道：
>
> > I think it could introduce
diligence has been conducted.
> 3. Exclude zookeeper where we bring in hadoop-common
I think this is one we can do. I don't think an issues was raised from
this finding after 2.3.0, so I have filed HBASE-25384.
> On Thu, Dec 10, 2020 at 11:47 AM Nick Dimiduk wrote:
>
> > +1 (bi
Nick Dimiduk created HBASE-25384:
Summary: Exclude ZooKeeper 3.4.9 from hadoop-common transitive
dependency for Hadoop2 profile
Key: HBASE-25384
URL: https://issues.apache.org/jira/browse/HBASE-25384
/X509Exception$SSLContextException (same as
2.3.0 release)
On Wed, Dec 9, 2020 at 5:29 PM Nick Dimiduk wrote:
>
> On Wed, Dec 9, 2020 at 5:23 PM Andrew Purtell
> wrote:
>>
>> ICYMI, the nightly build passes because the JDK version there has three
>> components “11.0.6” and y
es, I see that now (and I have read the offending Jetty code). My
apologies, Duo, for speaking past your earlier comment.
Nick Dimiduk 于2020年12月10日周四 上午9:10写道：
>
> > Rather than have a user rebuild HBase for themselves and specify
> > hadoop-three.version, why not bump the Hadoop3 version
>> wrote:
> >>>>
> >>>>>> parseJDK9:71, JavaVersion (org.eclipse.jetty.util)
> >>>>>
> >>>>> So unless I am mistaken, some Jetty utility class is not able to
> parse
> >>>> the
> >>>
>>> version string of your particular JDK/JRE.
> >>>>
> >>>> We can try to downgrade Jetty but I am not sure in general how we are
> >>>> supposed to take on the risk of third party dependencies doing the
> wrong
> >>>> thin
gt; >
> >> > So unless I am mistaken, some Jetty utility class is not able to parse
> >> the
> >> > version string of your particular JDK/JRE.
> >> >
> >> > We can try to downgrade Jetty but I am not sure in general how we are
> >> > s
(java.util.concurrent)
run:834, Thread (java.lang)
On Wed, Dec 9, 2020 at 2:08 PM Nick Dimiduk wrote:
> On Mon, Dec 7, 2020 at 1:51 PM Nick Dimiduk wrote:
>
>> Has anyone successfully built/run this RC with JDK11 and Hadoop3 profile?
>> I'm seeing test failures locally in
On Mon, Dec 7, 2020 at 1:51 PM Nick Dimiduk wrote:
> Has anyone successfully built/run this RC with JDK11 and Hadoop3 profile?
> I'm seeing test failures locally in the hbase-asyncfs module.
> Reproducible with:
>
> $
> JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenj
Nick Dimiduk created HBASE-25375:
Summary: Provide a VM-based release environment
Key: HBASE-25375
URL: https://issues.apache.org/jira/browse/HBASE-25375
Project: HBase
Issue Type: Task
enkinsfile.
The dev-support/hbase-vote.sh has not been updated to match that logic.
Should we break this question out into a DISCUSS thread?
>
I don't think it's necessary, though I suppose the details are not well
socialized.
On Mon, Dec 7, 2020 at 1:52 PM Nick Dimiduk wrote:
>
> &
[
https://issues.apache.org/jira/browse/HBASE-25369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25369.
--
Fix Version/s: (was: 3.0.0-alpha-1)
Resolution: Duplicate
> hbase-vote.sh
Has anyone successfully built/run this RC with JDK11 and Hadoop3 profile?
I'm seeing test failures locally in the hbase-asyncfs module.
Reproducible with:
$
JAVA_HOME=/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
mvn clean install -Dhadoop.profile=3.0
Nick Dimiduk created HBASE-25369:
Summary: hbase-vote.sh mvn invocation broken with empty
MVN_PROPERTIES variable
Key: HBASE-25369
URL: https://issues.apache.org/jira/browse/HBASE-25369
Project
Hello!
When I search Jira for your email address, I find a single result, an
account with the username "SWH12". This user account has the contributor
permission and should already be assignable to issues and be able to assign
itself an issue. Please confirm that this is the account you're using.
Congratulations and thank you for your contributions!
On Thu, Dec 3, 2020 at 01:11 Guanghao Zhang wrote:
> Folks,
>
> On behalf of the Apache HBase PMC I am pleased to announce that Yulin Niu
> has accepted the PMC's invitation to become a committer on the project.
>
> We appreciate all of the
Congratulations and thank you for your contributions!
On Thu, Dec 3, 2020 at 01:13 Guanghao Zhang wrote:
> Folks,
>
> On behalf of the Apache HBase PMC I am pleased to announce that Xin Sun has
> accepted the PMC's invitation to become a committer on the project.
>
> We appreciate all of the
>From the section "11.1. Aspirational Semantic Versioning" [0], under the
heading "Client Binary compatibility", we say:
> If a Client implements an HBase Interface, a recompile MAY be required
upgrading to a newer minor version (See release notes for warning about
incompatible changes). All
Heya,
It's past time to start the 2.3.4 release process. I plan to let the 2.4.0
release run its course before adding this release to the PMC burden. I will
change my mind if the 2.4.0 release ends up dragging out for several weeks
for some reason. In the meantime, please wrap up any patch-level
On Wed, Dec 2, 2020 at 11:16 AM Andrew Purtell wrote:
> Like this?
>
> https://gist.github.com/apurtell/f5959f36b0b13d5e92f35b22549020cc
>
+1 !
On Wed, Dec 2, 2020 at 10:04 AM Nick Dimiduk wrote:
>
>> On Tue, Dec 1, 2020 at 12:16 PM Andrew Purtell
>> wrote:
>
rade marketing.
> > > >
> > > > If the objective is giving user-friendly and self-service answers to
> an
> > > operator or developer asking, "why should I upgrade? / what's new in
> this
> > > release?", then I humbly submit we should bring back the practice
bly submit we should bring back the practice of
> writing blog posts for blogs.apache.org/hbase. Speaking of which, that
> blog is in a somewhat sad state of disrepair with a lot of broken image
> links.
> >
> >
> >> On Mon, Nov 30, 2020 at 1:02 PM Stack wrote:
>
for some time about possibly including release notes /
> changes
> > for just those things in each individual release on the website before.
> > Would adding something like that be sufficient for the use you're
> thinking
> > of?
> >
> >
> >
> >
> &
Nice discussion here.
For my part, I am +1 for our community to define our meaning around this
aspect of metadata.
However, I don't like using both "signed-off-by" and "reviewed-by" as a
manual annotation on the part of the committer, because we as a community
don't care about the distinction
should I upgrade? / what's new in
this release?" The existing CHANGES.md file on the release tag would work,
except that the markdown doesn't render on Github due to size.
On Mon, Nov 9, 2020, 15:35 Nick Dimiduk wrote:
>
> > Heya,
> >
> > The CHANGES.md file on branch-2.3 weighs in at
Heya,
The CHANGES.md file on branch-2.3 weighs in at over 1mb and is too big for
Github to render. Its content covers back to 0.99. This isn't really usable
by someone who wants to easily see what's new in the latest patch release.
I propose we truncate these changes files to what's new for the
[
https://issues.apache.org/jira/browse/HBASE-25090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25090.
--
Resolution: Fixed
Backported all the way to branch-1.4. Thank you [~GeorryHuang
[
https://issues.apache.org/jira/browse/HBASE-25228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25228.
--
Resolution: Fixed
> Delete dev-support/jenkins_precommit_jira_yetus
might also be able to drop this "create-patch"
script.
Please take a look, and feel free to pick up any of this work that speaks
to you.
Thanks,
Nick
On Wed, Mar 4, 2020 at 9:50 AM Nick Dimiduk wrote:
> > If it is not easy to add JDK11 support for the PreCommit-HBASE-Build job
&
Nick Dimiduk created HBASE-25233:
Summary: Update book section "Submitting Patches" to exclusively
describe a Github workflow
Key: HBASE-25233
URL: https://issues.apache.org/jira/browse/H
[
https://issues.apache.org/jira/browse/HBASE-23888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-23888.
--
Resolution: Won't Fix
Per this [discuss
thread|https://lists.apache.org/thread.html
[
https://issues.apache.org/jira/browse/HBASE-23879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-23879.
--
Resolution: Won't Fix
Per this [discuss
thread|https://lists.apache.org/thread.html
+1 (binding)
I prefer we have a clean upstream build history at the time of release. It
appears there's something broken in building the refguide. This has
the potential to mask other issues. However, inspecting these runs, the
unit test suites are often passing. I filed
Nick Dimiduk created HBASE-25232:
Summary: Failure in refguide is causing build failures
Key: HBASE-25232
URL: https://issues.apache.org/jira/browse/HBASE-25232
Project: HBase
Issue Type
[
https://issues.apache.org/jira/browse/HBASE-25090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-25090:
--
Let's backport this to 2.3 and 2.2. It is applicable on branch-1?
> CompactionConfiguration l
[
https://issues.apache.org/jira/browse/HBASE-25231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25231.
--
Resolution: Duplicate
> Fix PreCommit builds for branch-
[
https://issues.apache.org/jira/browse/HBASE-24816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-24816:
--
Looks like branch-1.4 needs this too. Reopening for backport.
> Remove unused credential hbas
Nick Dimiduk created HBASE-25231:
Summary: Fix PreCommit builds for branch-1.4
Key: HBASE-25231
URL: https://issues.apache.org/jira/browse/HBASE-25231
Project: HBase
Issue Type: Task
Nick Dimiduk created HBASE-25228:
Summary: Delete dev-support/jenkins_precommit_jira_yetus.sh
Key: HBASE-25228
URL: https://issues.apache.org/jira/browse/HBASE-25228
Project: HBase
Issue
Heya,
FYI, I've landed the PR for master from HBASE-24200 that upgrades the Yetus
version there to 0.12.0. I don't anticipate any issues, but just in case
builds go sideways, this is an easy candidate to blame.
This change will be backported to all active release lines once the master
changes
[
https://issues.apache.org/jira/browse/HBASE-24463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24463.
--
Resolution: Won't Fix
The ability to limit the normalizer is now provided by rate limiting
[
https://issues.apache.org/jira/browse/HBASE-24845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24845.
--
Resolution: Fixed
Thanks for the review [~apurtell]
> Git/Jira Release Audit: limit branc
p.
> > > > > >
> > > > > > Thanks,
> > > > > > S
> > > > > >
> > > > > >
> > > > > >
> > > > > > > Andrew Purtell 于2020年10月15日周四 上午1:53写道：
> > > > &g
[
https://issues.apache.org/jira/browse/HBASE-23894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-23894.
--
Resolution: Won't Fix
I don't think we can solve this. ErrorProne's maven configurations
0日周二 上午11:42写道：
> >
> > > that sounds probable given the symptoms.
> > >
> > > On Mon, Oct 19, 2020 at 9:16 PM Nick Dimiduk
> > wrote:
> > > >
> > > > The Jenkins server was restarted within the last 24 hours, presumably
> > for
,
Nick
On Wed, Oct 21, 2020 at 9:57 AM ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com> wrote:
> Hi Nick
>
> Can I port https://issues.apache.org/jira/browse/HBASE-25065 to branch-2.2
> - Note that it is an improvement?
>
> Regards
> Ram
>
> On Wed, Oct 21, 202
Hello team,
It's come around to that time again. We have about 30 improvements on the
branch, which is my litmus test for another patch release. Please try to
land any patches you have in flight, and plan for an RC on or around
Tuesday, 27 Oct.
Thanks,
Nick
The Jenkins server was restarted within the last 24 hours, presumably for
maintenance. Maybe they changed the name of this binary mapping without
telling us?
On Mon, Oct 19, 2020 at 17:42 Guanghao Zhang wrote:
> See
>
>
, the task jira is HBASE-18070
> > > > > <https://issues.apache.org/jira/browse/HBASE-18070>. The source
> side
> > > > > change
> > > > > has been committed, Endpoint change is under review.
> > > > > Meta Replica load balance su
esired work has landed. I am not sensing any particular urgency with 1.x
> releasing. Anyway, doing 2.4 as well would be only incremental effort.
>
>
>
> On Tue, Oct 6, 2020 at 3:38 PM Nick Dimiduk wrote:
>
> > Bump.
> >
> > We still need a volunteer for a release
[
https://issues.apache.org/jira/browse/HBASE-25144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25144.
--
Resolution: Fixed
> Add Hadoop-3.3.0 to personality hadoopch
[
https://issues.apache.org/jira/browse/HBASE-24464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24464.
--
Resolution: Won't Fix
I don't think there's a strong case for this functionality. Reopen
Nick Dimiduk created HBASE-25180:
Summary: Update Hadoop compatibility guidelines in book re: Hadoop
3.3.0
Key: HBASE-25180
URL: https://issues.apache.org/jira/browse/HBASE-25180
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-25156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk reopened HBASE-25156:
--
Re-opening for addendum. Will focus on master until things look stable
Nick Dimiduk created HBASE-25167:
Summary: Normalizer support for hot config reloading
Key: HBASE-25167
URL: https://issues.apache.org/jira/browse/HBASE-25167
Project: HBase
Issue Type
[
https://issues.apache.org/jira/browse/HBASE-24636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24636.
--
Resolution: Won't Fix
Let's leave this at 5mins for now. The reason being
[
https://issues.apache.org/jira/browse/HBASE-24465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24465.
--
Resolution: Not A Problem
I think this is this actually a problem. The total size
Hello,
I see that we have `dev-support/adhoc_run_tests/Jenkinsfile` on master but
I don't see an associated job on ci-hadoop. Am I just blind, or did it not
make the transition? If the latter, was that an intention omission? Should
we drop the Jenkinsfile from our repo? Or should be restore the
, Aug 25, 2020 at 10:36 AM Nick Dimiduk wrote:
> Heya!
>
> Now that 2.3.x is in maintenance mode, I'd like to start a discussion on
> 2.4. We've long agreed that a more frequent cadence of minor releases is
> superior to a long gap between them. I think we should target a 2.4.0
>
[
https://issues.apache.org/jira/browse/HBASE-25144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25144.
--
Resolution: Fixed
> Add Hadoop-3.3.0 to personality hadoopch
Nick Dimiduk created HBASE-25157:
Summary: TestMasterRegionCompaction is flaky
Key: HBASE-25157
URL: https://issues.apache.org/jira/browse/HBASE-25157
Project: HBase
Issue Type: Test
Nick Dimiduk created HBASE-25156:
Summary: TestMasterFailover.testSimpleMasterFailover is flaky
Key: HBASE-25156
URL: https://issues.apache.org/jira/browse/HBASE-25156
Project: HBase
Issue
Nick Dimiduk created HBASE-25155:
Summary: Flaky Test Dashboard scripts are blocked
Key: HBASE-25155
URL: https://issues.apache.org/jira/browse/HBASE-25155
Project: HBase
Issue Type: Task
[
https://issues.apache.org/jira/browse/HBASE-25143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25143.
--
Fix Version/s: 3.0.0-alpha-1
Resolution: Fixed
> Remove branch-1.3 from precom
Nick Dimiduk created HBASE-25150:
Summary: Metrics recording a time duration should use
System.nanoTime()
Key: HBASE-25150
URL: https://issues.apache.org/jira/browse/HBASE-25150
Project: HBase
Nick Dimiduk created HBASE-25149:
Summary: Profiling servlet stuck in a loop when output directory
does not exist
Key: HBASE-25149
URL: https://issues.apache.org/jira/browse/HBASE-25149
Project
Nick Dimiduk created HBASE-25144:
Summary: Add Hadoop-3.3.0 to precommit check list
Key: HBASE-25144
URL: https://issues.apache.org/jira/browse/HBASE-25144
Project: HBase
Issue Type: Task
Nick Dimiduk created HBASE-25143:
Summary: Remove branch-1.3 from precommit and docs
Key: HBASE-25143
URL: https://issues.apache.org/jira/browse/HBASE-25143
Project: HBase
Issue Type: Task
Thank you Viraj for running this release!
On Sun, Sep 27, 2020 at 12:29 AM Viraj Jasani wrote:
> The HBase team is happy to announce the immediate availability of HBase
> 2.3.2.
>
> Apache HBase™ is an open-source, distributed, versioned, non-relational
> database.
> Apache HBase gives you low
[
https://issues.apache.org/jira/browse/HBASE-25043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25043.
--
Resolution: Done
> Update reporter tool with new rele
[
https://issues.apache.org/jira/browse/HBASE-25085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25085.
--
Resolution: Fixed
> Add support for java properties to hbase-vote
[
https://issues.apache.org/jira/browse/HBASE-25042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25042.
--
Resolution: Fixed
{noformat}
$ svn mv https://dist.apache.org/repos/dist/dev/hbase/2.3.2RC4
[
https://issues.apache.org/jira/browse/HBASE-24012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24012.
--
Resolution: Done
> Release 2.3.0
> -
>
> Key:
Nick Dimiduk created HBASE-25090:
Summary: CompactionConfiguration logs unrealistic store file sizes
Key: HBASE-25090
URL: https://issues.apache.org/jira/browse/HBASE-25090
Project: HBase
+1
* API compatibility report looks good: ok
* Changelog and Jira line up: ok
* Deployed to a small cluster and ran ITBLL with serverkilling chaos monkey
for several hours: ok
* Nightlies up on ci-hadoop are looking solid: ok
I also ran hbase-vote.sh against the artifacts mirrored to svn (at
Nick Dimiduk created HBASE-25085:
Summary: Add support for java properties to hbase-vote.sh
Key: HBASE-25085
URL: https://issues.apache.org/jira/browse/HBASE-25085
Project: HBase
Issue Type
On Mon, Sep 21, 2020 at 10:02 AM Tak-Lon (Stephen) Wu
wrote:
>
> In addition, just a learning point about the base of URL is not
> https://dist.apache.org/repos/dist/dev/hbase/, is it normal after RC1 ?
>
Hi Stephen.
While there is nothing in our policy that requires the person who assembles
a
On Sun, Sep 20, 2020 at 10:51 AM Viraj Jasani wrote:
>
> The release files, including signatures, digests, as well as CHANGES.md
> and RELEASENOTES.md included in this RC can be found at:
>
> http://home.apache.org/~vjasani/2.3.2RC4/
I'm syncing this version over to dist. Should be up in a
[
https://issues.apache.org/jira/browse/HBASE-25061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-25061.
--
Fix Version/s: 3.0.0-alpha-1
Resolution: Fixed
> Update default URL to KEYS f
Thanks for pulling this RC together, Viraj. I've mirrored the artifacts
from home.apache.org to the usual location in
https://dist.apache.org/repos/dist/dev/hbase/2.3.2RC1/
On Thu, Sep 17, 2020 at 11:43 AM Wellington Chevreuil <
wellington.chevre...@gmail.com> wrote:
> Note: The hbase-vote.sh
Nick Dimiduk created HBASE-25061:
Summary: Update default path to KEYS file in `hbase-vote.sh`
Key: HBASE-25061
URL: https://issues.apache.org/jira/browse/HBASE-25061
Project: HBase
Issue
Nick Dimiduk created HBASE-25059:
Summary: TransitionRegionStateProcedure should timeout, rollback,
retry instead of waiting infinitely on CONFIRMED_OPEN
Key: HBASE-25059
URL: https://issues.apache.org/jira
Nick Dimiduk created HBASE-25058:
Summary: Investigate netty:
"jdk.internal.misc.Unsafe.allocateUninitializedArray(int): unavailable"
Key: HBASE-25058
URL: https://issues.apache.org/jira/browse/H
Nick Dimiduk created HBASE-25053:
Summary: WAL replay should ignore 0-length files
Key: HBASE-25053
URL: https://issues.apache.org/jira/browse/HBASE-25053
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-24227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-24227.
--
Resolution: Cannot Reproduce
Thanks for checking.
> [JDK11] shell fails to lau
FYI, Viraj has volunteered to run this release. Expect to see a VOTE thread
for him, not from me, on 2.3.2.
Thanks,
Nick
On Tue, Sep 8, 2020 at 11:23 AM Nick Dimiduk wrote:
> Heya,
>
> It's about time to prepare a 2.3.2 release [0]. Notably, we have two
> issues marked critical th
On Mon, Sep 14, 2020 at 19:24 Sean Busbey wrote:
> meta isn't the only system table and not all system tables have a
>
> representation in HDFS. i.e. the ACL table.
>
+1
On Mon, Sep 14, 2020 at 5:13 PM Nick Dimiduk wrote:
>
> >
>
> > Is it really a good idea
Is it really a good idea to restore to a previous copy of meta? Wouldn't it
be better to fix meta using hbck2? The only thing we know for certain about
a past meta state is it's in the past.
On Sat, Sep 12, 2020 at 9:27 AM Sean Busbey wrote:
> Now that we have snapshots with TTLs, it would be
501 - 600 of 2152 matches
Mail list logo
