neils-dev opened a new pull request, #3295:
URL: https://github.com/apache/ozone/pull/3295

   ## What changes were proposed in this pull request?
   
   Merge of master into feature branch to sync the feature branch to the 
current master.  Resolved conflicts affecting feature versioning HDDS-6393 
PR#3211 & HDDS-6391 PR#3155, propagating s3 exception stack trace HDDS-6257 
PR#3066 and performFailover PR#3160.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-6571
   
   ## How was this patch tested?
   Manually testing s3 gateway grpc feature servicing s3 requests with failover 
in HA configuration.
   
   Using ozone-ha cluster, 
   Add the following configuration key settings to the docker-compose.yaml : 
   om container - `OZONE-SITE.XML_ozone.om.s3.gprc.server_enabled: "true"`
   & s3g container - `OZONE-SITE.XML_ozone.om.transport.class: 
"org.apache.hadoop.ozone.om.protocolPB.GrpcOmTransportFactory"`
    
   `hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/ozone-ha$ ./test.sh`
   and,
   `hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/ozone-ha$ 
docker-compose up -d --scale datanode=3`
   `hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/ozone-ha$ aws s3api 
--endpoint http://localhost:9878 create-bucket --bucket bucket1`
   
   _**disable om leader node**_
   `hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/ozone-ha$ 
docker-compose stop om1 <leader>`
   `hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/compose/ozone-ha$ aws s3api 
--endpoint http://localhost:9878 create-bucket --bucket bucket2`
   _**will pass after failover to new leader om.**_
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to