You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by Guanghao Zhang <zg...@gmail.com> on 2019/09/19 00:55:40 UTC
NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please
avoid downloading these releases. If you already running these versions in
your cluster, please use splitormerge_switch to disable region merge
now. See HBASE-23044 for more details.
Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack
for branch-2.0, do we need a more release 2.0.7?
Thanks
Guanghao Zhang
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by Guanghao Zhang <zg...@gmail.com>.
>
> Either we call merge manually, or the region normalizer is enabled?
Got it. I found this because I use hbck2 to fixMeta overlap many times.
fixMeta overlap will call merge manually.
张铎(Duo Zhang) <pa...@gmail.com> 于2019年9月19日周四 上午11:04写道：
> I do not think we will merge regions automatically? Either we call merge
> manually, or the region normalizer is enabled? And the way to produce the
> bug is a bit complicated, need multiple round of mergings.
>
> So agree that we should roll new releases soon, but the actual damage
> should be fine.
>
> Guanghao Zhang <zg...@gmail.com> 于2019年9月19日周四 上午8:55写道：
>
> > Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine.
> Please
> > avoid downloading these releases. If you already running these versions
> in
> > your cluster, please use splitormerge_switch to disable region merge
> > now. See HBASE-23044 for more details.
> >
> > Need to rolling new release for branch-2.1 and branch-2.2 line. Ping
> @stack
> > for branch-2.0, do we need a more release 2.0.7?
> >
> > Thanks
> > Guanghao Zhang
> >
>
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by Guanghao Zhang <zg...@gmail.com>.
>
> Either we call merge manually, or the region normalizer is enabled?
Got it. I found this because I use hbck2 to fixMeta overlap many times.
fixMeta overlap will call merge manually.
张铎(Duo Zhang) <pa...@gmail.com> 于2019年9月19日周四 上午11:04写道：
> I do not think we will merge regions automatically? Either we call merge
> manually, or the region normalizer is enabled? And the way to produce the
> bug is a bit complicated, need multiple round of mergings.
>
> So agree that we should roll new releases soon, but the actual damage
> should be fine.
>
> Guanghao Zhang <zg...@gmail.com> 于2019年9月19日周四 上午8:55写道：
>
> > Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine.
> Please
> > avoid downloading these releases. If you already running these versions
> in
> > your cluster, please use splitormerge_switch to disable region merge
> > now. See HBASE-23044 for more details.
> >
> > Need to rolling new release for branch-2.1 and branch-2.2 line. Ping
> @stack
> > for branch-2.0, do we need a more release 2.0.7?
> >
> > Thanks
> > Guanghao Zhang
> >
>
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
I do not think we will merge regions automatically? Either we call merge
manually, or the region normalizer is enabled? And the way to produce the
bug is a bit complicated, need multiple round of mergings.
So agree that we should roll new releases soon, but the actual damage
should be fine.
Guanghao Zhang <zg...@gmail.com> 于2019年9月19日周四 上午8:55写道：
> Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please
> avoid downloading these releases. If you already running these versions in
> your cluster, please use splitormerge_switch to disable region merge
> now. See HBASE-23044 for more details.
>
> Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack
> for branch-2.0, do we need a more release 2.0.7?
>
> Thanks
> Guanghao Zhang
>
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
I do not think we will merge regions automatically? Either we call merge
manually, or the region normalizer is enabled? And the way to produce the
bug is a bit complicated, need multiple round of mergings.
So agree that we should roll new releases soon, but the actual damage
should be fine.
Guanghao Zhang <zg...@gmail.com> 于2019年9月19日周四 上午8:55写道：
> Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please
> avoid downloading these releases. If you already running these versions in
> your cluster, please use splitormerge_switch to disable region merge
> now. See HBASE-23044 for more details.
>
> Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack
> for branch-2.0, do we need a more release 2.0.7?
>
> Thanks
> Guanghao Zhang
>
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by Sean Busbey <bu...@apache.org>.
I'm scheduled to remove 2.0 related materials tomorrow, so I'd really
like us to avoid restarting that clock.
As far as known issues, just make sure the affected version(s) include
2.0.6 and call it a day.
On Thu, Sep 19, 2019 at 11:04 AM Stack <st...@duboce.net> wrote:
>
> First, good find Guanghao. Thanks for the fix.
>
> I can roll RCs for branch-2 (Would be good to do it after
> hbase-operator-tools goes out because then these new releases become
> candidates for the stable pointer).
>
> On branch-2.0, given its EOM, I could add a 'KNOWN_ISSUES.md' file to
> http://apache.mirrors.lucidnetworks.net/hbase/2.1.6/ and list this issue in
> it. Then update the note in the download page to point at new known issues
> doc? (Suggestions appreciated).
>
> S
>
>
>
> On Wed, Sep 18, 2019 at 5:55 PM Guanghao Zhang <zg...@gmail.com> wrote:
>
> > Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please
> > avoid downloading these releases. If you already running these versions in
> > your cluster, please use splitormerge_switch to disable region merge
> > now. See HBASE-23044 for more details.
> >
> > Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack
> > for branch-2.0, do we need a more release 2.0.7?
> >
> > Thanks
> > Guanghao Zhang
> >
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by Sean Busbey <bu...@apache.org>.
I'm scheduled to remove 2.0 related materials tomorrow, so I'd really
like us to avoid restarting that clock.
As far as known issues, just make sure the affected version(s) include
2.0.6 and call it a day.
On Thu, Sep 19, 2019 at 11:04 AM Stack <st...@duboce.net> wrote:
>
> First, good find Guanghao. Thanks for the fix.
>
> I can roll RCs for branch-2 (Would be good to do it after
> hbase-operator-tools goes out because then these new releases become
> candidates for the stable pointer).
>
> On branch-2.0, given its EOM, I could add a 'KNOWN_ISSUES.md' file to
> http://apache.mirrors.lucidnetworks.net/hbase/2.1.6/ and list this issue in
> it. Then update the note in the download page to point at new known issues
> doc? (Suggestions appreciated).
>
> S
>
>
>
> On Wed, Sep 18, 2019 at 5:55 PM Guanghao Zhang <zg...@gmail.com> wrote:
>
> > Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please
> > avoid downloading these releases. If you already running these versions in
> > your cluster, please use splitormerge_switch to disable region merge
> > now. See HBASE-23044 for more details.
> >
> > Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack
> > for branch-2.0, do we need a more release 2.0.7?
> >
> > Thanks
> > Guanghao Zhang
> >
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by Stack <st...@duboce.net>.
First, good find Guanghao. Thanks for the fix.
I can roll RCs for branch-2 (Would be good to do it after
hbase-operator-tools goes out because then these new releases become
candidates for the stable pointer).
On branch-2.0, given its EOM, I could add a 'KNOWN_ISSUES.md' file to
http://apache.mirrors.lucidnetworks.net/hbase/2.1.6/ and list this issue in
it. Then update the note in the download page to point at new known issues
doc? (Suggestions appreciated).
S
On Wed, Sep 18, 2019 at 5:55 PM Guanghao Zhang <zg...@gmail.com> wrote:
> Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please
> avoid downloading these releases. If you already running these versions in
> your cluster, please use splitormerge_switch to disable region merge
> now. See HBASE-23044 for more details.
>
> Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack
> for branch-2.0, do we need a more release 2.0.7?
>
> Thanks
> Guanghao Zhang
>
Re: NOTICE: hbase-2.2.1, 2.1.6 and 2.0.6 have a bug may cause data loss
Posted by Stack <st...@duboce.net>.
First, good find Guanghao. Thanks for the fix.
I can roll RCs for branch-2 (Would be good to do it after
hbase-operator-tools goes out because then these new releases become
candidates for the stable pointer).
On branch-2.0, given its EOM, I could add a 'KNOWN_ISSUES.md' file to
http://apache.mirrors.lucidnetworks.net/hbase/2.1.6/ and list this issue in
it. Then update the note in the download page to point at new known issues
doc? (Suggestions appreciated).
S
On Wed, Sep 18, 2019 at 5:55 PM Guanghao Zhang <zg...@gmail.com> wrote:
> Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please
> avoid downloading these releases. If you already running these versions in
> your cluster, please use splitormerge_switch to disable region merge
> now. See HBASE-23044 for more details.
>
> Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack
> for branch-2.0, do we need a more release 2.0.7?
>
> Thanks
> Guanghao Zhang
>