[jira] [Created] (HADOOP-15909) KeyProvider class should implement Closeable
Kuhu Shukla created HADOOP-15909: Summary: KeyProvider class should implement Closeable Key: HADOOP-15909 URL: https://issues.apache.org/jira/browse/HADOOP-15909 Project: Hadoop Common Issue Type: Improvement Components: kms Affects Versions: 2.8.5, 3.0.3 Reporter: Kuhu Shukla Assignee: Kuhu Shukla KeyProviders and the extensions have close() methods. The classes should implement Closeable that will allow try-with-resources to work and help catch original exceptions instead of finally blocks and exception masking that follows that. -- 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] [Updated] (HADOOP-14128) ChecksumFs should override rename with overwrite flag
[ https://issues.apache.org/jira/browse/HADOOP-14128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrishikesh Gadre updated HADOOP-14128: -- Resolution: Not A Problem Status: Resolved (was: Patch Available) [~mathieu_c] I am resolving this Jira as per my last comment. Feel free to reopen if you can reproduce the checksum file issue consistently (e.g. a unit test etc.) > ChecksumFs should override rename with overwrite flag > - > > Key: HADOOP-14128 > URL: https://issues.apache.org/jira/browse/HADOOP-14128 > Project: Hadoop Common > Issue Type: Bug > Components: common, fs >Affects Versions: 2.8.1 >Reporter: Mathieu Chataigner >Assignee: Hrishikesh Gadre >Priority: Major > Attachments: HADOOP-14128-003.patch, > HADOOP-14128-branch-2.8.1-001.patch, HADOOP-14128-branch2.8.1-001.patch, > HADOOP-14128.001.patch, HADOOP-14128.002.patch > > > When I call FileContext.rename(src, dst, Options.Rename.OVERWRITE) on a > LocalFs (which extends ChecksumFs), it does not update crc files. > Every subsequent read on moved files will result in failures due to crc > missmatch. > One solution is to override rename(src, dst, overwrite) the same way it's > done with rename(src, dst) and moving crc files accordingly. -- 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] [Updated] (HADOOP-15909) KeyProvider class should implement Closeable
[ https://issues.apache.org/jira/browse/HADOOP-15909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated HADOOP-15909: - Status: Patch Available (was: Open) > KeyProvider class should implement Closeable > > > Key: HADOOP-15909 > URL: https://issues.apache.org/jira/browse/HADOOP-15909 > Project: Hadoop Common > Issue Type: Improvement > Components: kms >Affects Versions: 2.8.5, 3.0.3 >Reporter: Kuhu Shukla >Assignee: Kuhu Shukla >Priority: Major > Attachments: HADOOP-15909.001.patch > > > KeyProviders and the extensions have close() methods. The classes should > implement Closeable that will allow try-with-resources to work and help catch > original exceptions instead of finally blocks and exception masking that > follows that. -- 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] [Updated] (HADOOP-15909) KeyProvider class should implement Closeable
[ https://issues.apache.org/jira/browse/HADOOP-15909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated HADOOP-15909: - Attachment: HADOOP-15909.001.patch > KeyProvider class should implement Closeable > > > Key: HADOOP-15909 > URL: https://issues.apache.org/jira/browse/HADOOP-15909 > Project: Hadoop Common > Issue Type: Improvement > Components: kms >Affects Versions: 3.0.3, 2.8.5 >Reporter: Kuhu Shukla >Assignee: Kuhu Shukla >Priority: Major > Attachments: HADOOP-15909.001.patch > > > KeyProviders and the extensions have close() methods. The classes should > implement Closeable that will allow try-with-resources to work and help catch > original exceptions instead of finally blocks and exception masking that > follows that. -- 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-14176) distcp reports beyond physical memory limits on 2.X
[
https://issues.apache.org/jira/browse/HADOOP-14176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678621#comment-16678621
]
Tak Lon (Stephen) Wu commented on HADOOP-14176:
---
any update on this? I recently got into an issue that on a very large memory
instance, it went `{color:#22}beyond virtual memory limits{color}`. IMO if
we don't have this `distcp-default.xml` and only use the system default, this
issue will not happened and operator don't need to guess what's happening
behind the scenes.
> distcp reports beyond physical memory limits on 2.X
> ---
>
> Key: HADOOP-14176
> URL: https://issues.apache.org/jira/browse/HADOOP-14176
> Project: Hadoop Common
> Issue Type: Bug
> Components: tools/distcp
>Affects Versions: 2.9.0
>Reporter: Fei Hui
>Assignee: Fei Hui
>Priority: Major
> Attachments: HADOOP-14176-branch-2.001.patch,
> HADOOP-14176-branch-2.002.patch, HADOOP-14176-branch-2.003.patch,
> HADOOP-14176-branch-2.004.patch
>
>
> When i run distcp, i get some errors as follow
> {quote}
> 17/02/21 15:31:18 INFO mapreduce.Job: Task Id :
> attempt_1487645941615_0037_m_03_0, Status : FAILED
> Container [pid=24661,containerID=container_1487645941615_0037_01_05] is
> running beyond physical memory limits. Current usage: 1.1 GB of 1 GB physical
> memory used; 4.0 GB of 5 GB virtual memory used. Killing container.
> Dump of the process-tree for container_1487645941615_0037_01_05 :
> |- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS)
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE
> |- 24661 24659 24661 24661 (bash) 0 0 108650496 301 /bin/bash -c
> /usr/lib/jvm/java/bin/java -Djava.net.preferIPv4Stack=true
> -Dhadoop.metrics.log.level=WARN -Xmx2120m
> -Djava.io.tmpdir=/mnt/disk4/yarn/usercache/hadoop/appcache/application_1487645941615_0037/container_1487645941615_0037_01_05/tmp
> -Dlog4j.configuration=container-log4j.properties
> -Dyarn.app.container.log.dir=/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05
> -Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
> -Dhadoop.root.logfile=syslog org.apache.hadoop.mapred.YarnChild 192.168.1.208
> 44048 attempt_1487645941615_0037_m_03_0 5
> 1>/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05/stdout
>
> 2>/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05/stderr
> |- 24665 24661 24661 24661 (java) 1766 336 4235558912 280699
> /usr/lib/jvm/java/bin/java -Djava.net.preferIPv4Stack=true
> -Dhadoop.metrics.log.level=WARN -Xmx2120m
> -Djava.io.tmpdir=/mnt/disk4/yarn/usercache/hadoop/appcache/application_1487645941615_0037/container_1487645941615_0037_01_05/tmp
> -Dlog4j.configuration=container-log4j.properties
> -Dyarn.app.container.log.dir=/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05
> -Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
> -Dhadoop.root.logfile=syslog org.apache.hadoop.mapred.YarnChild 192.168.1.208
> 44048 attempt_1487645941615_0037_m_03_0 5
> Container killed on request. Exit code is 143
> Container exited with a non-zero exit code 143
> {quote}
> Deep into the code , i find that because distcp configuration covers
> mapred-site.xml
> {code}
>
> mapred.job.map.memory.mb
> 1024
>
>
> mapred.job.reduce.memory.mb
> 1024
>
> {code}
> When mapreduce.map.java.opts and mapreduce.map.memory.mb is setting in
> mapred-default.xml, and the value is larger than setted in
> distcp-default.xml, the error maybe occur.
> we should remove those two configurations in distcp-default.xml
--
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] [Updated] (HADOOP-15812) ABFS: Improve AbfsRestOperationException format to ensure full msg can be displayed on console
[ https://issues.apache.org/jira/browse/HADOOP-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Zhou updated HADOOP-15812: - Status: Patch Available (was: Open) Submitting patch 002. For failed HEAD request, the msg shown on console will be something like: HEAD request failed, StatusCode=403 [https://X|https://x/] StatusDescription=XX. For other failed request, the msg shown on console will be: PUT request failed, ErrorCode=X StatusCode=409 https://XX > ABFS: Improve AbfsRestOperationException format to ensure full msg can be > displayed on console > -- > > Key: HADOOP-15812 > URL: https://issues.apache.org/jira/browse/HADOOP-15812 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Affects Versions: 3.2.0 >Reporter: Da Zhou >Assignee: Da Zhou >Priority: Major > Attachments: HADOOP-15812-001.patch, HADOOP-15812-002.patch > > > AbfsRestOperationException msg contains multiple "\n" for displaying nicely, > however, hadoop cmd class split the error msg by "\n" and display the first > string in console, which lead to the incomplete error msg shown in console. > Hence we need to improve this format. -- 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] [Comment Edited] (HADOOP-15812) ABFS: Improve AbfsRestOperationException format to ensure full msg can be displayed on console
[ https://issues.apache.org/jira/browse/HADOOP-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678701#comment-16678701 ] Da Zhou edited comment on HADOOP-15812 at 11/7/18 7:52 PM: --- Submitting patch 002. For failed HEAD request, the msg shown on console will be something like: *HEAD request failed, StatusCode=403 [https://X|https://x/] StatusDescription=XX.* For other failed request, the msg shown on console will be something like: *PUT request failed, ErrorCode=X StatusCode=409 [https://XX|https://xx/]* was (Author: danielzhou): Submitting patch 002. For failed HEAD request, the msg shown on console will be something like: HEAD request failed, StatusCode=403 [https://X|https://x/] StatusDescription=XX. For other failed request, the msg shown on console will be: PUT request failed, ErrorCode=X StatusCode=409 https://XX > ABFS: Improve AbfsRestOperationException format to ensure full msg can be > displayed on console > -- > > Key: HADOOP-15812 > URL: https://issues.apache.org/jira/browse/HADOOP-15812 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Affects Versions: 3.2.0 >Reporter: Da Zhou >Assignee: Da Zhou >Priority: Major > Attachments: HADOOP-15812-001.patch, HADOOP-15812-002.patch > > > AbfsRestOperationException msg contains multiple "\n" for displaying nicely, > however, hadoop cmd class split the error msg by "\n" and display the first > string in console, which lead to the incomplete error msg shown in console. > Hence we need to improve this format. -- 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-15909) KeyProvider class should implement Closeable
[
https://issues.apache.org/jira/browse/HADOOP-15909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678664#comment-16678664
]
Hadoop QA commented on HADOOP-15909:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m
45s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 14m
38s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
51s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
13s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
14m 13s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
40s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
58s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 13m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 13m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 18s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
58s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m
9s{color} | {color:green} hadoop-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
40s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 94m 55s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | HADOOP-15909 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12947259/HADOOP-15909.001.patch
|
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 30ce5e6a6920 4.4.0-134-generic #160~14.04.1-Ubuntu SMP Fri Aug
17 11:07:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / c96cbe8 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC1 |
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15483/testReport/ |
| Max. process+thread count | 1515 (vs. ulimit of 1) |
| modules | C: hadoop-common-project/hadoop-common U:
hadoop-common-project/hadoop-common |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15483/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> KeyProvider class
[jira] [Comment Edited] (HADOOP-14176) distcp reports beyond physical memory limits on 2.X
[
https://issues.apache.org/jira/browse/HADOOP-14176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678621#comment-16678621
]
Tak Lon (Stephen) Wu edited comment on HADOOP-14176 at 11/7/18 6:44 PM:
any update on this? I recently got into an issue that on a very large memory
instance, it went `{color:#22}beyond virtual memory limits{color}`. IMO if
we don't have this `distcp-default.xml` and only use the system default in
mapred-site and yarn-site, this issue will not happened and operator don't need
to guess what's happening behind the scenes.
was (Author: taklwu):
any update on this? I recently got into an issue that on a very large memory
instance, it went `{color:#22}beyond virtual memory limits{color}`. IMO if
we don't have this `distcp-default.xml` and only use the system default, this
issue will not happened and operator don't need to guess what's happening
behind the scenes.
> distcp reports beyond physical memory limits on 2.X
> ---
>
> Key: HADOOP-14176
> URL: https://issues.apache.org/jira/browse/HADOOP-14176
> Project: Hadoop Common
> Issue Type: Bug
> Components: tools/distcp
>Affects Versions: 2.9.0
>Reporter: Fei Hui
>Assignee: Fei Hui
>Priority: Major
> Attachments: HADOOP-14176-branch-2.001.patch,
> HADOOP-14176-branch-2.002.patch, HADOOP-14176-branch-2.003.patch,
> HADOOP-14176-branch-2.004.patch
>
>
> When i run distcp, i get some errors as follow
> {quote}
> 17/02/21 15:31:18 INFO mapreduce.Job: Task Id :
> attempt_1487645941615_0037_m_03_0, Status : FAILED
> Container [pid=24661,containerID=container_1487645941615_0037_01_05] is
> running beyond physical memory limits. Current usage: 1.1 GB of 1 GB physical
> memory used; 4.0 GB of 5 GB virtual memory used. Killing container.
> Dump of the process-tree for container_1487645941615_0037_01_05 :
> |- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS)
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE
> |- 24661 24659 24661 24661 (bash) 0 0 108650496 301 /bin/bash -c
> /usr/lib/jvm/java/bin/java -Djava.net.preferIPv4Stack=true
> -Dhadoop.metrics.log.level=WARN -Xmx2120m
> -Djava.io.tmpdir=/mnt/disk4/yarn/usercache/hadoop/appcache/application_1487645941615_0037/container_1487645941615_0037_01_05/tmp
> -Dlog4j.configuration=container-log4j.properties
> -Dyarn.app.container.log.dir=/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05
> -Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
> -Dhadoop.root.logfile=syslog org.apache.hadoop.mapred.YarnChild 192.168.1.208
> 44048 attempt_1487645941615_0037_m_03_0 5
> 1>/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05/stdout
>
> 2>/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05/stderr
> |- 24665 24661 24661 24661 (java) 1766 336 4235558912 280699
> /usr/lib/jvm/java/bin/java -Djava.net.preferIPv4Stack=true
> -Dhadoop.metrics.log.level=WARN -Xmx2120m
> -Djava.io.tmpdir=/mnt/disk4/yarn/usercache/hadoop/appcache/application_1487645941615_0037/container_1487645941615_0037_01_05/tmp
> -Dlog4j.configuration=container-log4j.properties
> -Dyarn.app.container.log.dir=/mnt/disk2/log/hadoop-yarn/containers/application_1487645941615_0037/container_1487645941615_0037_01_05
> -Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
> -Dhadoop.root.logfile=syslog org.apache.hadoop.mapred.YarnChild 192.168.1.208
> 44048 attempt_1487645941615_0037_m_03_0 5
> Container killed on request. Exit code is 143
> Container exited with a non-zero exit code 143
> {quote}
> Deep into the code , i find that because distcp configuration covers
> mapred-site.xml
> {code}
>
> mapred.job.map.memory.mb
> 1024
>
>
> mapred.job.reduce.memory.mb
> 1024
>
> {code}
> When mapreduce.map.java.opts and mapreduce.map.memory.mb is setting in
> mapred-default.xml, and the value is larger than setted in
> distcp-default.xml, the error maybe occur.
> we should remove those two configurations in distcp-default.xml
--
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-15846) ABFS: fix mask related bugs in setAcl, modifyAclEntries and removeAclEntries.
[ https://issues.apache.org/jira/browse/HADOOP-15846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678809#comment-16678809 ] Da Zhou commented on HADOOP-15846: -- Updated patch name and resubmit it. > ABFS: fix mask related bugs in setAcl, modifyAclEntries and removeAclEntries. > - > > Key: HADOOP-15846 > URL: https://issues.apache.org/jira/browse/HADOOP-15846 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Affects Versions: 3.2.0 >Reporter: Thomas Marquardt >Assignee: junhua gu >Priority: Major > Attachments: HADOOP-15763-HADOOP-15846-001.patch, > HADOOP-15846-002.patch > > > # setAcl, modifyAclEntries and removeAclEntries should not re-calculate > default mask if not touched. > # Duplicate Acl Entries are not allowed. -- 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] [Updated] (HADOOP-15846) ABFS: fix mask related bugs in setAcl, modifyAclEntries and removeAclEntries.
[ https://issues.apache.org/jira/browse/HADOOP-15846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Zhou updated HADOOP-15846: - Attachment: HADOOP-15846-002.patch > ABFS: fix mask related bugs in setAcl, modifyAclEntries and removeAclEntries. > - > > Key: HADOOP-15846 > URL: https://issues.apache.org/jira/browse/HADOOP-15846 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Affects Versions: 3.2.0 >Reporter: Thomas Marquardt >Assignee: junhua gu >Priority: Major > Attachments: HADOOP-15763-HADOOP-15846-001.patch, > HADOOP-15846-002.patch > > > # setAcl, modifyAclEntries and removeAclEntries should not re-calculate > default mask if not touched. > # Duplicate Acl Entries are not allowed. -- 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-15812) ABFS: Improve AbfsRestOperationException format to ensure full msg can be displayed on console
[
https://issues.apache.org/jira/browse/HADOOP-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678761#comment-16678761
]
Hadoop QA commented on HADOOP-15812:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
23s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m
44s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
29s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
21s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
31s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 22s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
41s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
15s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
13m 21s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m
12s{color} | {color:green} hadoop-azure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
26s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 53m 47s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | HADOOP-15812 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12947272/HADOOP-15812-002.patch
|
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux b43c9b4288b2 3.13.0-144-generic #193-Ubuntu SMP Thu Mar 15
17:03:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / c96cbe8 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC1 |
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15485/testReport/ |
| Max. process+thread count | 308 (vs. ulimit of 1) |
| modules | C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15485/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> ABFS: Improve AbfsRestOperationException format
[jira] [Commented] (HADOOP-15909) KeyProvider class should implement Closeable
[ https://issues.apache.org/jira/browse/HADOOP-15909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678813#comment-16678813 ] Kuhu Shukla commented on HADOOP-15909: -- [~daryn], I have not added a test as it is a simple implements clause change. I can add a static object type check on what all it implements and such as a test if you think that is required. Appreciate a review. Thanks a lot! > KeyProvider class should implement Closeable > > > Key: HADOOP-15909 > URL: https://issues.apache.org/jira/browse/HADOOP-15909 > Project: Hadoop Common > Issue Type: Improvement > Components: kms >Affects Versions: 3.0.3, 2.8.5 >Reporter: Kuhu Shukla >Assignee: Kuhu Shukla >Priority: Major > Attachments: HADOOP-15909.001.patch > > > KeyProviders and the extensions have close() methods. The classes should > implement Closeable that will allow try-with-resources to work and help catch > original exceptions instead of finally blocks and exception masking that > follows that. -- 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-15812) ABFS: Improve AbfsRestOperationException format to ensure full msg can be displayed on console
[
https://issues.apache.org/jira/browse/HADOOP-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678928#comment-16678928
]
Da Zhou commented on HADOOP-15812:
--
Submitting patch 003.
Tested locally, exception example:
Exception for failed Head request:
{noformat}
Operation failed: "StatusErrorMsg.", 403, HEAD, https://
{noformat}
Exception for failed put request:
{noformat}
Operation failed: "StatusErrorMsg.", 409, PUT, https://XX, "X.
RequestId:XXX, Time:2018-11-0"
{noformat}
> ABFS: Improve AbfsRestOperationException format to ensure full msg can be
> displayed on console
> --
>
> Key: HADOOP-15812
> URL: https://issues.apache.org/jira/browse/HADOOP-15812
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
>Affects Versions: 3.2.0
>Reporter: Da Zhou
>Assignee: Da Zhou
>Priority: Major
> Attachments: HADOOP-15812-001.patch, HADOOP-15812-002.patch,
> HADOOP-15812-003.patch
>
>
> AbfsRestOperationException msg contains multiple "\n" for displaying nicely,
> however, hadoop cmd class split the error msg by "\n" and display the first
> string in console, which lead to the incomplete error msg shown in console.
> Hence we need to improve this format.
--
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-15846) ABFS: fix mask related bugs in setAcl, modifyAclEntries and removeAclEntries.
[
https://issues.apache.org/jira/browse/HADOOP-15846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16678893#comment-16678893
]
Hadoop QA commented on HADOOP-15846:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
19s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 19m
52s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
28s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
31s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 35s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
39s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
21s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
26s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
13m 12s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m
12s{color} | {color:green} hadoop-azure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
24s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 52m 50s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | HADOOP-15846 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12947284/HADOOP-15846-002.patch
|
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 67e3315a92de 3.13.0-144-generic #193-Ubuntu SMP Thu Mar 15
17:03:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / c96cbe8 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC1 |
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15486/testReport/ |
| Max. process+thread count | 315 (vs. ulimit of 1) |
| modules | C: hadoop-tools/hadoop-azure U: hadoop-tools/hadoop-azure |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15486/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> ABFS: fix mask related bugs in setAcl, modifyAclEntries and removeAclEntries.
> -
>
>
[jira] [Updated] (HADOOP-15812) ABFS: Improve AbfsRestOperationException format to ensure full msg can be displayed on console
[ https://issues.apache.org/jira/browse/HADOOP-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Zhou updated HADOOP-15812: - Attachment: HADOOP-15812-002.patch > ABFS: Improve AbfsRestOperationException format to ensure full msg can be > displayed on console > -- > > Key: HADOOP-15812 > URL: https://issues.apache.org/jira/browse/HADOOP-15812 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Affects Versions: 3.2.0 >Reporter: Da Zhou >Assignee: Da Zhou >Priority: Major > Attachments: HADOOP-15812-001.patch, HADOOP-15812-002.patch > > > AbfsRestOperationException msg contains multiple "\n" for displaying nicely, > however, hadoop cmd class split the error msg by "\n" and display the first > string in console, which lead to the incomplete error msg shown in console. > Hence we need to improve this format. -- 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] [Updated] (HADOOP-15812) ABFS: Improve AbfsRestOperationException format to ensure full msg can be displayed on console
[ https://issues.apache.org/jira/browse/HADOOP-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Zhou updated HADOOP-15812: - Attachment: HADOOP-15812-003.patch > ABFS: Improve AbfsRestOperationException format to ensure full msg can be > displayed on console > -- > > Key: HADOOP-15812 > URL: https://issues.apache.org/jira/browse/HADOOP-15812 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Affects Versions: 3.2.0 >Reporter: Da Zhou >Assignee: Da Zhou >Priority: Major > Attachments: HADOOP-15812-001.patch, HADOOP-15812-002.patch, > HADOOP-15812-003.patch > > > AbfsRestOperationException msg contains multiple "\n" for displaying nicely, > however, hadoop cmd class split the error msg by "\n" and display the first > string in console, which lead to the incomplete error msg shown in console. > Hence we need to improve this format. -- 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] [Updated] (HADOOP-15912) start-build-env.sh still creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry after HADOOP-15802
[
https://issues.apache.org/jira/browse/HADOOP-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-15912:
---
Attachment: HADOOP-15912.01.patch
> start-build-env.sh still creates an invalid
> /etc/sudoers.d/hadoop-build-${USER_ID} file entry after HADOOP-15802
>
>
> Key: HADOOP-15912
> URL: https://issues.apache.org/jira/browse/HADOOP-15912
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Environment: CentOS 7.5 and Docker 1.13.1
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Attachments: HADOOP-15912.01.patch
>
>
> {noformat}
> RUN echo -e "${USER_NAME}\tALL=NOPASSWD: ALL" >
> "/etc/sudoers.d/hadoop-build-${USER_ID}"
> {noformat}
> creates
> {noformat}
> -e ALL=NOPASSWD: ALL
> {noformat}
--
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] [Updated] (HADOOP-15912) start-build-env.sh still creates an invalid /etc/sudoers.d/hadoop-build-${USER_ID} file entry after HADOOP-15802
[
https://issues.apache.org/jira/browse/HADOOP-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HADOOP-15912:
---
Target Version/s: 3.3.0, 3.1.2, 3.2.1
Status: Patch Available (was: Open)
> start-build-env.sh still creates an invalid
> /etc/sudoers.d/hadoop-build-${USER_ID} file entry after HADOOP-15802
>
>
> Key: HADOOP-15912
> URL: https://issues.apache.org/jira/browse/HADOOP-15912
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Environment: CentOS 7.5 and Docker 1.13.1
>Reporter: Akira Ajisaka
>Assignee: Akira Ajisaka
>Priority: Major
> Attachments: HADOOP-15912.01.patch
>
>
> {noformat}
> RUN echo -e "${USER_NAME}\tALL=NOPASSWD: ALL" >
> "/etc/sudoers.d/hadoop-build-${USER_ID}"
> {noformat}
> creates
> {noformat}
> -e ALL=NOPASSWD: ALL
> {noformat}
--
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-15908) hadoop-build-tools jar is downloaded from remote repository instead of using from local
[
https://issues.apache.org/jira/browse/HADOOP-15908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677910#comment-16677910
]
Oleksandr Shevchenko commented on HADOOP-15908:
---
Thanks [~ajisakaa] for the review. I missed this. I'll recheck this and submit
a new patch.
> hadoop-build-tools jar is downloaded from remote repository instead of using
> from local
> ---
>
> Key: HADOOP-15908
> URL: https://issues.apache.org/jira/browse/HADOOP-15908
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Oleksandr Shevchenko
>Priority: Minor
> Attachments: HADOOP-15908.001.patch
>
>
> HADOOP-12893 added "maven-remote-resources-plugin" to hadoop-project/pom.xml
> to verify LICENSE.txt and NOTICE.txt files which includes
> "hadoop-build-tools" remote resource bundles.
> {code}
>
> org.apache.maven.plugins
> maven-remote-resources-plugin
> ${maven-remote-resources-plugin.version}
>
>
>
> org.apache.hadoop:hadoop-build-tools:${hadoop.version}
>
>
>
>
> org.apache.hadoop
> hadoop-build-tools
> ${hadoop.version}
>
>
>
>
>
> process
>
>
>
>
> {code}
> If we build only some module we always download " hadoop-build-tools" from
> maven repository.
> For example run:
> cd hadoop-common-project/
> mvn test
> Then we will get the following output:
> {noformat}
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @
> hadoop-annotations ---
> Downloading from apache.snapshots:
> http://repository.apache.org/snapshots/org/apache/hadoop/hadoop-build-tools/3.3.0-SNAPSHOT/maven-metadata.xml
> Downloaded from apache.snapshots:
> http://repository.apache.org/snapshots/org/apache/hadoop/hadoop-build-tools/3.3.0-SNAPSHOT/maven-metadata.xml
> (791 B at 684 B/s)
> Downloading from apache.snapshots:
> http://repository.apache.org/snapshots/org/apache/hadoop/hadoop-main/3.3.0-SNAPSHOT/maven-metadata.xml
> Downloaded from apache.snapshots:
> http://repository.apache.org/snapshots/org/apache/hadoop/hadoop-main/3.3.0-SNAPSHOT/maven-metadata.xml
> (609 B at 547 B/s)
> Downloading from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-build-tools/3.3.0-SNAPSHOT/maven-metadata.xml
> Downloaded from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-build-tools/3.3.0-SNAPSHOT/maven-metadata.xml
> (791 B at 343 B/s)
> Downloading from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-build-tools/3.3.0-SNAPSHOT/hadoop-build-tools-3.3.0-20181022.232020-179.jar
> Downloaded from apache.snapshots.https:
> https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-build-tools/3.3.0-SNAPSHOT/hadoop-build-tools-3.3.0-20181022.232020-179.jar
> (0 B at 0 B/s)
> {noformat}
> If "hadoop-build-tools" jar doesn't exist in maven repository (for example we
> try to build new version locally before repository will be created ) we can't
> build some module:
> For example run:
> cd hadoop-common-project/
> mvn test
> Then we will get the following output:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project hadoop-annotations: Execution default of goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process failed:
> Plugin org.apache.maven.plugins:maven-remote-resources-plugin:1.5 or one of
> its dependencies could not be resolved: Failure to find
> org.apache.hadoop:hadoop-build-tools:jar:3.2.0 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced -> [Help 1]
> {noformat}
> Therefore, we need to limit execution of the Remote Resources Plugin only in
> the root directory in which the build was run.
> To accomplish this, we can use the "runOnlyAtExecutionRoot parameter"
> From maven documentation
> http://maven.apache.org/plugins/maven-remote-resources-plugin/usage.html
--
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-15891) Provide Regex Based Mount Point In Inode Tree
[
https://issues.apache.org/jira/browse/HADOOP-15891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677937#comment-16677937
]
Hadoop QA commented on HADOOP-15891:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 5 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
4s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 21m
32s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 16m
18s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 3m
32s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 2m
27s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
18m 54s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
50s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
59s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
42s{color} | {color:red} hadoop-common in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
54s{color} | {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 1m
6s{color} | {color:red} root in the patch failed. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 1m 6s{color}
| {color:red} root in the patch failed. {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
3m 14s{color} | {color:orange} root: The patch generated 1 new + 92 unchanged -
3 fixed = 93 total (was 95) {color} |
| {color:red}-1{color} | {color:red} mvnsite {color} | {color:red} 0m
46s{color} | {color:red} hadoop-common in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvnsite {color} | {color:red} 0m
55s{color} | {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} shadedclient {color} | {color:red} 0m
47s{color} | {color:red} patch has errors when building and testing our client
artifacts. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
28s{color} | {color:red} hadoop-common in the patch failed. {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m
33s{color} | {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
34s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 0m 47s{color}
| {color:red} hadoop-common in the patch failed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 0m 51s{color}
| {color:red} hadoop-hdfs in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
23s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 79m 25s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f |
| JIRA Issue | HADOOP-15891 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12947200/HDFS-13948.011.patch |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux
[jira] [Commented] (HADOOP-15907) Add missing maven modules in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677902#comment-16677902 ] Hudson commented on HADOOP-15907: - SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15381 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/15381/]) HADOOP-15907. Add missing maven modules in BUILDING.txt. Contributed (wwei: rev e6444f1c640cda86e1c97fbfebf68de92a162c95) * (edit) BUILDING.txt > Add missing maven modules in BUILDING.txt > - > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Fix For: 3.3.0 > > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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] [Updated] (HADOOP-15907) Add missing maven modules in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated HADOOP-15907: - Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 3.3.0 Status: Resolved (was: Patch Available) > Add missing maven modules in BUILDING.txt > - > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Fix For: 3.3.0 > > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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] [Updated] (HADOOP-15891) Provide Regex Based Mount Point In Inode Tree
[ https://issues.apache.org/jira/browse/HADOOP-15891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhenzhao wang updated HADOOP-15891: --- Attachment: HDFS-13948.011.patch > Provide Regex Based Mount Point In Inode Tree > - > > Key: HADOOP-15891 > URL: https://issues.apache.org/jira/browse/HADOOP-15891 > Project: Hadoop Common > Issue Type: New Feature > Components: fs >Reporter: zhenzhao wang >Assignee: zhenzhao wang >Priority: Major > Attachments: HDFS-13948.001.patch, HDFS-13948.002.patch, > HDFS-13948.003.patch, HDFS-13948.004.patch, HDFS-13948.005.patch, > HDFS-13948.006.patch, HDFS-13948.007.patch, HDFS-13948.008.patch, > HDFS-13948.009.patch, HDFS-13948.011.patch, HDFS-13948_ Regex Link Type In > Mont Table-V0.pdf, HDFS-13948_ Regex Link Type In Mount Table-v1.pdf > > > This jira is created to support regex based mount point in Inode Tree. We > noticed that mount point only support fixed target path. However, we might > have user cases when target needs to refer some fields from source. e.g. We > might want a mapping of /cluster1/user1 => /cluster1-dc1/user-nn-user1, we > want to refer `cluster` and `user` field in source to construct target. It's > impossible to archive this with current link type. Though we could set > one-to-one mapping, the mount table would become bloated if we have thousands > of users. Besides, a regex mapping would empower us more flexibility. So we > are going to build a regex based mount point which target could refer groups > from src regex mapping. -- 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-15907) Add missing maven modules in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677866#comment-16677866 ] Weiwei Yang commented on HADOOP-15907: -- I just committed this to trunk. I firstly pushed to branch-3.2 too but then realize hadoop-hdds/hadoop-ozone modules were not there, so reverted it from branch-3.2. Thanks for the contribution [~jiwq]. > Add missing maven modules in BUILDING.txt > - > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Fix For: 3.3.0 > > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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] [Updated] (HADOOP-15907) Add missing maven module in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated HADOOP-15907: - Summary: Add missing maven module in BUILDING.txt (was: Add YARN module to the main modules section in BUILDING.txt) > Add missing maven module in BUILDING.txt > > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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-15907) Add YARN module to the main modules section in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16677846#comment-16677846 ] Weiwei Yang commented on HADOOP-15907: -- LGTM, +1 > Add YARN module to the main modules section in BUILDING.txt > --- > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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] [Updated] (HADOOP-15907) Add missing maven modules in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated HADOOP-15907: - Summary: Add missing maven modules in BUILDING.txt (was: Add missing maven module in BUILDING.txt) > Add missing maven modules in BUILDING.txt > - > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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] [Updated] (HADOOP-15907) Add missing maven modules in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated HADOOP-15907: - Fix Version/s: (was: 3.2.1) > Add missing maven modules in BUILDING.txt > - > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Fix For: 3.3.0 > > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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] [Updated] (HADOOP-15907) Add missing maven modules in BUILDING.txt
[ https://issues.apache.org/jira/browse/HADOOP-15907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated HADOOP-15907: - Fix Version/s: 3.2.1 > Add missing maven modules in BUILDING.txt > - > > Key: HADOOP-15907 > URL: https://issues.apache.org/jira/browse/HADOOP-15907 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wanqiang Ji >Assignee: Wanqiang Ji >Priority: Trivial > Fix For: 3.3.0, 3.2.1 > > Attachments: HADOOP-15907.001.patch, HADOOP-15907.002.patch, > HADOOP-15907.003.patch > > > In the Maven main modules section, I found the missing main module YARN. -- 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
