date:20211020

Re: [VOTE] First release candidate for HBase 1.4.14 is available for download

2021-10-20 Thread Reid Chan

+1
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_232): ok
 - mvn clean apache-rat:check
* Built from source (1.8.0_232): ok
 - mvn clean install  -DskipTests
* Unit tests pass (1.8.0_232): ok
 - mvn package -P runSmallTests  -Dsurefire.rerunFailingTestsCount=3


On Thu, Oct 21, 2021 at 9:27 AM Duo Zhang  wrote:

> Please vote on this Apache HBase release candidate,
> hbase-1.4.14RC0
>
> The VOTE will remain open for at least 72 hours.
>
> [ ] +1 Release this package as Apache HBase 1.4.14
> [ ] -1 Do not release this package because ...
>
> The tag to be voted on is 1.4.14RC0:
>
>   https://github.com/apache/hbase/tree/1.4.14RC0
>
> This tag currently points to git reference
>
>   e7cbc2debc11a01dd4f3e6f6d6992b7bd307bbcb
>
> The release files, including signatures, digests included
> in this RC can be found at:
>
>   https://dist.apache.org/repos/dist/dev/hbase/1.4.14RC0/
>
> The release notes can be found at:
>
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753=12346995
>
> Maven artifacts are available in a staging repository at:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-1467/
>
> Artifacts were signed with the 9AD2AE49 key which can be found in:
>
>   https://dist.apache.org/repos/dist/release/hbase/KEYS
>
> Notice that 1.4.14 will be the last release for the 1.4.x release line.
> Users
> are encouraged to upgrade to the 2.x stable release line.
>
> To learn more about Apache HBase, please see
>
>   http://hbase.apache.org/
>
> Thanks,
> Your HBase Release Manager
>

Re: [DISCUSS] Contribution of a thrift2 python api

2021-10-20 Thread Sean Uetung

Have submitted an MR about this in the ticket
https://issues.apache.org/jira/browse/HBASE-26354. The MR passed the QA.

Sean Busbey  于2021年9月29日周三 下午10:49写道：

> yes, generally a PMC member associated with a specific release should
> push the released artifacts to pypi. Someone will need to run down the
> details of doing that, but there is precedent of other ASF projects
> doing so.
>
> On Tue, Sep 28, 2021 at 10:14 PM Yutong Xiao  wrote:
> >
> > Contributing to hbase-connectors is ok for me. But there is a question
> > about how to release the package. Currently, I upload the package to pypi
> > with my own pypi account. Not clear whether this should change if I
> > contribute the client to hbase-connectors.
> >
> > Reid Chan  于2021年8月3日周二 下午10:27写道：
> >
> > > Brief summaries from this thread:
> > >
> > > I think you can push to hbase-connectors
> > >  repo. Just create a new
> dir
> > > hbase-thrift-python, and put your codes under it.
> > > Your codes need to be reviewed by good Pythoners in the community.
> > >
> > > Some follow-up tasks include (but not limited to):
> > >
> > >- requirements.txt
> > >- docs about how to release
> > >- some client examples
> > >- add some test codes (I'm not sure this part, whether there are
> similar
> > >conventions in python world)
> > >- other related information
> > >
> > >
> > > About the *.thrfit files you mentioned, I can't come up a good idea by
> now.
> > > Looks like we still need to create two separate PRs to update both
> hbase
> > > and hbase-connectors repo.
> > > However, as *.thrfit files seldom get updated, I feel it should be a
> ok.
> > >
> > >
> > > --
> > > Best Regards,
> > > R.C
> > >
> > >
> > > On Tue, Aug 3, 2021 at 10:42 AM Yutong Xiao 
> wrote:
> > >
> > > > Hello, any other thoughts about this?
> > > >
> > > > Yutong Xiao  于2021年7月21日周三 上午11:30写道：
> > > >
> > > > > Hi. I have removed the personal info in the licenses. For the point
> > > 3.2,
> > > > > thbase is dependent on the hbase.thrift file. I have involved the
> > > > > hbase.thrift file, that thbase used, in the repo. In this case,
> repo
> > > > > separation will lead to a sync problem between the hbase.thrfit
> files
> > > in
> > > > > HBase repo and the connector repo. I am concerned this may make it
> hard
> > > > for
> > > > > maintenance. What do you think?
> > > > >
> > > > > 张铎(Duo Zhang)  于2021年7月17日周六 上午9:39写道：
> > > > >
> > > > >> One of the difficulties of moving hbase-thrift and hbase-rest out
> is
> > > > >> because we make use of hbase-http in these two modules, at least
> for
> > > > >> setting up the status servlet...
> > > > >>
> > > > >> Sean Busbey  于2021年7月16日周五 下午11:01写道：
> > > > >>
> > > > >> > maybe a good fit for the hbase-connectors repo? I know we've
> talked
> > > a
> > > > >> > few times about moving the thrift server out there. if we did
> both
> > > > >> > then the compatibility question becomes just the standard
> > > > >> > client/server compatibility provided the thrift server only
> uses our
> > > > >> > public java client API.
> > > > >> >
> > > > >> > On Thu, Jul 15, 2021 at 10:21 PM Yutong Xiao <
> yutongs...@gmail.com>
> > > > >> wrote:
> > > > >> > >
> > > > >> > > btw for point 2, if allowed I can do that.
> > > > >> > > And for point 3.2 it is only a personal idea, the final
> decision
> > > > >> should
> > > > >> > be
> > > > >> > > made by the community.
> > > > >> > > Besides, many of my python user colleagues started using this
> > > > library.
> > > > >> > > I think many python users have the demand of a good HBase
> python
> > > > >> client.
> > > > >> > >
> > > > >> > > Yutong Xiao  于2021年7月16日周五 上午11:07写道：
> > > > >> > >
> > > > >> > > > 1. The license is no problem.
> > > > >> > > > 2. This should see if any committer or PMC has interests to
> do
> > > > that.
> > > > >> > > > 3. I can be responsible for those documents. About 3.2, as
> > > thbase
> > > > >> has
> > > > >> > been
> > > > >> > > > uploaded to Pypi, I think it would be better if it is a new,
> > > > >> separate
> > > > >> > repo.
> > > > >> > > >
> > > > >> > > > Wei-Chiu Chuang  于2021年7月6日周二
> 上午10:22写道：
> > > > >> > > >
> > > > >> > > >> Hi
> > > > >> > > >> thanks for your interest in contributing the python api to
> the
> > > > >> HBase
> > > > >> > > >> project.
> > > > >> > > >>
> > > > >> > > >> I quickly check and it doesn't look like there's another
> active
> > > > >> python
> > > > >> > > >> HBase thrift client project at this point.
> > > > >> > > >> I don't have a demand to use a python thrift hbase client
> > > > library.
> > > > >> If
> > > > >> > > >> there
> > > > >> > > >> are people who will benefit from this library, then it's a
> good
> > > > >> idea
> > > > >> > to
> > > > >> > > >> make sure the library is well maintained, by having it
> become
> > > > part
> > > > >> of
> > > > >> > the
> > > > >> > > >> Apache HBase project and that more developers can
> contribute to
>

[jira] [Resolved] (HBASE-26386) Refactor StoreFileTracker implementations to expose the set method

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-26386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-26386.
---
Fix Version/s: HBASE-26067
 Hadoop Flags: Reviewed
   Resolution: Fixed

Merged to branch HBASE-26067.

Thanks [~wchevreuil] for reviewing.

> Refactor StoreFileTracker implementations to expose the set method
> --
>
> Key: HBASE-26386
> URL: https://issues.apache.org/jira/browse/HBASE-26386
> Project: HBase
>  Issue Type: Sub-task
>  Components: HFile
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: HBASE-26067
>
>
> As when clone/restore a snapshot, we need to set the store file list directly 
> to StoreFileTracker, which means we need this method in upper layer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] move stable pointer to 2.4.6+

2021-10-20 Thread Duo Zhang

Filed HBASE-26387

张铎(Duo Zhang)  于2021年10月21日周四 上午9:49写道：

> Done.
>
> Let me file an issue to update our HEADER.html.
>
> 张铎(Duo Zhang)  于2021年10月21日周四 上午8:41写道：
>
>> I think we have reached an agreement here to move the stable pointer
>> 2.4.x.
>>
>> Since 2.4.7 has been released, let's move the stable pointer to 2.4.7.
>>
>> Will do this later today.
>>
>> Thanks all for helping!
>>
>> Viraj Jasani  于2021年10月12日周二 下午2:59写道：
>>
>>> Sounds good. Created HBASE-26352
>>> , will get to it
>>> after
>>> completing some additional testing.
>>>
>>> On Mon, Oct 11, 2021 at 8:47 PM 张铎(Duo Zhang) 
>>> wrote:
>>>
>>> > I was thinking we can add these things to the upgrade section.
>>> >
>>> > https://hbase.apache.org/book.html#upgrade2.0.rolling.upgrades
>>> >
>>> > Nick Dimiduk  于2021年10月11日周一 下午10:59写道：
>>> >
>>> > > On Mon, Oct 11, 2021 at 2:24 AM 张铎(Duo Zhang) >> >
>>> > > wrote:
>>> > >
>>> > > > Could you please file an issue to add these to our ref guide? I
>>> think
>>> > > these
>>> > > > are all very important experiences for our end users.
>>> > > >
>>> > >
>>> > > Question: Is the ref guide the place where we want to document what
>>> > > community testing has been performed on any given release? What would
>>> > such
>>> > > a section look like? Who do we imagine will benefit from such
>>> > information?
>>> > > How will they find it? How will they volunteer new results?
>>> > >
>>> > > Viraj Jasani  于2021年10月11日周一 下午3:46写道：
>>> > > >
>>> > > > > Moreover, I have also tested rollback from 2.4 to 1.6 and after
>>> > taking
>>> > > > care
>>> > > > > of some rsgroup ordering issues as part of the downgrade, we have
>>> > seen
>>> > > > > smooth downgrade as well (with the only exception that last RS
>>> that
>>> > > stays
>>> > > > > on 2.4 needs to be shutdown non-gracefully or killed, because of
>>> > > > > HBASE-17931).
>>> > > > >
>>> > > > >
>>> > > > > On Mon, 11 Oct 2021 at 1:10 PM, Viraj Jasani >> >
>>> > > wrote:
>>> > > > >
>>> > > > > > I have done some chaos testing as well as ingestion testing 3-4
>>> > times
>>> > > > on
>>> > > > > > the recent 2.4 versions, each spanning the duration of around
>>> 8-10
>>> > > hr.
>>> > > > > And
>>> > > > > > also tested rolling upgrade from 1.6 to 2.4 a couple of times
>>> after
>>> > > > > > applying the recent fixes on adding missing CFs in meta table
>>> as
>>> > part
>>> > > > of
>>> > > > > > the upgrade. (Upgrade requires upgrading all RS first before
>>> > masters)
>>> > > > > >
>>> > > > > > Things seem to be running well so far, no significant concerns
>>> have
>>> > > > been
>>> > > > > > identified with default configs so far.
>>> > > > > >
>>> > > > > > Andrew and I will keep testing this release line on different
>>> > > > > > infrastructure with different tooling, but for now, I have
>>> > sufficient
>>> > > > > test
>>> > > > > > data to provide my +1 for moving the stable pointers to 2.4.
>>> And
>>> > > thank
>>> > > > > you
>>> > > > > > for starting this thread, Sean!
>>> > > > > >
>>> > > > > >
>>> > > > > > On Mon, 11 Oct 2021 at 1:46 AM, Sean Busbey >> >
>>> > > wrote:
>>> > > > > >
>>> > > > > >> Hi folks!
>>> > > > > >>
>>> > > > > >> I'd like us to move the stable pointer from 2.3.z releases to
>>> > 2.4.6+
>>> > > > > >> releases.
>>> > > > > >>
>>> > > > > >> The last time we talked about doing so[1] there was a desire
>>> to
>>> > get
>>> > > > > >> some documentation together on what we as a community expect
>>> from
>>> > > the
>>> > > > > >> "stable" release line. We have an issue tracking those
>>> needs[2],
>>> > but
>>> > > > > >> AFAICT we haven't had sufficient community interest to get
>>> > criteria
>>> > > > > >> together over the last 6 months.
>>> > > > > >>
>>> > > > > >> The 2.3 release line started in July 2020 and there is active
>>> > > > > >> discussion about declaring it EOL[3]. 2.4 releases have been
>>> going
>>> > > > > >> since Dec 2020 and there is attestation that 2.4 has been as
>>> or
>>> > more
>>> > > > > >> stable than 2.3 in a testing environment[4].
>>> > > > > >>
>>> > > > > >> Personally, I view the "stable" pointer as simply a way to
>>> say "if
>>> > > you
>>> > > > > >> are new to our community we'd like you to use this release." I
>>> > > > > >> personally think 2.4.z currently meets that standard and we
>>> need
>>> > not
>>> > > > > >> block updating on something more rigorous.
>>> > > > > >>
>>> > > > > >> What do folks think?
>>> > > > > >>
>>> > > > > >> -busbey
>>> > > > > >>
>>> > > > > >> [1]:
>>> > > > > >> "[DISCUSS] Updating the 'stable' pointer to 2.4.2" :
>>> > > > > >> https://s.apache.org/6cz3t
>>> > > > > >>
>>> > > > > >> [2]:
>>> > > > > >> https://issues.apache.org/jira/browse/HBASE-25690
>>> > > > > >>
>>> > > > > >> [3]:
>>> > > > > >> "[DISCUSS] EOL 2.3" : https://s.apache.org/pgkge
>>> > > > > >>
>>> > > > > >> [4]:
>>> > > > > >> Message on thread "[DISCUSS] EOL 2.3"
>>> > > > > >> https://s.apache.org/ks7wk
>>>

