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

Control utility doesn't print results to stdout.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 2.10
    • 2.10
    • control.sh
    • None
    • Docs Required, Release Notes Required

    Description

      After merging IGNITE-13262 control.sh doesn't work properly either in dev mode, or in release mode. Specifically, no output printed in stdout.

      For example, incorrect output for control.sh -baseline set after commit is:

      Control utility [ver. 2.10.0-SNAPSHOT#20200803-sha1:DEV], 
      2020 Copyright(C) Apache Software Foundation, 
      User: ducker, 
      Time: 2020-08-03T14:24:33.193, 
      Command [BASELINE] started, 
        Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes, 
        --------------------------------------------------------------------------------
      

      Correct output for control.sh -baseline set before commit is:

      Control utility [ver. 2.8.1#20200521-sha1:86422096], 
      2020 Copyright(C) Apache Software Foundation, 
      User: ducker, 
      Time: 2020-08-03T14:23:55.793, 
      Command [BASELINE] started, 
       Arguments: --host ducker04 --baseline set ducker02,ducker03,ducker04 --yes, 
       --------------------------------------------------------------------------------, 
       Cluster state: active, 
       Current topology version: 3, 
       Baseline auto adjustment disabled: softTimeout=300000
         Current topology version: 3 (Coordinator: ConsistentId=ducker02, Order=1)
          Baseline nodes: 
             ConsistentId=ducker02, State=ONLINE, Order=1, 
             ConsistentId=ducker03, State=ONLINE, Order=2, 
             ConsistentId=ducker04, State=ONLINE, Order=3, 
      --------------------------------------------------------------------------------, 
            Number of baseline nodes: 3,  
            Other nodes not found., 
            Command [BASELINE] finished with code: 0, 
            Control utility has completed execution at: 2020-08-03T14:23:57.351, 
            Execution time: 1558 ms
      

      However, command seems to execute and baseline actually changes.

      Attachments

        Issue Links

          Activity

            People

              kuaw26 Alexey Kuznetsov
              ivandasch Ivan Daschinsky
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: