[
https://issues.apache.org/jira/browse/CASSANDRA-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380063#comment-14380063
]
Philip Thompson commented on CASSANDRA-9032:
--------------------------------------------
Okay. I agree that the proposed solution is better than disabling the tests.
> Reduce logging level for MigrationTask abort due to down node from ERROR to
> INFO
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-9032
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9032
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Tyler Hobbs
> Assignee: Tyler Hobbs
> Priority: Minor
> Fix For: 2.1.4, 2.0.14
>
> Attachments: 9032.txt
>
>
> A lot of the dtests are failing during Jenkins runs due to the following
> error message in the logs:
> {noformat}
> "ERROR [MigrationStage:1] 2015-03-24 20:02:03,464 MigrationTask.java:62 -
> Can't send migration request: node /127.0.0.3 is down.\n"]
> {noformat}
> This log message happens when a schema pull is scheduled, but the target
> endpoint is down when the scheduled task actually runs. The failing dtests
> generally stop a node as part of the test, which results in this.
> I believe the log message should be moved from ERROR to INFO (or perhaps even
> DEBUG). This isn't an unexpected type of problem (nodes go down all the
> time), and it's not actionable by the user. This would also have the nice
> side effect of fixing the dtests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