[jira] [Reopened] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

2021-10-20 Thread Andrew Kyle Purtell (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Kyle Purtell reopened HBASE-26190:
-

Is it just me or is this not terribly useful? 

{noformat}
2021-10-21 01:48:42,860 WARN  [main-BucketCacheWriter-0] bucket.BucketCache: 
Most recent failed allocation in 6 milliseconds; Table
Name = null, Column Family = null, HFile Name : 1919692f80b841b7a3d4453ec01186f1
org.apache.hadoop.hbase.io.hfile.bucket.BucketAllocatorException: Allocation 
too big size=1050637; adjust BucketCache sizes hbase.bucket
cache.bucket.sizes to accomodate if size seems reasonable and you want it 
cached.
{noformat}

Table is always null and column family is always null in these messages. This 
is with latest branch-2.4. I think this should be corrected now with an 
addendum or this should be reverted and improved later. [~anoop.hbase]

> High rate logging of BucketAllocatorException: Allocation too big 
> --
>
> Key: HBASE-26190
> URL: https://issues.apache.org/jira/browse/HBASE-26190
> Project: HBase
>  Issue Type: Bug
>  Components: BucketCache, Operability
>Affects Versions: 2.4.5
>Reporter: Andrew Kyle Purtell
>Assignee: Kulwant Singh
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.8
>
>
> These log lines may be printed at high frequency when using a schema that 
> creates large blocks and the bucket cache is enabled. It makes sense to warn 
> about this initially, but the very high rate of warnings when the use case is 
> legit and this is expected does not. Print this once, then not again; or, 
> rate-limit this message to be printed at a more reasonable rate, like once 
> per minute. 
> {noformat}
> 2021-08-11 23:42:10,902 WARN  [main-BucketCacheWriter-0]
> bucket.BucketCache: Failed allocation for 
> 4842189251414b8a9212f6831462e415_218610843;
> org.apache.hadoop.hbase.io.hfile.bucket.BucketAllocatorException:
> Allocation too big size=1049337;
> adjust BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate
> if size seems reasonable and you want it cached.
> {noformat}
> Also, it might be better to log this at INFO given the caveat "if size seems 
> reasonable and you want it cached". Reads like an informational message.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-26387) Modify HEADER.html to reflect recent stable and EOL release line changes

2021-10-20 Thread Duo Zhang (Jira)

Duo Zhang created HBASE-26387:
-

 Summary: Modify HEADER.html to reflect recent stable and EOL 
release line changes
 Key: HBASE-26387
 URL: https://issues.apache.org/jira/browse/HBASE-26387
 Project: HBase
  Issue Type: Task
Reporter: Duo Zhang
Assignee: Duo Zhang






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] move stable pointer to 2.4.6+

