[
https://issues.apache.org/jira/browse/HBASE-19234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-19234.
---
Resolution: Fixed
Assignee: Wellington Chevreuil
Let me resolve (assigning [~wchevreuil] because did
[
https://issues.apache.org/jira/browse/HBASE-21131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-21131.
--
Resolution: Duplicate
Duplicate of HBASE-16870.
> HBase shell 'status
Okay it sounds like we definitely need a better doc about this as a
starting point. I have some additional questions about failure handling;
should we go through them here or in a jira about improving how upgrade
from 2.0/2.1 gets handled?
On Wed, Jan 23, 2019, 07:33 张铎(Duo Zhang) Oh, you
Sergey Shelukhin created HBASE-21767:
Summary: findRegionsToForceFlush could be improved
Key: HBASE-21767
URL: https://issues.apache.org/jira/browse/HBASE-21767
Project: HBase
Issue
Andrew Purtell created HBASE-21766:
--
Summary: TestSimpleRpcScheduler is flaky (branch-1)
Key: HBASE-21766
URL: https://issues.apache.org/jira/browse/HBASE-21766
Project: HBase
Issue Type:
Sean Busbey created HBASE-21765:
---
Summary: Website should point to lists.apache.org
Key: HBASE-21765
URL: https://issues.apache.org/jira/browse/HBASE-21765
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-18531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-18531.
-
Resolution: Duplicate
Fix Version/s: HBASE-15297
> incorrect error msg
>
Zheng Hu created HBASE-21764:
Summary: Size of in-memory compaction thread pool shoud be
configurable
Key: HBASE-21764
URL: https://issues.apache.org/jira/browse/HBASE-21764
Project: HBase
Oh, you misunderstood me. It is just for master, you need make sure that
before you killing the old version master, there is no RITs. And once the
new master is up, everything is fine., as the new master will detect if
there are old style AssignProcedure/UnassignProcedures, if so it will quit
Yes, please. I don't think it's reasonable to expect no region transitions
during a rolling upgrade window; that would imply no servers can crash
during the upgrade.
On Wed, Jan 23, 2019, 07:04 张铎(Duo Zhang) From 1.x it is OK, but from 2.0 or 2.1, we need make sure that there are no
> RITs
>From 1.x it is OK, but from 2.0 or 2.1, we need make sure that there are no
RITs ongoing. We could see if we can make the upgrading more smoothly.
Guanghao Zhang 于2019年1月23日周三 下午8:56写道：
> Our new internal branch is based on branch-2. And we already rolling
> upgrade our staging cluster from
Thank you everyone! It is a great honor for me!
Peter
On Tue, Jan 22, 2019 at 2:36 AM Duo Zhang wrote:
> On behalf of the Apache HBase PMC I am pleased to announce that Peter
> Somogyi
> has accepted our invitation to become a PMC member on the Apache HBase
> project.
> We appreciate Peter
Our new internal branch is based on branch-2. And we already rolling
upgrade our staging cluster from our internal 0.98 branch to it... I will
take a try for 2.0.* to 2.2.0.
Are you saying we need to make sure it can do this? Or are you
> asserting that it already does?
>
It already does.
Sean
[
https://issues.apache.org/jira/browse/HBASE-21686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-21686.
-
Resolution: Fixed
pushed a signed tag for rel/1.2.10,
14 matches
Mail list logo
