[jira] [Commented] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17020054#comment-17020054 ] Zhankun Tang commented on HADOOP-16670: --- [~aajisaka], thanks a lot! [~weichiu], could you please help to review and merge it? > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch, > HADOOP-16670-trunk.008.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17020045#comment-17020045 ] Zhankun Tang commented on HADOOP-16670: --- [~aajisaka], could you please help to review? Thanks! > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch, > HADOOP-16670-trunk.008.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019357#comment-17019357 ] Zhankun Tang commented on HADOOP-16670: --- [~aajisaka], sorry for the late reply. I updated the patch based on Wanqiang's comment. Not sure why the Jenkins result hasn't appeared. > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch, > HADOOP-16670-trunk.008.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.008.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch, > HADOOP-16670-trunk.008.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Patch Available (was: Open) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch, > HADOOP-16670-trunk.008.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Open (was: Patch Available) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Patch Available (was: Open) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Open (was: Patch Available) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.007.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Blocker > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch, HADOOP-16670-trunk.007.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1634#comment-1634 ] Zhankun Tang commented on HADOOP-16670: --- [~weichiu]. [~jiwq] , Thanks for the review. Fixed the remaining issue in the latest patch. I checked the findbug, unit test and ASF license failure. It seems unrelated. Could you please help to review it again? Thanks a lot! > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Patch Available (was: Open) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Open (was: Patch Available) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.006.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch, > HADOOP-16670-trunk.006.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Patch Available (was: Open) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Open (was: Patch Available) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.005.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch, HADOOP-16670-trunk.005.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962057#comment-16962057 ] Zhankun Tang commented on HADOOP-16670: --- [~weichiu], could you please help to review? The Jenkins result for hadoop without submarine doesn't make sense to me. > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Open (was: Patch Available) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.004.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Patch Available (was: Open) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch, > HADOOP-16670-trunk.004.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Patch Available (was: Open) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.003.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Open (was: Patch Available) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch, HADOOP-16670-trunk.003.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.002.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch, > HADOOP-16670-trunk.002.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Attachment: HADOOP-16670-trunk.001.patch > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16670) Stripping Submarine code from Hadoop codebase.
[ https://issues.apache.org/jira/browse/HADOOP-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16670: -- Status: Patch Available (was: Open) > Stripping Submarine code from Hadoop codebase. > -- > > Key: HADOOP-16670 > URL: https://issues.apache.org/jira/browse/HADOOP-16670 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Zhankun Tang >Priority: Major > Attachments: HADOOP-16670-trunk.001.patch > > > Now that Submarine is getting out of Hadoop and has its own repo, it's time > to stripe the Submarine code from Hadoop codebase in Hadoop 3.3.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15226) Über-JIRA: S3Guard Phase III: Hadoop 3.2 features
[ https://issues.apache.org/jira/browse/HADOOP-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932977#comment-16932977 ] Zhankun Tang commented on HADOOP-15226: --- Thanks for this valuable information. No. I don't think we need to pull it back. Thanks! [~steve_l] > Über-JIRA: S3Guard Phase III: Hadoop 3.2 features > - > > Key: HADOOP-15226 > URL: https://issues.apache.org/jira/browse/HADOOP-15226 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Affects Versions: 3.0.0, 3.1.0 >Reporter: Steve Loughran >Priority: Major > Fix For: 3.2.0 > > > S3Guard features/improvements/fixes for Hadoop 3.2 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15226) Über-JIRA: S3Guard Phase III: Hadoop 3.2 features
[ https://issues.apache.org/jira/browse/HADOOP-15226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932116#comment-16932116 ] Zhankun Tang commented on HADOOP-15226: --- [~ste...@apache.org], any plan to backport this to branch 3.1? > Über-JIRA: S3Guard Phase III: Hadoop 3.2 features > - > > Key: HADOOP-15226 > URL: https://issues.apache.org/jira/browse/HADOOP-15226 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/s3 >Affects Versions: 3.0.0, 3.1.0 >Reporter: Steve Loughran >Priority: Major > Fix For: 3.2.0 > > > S3Guard features/improvements/fixes for Hadoop 3.2 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-14671) Upgrade to Apache Yetus 0.8.0
[ https://issues.apache.org/jira/browse/HADOOP-14671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927469#comment-16927469 ] Zhankun Tang commented on HADOOP-14671: --- [~aajisaka], got it. Thanks! > Upgrade to Apache Yetus 0.8.0 > - > > Key: HADOOP-14671 > URL: https://issues.apache.org/jira/browse/HADOOP-14671 > Project: Hadoop Common > Issue Type: Improvement > Components: build, documentation, test >Affects Versions: 3.0.0-beta1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 3.2.0 > > Attachments: HADOOP-14671.001.patch, HADOOP-14671.02.patch > > > Apache Yetus 0.7.0 was released. Let's upgrade the bundled reference to the > new version. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-14671) Upgrade to Apache Yetus 0.8.0
[ https://issues.apache.org/jira/browse/HADOOP-14671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927291#comment-16927291 ] Zhankun Tang commented on HADOOP-14671: --- [~aw], [~aajisaka], one question on this. I saw this commits generated the missing release note and changelog file for some releases. But there're releases like 2.8.0, 3.1.3, 3.2.0 commit these files manually. Which way is preferred? These things are not mentioned in the howToRelease guide. > Upgrade to Apache Yetus 0.8.0 > - > > Key: HADOOP-14671 > URL: https://issues.apache.org/jira/browse/HADOOP-14671 > Project: Hadoop Common > Issue Type: Improvement > Components: build, documentation, test >Affects Versions: 3.0.0-beta1 >Reporter: Allen Wittenauer >Assignee: Allen Wittenauer >Priority: Major > Fix For: 3.2.0 > > Attachments: HADOOP-14671.001.patch, HADOOP-14671.02.patch > > > Apache Yetus 0.7.0 was released. Let's upgrade the bundled reference to the > new version. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang updated HADOOP-16551:
--
Fix Version/s: 3.1.4
3.1.3
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
> Fix For: 3.1.3, 3.1.4
>
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is missing.
> *Update:*
> Found that the CHANGELOG.md and RELEASENOTES.md are generated but not in
> directory "3.1.3"
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/
> 0.1.0 0.15.2 0.19.2 0.23.2 0.7.2 2.0.1-alpha 2.6.3 3.0.0-alpha3
> 0.10.0 0.15.3 0.2.0 0.23.3 0.8.0 2.0.2-alpha 2.6.4 3.0.0-alpha4
> 0.10.1 0.15.4 0.20.0 0.23.4 0.9.0 2.0.3-alpha 2.6.5 3.0.0-beta1
> 0.1.1 0.16.0 0.20.1 0.23.5 0.9.1 2.0.4-alpha 2.6.6 3.0.1
> 0.11.0 0.16.1 0.20.2 0.23.6 0.9.2 2.0.5-alpha 2.7.0 3.0.3
> 0.11.1 0.16.2 0.20.203.0 0.23.7 1.0.0 2.0.6-alpha 2.7.1 3.1.0
> 0.11.2 0.16.3 0.20.203.1 0.23.8 1.0.1 2.1.0-beta 2.7.2 3.1.1
> 0.12.0 0.16.4 0.20.204.0 0.23.9 1.0.2 2.1.1-beta 2.7.3 3.1.2
> 0.12.1 0.17.0 0.20.205.0 0.24.0 1.0.3 2.2.0 2.7.4 CHANGELOG.md
> 0.12.2 0.17.1 0.20.3 0.3.0 1.0.4 2.2.1 2.7.5 index.md
> 0.12.3 0.17.2 0.2.1 0.3.1 1.1.0 2.3.0 2.8.0 README.md
> 0.13.0 0.17.3 0.21.0 0.3.2 1.1.1 2.4.0 2.8.1 RELEASENOTES.md
> 0.14.0 0.18.0 0.21.1 0.4.0 1.1.2 2.4.1 2.8.2
> 0.14.1 0.18.1 0.22.0 0.5.0 1.1.3 2.5.0 2.8.3
> 0.14.2 0.18.2 0.22.1 0.6.0 1.2.0 2.5.1 2.9.0
> 0.14.3 0.18.3 0.23.0 0.6.1 1.2.1 2.5.2 2.9.1
> 0.14.4 0.18.4 0.23.1 0.6.2 1.2.2 2.6.0 3.0.0
> 0.15.0 0.19.0 0.23.10 0.7.0 1.3.0 2.6.1 3.0.0-alpha1
> 0.15.1 0.19.1 0.23.11 0.7.1 2.0.0-alpha 2.6.2 3.0.0-alpha2{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang resolved HADOOP-16551.
---
Resolution: Fixed
Close this since revert HADOOP-16061 has fixed it.
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is missing.
> *Update:*
> Found that the CHANGELOG.md and RELEASENOTES.md are generated but not in
> directory "3.1.3"
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/
> 0.1.0 0.15.2 0.19.2 0.23.2 0.7.2 2.0.1-alpha 2.6.3 3.0.0-alpha3
> 0.10.0 0.15.3 0.2.0 0.23.3 0.8.0 2.0.2-alpha 2.6.4 3.0.0-alpha4
> 0.10.1 0.15.4 0.20.0 0.23.4 0.9.0 2.0.3-alpha 2.6.5 3.0.0-beta1
> 0.1.1 0.16.0 0.20.1 0.23.5 0.9.1 2.0.4-alpha 2.6.6 3.0.1
> 0.11.0 0.16.1 0.20.2 0.23.6 0.9.2 2.0.5-alpha 2.7.0 3.0.3
> 0.11.1 0.16.2 0.20.203.0 0.23.7 1.0.0 2.0.6-alpha 2.7.1 3.1.0
> 0.11.2 0.16.3 0.20.203.1 0.23.8 1.0.1 2.1.0-beta 2.7.2 3.1.1
> 0.12.0 0.16.4 0.20.204.0 0.23.9 1.0.2 2.1.1-beta 2.7.3 3.1.2
> 0.12.1 0.17.0 0.20.205.0 0.24.0 1.0.3 2.2.0 2.7.4 CHANGELOG.md
> 0.12.2 0.17.1 0.20.3 0.3.0 1.0.4 2.2.1 2.7.5 index.md
> 0.12.3 0.17.2 0.2.1 0.3.1 1.1.0 2.3.0 2.8.0 README.md
> 0.13.0 0.17.3 0.21.0 0.3.2 1.1.1 2.4.0 2.8.1 RELEASENOTES.md
> 0.14.0 0.18.0 0.21.1 0.4.0 1.1.2 2.4.1 2.8.2
> 0.14.1 0.18.1 0.22.0 0.5.0 1.1.3 2.5.0 2.8.3
> 0.14.2 0.18.2 0.22.1 0.6.0 1.2.0 2.5.1 2.9.0
> 0.14.3 0.18.3 0.23.0 0.6.1 1.2.1 2.5.2 2.9.1
> 0.14.4 0.18.4 0.23.1 0.6.2 1.2.2 2.6.0 3.0.0
> 0.15.0 0.19.0 0.23.10 0.7.0 1.3.0 2.6.1 3.0.0-alpha1
> 0.15.1 0.19.1 0.23.11 0.7.1 2.0.0-alpha 2.6.2 3.0.0-alpha2{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927211#comment-16927211
]
Zhankun Tang commented on HADOOP-16551:
---
[~aajisaka], it works well. Thanks!
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is missing.
> *Update:*
> Found that the CHANGELOG.md and RELEASENOTES.md are generated but not in
> directory "3.1.3"
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/
> 0.1.0 0.15.2 0.19.2 0.23.2 0.7.2 2.0.1-alpha 2.6.3 3.0.0-alpha3
> 0.10.0 0.15.3 0.2.0 0.23.3 0.8.0 2.0.2-alpha 2.6.4 3.0.0-alpha4
> 0.10.1 0.15.4 0.20.0 0.23.4 0.9.0 2.0.3-alpha 2.6.5 3.0.0-beta1
> 0.1.1 0.16.0 0.20.1 0.23.5 0.9.1 2.0.4-alpha 2.6.6 3.0.1
> 0.11.0 0.16.1 0.20.2 0.23.6 0.9.2 2.0.5-alpha 2.7.0 3.0.3
> 0.11.1 0.16.2 0.20.203.0 0.23.7 1.0.0 2.0.6-alpha 2.7.1 3.1.0
> 0.11.2 0.16.3 0.20.203.1 0.23.8 1.0.1 2.1.0-beta 2.7.2 3.1.1
> 0.12.0 0.16.4 0.20.204.0 0.23.9 1.0.2 2.1.1-beta 2.7.3 3.1.2
> 0.12.1 0.17.0 0.20.205.0 0.24.0 1.0.3 2.2.0 2.7.4 CHANGELOG.md
> 0.12.2 0.17.1 0.20.3 0.3.0 1.0.4 2.2.1 2.7.5 index.md
> 0.12.3 0.17.2 0.2.1 0.3.1 1.1.0 2.3.0 2.8.0 README.md
> 0.13.0 0.17.3 0.21.0 0.3.2 1.1.1 2.4.0 2.8.1 RELEASENOTES.md
> 0.14.0 0.18.0 0.21.1 0.4.0 1.1.2 2.4.1 2.8.2
> 0.14.1 0.18.1 0.22.0 0.5.0 1.1.3 2.5.0 2.8.3
> 0.14.2 0.18.2 0.22.1 0.6.0 1.2.0 2.5.1 2.9.0
> 0.14.3 0.18.3 0.23.0 0.6.1 1.2.1 2.5.2 2.9.1
> 0.14.4 0.18.4 0.23.1 0.6.2 1.2.2 2.6.0 3.0.0
> 0.15.0 0.19.0 0.23.10 0.7.0 1.3.0 2.6.1 3.0.0-alpha1
> 0.15.1 0.19.1 0.23.11 0.7.1 2.0.0-alpha 2.6.2 3.0.0-alpha2{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16925330#comment-16925330
]
Zhankun Tang commented on HADOOP-16551:
---
Could you please take a look at this? [~aajisaka]
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is missing.
> *Update:*
> Found that the CHANGELOG.md and RELEASENOTES.md are generated but not in
> directory "3.1.3"
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/
> 0.1.0 0.15.2 0.19.2 0.23.2 0.7.2 2.0.1-alpha 2.6.3 3.0.0-alpha3
> 0.10.0 0.15.3 0.2.0 0.23.3 0.8.0 2.0.2-alpha 2.6.4 3.0.0-alpha4
> 0.10.1 0.15.4 0.20.0 0.23.4 0.9.0 2.0.3-alpha 2.6.5 3.0.0-beta1
> 0.1.1 0.16.0 0.20.1 0.23.5 0.9.1 2.0.4-alpha 2.6.6 3.0.1
> 0.11.0 0.16.1 0.20.2 0.23.6 0.9.2 2.0.5-alpha 2.7.0 3.0.3
> 0.11.1 0.16.2 0.20.203.0 0.23.7 1.0.0 2.0.6-alpha 2.7.1 3.1.0
> 0.11.2 0.16.3 0.20.203.1 0.23.8 1.0.1 2.1.0-beta 2.7.2 3.1.1
> 0.12.0 0.16.4 0.20.204.0 0.23.9 1.0.2 2.1.1-beta 2.7.3 3.1.2
> 0.12.1 0.17.0 0.20.205.0 0.24.0 1.0.3 2.2.0 2.7.4 CHANGELOG.md
> 0.12.2 0.17.1 0.20.3 0.3.0 1.0.4 2.2.1 2.7.5 index.md
> 0.12.3 0.17.2 0.2.1 0.3.1 1.1.0 2.3.0 2.8.0 README.md
> 0.13.0 0.17.3 0.21.0 0.3.2 1.1.1 2.4.0 2.8.1 RELEASENOTES.md
> 0.14.0 0.18.0 0.21.1 0.4.0 1.1.2 2.4.1 2.8.2
> 0.14.1 0.18.1 0.22.0 0.5.0 1.1.3 2.5.0 2.8.3
> 0.14.2 0.18.2 0.22.1 0.6.0 1.2.0 2.5.1 2.9.0
> 0.14.3 0.18.3 0.23.0 0.6.1 1.2.1 2.5.2 2.9.1
> 0.14.4 0.18.4 0.23.1 0.6.2 1.2.2 2.6.0 3.0.0
> 0.15.0 0.19.0 0.23.10 0.7.0 1.3.0 2.6.1 3.0.0-alpha1
> 0.15.1 0.19.1 0.23.11 0.7.1 2.0.0-alpha 2.6.2 3.0.0-alpha2{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang updated HADOOP-16551:
--
Description:
Hi,
When creating Hadoop 3.1.3 release with "create-release" script, after the mvn
site succeeded. But it complains about this and failed:
{code:java}
dev-support/bin/create-release --asfrelease --docker --dockercache{code}
{code:java}
$ cd /build/source
$ mv /build/source/target/hadoop-site-3.1.3.tar.gz
/build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
$ cp -p
/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
/build/source/target/artifacts/CHANGES.md
cp: cannot stat
'/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
No such file or directory
{code}
And there's no 3.1.3 release site markdown folder.
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
ls: cannot access
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
file or directory
{code}
I've checked the HADOOP-14671 but have no idea why this changelog is missing.
*Update:*
Found that the CHANGELOG.md and RELEASENOTES.md are generated but not in
directory "3.1.3"
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/
0.1.0 0.15.2 0.19.2 0.23.2 0.7.2 2.0.1-alpha 2.6.3 3.0.0-alpha3
0.10.0 0.15.3 0.2.0 0.23.3 0.8.0 2.0.2-alpha 2.6.4 3.0.0-alpha4
0.10.1 0.15.4 0.20.0 0.23.4 0.9.0 2.0.3-alpha 2.6.5 3.0.0-beta1
0.1.1 0.16.0 0.20.1 0.23.5 0.9.1 2.0.4-alpha 2.6.6 3.0.1
0.11.0 0.16.1 0.20.2 0.23.6 0.9.2 2.0.5-alpha 2.7.0 3.0.3
0.11.1 0.16.2 0.20.203.0 0.23.7 1.0.0 2.0.6-alpha 2.7.1 3.1.0
0.11.2 0.16.3 0.20.203.1 0.23.8 1.0.1 2.1.0-beta 2.7.2 3.1.1
0.12.0 0.16.4 0.20.204.0 0.23.9 1.0.2 2.1.1-beta 2.7.3 3.1.2
0.12.1 0.17.0 0.20.205.0 0.24.0 1.0.3 2.2.0 2.7.4 CHANGELOG.md
0.12.2 0.17.1 0.20.3 0.3.0 1.0.4 2.2.1 2.7.5 index.md
0.12.3 0.17.2 0.2.1 0.3.1 1.1.0 2.3.0 2.8.0 README.md
0.13.0 0.17.3 0.21.0 0.3.2 1.1.1 2.4.0 2.8.1 RELEASENOTES.md
0.14.0 0.18.0 0.21.1 0.4.0 1.1.2 2.4.1 2.8.2
0.14.1 0.18.1 0.22.0 0.5.0 1.1.3 2.5.0 2.8.3
0.14.2 0.18.2 0.22.1 0.6.0 1.2.0 2.5.1 2.9.0
0.14.3 0.18.3 0.23.0 0.6.1 1.2.1 2.5.2 2.9.1
0.14.4 0.18.4 0.23.1 0.6.2 1.2.2 2.6.0 3.0.0
0.15.0 0.19.0 0.23.10 0.7.0 1.3.0 2.6.1 3.0.0-alpha1
0.15.1 0.19.1 0.23.11 0.7.1 2.0.0-alpha 2.6.2 3.0.0-alpha2{code}
was:
Hi,
When creating Hadoop 3.1.3 release with "create-release" script, after the mvn
site succeeded. But it complains about this and failed:
{code:java}
dev-support/bin/create-release --asfrelease --docker --dockercache{code}
{code:java}
$ cd /build/source
$ mv /build/source/target/hadoop-site-3.1.3.tar.gz
/build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
$ cp -p
/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
/build/source/target/artifacts/CHANGES.md
cp: cannot stat
'/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
No such file or directory
{code}
And there's no 3.1.3 release site markdown folder.
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
ls: cannot access
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
file or directory
{code}
I've checked the HADOOP-14671 but have no idea why this changelog is missing.
Update:
Found that the CHANGELOG.md and RELEASENOTES.md are generated but not in
directory "3.1.3"
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/
0.1.0 0.15.2 0.19.2 0.23.2 0.7.2 2.0.1-alpha 2.6.3 3.0.0-alpha3
0.10.0 0.15.3 0.2.0 0.23.3 0.8.0 2.0.2-alpha 2.6.4 3.0.0-alpha4
0.10.1 0.15.4 0.20.0 0.23.4 0.9.0 2.0.3-alpha 2.6.5 3.0.0-beta1
0.1.1 0.16.0 0.20.1 0.23.5 0.9.1 2.0.4-alpha 2.6.6 3.0.1
0.11.0 0.16.1 0.20.2 0.23.6 0.9.2 2.0.5-alpha 2.7.0 3.0.3
0.11.1 0.16.2 0.20.203.0 0.23.7 1.0.0 2.0.6-alpha 2.7.1 3.1.0
0.11.2 0.16.3 0.20.203.1 0.23.8 1.0.1 2.1.0-beta 2.7.2 3.1.1
0.12.0 0.16.4 0.20.204.0 0.23.9 1.0.2 2.1.1-beta 2.7.3 3.1.2
0.12.1 0.17.0 0.20.205.0 0.24.0 1.0.3 2.2.0 2.7.4 CHANGELOG.md
0.12.2 0.17.1 0.20.3 0.3.0 1.0.4 2.2.1 2.7.5 index.md
0.12.3 0.17.2 0.2.1 0.3.1 1.1.0 2.3.0 2.8.0 README.md
0.13.0 0.17.3 0.21.0 0.3.2 1.1.1 2.4.0 2.8.1 RELEASENOTES.md
0.14.0 0.18.0 0.21.1 0.4.0 1.1.2 2.4.1 2.8.2
0.14.1 0.18.1 0.22.0 0.5.0 1.1.3 2.5.0 2.8.3
0.14.2 0.18.2 0.22.1 0.6.0 1.2.0 2.5.1 2.9.0
0.14.3 0.18.3 0.23.0 0.6.1 1.2.1 2.5.2 2.9.1
0.14.4 0.18.4 0.23.1 0.6.2 1.2.2 2.6.0 3.0.0
0.15.0 0.19.0 0.23.10 0.7.0 1.3.0 2.6.1 3.0.0-alpha1
0.15.1 0.19.1 0.23.11 0.7.1 2.0.0-alpha 2.6.2 3.0.0-alpha2{code}
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
>
[jira] [Updated] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang updated HADOOP-16551:
--
Description:
Hi,
When creating Hadoop 3.1.3 release with "create-release" script, after the mvn
site succeeded. But it complains about this and failed:
{code:java}
dev-support/bin/create-release --asfrelease --docker --dockercache{code}
{code:java}
$ cd /build/source
$ mv /build/source/target/hadoop-site-3.1.3.tar.gz
/build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
$ cp -p
/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
/build/source/target/artifacts/CHANGES.md
cp: cannot stat
'/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
No such file or directory
{code}
And there's no 3.1.3 release site markdown folder.
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
ls: cannot access
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
file or directory
{code}
I've checked the HADOOP-14671 but have no idea why this changelog is missing.
Update:
Found that the CHANGELOG.md and RELEASENOTES.md are generated but not in
directory "3.1.3"
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/
0.1.0 0.15.2 0.19.2 0.23.2 0.7.2 2.0.1-alpha 2.6.3 3.0.0-alpha3
0.10.0 0.15.3 0.2.0 0.23.3 0.8.0 2.0.2-alpha 2.6.4 3.0.0-alpha4
0.10.1 0.15.4 0.20.0 0.23.4 0.9.0 2.0.3-alpha 2.6.5 3.0.0-beta1
0.1.1 0.16.0 0.20.1 0.23.5 0.9.1 2.0.4-alpha 2.6.6 3.0.1
0.11.0 0.16.1 0.20.2 0.23.6 0.9.2 2.0.5-alpha 2.7.0 3.0.3
0.11.1 0.16.2 0.20.203.0 0.23.7 1.0.0 2.0.6-alpha 2.7.1 3.1.0
0.11.2 0.16.3 0.20.203.1 0.23.8 1.0.1 2.1.0-beta 2.7.2 3.1.1
0.12.0 0.16.4 0.20.204.0 0.23.9 1.0.2 2.1.1-beta 2.7.3 3.1.2
0.12.1 0.17.0 0.20.205.0 0.24.0 1.0.3 2.2.0 2.7.4 CHANGELOG.md
0.12.2 0.17.1 0.20.3 0.3.0 1.0.4 2.2.1 2.7.5 index.md
0.12.3 0.17.2 0.2.1 0.3.1 1.1.0 2.3.0 2.8.0 README.md
0.13.0 0.17.3 0.21.0 0.3.2 1.1.1 2.4.0 2.8.1 RELEASENOTES.md
0.14.0 0.18.0 0.21.1 0.4.0 1.1.2 2.4.1 2.8.2
0.14.1 0.18.1 0.22.0 0.5.0 1.1.3 2.5.0 2.8.3
0.14.2 0.18.2 0.22.1 0.6.0 1.2.0 2.5.1 2.9.0
0.14.3 0.18.3 0.23.0 0.6.1 1.2.1 2.5.2 2.9.1
0.14.4 0.18.4 0.23.1 0.6.2 1.2.2 2.6.0 3.0.0
0.15.0 0.19.0 0.23.10 0.7.0 1.3.0 2.6.1 3.0.0-alpha1
0.15.1 0.19.1 0.23.11 0.7.1 2.0.0-alpha 2.6.2 3.0.0-alpha2{code}
was:
Hi,
When creating Hadoop 3.1.3 release with "create-release" script, after the mvn
site succeeded. But it complains about this and failed:
{code:java}
dev-support/bin/create-release --asfrelease --docker --dockercache{code}
{code:java}
$ cd /build/source
$ mv /build/source/target/hadoop-site-3.1.3.tar.gz
/build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
$ cp -p
/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
/build/source/target/artifacts/CHANGES.md
cp: cannot stat
'/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
No such file or directory
{code}
And there's no 3.1.3 release site markdown folder.
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
ls: cannot access
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
file or directory
{code}
I've checked the HADOOP-14671 but have no idea why this changelog is not
generated.
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is missing.
>
[jira] [Commented] (HADOOP-15958) Revisiting LICENSE and NOTICE files
[
https://issues.apache.org/jira/browse/HADOOP-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924119#comment-16924119
]
Zhankun Tang commented on HADOOP-15958:
---
[~aajisaka], Thanks for the great work!
One question is that how can we know in the file level, which source code uses
which license? Like below snippet:
{code:java}
BSD 3-Clause
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/bloom/*
hadoop-common-project/hadoop-common/src/main/native/gtest/gtest-all.cc
hadoop-common-project/hadoop-common/src/main/native/gtest/include/gtest/gtest.h
hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/util/bulk_crc32_x86.c
hadoop-tools/hadoop-sls/src/main/html/js/thirdparty/d3.v3.js
hadoop-hdfs-project/hadoop-hdfs/src/main/webapps/static/d3-3.5.17.min.js
{code}
Is there any tool that can help? I check the "mvn site" output HTML, but it
seems doesn't have this kind of info. Thanks.
> Revisiting LICENSE and NOTICE files
> ---
>
> Key: HADOOP-15958
> URL: https://issues.apache.org/jira/browse/HADOOP-15958
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Blocker
> Fix For: 3.3.0
>
> Attachments: HADOOP-15958-002.patch, HADOOP-15958-003.patch,
> HADOOP-15958-004.patch, HADOOP-15958-wip.001.patch, HADOOP-15958.005.patch,
> HADOOP-15958.006.patch, HADOOP-15958.007.patch
>
>
> Originally reported from [~jmclean]:
> * NOTICE file incorrectly lists copyrights that shouldn't be there and
> mentions licenses such as MIT, BSD, and public domain that should be
> mentioned in LICENSE only.
> * It's better to have a separate LICENSE and NOTICE for the source and binary
> releases.
> http://www.apache.org/dev/licensing-howto.html
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923901#comment-16923901
]
Zhankun Tang edited comment on HADOOP-16551 at 9/6/19 3:30 AM:
---
Am I missing something before running this script? It seems not. I'm following
[https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease]
Could you please help with this? [~aw]
was (Author: tangzhankun):
Am I missing something before running this script? It seems not. I'm following
[https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease]
Could you please help with this? @Allen Wittenauer
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is not
> generated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923901#comment-16923901
]
Zhankun Tang commented on HADOOP-16551:
---
Am I miss something before running this script? I'm following
[https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease]
Could you please help with this? @Allen Wittenauer
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is not
> generated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HADOOP-16551) The changelog*.md seems not generated when create-release
[
https://issues.apache.org/jira/browse/HADOOP-16551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923901#comment-16923901
]
Zhankun Tang edited comment on HADOOP-16551 at 9/6/19 3:27 AM:
---
Am I missing something before running this script? It seems not. I'm following
[https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease]
Could you please help with this? @Allen Wittenauer
was (Author: tangzhankun):
Am I miss something before running this script? I'm following
[https://cwiki.apache.org/confluence/display/HADOOP2/HowToRelease]
Could you please help with this? @Allen Wittenauer
> The changelog*.md seems not generated when create-release
> -
>
> Key: HADOOP-16551
> URL: https://issues.apache.org/jira/browse/HADOOP-16551
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Blocker
>
> Hi,
> When creating Hadoop 3.1.3 release with "create-release" script, after the
> mvn site succeeded. But it complains about this and failed:
> {code:java}
> dev-support/bin/create-release --asfrelease --docker --dockercache{code}
> {code:java}
> $ cd /build/source
> $ mv /build/source/target/hadoop-site-3.1.3.tar.gz
> /build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
> $ cp -p
> /build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
> /build/source/target/artifacts/CHANGES.md
> cp: cannot stat
> '/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
> No such file or directory
> {code}
> And there's no 3.1.3 release site markdown folder.
> {code:java}
> [ztang@release-vm hadoop]$ ls
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
> ls: cannot access
> hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
> file or directory
> {code}
> I've checked the HADOOP-14671 but have no idea why this changelog is not
> generated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-16551) The changelog*.md seems not generated when create-release
Zhankun Tang created HADOOP-16551:
-
Summary: The changelog*.md seems not generated when create-release
Key: HADOOP-16551
URL: https://issues.apache.org/jira/browse/HADOOP-16551
Project: Hadoop Common
Issue Type: Task
Reporter: Zhankun Tang
Hi,
When creating Hadoop 3.1.3 release with "create-release" script, after the mvn
site succeeded. But it complains about this and failed:
{code:java}
dev-support/bin/create-release --asfrelease --docker --dockercache{code}
{code:java}
$ cd /build/source
$ mv /build/source/target/hadoop-site-3.1.3.tar.gz
/build/source/target/artifacts/hadoop-3.1.3-site.tar.gz
$ cp -p
/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md
/build/source/target/artifacts/CHANGES.md
cp: cannot stat
'/build/source/hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3/CHANGES*.md':
No such file or directory
{code}
And there's no 3.1.3 release site markdown folder.
{code:java}
[ztang@release-vm hadoop]$ ls
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3
ls: cannot access
hadoop-common-project/hadoop-common/src/site/markdown/release/3.1.3: No such
file or directory
{code}
I've checked the HADOOP-14671 but have no idea why this changelog is not
generated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16545) Update the release year to 2019
[
https://issues.apache.org/jira/browse/HADOOP-16545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922990#comment-16922990
]
Zhankun Tang commented on HADOOP-16545:
---
[~ayushtkn], yeah. it helps. Thanks.
> Update the release year to 2019
> ---
>
> Key: HADOOP-16545
> URL: https://issues.apache.org/jira/browse/HADOOP-16545
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Critical
>
> Is doing the release. We need to update the release year from 2018 to 2019.
> {code:java}
> $ find . -name "pom.xml" | xargs grep -n 2018
> ./hadoop-project/pom.xml:34:2018
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16025) Update the year to 2019
[ https://issues.apache.org/jira/browse/HADOOP-16025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922308#comment-16922308 ] Zhankun Tang commented on HADOOP-16025: --- [~ayushtkn], found that branch-3.1 is not updated. I've done that. > Update the year to 2019 > --- > > Key: HADOOP-16025 > URL: https://issues.apache.org/jira/browse/HADOOP-16025 > Project: Hadoop Common > Issue Type: Task > Components: build >Reporter: Ayush Saxena >Assignee: Ayush Saxena >Priority: Major > Fix For: 3.2.0, 2.7.8, 3.0.4, 2.8.6, 2.9.3, 3.1.3 > > Attachments: HADOOP-16025-01.patch > > > Update the year to 2019 from 2018. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-16545) Update the release year to 2019
[
https://issues.apache.org/jira/browse/HADOOP-16545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang resolved HADOOP-16545.
---
Resolution: Duplicate
close this due to duplicated with HADOOP-16025
> Update the release year to 2019
> ---
>
> Key: HADOOP-16545
> URL: https://issues.apache.org/jira/browse/HADOOP-16545
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Zhankun Tang
>Priority: Critical
>
> Is doing the release. We need to update the release year from 2018 to 2019.
> {code:java}
> $ find . -name "pom.xml" | xargs grep -n 2018
> ./hadoop-project/pom.xml:34:2018
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-16545) Update the release year to 2019
Zhankun Tang created HADOOP-16545:
-
Summary: Update the release year to 2019
Key: HADOOP-16545
URL: https://issues.apache.org/jira/browse/HADOOP-16545
Project: Hadoop Common
Issue Type: Task
Reporter: Zhankun Tang
Is doing the release. We need to update the release year from 2018 to 2019.
{code:java}
$ find . -name "pom.xml" | xargs grep -n 2018
./hadoop-project/pom.xml:34:2018
{code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15747) warning about user:pass in URI to explicitly call out Hadoop 3.2 as removal
[ https://issues.apache.org/jira/browse/HADOOP-15747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-15747: -- Target Version/s: 2.10.0, 3.0.4, 3.1.4 (was: 2.10.0, 3.0.4, 3.1.3) > warning about user:pass in URI to explicitly call out Hadoop 3.2 as removal > --- > > Key: HADOOP-15747 > URL: https://issues.apache.org/jira/browse/HADOOP-15747 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.9.1, 3.1.1, 3.0.3 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Major > > Now that HADOOP-14833 has removed user:secret from URIs, change the warning > printed when people to that to explicitly declare Hadoop 3.3 as when it will > happen. Do the same in the docs. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15747) warning about user:pass in URI to explicitly call out Hadoop 3.2 as removal
[ https://issues.apache.org/jira/browse/HADOOP-15747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915822#comment-16915822 ] Zhankun Tang commented on HADOOP-15747: --- Bulk update: Preparing for 3.1.3 release. moved all 3.1.3 non-blocker issues to 3.1.4, please move back if it is a blocker for you. > warning about user:pass in URI to explicitly call out Hadoop 3.2 as removal > --- > > Key: HADOOP-15747 > URL: https://issues.apache.org/jira/browse/HADOOP-15747 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.9.1, 3.1.1, 3.0.3 >Reporter: Steve Loughran >Assignee: Steve Loughran >Priority: Major > > Now that HADOOP-14833 has removed user:secret from URIs, change the warning > printed when people to that to explicitly declare Hadoop 3.3 as when it will > happen. Do the same in the docs. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16083) DistCp shouldn't always overwrite the target file when checksums match
[
https://issues.apache.org/jira/browse/HADOOP-16083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915817#comment-16915817
]
Zhankun Tang commented on HADOOP-16083:
---
Bulk update: Preparing for 3.1.3 release. moved all 3.1.3 non-blocker issues to
3.1.4, please move back if it is a blocker for you.
> DistCp shouldn't always overwrite the target file when checksums match
> --
>
> Key: HADOOP-16083
> URL: https://issues.apache.org/jira/browse/HADOOP-16083
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.2.0, 3.1.1, 3.3.0
>Reporter: Siyao Meng
>Assignee: Siyao Meng
>Priority: Major
> Attachments: HADOOP-16083.001.patch
>
>
> {code:java|title=CopyMapper#setup}
> ...
> try {
> overWrite = overWrite ||
> targetFS.getFileStatus(targetFinalPath).isFile();
> } catch (FileNotFoundException ignored) {
> }
> ...
> {code}
> The above code overrides config key "overWrite" to "true" when the target
> path is a file. Therefore, unnecessary transfer happens when the source and
> target file have the same checksums.
> My suggestion is: remove the code above. If the user insists to overwrite,
> just add -overwrite in the options:
> {code:bash|title=DistCp command with -overwrite option}
> hadoop distcp -overwrite hdfs://localhost:64464/source/5/6.txt
> hdfs://localhost:64464/target/5/6.txt
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16082) FsShell ls: Add option -i to print inode id
[ https://issues.apache.org/jira/browse/HADOOP-16082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915816#comment-16915816 ] Zhankun Tang commented on HADOOP-16082: --- Bulk update: Preparing for 3.1.3 release. moved all 3.1.3 non-blocker issues to 3.1.4, please move back if it is a blocker for you. > FsShell ls: Add option -i to print inode id > --- > > Key: HADOOP-16082 > URL: https://issues.apache.org/jira/browse/HADOOP-16082 > Project: Hadoop Common > Issue Type: Improvement > Components: common >Affects Versions: 3.2.0, 3.1.1 >Reporter: Siyao Meng >Assignee: Siyao Meng >Priority: Major > Attachments: HADOOP-16082.001.patch > > > When debugging the FSImage corruption issue, I often need to know a file's or > directory's inode id. At this moment, the only way to do that is to use OIV > tool to dump the FSImage and look up the filename, which is very inefficient. > Here I propose adding option "-i" in FsShell that prints files' or > directories' inode id. > h2. Implementation > h3. For hdfs:// (HDFS) > fileId exists in HdfsLocatedFileStatus, which is already returned to > hdfs-client. We just need to print it in Ls#processPath(). > h3. For file:// (Local FS) > h4. Linux > Use java.nio. > h4. Windows > Windows has the concept of "File ID" which is similar to inode id. It is > unique in NTFS and ReFS. > h3. For other FS > The fileId entry will be "0" in FileStatus if it is not set. We could either > ignore or throw an exception. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16083) DistCp shouldn't always overwrite the target file when checksums match
[
https://issues.apache.org/jira/browse/HADOOP-16083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang updated HADOOP-16083:
--
Target Version/s: 3.3.0, 3.2.1, 3.1.4 (was: 3.3.0, 3.2.1, 3.1.3)
> DistCp shouldn't always overwrite the target file when checksums match
> --
>
> Key: HADOOP-16083
> URL: https://issues.apache.org/jira/browse/HADOOP-16083
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.2.0, 3.1.1, 3.3.0
>Reporter: Siyao Meng
>Assignee: Siyao Meng
>Priority: Major
> Attachments: HADOOP-16083.001.patch
>
>
> {code:java|title=CopyMapper#setup}
> ...
> try {
> overWrite = overWrite ||
> targetFS.getFileStatus(targetFinalPath).isFile();
> } catch (FileNotFoundException ignored) {
> }
> ...
> {code}
> The above code overrides config key "overWrite" to "true" when the target
> path is a file. Therefore, unnecessary transfer happens when the source and
> target file have the same checksums.
> My suggestion is: remove the code above. If the user insists to overwrite,
> just add -overwrite in the options:
> {code:bash|title=DistCp command with -overwrite option}
> hadoop distcp -overwrite hdfs://localhost:64464/source/5/6.txt
> hdfs://localhost:64464/target/5/6.txt
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16082) FsShell ls: Add option -i to print inode id
[ https://issues.apache.org/jira/browse/HADOOP-16082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-16082: -- Target Version/s: 3.3.0, 3.2.1, 3.1.4 (was: 3.3.0, 3.2.1, 3.1.3) > FsShell ls: Add option -i to print inode id > --- > > Key: HADOOP-16082 > URL: https://issues.apache.org/jira/browse/HADOOP-16082 > Project: Hadoop Common > Issue Type: Improvement > Components: common >Affects Versions: 3.2.0, 3.1.1 >Reporter: Siyao Meng >Assignee: Siyao Meng >Priority: Major > Attachments: HADOOP-16082.001.patch > > > When debugging the FSImage corruption issue, I often need to know a file's or > directory's inode id. At this moment, the only way to do that is to use OIV > tool to dump the FSImage and look up the filename, which is very inefficient. > Here I propose adding option "-i" in FsShell that prints files' or > directories' inode id. > h2. Implementation > h3. For hdfs:// (HDFS) > fileId exists in HdfsLocatedFileStatus, which is already returned to > hdfs-client. We just need to print it in Ls#processPath(). > h3. For file:// (Local FS) > h4. Linux > Use java.nio. > h4. Windows > Windows has the concept of "File ID" which is similar to inode id. It is > unique in NTFS and ReFS. > h3. For other FS > The fileId entry will be "0" in FileStatus if it is not set. We could either > ignore or throw an exception. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16310) Log of a slow RPC request should contain the parameter of the request
[
https://issues.apache.org/jira/browse/HADOOP-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang updated HADOOP-16310:
--
Target Version/s: 3.1.4 (was: 3.1.2)
> Log of a slow RPC request should contain the parameter of the request
> -
>
> Key: HADOOP-16310
> URL: https://issues.apache.org/jira/browse/HADOOP-16310
> Project: Hadoop Common
> Issue Type: Improvement
> Components: rpc-server
>Affects Versions: 3.1.1, 2.7.7, 3.1.2
>Reporter: lindongdong
>Priority: Minor
>
> Now, the log of a slow RPC request just contains the
> *methodName*,*processingTime* and *client*. Code is here:
> {code:java}
> if ((rpcMetrics.getProcessingSampleCount() > minSampleSize) &&
> (processingTime > threeSigma)) {
> if(LOG.isWarnEnabled()) {
> String client = CurCall.get().toString();
> LOG.warn(
> "Slow RPC : " + methodName + " took " + processingTime +
> " milliseconds to process from client " + client);
> }
> rpcMetrics.incrSlowRpc();
> }{code}
>
> It is not enough to analyze why the RPC request is slow.
> The parameter of the request is a very important thing, and need to be logged.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16310) Log of a slow RPC request should contain the parameter of the request
[
https://issues.apache.org/jira/browse/HADOOP-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915805#comment-16915805
]
Zhankun Tang commented on HADOOP-16310:
---
Bulk update: Preparing for 3.1.3 release. moved all 3.1.2 non-blocker issues to
3.1.4, please move back if it is a blocker for you.
> Log of a slow RPC request should contain the parameter of the request
> -
>
> Key: HADOOP-16310
> URL: https://issues.apache.org/jira/browse/HADOOP-16310
> Project: Hadoop Common
> Issue Type: Improvement
> Components: rpc-server
>Affects Versions: 3.1.1, 2.7.7, 3.1.2
>Reporter: lindongdong
>Priority: Minor
>
> Now, the log of a slow RPC request just contains the
> *methodName*,*processingTime* and *client*. Code is here:
> {code:java}
> if ((rpcMetrics.getProcessingSampleCount() > minSampleSize) &&
> (processingTime > threeSigma)) {
> if(LOG.isWarnEnabled()) {
> String client = CurCall.get().toString();
> LOG.warn(
> "Slow RPC : " + methodName + " took " + processingTime +
> " milliseconds to process from client " + client);
> }
> rpcMetrics.incrSlowRpc();
> }{code}
>
> It is not enough to analyze why the RPC request is slow.
> The parameter of the request is a very important thing, and need to be logged.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HADOOP-16310) Log of a slow RPC request should contain the parameter of the request
[
https://issues.apache.org/jira/browse/HADOOP-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915805#comment-16915805
]
Zhankun Tang edited comment on HADOOP-16310 at 8/26/19 2:03 PM:
Bulk update: Preparing for 3.1.3 release. moved all legacy 3.1.2 non-blocker
issues to 3.1.4, please move back if it is a blocker for you.
was (Author: tangzhankun):
Bulk update: Preparing for 3.1.3 release. moved all 3.1.2 non-blocker issues to
3.1.4, please move back if it is a blocker for you.
> Log of a slow RPC request should contain the parameter of the request
> -
>
> Key: HADOOP-16310
> URL: https://issues.apache.org/jira/browse/HADOOP-16310
> Project: Hadoop Common
> Issue Type: Improvement
> Components: rpc-server
>Affects Versions: 3.1.1, 2.7.7, 3.1.2
>Reporter: lindongdong
>Priority: Minor
>
> Now, the log of a slow RPC request just contains the
> *methodName*,*processingTime* and *client*. Code is here:
> {code:java}
> if ((rpcMetrics.getProcessingSampleCount() > minSampleSize) &&
> (processingTime > threeSigma)) {
> if(LOG.isWarnEnabled()) {
> String client = CurCall.get().toString();
> LOG.warn(
> "Slow RPC : " + methodName + " took " + processingTime +
> " milliseconds to process from client " + client);
> }
> rpcMetrics.incrSlowRpc();
> }{code}
>
> It is not enough to analyze why the RPC request is slow.
> The parameter of the request is a very important thing, and need to be logged.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15602) Support SASL Rpc request handling in separate Handlers
[ https://issues.apache.org/jira/browse/HADOOP-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915802#comment-16915802 ] Zhankun Tang commented on HADOOP-15602: --- Bulk update: Preparing for 3.1.3 release. moved all 3.1.3 non-blocker issues to 3.1.4, please move back if it is a blocker for you. > Support SASL Rpc request handling in separate Handlers > --- > > Key: HADOOP-15602 > URL: https://issues.apache.org/jira/browse/HADOOP-15602 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Reporter: Vinayakumar B >Assignee: Vinayakumar B >Priority: Major > Attachments: HADOOP-15602.01.patch, HADOOP-15602.02.patch, > HADOOP-15602.04.patch > > > Right now, during RPC Connection establishment, all SASL requests are > considered as OutOfBand requests and handled within the same Reader thread. > SASL handling involves authentication with Kerberos and SecretManagers(for > Token validation). During this time, Reader thread would be blocked, hence > blocking all the incoming RPC requests on other established connections. Some > secretManager impls require to communicate to external systems (ex: ZK) for > verification. > SASL RPC handling in separate dedicated handlers, would enable Reader threads > to read RPC requests from established connections without blocking. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15602) Support SASL Rpc request handling in separate Handlers
[ https://issues.apache.org/jira/browse/HADOOP-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhankun Tang updated HADOOP-15602: -- Target Version/s: 3.1.4 (was: 3.1.3) > Support SASL Rpc request handling in separate Handlers > --- > > Key: HADOOP-15602 > URL: https://issues.apache.org/jira/browse/HADOOP-15602 > Project: Hadoop Common > Issue Type: Improvement > Components: ipc >Reporter: Vinayakumar B >Assignee: Vinayakumar B >Priority: Major > Attachments: HADOOP-15602.01.patch, HADOOP-15602.02.patch, > HADOOP-15602.04.patch > > > Right now, during RPC Connection establishment, all SASL requests are > considered as OutOfBand requests and handled within the same Reader thread. > SASL handling involves authentication with Kerberos and SecretManagers(for > Token validation). During this time, Reader thread would be blocked, hence > blocking all the incoming RPC requests on other established connections. Some > secretManager impls require to communicate to external systems (ex: ZK) for > verification. > SASL RPC handling in separate dedicated handlers, would enable Reader threads > to read RPC requests from established connections without blocking. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15821) Move Hadoop YARN Registry to Hadoop Registry
[ https://issues.apache.org/jira/browse/HADOOP-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658483#comment-16658483 ] Zhankun Tang commented on HADOOP-15821: --- [~eyang], Thanks! > Move Hadoop YARN Registry to Hadoop Registry > > > Key: HADOOP-15821 > URL: https://issues.apache.org/jira/browse/HADOOP-15821 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Íñigo Goiri >Assignee: Íñigo Goiri >Priority: Major > Fix For: 3.3.0 > > Attachments: HADOOP-15821.000.patch, HADOOP-15821.001.patch, > HADOOP-15821.002.patch, HADOOP-15821.003.patch, HADOOP-15821.004.patch, > HADOOP-15821.005.patch, HADOOP-15821.006.patch, HADOOP-15821.007.patch, > HADOOP-15821.008.patch, HADOOP-15821.009.patch, HADOOP-15821.addendum.patch > > > Currently, Hadoop YARN Registry is in YARN. However, this can be used by > other parts of the project (e.g., HDFS). In addition, it does not have any > real dependency to YARN. > We should move it into commons and make it Hadoop Registry. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15821) Move Hadoop YARN Registry to Hadoop Registry
[ https://issues.apache.org/jira/browse/HADOOP-15821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658103#comment-16658103 ] Zhankun Tang commented on HADOOP-15821: --- [~elgoiri] , [~eyang] , I git pull in my Ubuntu develop VM just now and my build failed. It has the same error message as you posted. But I can build with my Mac. > Move Hadoop YARN Registry to Hadoop Registry > > > Key: HADOOP-15821 > URL: https://issues.apache.org/jira/browse/HADOOP-15821 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: Íñigo Goiri >Assignee: Íñigo Goiri >Priority: Major > Fix For: 3.3.0 > > Attachments: HADOOP-15821.000.patch, HADOOP-15821.001.patch, > HADOOP-15821.002.patch, HADOOP-15821.003.patch, HADOOP-15821.004.patch, > HADOOP-15821.005.patch, HADOOP-15821.006.patch, HADOOP-15821.007.patch, > HADOOP-15821.008.patch, HADOOP-15821.009.patch, HADOOP-15821.addendum.patch > > > Currently, Hadoop YARN Registry is in YARN. However, this can be used by > other parts of the project (e.g., HDFS). In addition, it does not have any > real dependency to YARN. > We should move it into commons and make it Hadoop Registry. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