2021-10-20 Thread Duo Zhang

Done.

Let me file an issue to update our HEADER.html.

张铎(Duo Zhang)  于2021年10月21日周四 上午8:41写道：

> I think we have reached an agreement here to move the stable pointer 2.4.x.
>
> Since 2.4.7 has been released, let's move the stable pointer to 2.4.7.
>
> Will do this later today.
>
> Thanks all for helping!
>
> Viraj Jasani  于2021年10月12日周二 下午2:59写道：
>
>> Sounds good. Created HBASE-26352
>> , will get to it after
>> completing some additional testing.
>>
>> On Mon, Oct 11, 2021 at 8:47 PM 张铎(Duo Zhang) 
>> wrote:
>>
>> > I was thinking we can add these things to the upgrade section.
>> >
>> > https://hbase.apache.org/book.html#upgrade2.0.rolling.upgrades
>> >
>> > Nick Dimiduk  于2021年10月11日周一 下午10:59写道：
>> >
>> > > On Mon, Oct 11, 2021 at 2:24 AM 张铎(Duo Zhang) 
>> > > wrote:
>> > >
>> > > > Could you please file an issue to add these to our ref guide? I
>> think
>> > > these
>> > > > are all very important experiences for our end users.
>> > > >
>> > >
>> > > Question: Is the ref guide the place where we want to document what
>> > > community testing has been performed on any given release? What would
>> > such
>> > > a section look like? Who do we imagine will benefit from such
>> > information?
>> > > How will they find it? How will they volunteer new results?
>> > >
>> > > Viraj Jasani  于2021年10月11日周一 下午3:46写道：
>> > > >
>> > > > > Moreover, I have also tested rollback from 2.4 to 1.6 and after
>> > taking
>> > > > care
>> > > > > of some rsgroup ordering issues as part of the downgrade, we have
>> > seen
>> > > > > smooth downgrade as well (with the only exception that last RS
>> that
>> > > stays
>> > > > > on 2.4 needs to be shutdown non-gracefully or killed, because of
>> > > > > HBASE-17931).
>> > > > >
>> > > > >
>> > > > > On Mon, 11 Oct 2021 at 1:10 PM, Viraj Jasani 
>> > > wrote:
>> > > > >
>> > > > > > I have done some chaos testing as well as ingestion testing 3-4
>> > times
>> > > > on
>> > > > > > the recent 2.4 versions, each spanning the duration of around
>> 8-10
>> > > hr.
>> > > > > And
>> > > > > > also tested rolling upgrade from 1.6 to 2.4 a couple of times
>> after
>> > > > > > applying the recent fixes on adding missing CFs in meta table as
>> > part
>> > > > of
>> > > > > > the upgrade. (Upgrade requires upgrading all RS first before
>> > masters)
>> > > > > >
>> > > > > > Things seem to be running well so far, no significant concerns
>> have
>> > > > been
>> > > > > > identified with default configs so far.
>> > > > > >
>> > > > > > Andrew and I will keep testing this release line on different
>> > > > > > infrastructure with different tooling, but for now, I have
>> > sufficient
>> > > > > test
>> > > > > > data to provide my +1 for moving the stable pointers to 2.4. And
>> > > thank
>> > > > > you
>> > > > > > for starting this thread, Sean!
>> > > > > >
>> > > > > >
>> > > > > > On Mon, 11 Oct 2021 at 1:46 AM, Sean Busbey 
>> > > wrote:
>> > > > > >
>> > > > > >> Hi folks!
>> > > > > >>
>> > > > > >> I'd like us to move the stable pointer from 2.3.z releases to
>> > 2.4.6+
>> > > > > >> releases.
>> > > > > >>
>> > > > > >> The last time we talked about doing so[1] there was a desire to
>> > get
>> > > > > >> some documentation together on what we as a community expect
>> from
>> > > the
>> > > > > >> "stable" release line. We have an issue tracking those
>> needs[2],
>> > but
>> > > > > >> AFAICT we haven't had sufficient community interest to get
>> > criteria
>> > > > > >> together over the last 6 months.
>> > > > > >>
>> > > > > >> The 2.3 release line started in July 2020 and there is active
>> > > > > >> discussion about declaring it EOL[3]. 2.4 releases have been
>> going
>> > > > > >> since Dec 2020 and there is attestation that 2.4 has been as or
>> > more
>> > > > > >> stable than 2.3 in a testing environment[4].
>> > > > > >>
>> > > > > >> Personally, I view the "stable" pointer as simply a way to say
>> "if
>> > > you
>> > > > > >> are new to our community we'd like you to use this release." I
>> > > > > >> personally think 2.4.z currently meets that standard and we
>> need
>> > not
>> > > > > >> block updating on something more rigorous.
>> > > > > >>
>> > > > > >> What do folks think?
>> > > > > >>
>> > > > > >> -busbey
>> > > > > >>
>> > > > > >> [1]:
>> > > > > >> "[DISCUSS] Updating the 'stable' pointer to 2.4.2" :
>> > > > > >> https://s.apache.org/6cz3t
>> > > > > >>
>> > > > > >> [2]:
>> > > > > >> https://issues.apache.org/jira/browse/HBASE-25690
>> > > > > >>
>> > > > > >> [3]:
>> > > > > >> "[DISCUSS] EOL 2.3" : https://s.apache.org/pgkge
>> > > > > >>
>> > > > > >> [4]:
>> > > > > >> Message on thread "[DISCUSS] EOL 2.3"
>> > > > > >> https://s.apache.org/ks7wk
>> > > > > >>
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>

