[ 
https://issues.apache.org/jira/browse/CASSANDRA-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380058#comment-14380058
 ] 

Tyler Hobbs commented on CASSANDRA-9032:
----------------------------------------

I would guess that the difference is due to how quickly the tests are running.  
This particular task is scheduled with a 60s delay, so if the trunk tests are, 
for example, taking longer to stop nodes, that might explain why we're seeing 
it there.

If there _is_ a problem with schema migrations (or something else that might 
cause this), then hopefully tests that are more specific to that will catch it. 
 Right now it's too hard to tell where we actually have problems on trunk due 
to unrelated failures like this, so the alternative is basically disabling 
those tests for now.

> 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)

Reply via email to