Hi Duo,
Both replication and the backup&restore work suffer from this problem.
The approach we think will work best is that when we get to a certain
size-limit (e.g. 100MB), we will take the current Log Stream (the RAFT
quorum), flip over the RegionServer to use a new Log Stream, and then
wri
How do we deal with replication? It is file based...
2018-05-08 10:12 GMT+08:00 Josh Elser :
>
>
> On 5/7/18 2:53 PM, Stack wrote:
>
>> On Thu, May 3, 2018 at 9:04 AM, Josh Elser wrote:
>>
>> Hi,
>>>
>>> ... I'm happy to delve some more into how I think we can implement this.
>>>
>>> I'd be inte
On 5/7/18 2:53 PM, Stack wrote:
On Thu, May 3, 2018 at 9:04 AM, Josh Elser wrote:
Hi,
... I'm happy to delve some more into how I think we can implement this.
I'd be interested in this part.
St.Ack
You got it, boss. Let me find the time to get that document exported as
well. Will get b
Thanks for the read, Lars!
That's a good question on the sequenceid part. Like my reply to
Chia-Ping, I don't think I have a good answer at this point.
I would assume that there could/should be common sequenceid logic across
WAL implementations, but I'm not sure if it's better done as "helper
Thanks for the read, Chia-Ping!
I don't have a good answer for you at this point, but that's a good
question.
I think a significant part of the core WAL refactoring work will require
us to work with all of the various WAL impls we're accruing :)
* FSHWAL
* AsyncWAL
* WALLess
* Ratis-WAL
Th
On Thu, May 3, 2018 at 9:04 AM, Josh Elser wrote:
> Hi,
>
> ... I'm happy to delve some more into how I think we can implement this.
>
> I'd be interested in this part.
St.Ack
> - Josh
>
> [1] https://docs.google.com/document/d/1Su5py_T5Ytfh9RoTTX2s20Kb
> SJwBHVxbO7ge5ORqbCk/edit#
> [2] http
Thanks for the great sharing Josh. I have benefited greatly from the docs.
Just curious. There is another related issue about walless.
https://issues.apache.org/jira/browse/HBASE-20003. I have absolutely no
imagination..but how we integrate both features to hbase? to be exact, does
they have si
Josh,
thanks to you (and all the others working on this). I did read it once and
I think it sounds very sane. It answers questions that I face more and more
from customers. I have not looked at Ratis in detail so I can't comment on
the challenge of adopting it but I agree with the comments on avoi
Hi,
I'm pleased to finally be able to share this design document with you
all. It's the result of internal review from half a dozen or so from
within our community (Enis, Devaraj, Artem, and Clay easily come to
mind) after multiple months of review and iteration.
Abstract:
Infrastructure a
