>
> We've done the work to make sure hbase:meta
> is up before everything else. It has its own WALs so we can split these
> ahead of user-space WALs, and so on. We've not done the work to for
> hbase:replication or hbase:namespace, hbase:acl... etc.
If we import a new SYSTEM-TABLE-ONLY state for r
stack created HBASE-20213:
-
Summary: [LOGGING] Aligning formatting and logging less
(compactions, in-memory compactions)
Key: HBASE-20213
URL: https://issues.apache.org/jira/browse/HBASE-20213
Project: HBase
The HBASE-15867 will not be introduced into 2.0.0, I expect to introduce
in 2.1.0 release .
Thanks.
On Fri, Mar 16, 2018 at 12:45 AM, Mike Drob wrote:
> I'm also +1 for splitting RS startup into multiple steps.
>
> Looking at the linked JIRA and the parent issue it was not immediately
> appar
[
https://issues.apache.org/jira/browse/HBASE-19713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-19713.
Resolution: Won't Fix
The PR enabling filter only Public class have been merged to
warbuck
Chia-Ping Tsai created HBASE-20212:
--
Summary: Make all Public classes have InterfaceAudience category
Key: HBASE-20212
URL: https://issues.apache.org/jira/browse/HBASE-20212
Project: HBase
I
On Thu, Mar 15, 2018 at 5:39 PM, 张铎(Duo Zhang)
wrote:
>
> But for other stuffs for replication, such as the WAL files we need to
> replicate, the row key will be a peer id, and multiplies the server name,
> and maybe also the file name? This is a completely different thing. If we
> put this in me
IIRC there is an issue on compiling hbase on arm, and the guy there faced
the same problem. Seems the final solution is that they filed an issue for
the protobuf project and now there is a pre complied binary for arm64
available in the central maven repo...
http://central.maven.org/maven2/com/goog
The problem for putting more things in meta is that, the row key pattern
are different. For example, when re-implementing the serial replication
feature, the 'replication barrier', which is actually the sequence of the
open sequence number for a region, is stored in meta as the row key can the
regi
[
https://issues.apache.org/jira/browse/HBASE-18788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-18788.
---
Resolution: Not A Problem
Hadoop Flags: (was: Reviewed)
The old TestSerialReplication has alr
[
https://issues.apache.org/jira/browse/HBASE-20210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-20210.
---
Resolution: Fixed
Assignee: stack
Hadoop Flags: Reviewed
Pushed to master. Thanks [~psomogyi]
BELUGA BEHR created HBASE-20211:
---
Summary: ReadOnlyBufferException In UnsafeAccess
Key: HBASE-20211
URL: https://issues.apache.org/jira/browse/HBASE-20211
Project: HBase
Issue Type: Bug
On 3/15/18 3:45 PM, Stack wrote:
On Thu, Mar 15, 2018 at 12:03 PM, Josh Elser wrote:
I'm faced with what I think is a tricky issue. I'm trying to help folks to
compile HBase on PPC. The protobuf community does not publish a PPC binary
for protoc which means that the HBase build can't generat
I ran TestThriftHttpServer from the tip of branch-1.3 and it passed.
FYI
On Thu, Mar 15, 2018 at 12:23 PM, Artem Ervits
wrote:
> *+0 (non-binding) - see NOKs below*
>
> Hadoop Pseudo-distrbibuted: 2.7.5
> $M2_HOME from scratch
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 20
On Thu, Mar 15, 2018 at 12:03 PM, Josh Elser wrote:
> I'm faced with what I think is a tricky issue. I'm trying to help folks to
> compile HBase on PPC. The protobuf community does not publish a PPC binary
> for protoc which means that the HBase build can't generate our protobuf
> files. Protobuf
*+0 (non-binding) - see NOKs below*
Hadoop Pseudo-distrbibuted: 2.7.5
$M2_HOME from scratch
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T19:49:05Z)
Maven home: /opt/maven/apache-maven-3.5.3
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java
I'm faced with what I think is a tricky issue. I'm trying to help folks
to compile HBase on PPC. The protobuf community does not publish a PPC
binary for protoc which means that the HBase build can't generate our
protobuf files. Protobuf supports: x86/x86_64 for linux, windows, and
osx in 3.3.0
On Wed, Mar 14, 2018 at 11:55 PM, OpenInx wrote:
> Hi :
>
> (Paste from https://issues.apache.org/jira/browse/HBASE-20166?
> focusedCommentId=16399886&page=com.atlassian.jira.
> plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16399886)
>
> There's a really big problem here if we use table
Sent.
On 3/15/18 6:32 AM, Rotem Tamir wrote:
hi
can i get an invite to the hbase slack org?
thx
[
https://issues.apache.org/jira/browse/HBASE-18216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-18216.
---
Resolution: Fixed
Re-resolving. My backport trashed branch-1. Sorry about that [~apurtell] (Just
saw the dam
[
https://issues.apache.org/jira/browse/HBASE-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-13840.
---
Resolution: Duplicate
Fix Version/s: (was: 1.5.0)
(was: 2.0.0)
Clos
stack created HBASE-20210:
-
Summary: Note in refguide that RSGroups API is private, not for
public consumption; shell is only access
Key: HBASE-20210
URL: https://issues.apache.org/jira/browse/HBASE-20210
Pro
I'm also +1 for splitting RS startup into multiple steps.
Looking at the linked JIRA and the parent issue it was not immediately
apparent if this is an issue for 2.0 or not - can somebody clarify?
On Thu, Mar 15, 2018 at 5:14 AM, 张铎(Duo Zhang)
wrote:
> I'm +1 on the second solution.
>
> 2018-03
BELUGA BEHR created HBASE-20209:
---
Summary: Do Not Use Both Map containsKey and get Methods
Key: HBASE-20209
URL: https://issues.apache.org/jira/browse/HBASE-20209
Project: HBase
Issue Type: Imp
hi
can i get an invite to the hbase slack org?
thx
BELUGA BEHR created HBASE-20208:
---
Summary: Review of SequenceIdAccounting.java
Key: HBASE-20208
URL: https://issues.apache.org/jira/browse/HBASE-20208
Project: HBase
Issue Type: Improvement
Biju Nair created HBASE-20207:
-
Summary: Update doc on the steps to revert RegionServer groups
feature
Key: HBASE-20207
URL: https://issues.apache.org/jira/browse/HBASE-20207
Project: HBase
Issu
Duo Zhang created HBASE-20206:
-
Summary: WALEntryStream should not switch WAL file silently
Key: HBASE-20206
URL: https://issues.apache.org/jira/browse/HBASE-20206
Project: HBase
Issue Type: Bug
I'm +1 on the second solution.
2018-03-15 16:59 GMT+08:00 Guanghao Zhang :
> From a more general perspective, this may be a general problem as we may
> move more and more data from zookeeper to system table. Or we may have more
> features to create new system table. But if the RS relays some syst
Zheng Hu created HBASE-20205:
Summary: Let all replication related UTs can work fine on both ZK
based storage and Table based storage
Key: HBASE-20205
URL: https://issues.apache.org/jira/browse/HBASE-20205
>From a more general perspective, this may be a general problem as we may
move more and more data from zookeeper to system table. Or we may have more
features to create new system table. But if the RS relays some system table
to start up, we will meet a dead lock...
One solution is let master to s
> I think unless we can make the regionserver start without replication,
and initialize it later, otherwise we can not break the tie
Yes, what we thought before was : we can assign all system table in
master because it run as a region server now in 2.0. the problem is once we
restart the master
Oh, it should be 'The replication peer related data is small'.
2018-03-15 15:56 GMT+08:00 张铎(Duo Zhang) :
> I think this is a bit awkward... A region server even does not need the
> meta table to be online when starting, but it needs another system table
> when starting...
>
> I think unless we c
I think this is a bit awkward... A region server even does not need the
meta table to be online when starting, but it needs another system table
when starting...
I think unless we can make the regionserver start without replication, and
initialize it later, otherwise we can not break the tie. Havi
33 matches
Mail list logo
