hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <els...@apache.org>
Subject Re: How to avoid write hot spot, While using cross row transactions.
Date Tue, 04 Feb 2020 14:10:50 GMT
They are not dead. I have personally gone through the efforts to keep 
them alive under the Apache Phoenix PMC.

If you have an interest in them, please get involved :)

On 2/3/20 9:13 PM, Kang Minwoo wrote:
> I looked around Apache Omid and Apache Tephra.
> It seems like the dead.
> Are there projects improving?
> 
> Best regards,
> Minwoo Kang
> 
> ________________________________________
> 보낸 사람: Kang Minwoo <minwoo.kang@outlook.com>
> 보낸 날짜: 2020년 1월 10일 금요일 15:37
> 받는 사람: hbase-user
> 제목: Re: How to avoid write hot spot, While using cross row transactions.
> 
> Thanks for your reply.
> 
> I will look around phoenix and tephra.
> 
> Best regards,
> Minwoo Kang
> 
> ________________________________________
> 보낸 사람: 张铎(Duo Zhang) <palomino219@gmail.com>
> 보낸 날짜: 2020년 1월 10일 금요일 15:14
> 받는 사람: hbase-user
> 제목: Re: How to avoid write hot spot, While using cross row transactions.
> 
> Maybe you need Phoenix?
> 
> You need to use special algorithm to get cross region transactions on
> HBase. IIRC, Phoenix has a sub project call Txxx, which implements the
> algorithm described in the google percolator paper.
> 
> Thanks.
> 
> Reid Chan <reidddchan@outlook.com> 于2020年1月10日周五 下午1:47写道:
> 
>> I think you need some more coding works for fulfilling Atomicity in cross
>> region scenario, by aid of some third party softwares, like Zookeeper.
>>
>> AFAIK, Procedure framework in Master may also have ability to do that, but
>> I'm not sure the details of it and if it supports client customized
>> procedure (I remember the answer is negative).
>>
>> Last but not lease, what about trying Phoenix?
>>
>>
>>
>> --------------------------
>>
>> Best regards,
>> R.C
>>
>>
>>
>> ________________________________________
>> From: Kang Minwoo <minwoo.kang@outlook.com>
>> Sent: 10 January 2020 12:51
>> To: user@hbase.apache.org
>> Subject: How to avoid write hot spot, While using cross row transactions.
>>
>> Hello, users.
>>
>> I use MultiRowMutationEndpoint coprocessor for cross row transactions.
>> It has a constraint that is rows must be located in the same region.
>> I removed random hash bytes in the row key.
>> After that, I suffer write hot-spot.
>>
>> But cross row transactions are a core feature in my application. When I
>> put a new data row, I put an index row.
>>
>> Before I use MultiRowMutationEndpoint coprocessor, I had a mismatch
>> between the data row and the index row.
>>
>> Is there any best practice in that situation?
>> I want to avoid write hot-spot and use an index.
>>
>>
>> Best regards,
>> Minwoo Kang
>>

Mime
View raw message