[
https://issues.apache.org/jira/browse/CASSANDRA-13481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15988156#comment-15988156
]
ASF GitHub Bot commented on CASSANDRA-13481:
--------------------------------------------
GitHub user Garciat opened a pull request:
https://github.com/apache/cassandra/pull/107
[CASSANDRA-13481] Provide a method for flushing a CQLSSTableWriter
Jira: https://issues.apache.org/jira/browse/CASSANDRA-13481
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Garciat/cassandra CASSANDRA-13481
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cassandra/pull/107.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #107
----
commit 23c913f4642cc2463966f86dba6a24b987bc0f0a
Author: Gabriel Garcia <garc...@live.com>
Date: 2017-04-28T03:33:28Z
Provide a method for flushing a CQLSSTableWriter.
----
> Provide a method for flushing a CQLSSTableWriter
> ------------------------------------------------
>
> Key: CASSANDRA-13481
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13481
> Project: Cassandra
> Issue Type: Wish
> Reporter: Gabriel Garcia
> Priority: Minor
> Fix For: 3.11.0
>
>
> The buffer size estimation in SSTableSimpleUnsortedWriter is not very
> accurate and causes OOM errors quite often (or lots of GC pressure) for my
> specific use case (rows that vary greatly in # of columns). I guess if the
> user knows their data well enough, they can schedule flushes when really
> needed.
> It's just an idea, not sure if flushing would actually help. However, playing
> with bufferSizeInMB is not of much help.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
