[
https://issues.apache.org/jira/browse/USERGRID-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334385#comment-14334385
]
Todd Nine commented on USERGRID-405:
------------------------------------
We also have to create a unique property ledger. We're going to need to follow
the same pattern, however, we can restrict the size of the input, greatly
reducing this problem of load since we'll only be storing a single property,
not the entire entity.
> Fix hotspot from continuous writes of entities
> ----------------------------------------------
>
> Key: USERGRID-405
> URL: https://issues.apache.org/jira/browse/USERGRID-405
> Project: Usergrid
> Issue Type: Story
> Reporter: Todd Nine
> Assignee: Todd Nine
>
> Currently, performing a continuous PUT in 2.0 under heavy load causes a
> hotspot in our cassandra data.
> Cause:
> # Under load, entities can be PUT continuously
> # Asynchronous cleanups run and delete previous versions
> # These versions are retained in cassandra for long periods of time. This
> causes severe row bloating before compaction occurs.
> Solution:
> For entity data, we only care about the current max version. We should
> change this column family to store only the maximum data format. We will
> need to keep the log of previous versions, so that we can bring ES into a
> consistent state
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