[VOTE] First release candidate for HBase 1.4.14 is available for download

2021-10-20 Thread Duo Zhang

Please vote on this Apache HBase release candidate,
hbase-1.4.14RC0

The VOTE will remain open for at least 72 hours.

[ ] +1 Release this package as Apache HBase 1.4.14
[ ] -1 Do not release this package because ...

The tag to be voted on is 1.4.14RC0:

  https://github.com/apache/hbase/tree/1.4.14RC0

This tag currently points to git reference

  e7cbc2debc11a01dd4f3e6f6d6992b7bd307bbcb

The release files, including signatures, digests included
in this RC can be found at:

  https://dist.apache.org/repos/dist/dev/hbase/1.4.14RC0/

The release notes can be found at:


https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753=12346995

Maven artifacts are available in a staging repository at:

  https://repository.apache.org/content/repositories/orgapachehbase-1467/

Artifacts were signed with the 9AD2AE49 key which can be found in:

  https://dist.apache.org/repos/dist/release/hbase/KEYS

Notice that 1.4.14 will be the last release for the 1.4.x release line.
Users
are encouraged to upgrade to the 2.x stable release line.

To learn more about Apache HBase, please see

  http://hbase.apache.org/

Thanks,
Your HBase Release Manager

Re: [DISCUSS] move stable pointer to 2.4.6+

2021-10-20 Thread Duo Zhang

I think we have reached an agreement here to move the stable pointer 2.4.x.

Since 2.4.7 has been released, let's move the stable pointer to 2.4.7.

Will do this later today.

Thanks all for helping!

Viraj Jasani  于2021年10月12日周二 下午2:59写道：

> Sounds good. Created HBASE-26352
> , will get to it after
> completing some additional testing.
>
> On Mon, Oct 11, 2021 at 8:47 PM 张铎(Duo Zhang) 
> wrote:
>
> > I was thinking we can add these things to the upgrade section.
> >
> > https://hbase.apache.org/book.html#upgrade2.0.rolling.upgrades
> >
> > Nick Dimiduk  于2021年10月11日周一 下午10:59写道：
> >
> > > On Mon, Oct 11, 2021 at 2:24 AM 张铎(Duo Zhang) 
> > > wrote:
> > >
> > > > Could you please file an issue to add these to our ref guide? I think
> > > these
> > > > are all very important experiences for our end users.
> > > >
> > >
> > > Question: Is the ref guide the place where we want to document what
> > > community testing has been performed on any given release? What would
> > such
> > > a section look like? Who do we imagine will benefit from such
> > information?
> > > How will they find it? How will they volunteer new results?
> > >
> > > Viraj Jasani  于2021年10月11日周一 下午3:46写道：
> > > >
> > > > > Moreover, I have also tested rollback from 2.4 to 1.6 and after
> > taking
> > > > care
> > > > > of some rsgroup ordering issues as part of the downgrade, we have
> > seen
> > > > > smooth downgrade as well (with the only exception that last RS that
> > > stays
> > > > > on 2.4 needs to be shutdown non-gracefully or killed, because of
> > > > > HBASE-17931).
> > > > >
> > > > >
> > > > > On Mon, 11 Oct 2021 at 1:10 PM, Viraj Jasani 
> > > wrote:
> > > > >
> > > > > > I have done some chaos testing as well as ingestion testing 3-4
> > times
> > > > on
> > > > > > the recent 2.4 versions, each spanning the duration of around
> 8-10
> > > hr.
> > > > > And
> > > > > > also tested rolling upgrade from 1.6 to 2.4 a couple of times
> after
> > > > > > applying the recent fixes on adding missing CFs in meta table as
> > part
> > > > of
> > > > > > the upgrade. (Upgrade requires upgrading all RS first before
> > masters)
> > > > > >
> > > > > > Things seem to be running well so far, no significant concerns
> have
> > > > been
> > > > > > identified with default configs so far.
> > > > > >
> > > > > > Andrew and I will keep testing this release line on different
> > > > > > infrastructure with different tooling, but for now, I have
> > sufficient
> > > > > test
> > > > > > data to provide my +1 for moving the stable pointers to 2.4. And
> > > thank
> > > > > you
> > > > > > for starting this thread, Sean!
> > > > > >
> > > > > >
> > > > > > On Mon, 11 Oct 2021 at 1:46 AM, Sean Busbey 
> > > wrote:
> > > > > >
> > > > > >> Hi folks!
> > > > > >>
> > > > > >> I'd like us to move the stable pointer from 2.3.z releases to
> > 2.4.6+
> > > > > >> releases.
> > > > > >>
> > > > > >> The last time we talked about doing so[1] there was a desire to
> > get
> > > > > >> some documentation together on what we as a community expect
> from
> > > the
> > > > > >> "stable" release line. We have an issue tracking those needs[2],
> > but
> > > > > >> AFAICT we haven't had sufficient community interest to get
> > criteria
> > > > > >> together over the last 6 months.
> > > > > >>
> > > > > >> The 2.3 release line started in July 2020 and there is active
> > > > > >> discussion about declaring it EOL[3]. 2.4 releases have been
> going
> > > > > >> since Dec 2020 and there is attestation that 2.4 has been as or
> > more
> > > > > >> stable than 2.3 in a testing environment[4].
> > > > > >>
> > > > > >> Personally, I view the "stable" pointer as simply a way to say
> "if
> > > you
> > > > > >> are new to our community we'd like you to use this release." I
> > > > > >> personally think 2.4.z currently meets that standard and we need
> > not
> > > > > >> block updating on something more rigorous.
> > > > > >>
> > > > > >> What do folks think?
> > > > > >>
> > > > > >> -busbey
> > > > > >>
> > > > > >> [1]:
> > > > > >> "[DISCUSS] Updating the 'stable' pointer to 2.4.2" :
> > > > > >> https://s.apache.org/6cz3t
> > > > > >>
> > > > > >> [2]:
> > > > > >> https://issues.apache.org/jira/browse/HBASE-25690
> > > > > >>
> > > > > >> [3]:
> > > > > >> "[DISCUSS] EOL 2.3" : https://s.apache.org/pgkge
> > > > > >>
> > > > > >> [4]:
> > > > > >> Message on thread "[DISCUSS] EOL 2.3"
> > > > > >> https://s.apache.org/ks7wk
> > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
>

