Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-7826

met error when run rebalance by REST API on running 2 locators of 1 vm

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.13.0
    • management, rest (admin)
    • None

    Description

      the reproduced steps:
      1. gfsh start locator --port=0 --http-service-port=8081 --name=loc1
      2. gfsh start locator --port=0 --name=loc2
      3. gfsh start server --server-port=0 --name=s1
      4. gfsh create region --name=/regionTest --type=PARTITION
      5. java code to put 10 million data to regionTest
      6. gfsh start server --server-port=0 --name=s2
      7.run rebalance by [post] " http://127.0.0.1:7070/management/v1/operations/rebalances"
      8. run [GET]"http://127.0.0.1:8081/management/v1/operations/rebalances"
      9. met the following error

      {
          "statusCode": "ERROR",
          "links": {
              "self": "http://127.0.0.1:7070/management/v1/operations/rebalances/3bb2f394-3d21-4076-8c24-3cf3ce7bbbea",
              "list": "http://127.0.0.1:7070/management/v1/operations/rebalances"
          },
          "operationStart": "2020-02-26T22:06:44.601Z",
          "operationEnd": "2020-02-26T22:06:44.603Z",
          "operationId": "3bb2f394-3d21-4076-8c24-3cf3ce7bbbea",
          "operation": {
              "simulate": false
          },
          "throwable": {
              "stackTrace": [
                  {
                      "methodName": "getMemberRegionList",
                      "fileName": "RebalanceOperationPerformer.java",
                      "lineNumber": 208,
                      "className": "org.apache.geode.management.internal.operation.RebalanceOperationPerformer",
                      "nativeMethod": false
                  },
                  {
                      "methodName": "executeRebalanceOnDS",
                      "fileName": "RebalanceOperationPerformer.java",
                      "lineNumber": 326,
                      "className": "org.apache.geode.management.internal.operation.RebalanceOperationPerformer",
                      "nativeMethod": false
                  },
                  {
                      "methodName": "perform",
                      "fileName": "RebalanceOperationPerformer.java",
                      "lineNumber": 91,
                      "className": "org.apache.geode.management.internal.operation.RebalanceOperationPerformer",
                      "nativeMethod": false
                  },
                  {
                      "methodName": "lambda$submit$0",
                      "fileName": "OperationManager.java",
                      "lineNumber": 67,
                      "className": "org.apache.geode.management.internal.operation.OperationManager",
                      "nativeMethod": false
                  },
                  {
                      "methodName": "run",
                      "fileName": "CompletableFuture.java",
                      "lineNumber": 1590,
                      "className": "java.util.concurrent.CompletableFuture$AsyncSupply",
                      "nativeMethod": false
                  },
                  {
                      "methodName": "run",
                      "fileName": "Thread.java",
                      "lineNumber": 748,
                      "className": "java.lang.Thread",
                      "nativeMethod": false
                  }
              ]
          }
      }
      

      expected things, 1 of the followings:
      1. stop or forbid users to run rebalance on the non-jmxManager locator
      2. return instructive info to let users find proper way to run rebalance
      3. stop or forbid a REST API for Management to run , when there is no jmx-manager on the locator.

      Attachments

        Issue Links

          Activity

            People

              dschneider Darrel Schneider
              gyan Gang Yan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1.5h
                  1.5h