cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-14151) [TRUNK] TestRepair.test_dead_sync_initiator failed due to ERROR in logs "SSTableTidier ran with no existing data file for an sstable that was not new"
Date Wed, 17 Jan 2018 14:47:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Eriksson updated CASSANDRA-14151:
----------------------------------------
    Fix Version/s: 4.x
                   3.11.x
           Status: Patch Available  (was: Open)

It is probably OK to drop the log level to WARN

Patch also prints more information to be able to debug this in the future

https://github.com/krummas/cassandra/commits/marcuse/14151
https://circleci.com/gh/krummas/cassandra/212

> [TRUNK] TestRepair.test_dead_sync_initiator failed due to ERROR in logs "SSTableTidier
ran with no existing data file for an sstable that was not new"
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14151
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14151
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Michael Kjellman
>            Assignee: Marcus Eriksson
>            Priority: Major
>             Fix For: 3.11.x, 4.x
>
>         Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, node2_debug.log,
node2_gc.log, node3.log, node3_debug.log, node3_gc.log, stdout-novnodes.txt
>
>
> TestRepair.test_dead_sync_initiator failed due to finding the following unexpected error
in the node's logs:
> {code}
> ERROR [NonPeriodicTasks:1] 2018-01-06 03:38:50,229 LogTransaction.java:347 - SSTableTidier
ran with no existing data file for an sstable that was not new
> {code}
> If this is "okay/expected" behavior we should change the log level to something different
(which will fix the test) or if it's an actual bug use this JIRA to fix it. I've attached
all of the logs from all 3 instances from the dtest run that hit this failure.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message