[jira] [Resolved] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

2021-10-20 Thread Andrew Kyle Purtell (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-26190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Kyle Purtell resolved HBASE-26190.
-
Hadoop Flags: Reviewed
  Resolution: Fixed

> High rate logging of BucketAllocatorException: Allocation too big 
> --
>
> Key: HBASE-26190
> URL: https://issues.apache.org/jira/browse/HBASE-26190
> Project: HBase
>  Issue Type: Bug
>  Components: BucketCache, Operability
>Affects Versions: 2.4.5
>Reporter: Andrew Kyle Purtell
>Assignee: Kulwant Singh
>Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.8
>
>
> These log lines may be printed at high frequency when using a schema that 
> creates large blocks and the bucket cache is enabled. It makes sense to warn 
> about this initially, but the very high rate of warnings when the use case is 
> legit and this is expected does not. Print this once, then not again; or, 
> rate-limit this message to be printed at a more reasonable rate, like once 
> per minute. 
> {noformat}
> 2021-08-11 23:42:10,902 WARN  [main-BucketCacheWriter-0]
> bucket.BucketCache: Failed allocation for 
> 4842189251414b8a9212f6831462e415_218610843;
> org.apache.hadoop.hbase.io.hfile.bucket.BucketAllocatorException:
> Allocation too big size=1049337;
> adjust BucketCache sizes hbase.bucketcache.bucket.sizes to accomodate
> if size seems reasonable and you want it cached.
> {noformat}
> Also, it might be better to log this at INFO given the caveat "if size seems 
> reasonable and you want it cached". Reads like an informational message.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-26386) Refactor StoreFileTracker implementations to expose the set method

2021-10-20 Thread Duo Zhang (Jira)

Duo Zhang created HBASE-26386:
-

 Summary: Refactor StoreFileTracker implementations to expose the 
set method
 Key: HBASE-26386
 URL: https://issues.apache.org/jira/browse/HBASE-26386
 Project: HBase
  Issue Type: Sub-task
  Components: HFile
Reporter: Duo Zhang
Assignee: Duo Zhang


As when clone/restore a snapshot, we need to set the store file list directly 
to StoreFileTracker, which means we need this method in upper layer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-26385) Clear CellScanner when replay

2021-10-20 Thread Lijin Bin (Jira)

Lijin Bin created HBASE-26385:
-

 Summary: Clear CellScanner when replay
 Key: HBASE-26385
 URL: https://issues.apache.org/jira/browse/HBASE-26385
 Project: HBase
  Issue Type: Bug
Affects Versions: 2.4.7
Reporter: Lijin Bin
Assignee: Lijin Bin


RSRpcServices#mutate and RSRpcServices#multi we clear CellScanner immediately 
when get CellScanner from  HBaseRpcController，so need it in 
RSRpcServices#replay and  RSRpcServices#replicateWALEntry also.
{code}
// rpc controller is how we bring in data via the back door;  it is 
unprotobuf'ed data.
// It is also the conduit via which we pass back data.
HBaseRpcController controller = (HBaseRpcController)rpcc;
CellScanner cellScanner = controller != null ? controller.cellScanner(): 
null;
if (controller != null) {
  controller.setCellScanner(null);
}
{code}

if not we will see the error like the following
{code}
2021-10-18 12:04:13,971 WARN  
[RpcServer.default.FPBQ.Fifo.handler=29,queue=2,port=16022] ipc.RpcServer: 
RpcServer.default.FPBQ.Fifo.handler=29,queue=2,port=16022: caught: 
java.lang.IllegalArgumentException: ReferenceCount : 0 (expected: > 0)
at 
org.apache.hbase.thirdparty.io.netty.util.internal.ObjectUtil.checkPositive(ObjectUtil.java:80)
at org.apache.hadoop.hbase.nio.ByteBuff.checkRefCount(ByteBuff.java:70)
at 
org.apache.hadoop.hbase.nio.SingleByteBuff.hasRemaining(SingleByteBuff.java:155)
at 
org.apache.hadoop.hbase.codec.KeyValueCodec$ByteBuffKeyValueDecoder.advance(KeyValueCodec.java:90)
at 
org.apache.hadoop.hbase.ipc.CellBlockBuilder.encodeCellsTo(CellBlockBuilder.java:191)
at 
org.apache.hadoop.hbase.ipc.CellBlockBuilder.buildCellBlockStream(CellBlockBuilder.java:228)
at 
org.apache.hadoop.hbase.ipc.ServerCall.setResponse(ServerCall.java:243)
at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:168)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338)
at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318)
{code}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-26384) Segment which already flushed to hfile may be still remained in CompactingMemStore

2021-10-20 Thread chenglei (Jira)

chenglei created HBASE-26384:


 Summary: Segment  which already flushed to hfile may be still 
