Thanks lars,
I ever ran scan to test TTL for several times, the data expired could not be
seen.
In my application scene, the capacity of everyday collecting data should be
almost similar. so the new collecting data should not be more than the data
expired.
Following your way, I forced a major c
I agree. This looks as it should.You also mentioned that you have compactions
enabled.
If you force a major_compact through the HBase shell, will some space be
reclaimed? (careful, this will compact everything in the table, which can put
some load on the net/disks).Lastly, did you stop collectin
As Stack and Andrew said, just wanted to give you fair warning that this
mode may need some love. Likewise, there are probably alternative that run
a bit lighter weight, though you flatter us with the reminder of the long
feature list.
I have no problem with helping to fix and committing fixes to
On:
- Future investment in a design that scales better
Indeed, designing against key value store is different from designing
against RDBMs.
I wonder if you explored an option to abstract the storage layer and using
"single node purposed" store until you grow enough to switch to another one?
E.g
CCing HBase's user ML.
Could you give an example of the row key and example of two different
queries you are making to better understand your case?
Thank you,
Alex Baranau
--
http://cdap.io - open source framework to build and run data applications
on Hadoop & HBase
On Mon, Mar 9, 2015 at 9:00
Glad you got it working. Ops are hard :)
-n
On Tue, Mar 10, 2015 at 4:56 AM, Michele Giusto wrote:
> Nick Dimiduk writes:
>
> >
> > In AWS you should use internal host names, not external host names.
> The
> > reason being is that when a host resolves it's own name, it is
> resolved to
> > the
Sorry, never answered your question about versions. I have 1.0.0 version
of hbase, which has hadoop-common 2.5.1 in its lib folder.
-j
On 3/10/15, 11:36 AM, "Rose, Joseph"
wrote:
>I tried it and it does work now. It looks like the interface for
>hadoop.fs.Syncable changed in March, 2012 to re
I tried it and it does work now. It looks like the interface for
hadoop.fs.Syncable changed in March, 2012 to remove the deprecated sync()
method and define only hsync() instead. The same committer did the right
thing and removed sync() from FSDataOutputStream at the same time. The
remaining hsync(
Nick Dimiduk writes:
>
> In AWS you should use internal host names, not external host names.
The
> reason being is that when a host resolves it's own name, it is
resolved to
> the internal name, which means that's how it is referenced when
entries are
> added to meta. If you use internal host
