You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2020/07/09 07:29:00 UTC

[jira] [Comment Edited] (HBASE-11288) Splittable Meta

    [ https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154253#comment-17154253 ] 

Duo Zhang edited comment on HBASE-11288 at 7/9/20, 7:28 AM:
------------------------------------------------------------

{quote}
Let's follow Stack's previous comment? Let's not discuss replicas or caching as they could be applied to either split meta implementation. Let's focus on the tiering issue?
{quote}

I do not know how can we make a cache server for a general root table. Please give a clear design on how to do it.

{quote}
I'm missing something. It is a POC and its intent was to gather information and help answer critical questions like this. So I'm not sure what the concern is against POCs doing what POCs are supposed to be used for? Rest assured for this particular case I am more concerned as to how we came to the decision than the actual decision. It would be best for everyone if we could apply some rigor for something so important.
{quote}
It is you that suggestted we run ITBLL against the POC, not me. Correct me if I'm wrong.

{quote}
It is definitely good for that. But what prevents us from using it for this purpose? Wether it always passes, fails sometimes or fail always we learn something and that is valuable for determining wether proc v2 can support 2-tier now, short term, long term or never. Then we can come to an informed decision. For example we might decide we cannot wait that long for proc v2 to mature so we go with 1-tier.
{quote}
I have shown my opinion above. I do not think this will help. But you're free to run ITBLL by yourself and post the result here, no one can stop you doing this right?

{quote}
It does help but it is still making a compromise to avoid the concerns of 2-tier. Which is why my main concern now is applying some rigor to help us come to a well informed decision as to wether proc v2 cannot support it and we should go with 1-tier. I think proc v2 is what was missing that prevented us from succeeding in the past although it’s possible it may not be mature enough at this stage.
{quote}

I'm a bit confused. Why do you think if proc-v2 can support 2-tier than we should use 2-tier? Please focus on the problem of the 'master local region' itself? Or your point is that 'master local region' does not use 2-tier so it is not a good solution? This does not make sense to me.

Thanks.


was (Author: apache9):
{quote}
Let's follow Stack's previous comment? Let's not discuss replicas or caching as they could be applied to either split meta implementation. Let's focus on the tiering issue?
{quote}

I do not know how can we make a cache server for a general root table. Please give a clear design on how to do it.

{quote}
I'm missing something. It is a POC and its intent was to gather information and help answer critical questions like this. So I'm not sure what the concern is against POCs doing what POCs are supposed to be used for? Rest assured for this particular case I am more concerned as to how we came to the decision than the actual decision. It would be best for everyone if we could apply some rigor for something so important.
{quote}
It is you that suggestted we run ITBLL against the POC, not me. Correct me if I'm wrong.

{quote}
It is definitely good for that. But what prevents us from using it for this purpose? Wether it always passes, fails sometimes or fail always we learn something and that is valuable for determining wether proc v2 can support 2-tier now, short term, long term or never. Then we can come to an informed decision. For example we might decide we cannot wait that long for proc v2 to mature so we go with 1-tier.
{quote}
I have shown my opinion above. I do not think this will help. But you're free to run ITBLL by yourself and post the result here, no one can stop you doing this right?

{quote}
It does help but it is still making a compromise to avoid the concerns of 2-tier. Which is why my main concern now is applying some rigor to help us come to a well informed decision as to wether proc v2 cannot support it and we should go with 1-tier. I think proc v2 is what was missing that prevented us from succeeding in the past although it’s possible it may not be mature enough at this stage.
{quote}

I'm a bit concerned. Why do you think if proc-v2 can support 2-tier than we should use 2-tier? Please focus on the problem of the 'master local region' itself? Or your point is that 'master local region' does not use 2-tier so it is not a good solution? This does not make sense to me.

Thanks.

> Splittable Meta
> ---------------
>
>                 Key: HBASE-11288
>                 URL: https://issues.apache.org/jira/browse/HBASE-11288
>             Project: HBase
>          Issue Type: Umbrella
>          Components: meta
>            Reporter: Francis Christopher Liu
>            Assignee: Francis Christopher Liu
>            Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)