remained in CompactingMemStore 
 Key: HBASE-26384
 URL: https://issues.apache.org/jira/browse/HBASE-26384
 Project: HBase
  Issue Type: Bug
  Components: in-memory-compaction
Affects Versions: 2.4.7, 3.0.0-alpha-1
Reporter: chenglei






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (HBASE-26383) HBCK incorrectly reports inconsistencies for recently split regions following a master failover

2021-10-20 Thread Benoit Sigoure (Jira)

Benoit Sigoure created HBASE-26383:
--

 Summary: HBCK incorrectly reports inconsistencies for recently 
split regions following a master failover
 Key: HBASE-26383
 URL: https://issues.apache.org/jira/browse/HBASE-26383
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 2.4.3
Reporter: Benoit Sigoure


When a region P splits into A and B, following a master failover the newly 
active master reports that P is in an inconsistent state. This seems to be a 
regression introduced in HBASE-25847 (cc [~andrew.purt...@gmail.com]) which 
changed {{regionInfo.isParentSplit()}} to {{regionState.isSplit()}}. The region 
state after restart is CLOSED (rather than SPLIT), so both region state and 
region info should be checked, presumably with {{regionState.isSplit() || 
regionInfo.isSplit()}}. This situation resolves itself on its own when a major 
compaction occurs and P is GCed, but having the master incorrectly report 
inconsistencies is pretty bad. We had a pretty big outage due to a series of 
operator errors as our SRE team was trying to fix this inconsistency that, in 
fact, didn't even exist.

Thanks to Stack for helping look over this issue and Vlad Hanciuta for root 
causing the bug.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (HBASE-25890) [branch-1] add -U for maven build to force a check for updated releases and snapshots on remote repositories

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang reopened HBASE-25890:
---

> [branch-1] add -U for maven build to force a check for updated releases and 
> snapshots on remote repositories
> 
>
> Key: HBASE-25890
> URL: https://issues.apache.org/jira/browse/HBASE-25890
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Blocker
> Fix For: 1.7.0
>
>
> {code}
> [ERROR] Failed to execute goal on project hbase-assembly: Could not resolve 
> dependencies for project org.apache.hbase:hbase-assembly:pom:1.7.0: Could not 
> find artifact org.apache.hbase:hbase-thrift:jar:1.7.0 in apache release 
> (https://repository.apache.org/content/repositories/releases/) -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :hbase-assembly
> {code}
> {code}
> [ERROR] Failed to execute goal on project hbase-assembly: Could not resolve 
> dependencies for project org.apache.hbase:hbase-assembly:pom:1.7.0: Failure 
> to find org.apache.hbase:hbase-thrift:jar:1.7.0 in 
> https://repository.apache.org/content/repositories/releases/ was cached in 
> the local repository, resolution will not be reattempted until the update 
> interval of apache release has elapsed or updates are forced -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :hbase-assembly
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25890) [branch-1] add -U for maven build to force a check for updated releases and snapshots on remote repositories

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-25890.
---
Resolution: Fixed

Cherry-picked to branch-1.4.

> [branch-1] add -U for maven build to force a check for updated releases and 
> snapshots on remote repositories
> 
>
> Key: HBASE-25890
> URL: https://issues.apache.org/jira/browse/HBASE-25890
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Blocker
> Fix For: 1.4.14, 1.7.0
>
>
> {code}
> [ERROR] Failed to execute goal on project hbase-assembly: Could not resolve 
> dependencies for project org.apache.hbase:hbase-assembly:pom:1.7.0: Could not 
> find artifact org.apache.hbase:hbase-thrift:jar:1.7.0 in apache release 
> (https://repository.apache.org/content/repositories/releases/) -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :hbase-assembly
> {code}
> {code}
> [ERROR] Failed to execute goal on project hbase-assembly: Could not resolve 
> dependencies for project org.apache.hbase:hbase-assembly:pom:1.7.0: Failure 
> to find org.apache.hbase:hbase-thrift:jar:1.7.0 in 
> https://repository.apache.org/content/repositories/releases/ was cached in 
> the local repository, resolution will not be reattempted until the update 
> interval of apache release has elapsed or updates are forced -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :hbase-assembly
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25858) [branch-1] make hbase-thrift optional in hbase-assembly module

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-25858.
---
Fix Version/s: 1.7.0
   1.4.14
 Hadoop Flags: Reviewed
   Resolution: Fixed

Cherry-picked to branch-1.4 and it has aleady been in 1.7.0.

Resolve.

> [branch-1] make hbase-thrift optional in hbase-assembly module
> --
>
> Key: HBASE-25858
> URL: https://issues.apache.org/jira/browse/HBASE-25858
> Project: HBase
>  Issue Type: Task
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Blocker
> Fix For: 1.4.14, 1.7.0
>
>
> {code}
> [ERROR] Failed to execute goal on project hbase-assembly: Could not resolve 
> dependencies for project org.apache.hbase:hbase-assembly:pom:1.7.0: Failure 
> to find org.apache.hbase:hbase-thrift:jar:1.7.0 in 
> https://repository.apache.org/content/repositories/releases/ was cached in 
> the local repository, resolution will not be reattempted until the update 
> interval of apache release has elapsed or updates are forced -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25831) [branch-1] remove thrift examples out of hbase-examples module for bypassing the thrift version check

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-25831.
---
Fix Version/s: 1.4.14
   Resolution: Fixed

Cherry-picked to branch-1.4.

