On Tue, Oct 23, 2018 at 10:36 AM Stack wrote:
> Heads-up. I'm going to cut an RC0 this evening unless objection. HBASE-21073
> landed this morning as did some other sweet fixes over night.
>
> This didn't happen. A bunch of other nice fixes showed up last night --
thanks for all the hard work --
[
https://issues.apache.org/jira/browse/HBASE-21364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allan Yang resolved HBASE-21364.
Resolution: Fixed
Fix Version/s: 2.2.0
3.0.0
> Procedure holds the lock
[
https://issues.apache.org/jira/browse/HBASE-21265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-21265:
---
Reopen for backport to branch-2.1.
> Split up TestRSGroups
> -
>
> Key:
[
https://issues.apache.org/jira/browse/HBASE-21215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-21215.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.3
2.2.0
[
https://issues.apache.org/jira/browse/HBASE-21364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-21364:
---
Reopen to push to master and branch-2, as HBASE-21384 needs the changes here.
> Procedure holds the
Allan Yang created HBASE-21384:
--
Summary: Procedure with holdlock=false should not be restored lock
when restarts
Key: HBASE-21384
URL: https://issues.apache.org/jira/browse/HBASE-21384
Project: HBase
stack created HBASE-21383:
-
Summary: Change refguide to point at hbck2 instead of hbck1
Key: HBASE-21383
URL: https://issues.apache.org/jira/browse/HBASE-21383
Project: HBase
Issue Type: Bug
stack created HBASE-21382:
-
Summary: [hbck2] Fix the dump of zk, etc., on STDERR/OUT when run
HBCK2 tool
Key: HBASE-21382
URL: https://issues.apache.org/jira/browse/HBASE-21382
Project: HBase
Issue
Yes, because they deployed when 2.6.5 wasn't the latest and they don't want
to deal with the headaches of Hadoop upgrades.
If we do only one, it should be the oldest IMHO.
But if we're just talking about changing thing in new minor releases of
HBase this is moot. We make 2.7.7 the minimum
IMO -- for the 2.6 line, let's just use 2.6.latest (2.6.5).
Hadoop seems to have moved beyond 2.6, it doesn't seem likely that we're
creating a lot of value for our users. Would someone deploying a Hadoop
2.6 release seriously try a release other than the latest?
On 10/22/18 9:32 PM, 张铎(Duo
[
https://issues.apache.org/jira/browse/HBASE-21318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reopened HBASE-21318:
> Make RefreshHFilesClient runnable
> -
>
> Key: HBASE-21318
[
https://issues.apache.org/jira/browse/HBASE-21149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved HBASE-21149.
Resolution: Duplicate
Fix Version/s: (was: 3.0.0)
> TestIncrementalBackupWithBulkLoad may fail
Ted Yu created HBASE-21381:
--
Summary: Document the hadoop versions using which backup and
restore feature works
Key: HBASE-21381
URL: https://issues.apache.org/jira/browse/HBASE-21381
Project: HBase
FYI HADOOP-15878 is tracking publishing impacted versions for the CVE
On Tue, Oct 23, 2018 at 11:37 AM Sean Busbey wrote:
>
> I can get behind more aggressively updating our dependencies to avoid
> CVEs. I don't think we should do this in maintenance releases though.
> Maintenance releases are
The current patch includes documentation changes that impact all
versions, so we'll have to update for that. Happy to deal with those
details on the JIRA though, if we have lazy consensus here on the
overall approach.
On Tue, Oct 23, 2018 at 3:11 PM Stack wrote:
>
> On Tue, Oct 23, 2018 at 9:44
Sean Busbey created HBASE-21380:
---
Summary: TesRSGroups failing
Key: HBASE-21380
URL: https://issues.apache.org/jira/browse/HBASE-21380
Project: HBase
Issue Type: Bug
Affects Versions:
justice created HBASE-21379:
---
Summary: RegionServer Stop by ArrayIndexOutOfBoundsException of
WAL when replication enabled
Key: HBASE-21379
URL: https://issues.apache.org/jira/browse/HBASE-21379
Project:
Jingyun Tian created HBASE-21378:
Summary: checkHBCKSupport blocks assigning hbase:meta or
hbase:namespace when master is not initialized
Key: HBASE-21378
URL: https://issues.apache.org/jira/browse/HBASE-21378
Duo Zhang created HBASE-21377:
-
Summary: Missing stack id when restarting
Key: HBASE-21377
URL: https://issues.apache.org/jira/browse/HBASE-21377
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-20540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-20540.
---
Resolution: Fixed
All sub tasks are done. Let's resolve.
> [umbrella] Hadoop 3 compatibility
>
20 matches
Mail list logo