hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-764) Run S3 smoke tests with replication STANDARD.
Date Thu, 10 Jan 2019 10:54:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-764?focusedWorklogId=183653&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-183653

ASF GitHub Bot logged work on HDDS-764:

                Author: ASF GitHub Bot
            Created on: 10/Jan/19 10:53
            Start Date: 10/Jan/19 10:53
    Worklog Time Spent: 10m 
      Work Description: elek commented on pull request #462: HDDS-764. Run S3 smoke tests
with replication STANDARD.
URL: https://github.com/apache/hadoop/pull/462
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

            Worklog Id:     (was: 183653)
            Time Spent: 10m
    Remaining Estimate: 0h

> Run S3 smoke tests with replication STANDARD.
> ---------------------------------------------
>                 Key: HDDS-764
>                 URL: https://issues.apache.org/jira/browse/HDDS-764
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Bharat Viswanadham
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: newbie, pull-request-available
>         Attachments: HDDS-764.001.patch
>          Time Spent: 10m
>  Remaining Estimate: 0h
> This Jira is created from the comment from [~elek]
> 1. I think sooner or later we need to run ozone tests with real replication. We can add
a 'scale up' to the hadoop-ozone/dist/src/main/smoketest/test.sh
> {code:java}
> docker-compose -f "$COMPOSE_FILE" down
> docker-compose -f "$COMPOSE_FILE" up -d
> docker-compose -f "$COMPOSE_FILE" scale datanode=3
> {code}
> And with this modification we don't need the '--storage-class REDUCED_REDUNDANCY'. (But
we can do it in separated jira)

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message