Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-9032

Reduce logging level for MigrationTask abort due to down node from ERROR to INFO

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Low
    • Resolution: Fixed
    • Fix Version/s: 2.0.15, 2.1.5
    • Component/s: None
    • Labels:
      None

      Description

      A lot of the dtests are failing during Jenkins runs due to the following error message in the logs:

      "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"]
      

      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.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              thobbs Tom Hobbs Assign to me
              Reporter:
              thobbs Tom Hobbs
              Authors:
              Tom Hobbs
              Reviewers:
              Aleksey Yeschenko

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment