[
https://issues.apache.org/jira/browse/CASSANDRA-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869655#comment-13869655
]
Aleksey Yeschenko commented on CASSANDRA-6569:
----------------------------------------------
bq. Also, would it be possible to get some INFO-level logging (like HH has) on
batchlog replay while we're here?
Sure. What do you have in mind?
> Batchlog replays copy the entire batchlog table into the heap
> -------------------------------------------------------------
>
> Key: CASSANDRA-6569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6569
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Rick Branson
> Assignee: Aleksey Yeschenko
> Fix For: 1.2.14, 2.0.5
>
> Attachments: 6569.txt
>
>
> The current batchlog replay path will read the entire batchlog table into the
> heap. This is pretty bad. This was compounded by CASSANDRA-5762, which caused
> the SELECT statement used by the batchlog replay to bring the entire row into
> memory instead of just the selected columns.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
