Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-10315

control.sh --baseline remove outputs wrong error message when trying to remove node from baseline when cluster is inactive.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • None
    • None
    • Docs Required

    Description

      1. start 2 nodes from clean lfs
      2. grep node consistent ids

      $ grep "Consistent ID" work/log/*.log
      work/log/ignite-15958745.0.log:[16:59:13,190][INFO][main][PdsFoldersResolver] Consistent ID used for local node is [7ee8018b-3f5f-4c58-b6dd-f53ed7af2679] according to persistence data storage folders
      work/log/ignite-300c7412.0.log:[16:59:15,678][INFO][main][PdsFoldersResolver] Consistent ID used for local node is [5adcf3a1-7ad9-40fa-88ac-40b488dc6b34] according to persistence data storage folders
      
      

      3. try to remove node from baseline
      expected: error message about cluster inactive state
      actual: error message about node id not found, BUG

      Caused by: java.lang.IllegalStateException: Node not found for consistent ID: 7ee8018b-3f5f-4c58-b6dd-f53ed7af2679
       at org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.remove(VisorBaselineTask.java:178)
       at org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:208)
       at org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:52)
       at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
       at org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
       at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
       at org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
       ... 19 more
      
      

      however, when trying to add node to baseline, error message is correct:

      Caused by: class org.apache.ignite.IgniteException: Changing BaselineTopology on inactive cluster is not allowed.
       at org.apache.ignite.internal.cluster.IgniteClusterImpl.validateBeforeBaselineChange(IgniteClusterImpl.java:406)
       at org.apache.ignite.internal.cluster.IgniteClusterImpl.setBaselineTopology(IgniteClusterImpl.java:356)
       at org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.set0(VisorBaselineTask.java:87)
       at org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.add(VisorBaselineTask.java:162)
       at org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:205)
       at org.apache.ignite.internal.visor.baseline.VisorBaselineTask$VisorBaselineJob.run(VisorBaselineTask.java:52)
       at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
       at org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
       at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
       at org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
       at org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
       at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
       at org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1123)
       at org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1407)
       at org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:660)
       at org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:532)
       ... 13 more
      
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              voropava Pavel Voronkin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: