[
https://issues.apache.org/jira/browse/HBASE-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979629#action_12979629
]
Jonathan Gray commented on HBASE-3434:
--------------------------------------
That will only work if the working set of counters will fit in memory. When
that is no longer the case is generally when you also see a rapid decline in
performance and throughput.
Also, the in-memory setting is not "in memory only" but just gives blocks from
that family a higher priority in the LRU.
> ability to increment a counter without reading original value from storage
> --------------------------------------------------------------------------
>
> Key: HBASE-3434
> URL: https://issues.apache.org/jira/browse/HBASE-3434
> Project: HBase
> Issue Type: Improvement
> Components: client, regionserver
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
>
> There are a bunch of applications that do read-modify-write operations on
> HBase constructs, e.g a counter; The counter value has to be read in from
> hdfs before it can be incremented. We have an application where the number
> of increments on a counter far outnumbers the number of times the counter is
> used or read. For these type of applications, it will be very beneficial to
> not have to read in the counter from disk before it can be incremented.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
