Yi Liang created HBASE-18803:
Summary: Mapreduce job get failed caused by NoClassDefFoundError:
org/apache/commons/lang3/ArrayUtils
Key: HBASE-18803
URL: https://issues.apache.org/jira/browse/HBASE-18803
Enis Soztutar created HBASE-18802:
-
Summary: [C++] Remove hbase-macros.h
Key: HBASE-18802
URL: https://issues.apache.org/jira/browse/HBASE-18802
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18733.
---
Resolution: Fixed
Pushed to branch-2 and master.
> [compat 1-2] Hide WALKey
>
>
>
On 9/12/17 2:51 PM, Andrew Purtell wrote:
making backup working in challenging conditions was not a goal of FT
design, correct failure handling was a goal.
Every real-world production environment has challenging conditions.
That said, making progress in the face of failures is only one aspec
> making backup working in challenging conditions was not a goal of FT
design, correct failure handling was a goal.
Every real-world production environment has challenging conditions.
That said, making progress in the face of failures is only one aspect of
FT, and an equally valid one is that fai
Yes, we have already some IT, so will need to upgrade it for scale testing.
On Tue, Sep 12, 2017 at 11:28 AM, Ted Yu wrote:
> bq. we need a test tool similar to ITBLL
>
> How about making the following such a tool ?
>
> hbase-it/src/test/java/org/apache/hadoop/hbase/
> IntegrationTestBackupResto
bq. we need a test tool similar to ITBLL
How about making the following such a tool ?
hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestBackupRestore.java
On Tue, Sep 12, 2017 at 11:25 AM, Vladimir Rodionov
wrote:
> >> Vlad: I'm obviously curious to see what you think about this st
>> Vlad: I'm obviously curious to see what you think about this stuff, in
addition to what you already had in mind :)
Yes, I think that we need a test tool similar to ITBLL. Btw, making backup
working in challenging conditions was not a goal of FT design, correct
failure handling was a goal.
On T
Ted Yu created HBASE-18801:
--
Summary: Bulk load cleanup may falsely deem file deletion
successful
Key: HBASE-18801
URL: https://issues.apache.org/jira/browse/HBASE-18801
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-18010:
---
Reopen so this set of fixes makes it into 2.0. Resolve after it makes it in.
Thanks [~anastas]
> Connect CellCh
stack created HBASE-18800:
-
Summary: [Propaganda] Push shaded hbase-client as gateway to an
hbase cluster going forward
Key: HBASE-18800
URL: https://issues.apache.org/jira/browse/HBASE-18800
Project: HBase
Let me put this one on this thread, G1GC on by default in hbase2?
St.Ack
On Wed, Aug 2, 2017 at 4:38 PM, Stack wrote:
> What are our expectations regards compatibility between hbase1 and hbase2?
>
> Lets have a chat about it. Here are some goal posts.
>
> + You have to upgrade to hbase-1.x befor
Thanks for the quick feedback!
On 9/12/17 12:36 PM, Stack wrote:
On Tue, Sep 12, 2017 at 9:33 AM, Andrew Purtell
wrote:
I think those are reasonable criteria Josh.
What I would like to see is something like "we ran ITBLL (or custom
generator with similar correctness validation if you prefer)
[
https://issues.apache.org/jira/browse/HBASE-18733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-18733:
---
We are not 'purging' WALKey after all; too much work. Reopening to change
audience to Private.
> [compat 1-2] H
On Tue, Sep 12, 2017 at 9:33 AM, Andrew Purtell
wrote:
> I think those are reasonable criteria Josh.
>
> What I would like to see is something like "we ran ITBLL (or custom
> generator with similar correctness validation if you prefer) on a dev
> cluster (5-10 nodes) for 24 hours with server kill
I think those are reasonable criteria Josh.
What I would like to see is something like "we ran ITBLL (or custom generator
with similar correctness validation if you prefer) on a dev cluster (5-10
nodes) for 24 hours with server killing chaos agents active, attempted 1,440
backups (one per minu
On 9/11/17 11:52 PM, Stack wrote:
On Mon, Sep 11, 2017 at 11:07 AM, Vladimir Rodionov
wrote:
...
That is mostly it. Yes, We have not done real testing with real data on a
real cluster yet, except QA testing on a small OpenStack
cluster (10 nodes). That is our probably the biggest minus right
On 9/11/17 11:52 PM, Stack wrote:
On Mon, Sep 11, 2017 at 11:07 AM, Vladimir Rodionov
wrote:
My plan is to finish HBASE-17825 (further performance optimizations). This
will cut down number of MR jobs during incremental backup
from 2*N to 2 (N - number of tables). That will probably take
Chia-Ping Tsai created HBASE-18799:
--
Summary: Revisit the AccessControl
Key: HBASE-18799
URL: https://issues.apache.org/jira/browse/HBASE-18799
Project: HBase
Issue Type: Task
Re
[
https://issues.apache.org/jira/browse/HBASE-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18791.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0-alpha-3
Pushed to branch-2 and mast
Chia-Ping Tsai created HBASE-18798:
--
Summary: Remove the unused methods in RegionServerCoprocessorHost
Key: HBASE-18798
URL: https://issues.apache.org/jira/browse/HBASE-18798
Project: HBase
Abhishek Singh Chouhan created HBASE-18797:
--
Summary: Deprecate Filter#filterKeyValue and add Filter#filterCell
Key: HBASE-18797
URL: https://issues.apache.org/jira/browse/HBASE-18797
Project:
Abhishek Singh Chouhan created HBASE-18796:
--
Summary: Admin#isTableAvailable returns incorrect result before
daughter regions are opened
Key: HBASE-18796
URL: https://issues.apache.org/jira/browse/HBASE-1
[
https://issues.apache.org/jira/browse/HBASE-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan resolved HBASE-10944.
Resolution: Won't Fix
We wont't be removing Kv.getBuffer() instead only exp
[
https://issues.apache.org/jira/browse/HBASE-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan reopened HBASE-10944:
MArking proper resolution.
> Remove all kv.getBuffer() and kv.getRow() referen
ramkrishna.s.vasudevan created HBASE-18795:
--
Summary: Expose KeyValue.getBuffer() for tests alone
Key: HBASE-18795
URL: https://issues.apache.org/jira/browse/HBASE-18795
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan resolved HBASE-7320.
---
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-3
3.0.0
[
https://issues.apache.org/jira/browse/HBASE-10944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan resolved HBASE-10944.
Resolution: Fixed
Fix Version/s: (was: 1.5.0)
KeyValue.getRow()
Chia-Ping Tsai created HBASE-18794:
--
Summary: Remove deprecated methods in MasterObserver
Key: HBASE-18794
URL: https://issues.apache.org/jira/browse/HBASE-18794
Project: HBase
Issue Type: S
29 matches
Mail list logo
