Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-2823 SCM HA Support
  3. HDDS-4860

Reopen replication/wait.robot added by HDDS-4834

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.0
    • Component/s: None
    • Labels:
      None

      Description

      For now upon HDDS-2823, the containerID is generated from UnqiueId,

      private ContainerInfo allocateContainer(final Pipeline pipeline,
                                              final String owner)
          throws IOException {
        // TODO: Replace this with Distributed unique id generator.
        final long uniqueId = UniqueId.next();
        Preconditions.checkState(uniqueId > 0,
            "Cannot allocate container, negative container id" +
                " generated. %s.", uniqueId);
        final ContainerID containerID = ContainerID.valueOf(uniqueId);
      

      But in master, the first created container always has the ID #1.

      After the distributed sequence id is implemented, the container ID will also start from #1 in HDDS-2823.

       

      trace for the security docker test:

      the container ID is 105784943294873600

      [hadoop@9 ~/glengeng/hadoop-ozone/hadoop-ozone/dist/target/ozone-1.1.0-SNAPSHOT/compose/ozonesecure]$ docker-compose exec scm sh
      sh-4.2$ bin/ozone admin container list
      {
        "state" : "OPEN",
        "replicationFactor" : "THREE",
        "replicationType" : "RATIS",
        "usedBytes" : 1280671,
        "numberOfKeys" : 126,
        "lastUsed" : "2021-02-24T07:03:55.832Z",
        "stateEnterTime" : "2021-02-24T07:02:15.726Z",
        "owner" : "om1",
        "containerID" : 105784943294873600,
        "deleteTransactionId" : 0,
        "sequenceId" : 508,
        "open" : true
      }
      

      the test is expecting container #1 to be replicated.

      ozonesecure_om_1 is up-to-date
      ozonesecure_recon_1 is up-to-date
      ozonesecure_kdc_1 is up-to-date
      Stopping and removing ozonesecure_datanode_3 ... 
      Stopping and removing ozonesecure_datanode_3 ... done
      Starting ozonesecure_datanode_1              ... done
      Starting ozonesecure_datanode_2              ... done
      ==============================================================================
      Wait :: Wait for replication to succeed                                       
      ==============================================================================
      Wait Until Container Replicated                                       ID #1
      ID #1
      ID #1
      ID #1
      ID #1
      ID #1
      ID #1
      | FAIL |
      Test timeout 5 minutes exceeded.
      ------------------------------------------------------------------------------
      Wait :: Wait for replication to succeed                               | FAIL |
      1 critical test, 0 passed, 1 failed
      1 test total, 0 passed, 1 failed
      ==============================================================================
      Output:  /tmp/smoketest/ozonesecure/result/robot-ozonesecure-ozonesecure-wait-scm.xml
      

       

        Attachments

          Activity

            People

            • Assignee:
              glengeng Glen Geng
              Reporter:
              glengeng Glen Geng
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: