[
https://issues.apache.org/jira/browse/CASSANDRA-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431679#comment-15431679
]
Jason Brown commented on CASSANDRA-12384:
-
I think there's a discrepancy in the log line emitted by the c* patch versus
what the dtest patch is looking for:
cassandra:
{code}logger.warn("Writing large partition {}/{}:{} ({} bytes to sstable {}) ",
metadata.ksName, metadata.cfName, keyString,
FBUtilities.prettyPrintMemory(rowSize), getFilename());{code}
dtest:
{code}node.watch_log_for('{} large partition ks/large:user \({}\ to sstable
'.format(verb, sizematcher), from_mark=mark, timeout=180){code}
The cassandra patch will will "bytes to sstable", while the dtest looks for "to
sstable" ("bytes " is missing)
> Include info about sstable on "Compacting large row” message
>
>
> Key: CASSANDRA-12384
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12384
> Project: Cassandra
> Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: sankalp kohli
>Priority: Trivial
> Attachments: CASSANDRA-12384_3.0.txt, CASSANDRA-12384_trunk.txt,
> Dtest.txt
>
>
> On a message like this one, it would be helpful to understand which sstable
> this large row is going in
> Compacting large row abc/xyz:38956kjhawf (xyz bytes) incrementally
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
