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

can see exception info when I try to run rebalance by REST API

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.13.0
    • Component/s: management, rest (admin)
    • Labels:
      None

      Description

      as a user, when I try to run rebalance by [POST] "http://127.0.0.1:7070/management/v1/operations/rebalances"
      , sometimes can get the following response:

      {
          "statusCode": "ACCEPTED",
          "statusMessage": "Operation started.  Use the URI to check its status.",
          "links": {
              "self": "http://127.0.0.1:7070/management/v1/operations/rebalances/7c39a7f0-6b7e-4177-9269-bfa7ce42808d",
              "list": "http://127.0.0.1:7070/management/v1/operations/rebalances"
          },
          "operationStart": "2020-02-27T22:48:49.716Z",
          "operationEnd": "2020-02-27T22:48:49.729Z",
          "operationId": "7c39a7f0-6b7e-4177-9269-bfa7ce42808d",
          "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
                  }
              ]
          }
      }
      

      if a post request of a-sync operation , as rebalance , is posted, the user wants to see whether it is accepted or not. When the user want to know detail info, he just needs to run
      [GET] http://127.0.0.1:7070/management/experimental/operations/rebalances/[operationID] to get more information.

      expected result: just show accepted or not, without throwable info

        Attachments

          Activity

            People

            • Assignee:
              dschneider Darrel Schneider
              Reporter:
              gyan Gang Yan

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

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

                  Issue deployment