[
https://issues.apache.org/jira/browse/HBASE-21354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-21354:
---
Compile error on master.
> Procedure may be deleted improperly during master restarts resulting in
>
Sakthi created HBASE-21362:
--
Summary: Disable printing of stack-trace in shell when quotas are
violated
Key: HBASE-21362
URL: https://issues.apache.org/jira/browse/HBASE-21362
Project: HBase
Issue
Sakthi created HBASE-21361:
--
Summary: Disable printing of stack-trace in shell when quotas are
not enabled
Key: HBASE-21361
URL: https://issues.apache.org/jira/browse/HBASE-21361
Project: HBase
Sakthi created HBASE-21360:
--
Summary: Disable printing of stack-trace in shell for quotas
Key: HBASE-21360
URL: https://issues.apache.org/jira/browse/HBASE-21360
Project: HBase
Issue Type:
I believe if there is a CVE for any of the dependencies we should try to
upgrade it, and IIRC there is an issue about finding these dependencies out
automatically. We haven't done this before does not mean ignoring a CVE is
the correct way, it is just because no one takes care of it...
And the
We should react to all CVEs if we’re going to. Fine to start now.
> On Oct 22, 2018, at 6:50 PM, Sean Busbey wrote:
>
> Has the Hadoop PMC put out a public notice on the impact of that CVE yet?
> Specifically have they stated what versions are vulnerable? Are we flagging
> all versions
Has the Hadoop PMC put out a public notice on the impact of that CVE yet?
Specifically have they stated what versions are vulnerable? Are we flagging
all versions impacted by it as "HBase says keep away"?
Is there some reason this particular CVE especially impacts users of HBase?
I presume not
See here:
https://access.redhat.com/security/cve/cve-2018-8009
All 2.7.x releases before 2.7.7 have the problem. And for 2.6.x, the hadoop
team seems to drop the support as there is no release about two years, so
either we keep the original support versions, or we just drop the support
for the
Zach you fine with conversation about this on the JIRA or you wanna do on
the list?
On Mon, Oct 22, 2018, 19:51 Zach York wrote:
> What is the main reason for the change? Build time speedup?
>
> Any reason for testing all of the 2.6.x line, but not the 2.7.x line? We
> don't check at all for
What is the main reason for the change? Build time speedup?
Any reason for testing all of the 2.6.x line, but not the 2.7.x line? We
don't check at all for 2.8.x?
Can we be more consistent with how we test compatibility? (Do we only care
about the latest patch release in a line?)
Sorry If I'm
Please leave me time to review before it is committed.
On Mon, Oct 22, 2018, 13:58 Stack wrote:
> Duo has a patch up on HBASE-20970 that changes the Hadoop versions we check
> at build time. Any objections to committing to branch-2.1+?
>
> It makes following changes:
>
> 2.6.1 2.6.2 2.6.3 2.6.4
Andrew Purtell created HBASE-21359:
--
Summary: Fix build problem against Hadoop 2.8.5
Key: HBASE-21359
URL: https://issues.apache.org/jira/browse/HBASE-21359
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-21294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-21294.
Resolution: Fixed
Hadoop Flags: Reviewed
Just put the original change and the addendums
Duo has a patch up on HBASE-20970 that changes the Hadoop versions we check
at build time. Any objections to committing to branch-2.1+?
It makes following changes:
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 2.7.4
becomes
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.7
And...
3.0.0
goes to
3.0.3
Andrew Purtell created HBASE-21358:
--
Summary: Snapshot procedure fails but SnapshotManager thinks it is
still running
Key: HBASE-21358
URL: https://issues.apache.org/jira/browse/HBASE-21358
Project:
On Mon, Oct 22, 2018 at 10:21 AM Josh Elser wrote:
> Orthogonal question: you codifying the "damage" you're doing?
>
>
No.
What you thinking? Writing unit tests that launch substantial clusters that
get damaged in various ways? We'd then use tools to fix and confirm
wholesomeness?
If so,
On Mon, Oct 22, 2018 at 10:00 AM Mike Drob wrote:
> Stack - I'm still working on HBASE-21073, there were tests that failed in
> precommit so I launched a retry. Please don't cut an RC without it.
>
>
NP. HBASE-21073 is not a blocker though. Hopefully lands in next day or so.
Thanks,
S
> On
Orthogonal question: you codifying the "damage" you're doing?
I remember trying to debug hbck1 unit test failures (and it was a pain).
Coming back with fresh/high-level test scenarios sounds like a great way
to keep quality on hbck2 up.
On 10/19/18 1:32 PM, Stack wrote:
* Lots of progress
Stack - I'm still working on HBASE-21073, there were tests that failed in
precommit so I launched a retry. Please don't cut an RC without it.
On Mon, Oct 22, 2018 at 11:56 AM Stack wrote:
> Back again
>
> Lets push out a 2.1.1RC0.
>
> Here are the list of outstanding issues:
>
Back again
Lets push out a 2.1.1RC0.
Here are the list of outstanding issues:
https://issues.apache.org/jira/projects/HBASE/versions/12343470
Nightlies are gettting better [1] but still some flakies in the mix[2].
If you are up for helping or you own any of the above outstanding issues,
[
https://issues.apache.org/jira/browse/HBASE-20331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-20331.
-
Resolution: Fixed
Fix Version/s: (was: 2.2.0)
(was: 3.0.0)
Allan Yang created HBASE-21357:
--
Summary: RS should abort if OOM in Reader thread
Key: HBASE-21357
URL: https://issues.apache.org/jira/browse/HBASE-21357
Project: HBase
Issue Type: Bug
22 matches
Mail list logo
