Re: How to designTemporal table in Hbase

I don't think trying to 'mimic' an RDBS table in HBase is a very good idea. They both are completely different from each other, both in design and usage. For example, In order to get the latest value for a given column you don't have to do anything extra. You just do a Get operation on the desired

Re: Major compaction cannot remove deleted rows until the region is split. Strange!

On Wed, Jun 1, 2016 at 10:56 AM, Tianying Chang wrote: > Hi, Stack > > After moving the region and issue a major compact on that region, its size > shrink from 99G down to 24G. So it looks like the region is in a bad state > that cannot recover, close/open it fixed the issue.

Re: HBase Master is shutting down with error

Hey Pranavan, You’ll likely have more luck on the user@hbase.apache.org mailing list. Cheers, Dima On Wed, Jun 1, 2016 at 9:39 AM, Pranavan Theivendiram < pranavan...@cse.mrt.ac.lk> wrote: > Hi Devs, > > I am Pranavan from Sri Lanka. I am doing a GSoC project for apache > pheonix. Please

Re: dfs.block.size recommendations for HBase

>> Does >> the datanode need to read that entire block when HBase tries to fetch data >> from it? No. -Vlad On Wed, Jun 1, 2016 at 8:51 AM, Bryan Beaudreault wrote: > Hello, > > There is very little information that I can find online with regards to > recommended

Re: Major compaction cannot remove deleted rows until the region is split. Strange!

Hi, Stack After moving the region and issue a major compact on that region, its size shrink from 99G down to 24G. So it looks like the region is in a bad state that cannot recover, close/open it fixed the issue. And from the region size metric graph, we can see major compaction stop working

dfs.block.size recommendations for HBase

Hello, There is very little information that I can find online with regards to recommended dfs.block.size setting for HBase. Often it conflates with the HBase blocksize, which we know should be smaller. Any chance we can get some recommendations for dfs.block.size? The default shipped with HDFS

Re: Memstore blocking

hi Stack: 1.Is region always on same machine or do you see this phenomenon on more than one machine? Not always on the same machine, but always on the machine which hold the first region of a table(the only table that its first region cannot flush,when restart the regionserver,

Re: Memstore blocking

hi all: 1.Is region always on same machine or do you see this phenomenon on more than one machine? Not always on the same machine, but always on the machine which hold the first region of a table(the only table that its first region cannot flush,when restart the regionserver, the first