[ https://issues.apache.org/jira/browse/HDDS-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855376#comment-16855376 ]
Hudson commented on HDDS-1629: ------------------------------ FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16660 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16660/]) HDDS-1629. Tar file creation can be optional for non-dist builds. (aengineer: rev e140a450465c903217c73942f1d9200ea7f27570) * (edit) hadoop-ozone/dist/pom.xml > Tar file creation can be optional for non-dist builds > ----------------------------------------------------- > > Key: HDDS-1629 > URL: https://issues.apache.org/jira/browse/HDDS-1629 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Reporter: Elek, Marton > Assignee: Elek, Marton > Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Ozone tar file creation is a very time consuming step. I propose to make it > optional and create the tar file only if the dist profile is enabled (-Pdist) > The tar file is not required to test ozone as the same content is available > from hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT which is enough to run > docker-compose pseudo clusters, smoketests. > If it's required, the tar file creation can be requested by the dist profile. > > On my machine (ssd based) it can cause 5-10% time improvements as the tar > size is ~500MB and it requires a lot of IO. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org