On Fri, Jun 15, 2012 at 10:50 AM, Em wrote:
> what are your experience with having more than one HBase-instance per
> machine?
>
My experience is ittle.
Its been done though by others on this list.
> One reason to do this could be that you got i.e. 32 GB RAM and want to
> give 12-14 GB of RAM t
Hello list,
what are your experience with having more than one HBase-instance per
machine?
One reason to do this could be that you got i.e. 32 GB RAM and want to
give 12-14 GB of RAM to each HBase instance so that you got little
issues with Garbage Collection while using the available RAM-capacit
Hi Cristina:
My understanding of HBase is that the isolation level fro read ops is Read
Committed. There is only write lock which could protect the data from
modifying by other requests but there is no read-lock (it is there but it
doesn't have any effect). Since put ops are atomic, it can succeed
Thought about this a little bit more...
You will want two tables for a solution.
1 Table is Key: Unique ID
Column: FilePathValue: Full Path to file
Column: Last Update timeValue: timestamp
2 Table is Key: Last Update time(The
Hi Ash,
What Dave said.
MemStore's are part of the write path only. BlockCache is part of the read path
only respectively. They only compete for heap on their own right, but have
otherwise no direct relation.
Lars
On Jun 13, 2012, at 10:15 PM, Dave Revell wrote:
> Here's a good starting poin
Hi,
I have read that Hbase has read committed as isolation level, but I have some
doubts.
Is it possible to chage this level, for instance to read uncommitted? How could
I do this?
Another question, Is this isolation level based on locks? I have doubts because
Hbase has multiversion concurrency co
Hi Ben,
See inline...
On Jun 15, 2012, at 6:56 AM, Ben Kim wrote:
> Hi,
>
> I've been posting questions in the mailing-list quiet often lately, and
> here goes another one about data locality
> I read the excellent blog post about data locality that Lars George wrote
> at http://www.larsgeorge.