> [branch-1] remove thrift examples out of hbase-examples module for bypassing 
> the thrift version check
> -
>
> Key: HBASE-25831
> URL: https://issues.apache.org/jira/browse/HBASE-25831
> Project: HBase
>  Issue Type: Task
>  Components: Thrift
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Blocker
> Fix For: 1.4.14, 1.7.0
>
>
> [ERROR] Failed to execute goal on project hbase-examples: Could not resolve 
> dependencies for project org.apache.hbase:hbase-examples:jar:1.7.0: Could not 
> find artifact org.apache.hbase:hbase-thrift:jar:1.7.0 in apache release 
> (https://repository.apache.org/content/repositories/releases/) -> [Help 1]
> This is the msg when I tried to run make_rc.sh, we need to remove thrift 
> related codes from hbase-examples for making release successfully.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (HBASE-25831) [branch-1] remove thrift examples out of hbase-examples module for bypassing the thrift version check

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang reopened HBASE-25831:
---

> [branch-1] remove thrift examples out of hbase-examples module for bypassing 
> the thrift version check
> -
>
> Key: HBASE-25831
> URL: https://issues.apache.org/jira/browse/HBASE-25831
> Project: HBase
>  Issue Type: Task
>  Components: Thrift
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Blocker
> Fix For: 1.7.0
>
>
> [ERROR] Failed to execute goal on project hbase-examples: Could not resolve 
> dependencies for project org.apache.hbase:hbase-examples:jar:1.7.0: Could not 
> find artifact org.apache.hbase:hbase-thrift:jar:1.7.0 in apache release 
> (https://repository.apache.org/content/repositories/releases/) -> [Help 1]
> This is the msg when I tried to run make_rc.sh, we need to remove thrift 
> related codes from hbase-examples for making release successfully.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Reopened] (HBASE-25804) [branch-1] Make hbase-thrift module build with jdk8

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang reopened HBASE-25804:
---

> [branch-1] Make hbase-thrift module build with jdk8
> ---
>
> Key: HBASE-25804
> URL: https://issues.apache.org/jira/browse/HBASE-25804
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Blocker
> Fix For: 1.7.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25804) [branch-1] Make hbase-thrift module build with jdk8

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-25804.
---
Hadoop Flags: Reviewed
  Resolution: Fixed

Cherry-pick to branch-1.4.

> [branch-1] Make hbase-thrift module build with jdk8
> ---
>
> Key: HBASE-25804
> URL: https://issues.apache.org/jira/browse/HBASE-25804
> Project: HBase
>  Issue Type: Task
>  Components: build
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Blocker
> Fix For: 1.7.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (HBASE-25725) Release 1.7.0

2021-10-20 Thread Duo Zhang (Jira)



 [ 
https://issues.apache.org/jira/browse/HBASE-25725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-25725.
---
Fix Version/s: (was: 1.7.0)
   Resolution: Fixed

> Release 1.7.0
> -
>
> Key: HBASE-25725
> URL: https://issues.apache.org/jira/browse/HBASE-25725
> Project: HBase
>  Issue Type: Task
>Reporter: Reid Chan
>Assignee: Reid Chan
>Priority: Major
>
> Discussion is 
> [here|https://lists.apache.org/thread.html/r34d3fb86d667f8b3e58cbba78655733ac76e10f5883650f4910adc5c%40%3Cuser.hbase.apache.org%3E],
>  this may or may not be the last release of branch-1.
> But please allow me to go through the whole process before making any words. 
> I'll spend the upcoming next whole week to do this release, having said to my 
> employer.
> cc [~andrew.purt...@gmail.com]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE] First release candidate for HBase 1.4.14 is available for download

Re: [DISCUSS] Contribution of a thrift2 python api

[jira] [Resolved] (HBASE-26386) Refactor StoreFileTracker implementations to expose the set method

Re: [DISCUSS] move stable pointer to 2.4.6+

[jira] [Reopened] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[jira] [Created] (HBASE-26387) Modify HEADER.html to reflect recent stable and EOL release line changes

Re: [DISCUSS] move stable pointer to 2.4.6+

[VOTE] First release candidate for HBase 1.4.14 is available for download

Re: [DISCUSS] move stable pointer to 2.4.6+

[jira] [Resolved] (HBASE-26190) High rate logging of BucketAllocatorException: Allocation too big

[jira] [Created] (HBASE-26386) Refactor StoreFileTracker implementations to expose the set method

[jira] [Created] (HBASE-26385) Clear CellScanner when replay

[jira] [Created] (HBASE-26384) Segment which already flushed to hfile may be still remained in CompactingMemStore

[jira] [Created] (HBASE-26383) HBCK incorrectly reports inconsistencies for recently split regions following a master failover

[jira] [Reopened] (HBASE-25890) [branch-1] add -U for maven build to force a check for updated releases and snapshots on remote repositories

[jira] [Resolved] (HBASE-25890) [branch-1] add -U for maven build to force a check for updated releases and snapshots on remote repositories

[jira] [Resolved] (HBASE-25858) [branch-1] make hbase-thrift optional in hbase-assembly module

[jira] [Resolved] (HBASE-25831) [branch-1] remove thrift examples out of hbase-examples module for bypassing the thrift version check

[jira] [Reopened] (HBASE-25831) [branch-1] remove thrift examples out of hbase-examples module for bypassing the thrift version check

[jira] [Reopened] (HBASE-25804) [branch-1] Make hbase-thrift module build with jdk8

[jira] [Resolved] (HBASE-25804) [branch-1] Make hbase-thrift module build with jdk8

[jira] [Resolved] (HBASE-25725) Release 1.7.0

22 matches

Site Navigation

Mail list logo

Footer information