taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-941241199
merged and if we need a new documentation, we can have a followup JIRA
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-941241199
merged and if we need a new documentation, we can have a followup JIRA
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-916299365
@joshelser should we wait till add the documentation in this commit ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-760640589
I have fixed the conflicts, probably will push it in two days and see if you
guys have any comments.
This is an au
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-751833447
thanks Duo for your understanding and comments ;) and happy holidays!
@z-york your point on idempotent is good, but at this point will you agree
that we create a follow up o
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-736772662
> Is clumsy operator deleting the meta location znode by mistake a valid
failure mode ?
no this is a special case that we have been supporting, where the HBase
cluster freshly
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-679418281
so.how can we get consensus on this PR or this series of idempotent
issues (for InitMetaProcedure) ? I don't mind to break them into more tasks as
Zach has created those follow
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-674265891
I apologized for the dev@ email, but I was thinking differently overnight
about your suggestion (sorry that I reread many times until I found the gap
this morning)
> You can
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-673880783
> how we could start a cluster with no data on zookeeper?
IMO the title of the google design may be going on the cloud use cases that
has been restarting on just HFiles with
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-673751605
> should not depend on the data on zookeeper.
I agreed with you that we may not be ready to totally skip relying on the
data stored on zookeeper, that's definitely a boarder
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-673253206
first of all, thanks Duo again.
> I think for the scenario here, we just need to write the cluster id and
other things to zookeeper? Just make sure that the current code in
taklwu commented on pull request #2237:
URL: https://github.com/apache/hbase/pull/2237#issuecomment-672204387
Thanks @Apache9 , I want to agree with you to have a HBCK option, but one
concern I have and keep struggling about making this automated instead of HBCK
options. If one HBase clust
12 matches
Mail list logo
