[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=16762447#comment-16762447 ] Vinayakumar B commented on HADOOP-15602: [~daryn], Please can you take a look at the patch? > 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 (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-16032) Distcp It should clear sub directory ACL before applying new ACL on it.
[
https://issues.apache.org/jira/browse/HADOOP-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762423#comment-16762423
]
Hadoop QA commented on HADOOP-16032:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
22s{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} 18m
37s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
27s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
22s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
30s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
12m 19s{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
35s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
20s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
22s{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
24s{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 50s{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
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
18s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 13m
16s{color} | {color:green} hadoop-distcp in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
27s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 62m 42s{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-16032 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12957858/HADOOP-16032.003.patch
|
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient findbugs checkstyle |
| uname | Linux 19cb9b41a8c1 4.4.0-138-generic #164~14.04.1-Ubuntu SMP Fri Oct
5 08:56:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/patchprocess/precommit/personality/provided.sh |
| git revision | trunk / 7fa62e1 |
| maven | version: Apache Maven 3.3.9 |
| Default Java | 1.8.0_191 |
| findbugs | v3.1.0-RC1 |
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15892/testReport/ |
| Max. process+thread count | 306 (vs. ulimit of 1) |
| modules | C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/15892/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Distcp It should clear sub directory ACL before applying new ACL on it.
> ---
>
>
[jira] [Commented] (HADOOP-16032) Distcp It should clear sub directory ACL before applying new ACL on it.
[ https://issues.apache.org/jira/browse/HADOOP-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762426#comment-16762426 ] Ranith Sardar commented on HADOOP-16032: Uploaded patch with said changes. Please review the patch. > Distcp It should clear sub directory ACL before applying new ACL on it. > --- > > Key: HADOOP-16032 > URL: https://issues.apache.org/jira/browse/HADOOP-16032 > Project: Hadoop Common > Issue Type: Bug > Components: tools/distcp >Affects Versions: 3.1.1 >Reporter: Ranith Sardar >Assignee: Ranith Sardar >Priority: Major > Attachments: HADOOP-16032.000.patch, HADOOP-16032.001.patch, > HADOOP-16032.002.patch, HADOOP-16032.003.patch > > > Distcp preserve can't update the ACL info properly when source dir has access > ACL and dest dir has default ACL. It will only modify the basic ACL part. -- 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-16032) Distcp It should clear sub directory ACL before applying new ACL on it.
[ https://issues.apache.org/jira/browse/HADOOP-16032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ranith Sardar updated HADOOP-16032: --- Attachment: HADOOP-16032.003.patch > Distcp It should clear sub directory ACL before applying new ACL on it. > --- > > Key: HADOOP-16032 > URL: https://issues.apache.org/jira/browse/HADOOP-16032 > Project: Hadoop Common > Issue Type: Bug > Components: tools/distcp >Affects Versions: 3.1.1 >Reporter: Ranith Sardar >Assignee: Ranith Sardar >Priority: Major > Attachments: HADOOP-16032.000.patch, HADOOP-16032.001.patch, > HADOOP-16032.002.patch, HADOOP-16032.003.patch > > > Distcp preserve can't update the ACL info properly when source dir has access > ACL and dest dir has default ACL. It will only modify the basic ACL part. -- 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-16077) Add an option in ls command to include storage policy
[
https://issues.apache.org/jira/browse/HADOOP-16077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762384#comment-16762384
]
Surendra Singh Lilhore commented on HADOOP-16077:
-
{quote}If everyone is happy with this failing
{quote}
I amOK for this.
> Add an option in ls command to include storage policy
> -
>
> Key: HADOOP-16077
> URL: https://issues.apache.org/jira/browse/HADOOP-16077
> Project: Hadoop Common
> Issue Type: Improvement
> Components: common
>Affects Versions: 3.3.0
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HADOOP-16077-01.patch, HADOOP-16077-02.patch,
> HADOOP-16077-03.patch, HADOOP-16077-04.patch, HADOOP-16077-05.patch,
> HADOOP-16077-06.patch, HADOOP-16077-07.patch
>
>
--
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-16077) Add an option in ls command to include storage policy
[
https://issues.apache.org/jira/browse/HADOOP-16077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762384#comment-16762384
]
Surendra Singh Lilhore edited comment on HADOOP-16077 at 2/7/19 5:33 AM:
-
{quote}If everyone is happy with this failing
{quote}
I am OK for this.
was (Author: surendrasingh):
{quote}If everyone is happy with this failing
{quote}
I amOK for this.
> Add an option in ls command to include storage policy
> -
>
> Key: HADOOP-16077
> URL: https://issues.apache.org/jira/browse/HADOOP-16077
> Project: Hadoop Common
> Issue Type: Improvement
> Components: common
>Affects Versions: 3.3.0
>Reporter: Ayush Saxena
>Assignee: Ayush Saxena
>Priority: Major
> Attachments: HADOOP-16077-01.patch, HADOOP-16077-02.patch,
> HADOOP-16077-03.patch, HADOOP-16077-04.patch, HADOOP-16077-05.patch,
> HADOOP-16077-06.patch, HADOOP-16077-07.patch
>
>
--
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-15954) ABFS: Enable owner and group conversion for MSI and login user using OAuth
[ https://issues.apache.org/jira/browse/HADOOP-15954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762381#comment-16762381 ] Surendra Singh Lilhore commented on HADOOP-15954: - Hi [~ste...@apache.org], I think you merged HADOOP-16077 with this jira. Pls check [commit|https://github.com/apache/hadoop/commit/fa8cd1bf28f5b81849ba351a2d7225fbc580350d#diff-a9b959cf40730e23c0438952fb843d2f]. > ABFS: Enable owner and group conversion for MSI and login user using OAuth > -- > > Key: HADOOP-15954 > URL: https://issues.apache.org/jira/browse/HADOOP-15954 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Affects Versions: 3.2.0 >Reporter: junhua gu >Assignee: Da Zhou >Priority: Major > Fix For: 3.3.0 > > Attachments: HADOOP-15954-001.patch, HADOOP-15954-002.patch, > HADOOP-15954-003.patch, HADOOP-15954-004.patch, HADOOP-15954-005.patch, > HADOOP-15954-006.patch, HADOOP-15954-007.patch, HADOOP-15954-008.patch, > HADOOP-15954-009.patch, HADOOP-15954-010.patch, HADOOP-15954-011.patch, > HADOOP-15954-012.patch, HADOOP-15954-013.patch > > > Add support for overwriting owner and group in set/get operations to be the > service principal id when OAuth is used. Add support for upn short name > format. > > Add Standard Transformer for SharedKey / Service > Add interface provides an extensible model for customizing the acquisition of > Identity Transformer. -- 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-16073) Use JDK1.7 StandardCharsets
[
https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762345#comment-16762345
]
BELUGA BEHR edited comment on HADOOP-16073 at 2/7/19 4:22 AM:
--
Or, if you would like some examples of using it beyond consistency:
{code:java}
-secret = sb.toString().getBytes(Charset.forName("UTF-8"));
+secret = sb.toString().getBytes(StandardCharsets.UTF_8);
{code}
In these situations, Java does not have to load the UTF-8 Charset every call,
it can simply use the one that is already defined. Better performance.
{code:java}
- try {
-return new String(bb.array(), bb.arrayOffset() + bb.position(),
-bb.remaining(), "UTF-8");
- } catch (UnsupportedEncodingException e) {
-throw new IllegalCharsetNameException("UTF-8"); // won't happen.
- }
+ return new String(bb.array(), bb.arrayOffset() + bb.position(),
+ bb.remaining(), StandardCharsets.UTF_8);
{code}
Since the JDK is required to provide this implementation, there is no need to
catch "no such character set" exceptions. Leaner and quicker code. And as you
can see, the coder here know that this "won't happen" yet it needs to be coded
for and overhead on try/catch.
was (Author: belugabehr):
Or, if you would like some examples of using it beyond consistency:
{code:java}
-secret = sb.toString().getBytes(Charset.forName("UTF-8"));
+secret = sb.toString().getBytes(StandardCharsets.UTF_8);
{code}
In these situations, Java does not have to load the UTF-8 Charset every call,
it can simply use the one that is already defined. Better performance.
{code:java}
- try {
-return new String(bb.array(), bb.arrayOffset() + bb.position(),
-bb.remaining(), "UTF-8");
- } catch (UnsupportedEncodingException e) {
-throw new IllegalCharsetNameException("UTF-8"); // won't happen.
- }
+ return new String(bb.array(), bb.arrayOffset() + bb.position(),
+ bb.remaining(), StandardCharsets.UTF_8);
{code}
Since the JDK is required to provide this implementation, there is no need to
catch "no such character set" exceptions. Leaner and quicker code.
> Use JDK1.7 StandardCharsets
> ---
>
> Key: HADOOP-16073
> URL: https://issues.apache.org/jira/browse/HADOOP-16073
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Major
> Attachments: HADOOP-16073.1.patch
>
>
> Use Java 1.7
> [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html].
> Every JDK must now include support for several common charsets.
--
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-16073) Use JDK1.7 StandardCharsets
[
https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762346#comment-16762346
]
BELUGA BEHR commented on HADOOP-16073:
--
[~elgoiri] Ha! Yes! As soon as I typed up that follow-up comment, I realized
what you meant. I was just about to correct myself. You are correct. I was
thinking you were talking about:
{code:java}
import com.google.common.base.Charsets;
{code}
It provides a similar capability to {{StandardCharsets}}
> Use JDK1.7 StandardCharsets
> ---
>
> Key: HADOOP-16073
> URL: https://issues.apache.org/jira/browse/HADOOP-16073
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Major
> Attachments: HADOOP-16073.1.patch
>
>
> Use Java 1.7
> [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html].
> Every JDK must now include support for several common charsets.
--
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-16073) Use JDK1.7 StandardCharsets
[
https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762345#comment-16762345
]
BELUGA BEHR edited comment on HADOOP-16073 at 2/7/19 4:19 AM:
--
Or, if you would like some examples of using it beyond consistency:
{code:java}
-secret = sb.toString().getBytes(Charset.forName("UTF-8"));
+secret = sb.toString().getBytes(StandardCharsets.UTF_8);
{code}
In these situations, Java does not have to load the UTF-8 Charset every call,
it can simply use the one that is already defined. Better performance.
{code:java}
- try {
-return new String(bb.array(), bb.arrayOffset() + bb.position(),
-bb.remaining(), "UTF-8");
- } catch (UnsupportedEncodingException e) {
-throw new IllegalCharsetNameException("UTF-8"); // won't happen.
- }
+ return new String(bb.array(), bb.arrayOffset() + bb.position(),
+ bb.remaining(), StandardCharsets.UTF_8);
{code}
Since the JDK is required to provide this implementation, there is no need to
catch "no such character set" exceptions. Leaner and quicker code.
was (Author: belugabehr):
Or, if you would like some examples of using it beyond consistency:
{code:java}
-secret = sb.toString().getBytes(Charset.forName("UTF-8"));
+secret = sb.toString().getBytes(StandardCharsets.UTF_8);
{code}
In these situations, Java does not have to load the UTF-8 Charset every call,
it can simply use the one that is already defined.
{code:java}
- try {
-return new String(bb.array(), bb.arrayOffset() + bb.position(),
-bb.remaining(), "UTF-8");
- } catch (UnsupportedEncodingException e) {
-throw new IllegalCharsetNameException("UTF-8"); // won't happen.
- }
+ return new String(bb.array(), bb.arrayOffset() + bb.position(),
+ bb.remaining(), StandardCharsets.UTF_8);
{code}
Since the JDK is required to provide this implementation, there is no need to
catch "no such character set" exceptions. Leaner and quicker code.
> Use JDK1.7 StandardCharsets
> ---
>
> Key: HADOOP-16073
> URL: https://issues.apache.org/jira/browse/HADOOP-16073
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Major
> Attachments: HADOOP-16073.1.patch
>
>
> Use Java 1.7
> [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html].
> Every JDK must now include support for several common charsets.
--
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-16073) Use JDK1.7 StandardCharsets
[
https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762344#comment-16762344
]
Íñigo Goiri commented on HADOOP-16073:
--
{code}
import java.nio.charset.Charset;
{code}
Is this in guava?
> Use JDK1.7 StandardCharsets
> ---
>
> Key: HADOOP-16073
> URL: https://issues.apache.org/jira/browse/HADOOP-16073
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Major
> Attachments: HADOOP-16073.1.patch
>
>
> Use Java 1.7
> [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html].
> Every JDK must now include support for several common charsets.
--
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-16073) Use JDK1.7 StandardCharsets
[
https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762345#comment-16762345
]
BELUGA BEHR commented on HADOOP-16073:
--
Or, if you would like some examples of using it beyond consistency:
{code:java}
-secret = sb.toString().getBytes(Charset.forName("UTF-8"));
+secret = sb.toString().getBytes(StandardCharsets.UTF_8);
{code}
In these situations, Java does not have to load the UTF-8 Charset every call,
it can simply use the one that is already defined.
{code:java}
- try {
-return new String(bb.array(), bb.arrayOffset() + bb.position(),
-bb.remaining(), "UTF-8");
- } catch (UnsupportedEncodingException e) {
-throw new IllegalCharsetNameException("UTF-8"); // won't happen.
- }
+ return new String(bb.array(), bb.arrayOffset() + bb.position(),
+ bb.remaining(), StandardCharsets.UTF_8);
{code}
Since the JDK is required to provide this implementation, there is no need to
catch "no such character set" exceptions. Leaner and quicker code.
> Use JDK1.7 StandardCharsets
> ---
>
> Key: HADOOP-16073
> URL: https://issues.apache.org/jira/browse/HADOOP-16073
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Major
> Attachments: HADOOP-16073.1.patch
>
>
> Use Java 1.7
> [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html].
> Every JDK must now include support for several common charsets.
--
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-16073) Use JDK1.7 StandardCharsets
[
https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762339#comment-16762339
]
BELUGA BEHR edited comment on HADOOP-16073 at 2/7/19 4:08 AM:
--
[~elgoiri]
With all due respect, there is no such thing as "regular {{Charset}}". There
is a {{Charset}} class offered by Google's Guava library that existed to fill
this shortcoming of the JDK. However, now that the JDK includes this
{{StandardCharsets}} class, we should be using it consistently across the
project. One could see a situation where the 3rd party library deprecates and
removes this because the JDK has usurped it. Moving everything over would
isolate Hadoop from this and also encourage folks to use the JDK version moving
forward if that's all they see in the code base. There's also a minuscule
memory footprint savings only having to use one instance of the UTF-8
{{Charset}}.
https://google.github.io/guava/releases/19.0/api/docs/com/google/common/base/Charsets.html
was (Author: belugabehr):
[~elgoiri]
With all due respect, there is no such thing as "regular {{Charset}}". There
is a {{Charset}} class offered by Google's Guava library that existed to fill
this shortcoming of the JDK. However, now that the JDK includes this
{{StandardCharsets}} class, we should be using it consistently across the
project. One could see a situation where the 3rd party library deprecates and
removes this because the JDK has usurped it. Moving everything over would
isolate Hadoop from this and also encourage folks to use the JDK version moving
forward if that's all they see in the code base. There's also a minuscule
memory footprint savings only having to use one instance of the UTF-8
{{Charset}}.
> Use JDK1.7 StandardCharsets
> ---
>
> Key: HADOOP-16073
> URL: https://issues.apache.org/jira/browse/HADOOP-16073
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Major
> Attachments: HADOOP-16073.1.patch
>
>
> Use Java 1.7
> [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html].
> Every JDK must now include support for several common charsets.
--
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-16073) Use JDK1.7 StandardCharsets
[
https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762339#comment-16762339
]
BELUGA BEHR commented on HADOOP-16073:
--
[~elgoiri]
With all due respect, there is no such thing as "regular {{Charset}}". There
is a {{Charset}} class offered by Google's Guava library that existed to fill
this shortcoming of the JDK. However, now that the JDK includes this
{{StandardCharsets}} class, we should be using it consistently across the
project. One could see a situation where the 3rd party library deprecates and
removes this because the JDK has usurped it. Moving everything over would
isolate Hadoop from this and also encourage folks to use the JDK version moving
forward if that's all they see in the code base. There's also a minuscule
memory footprint savings only having to use one instance of the UTF-8
{{Charset}}.
> Use JDK1.7 StandardCharsets
> ---
>
> Key: HADOOP-16073
> URL: https://issues.apache.org/jira/browse/HADOOP-16073
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.0
>Reporter: BELUGA BEHR
>Assignee: BELUGA BEHR
>Priority: Major
> Attachments: HADOOP-16073.1.patch
>
>
> Use Java 1.7
> [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html].
> Every JDK must now include support for several common charsets.
--
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-16090) deleteUnnecessaryFakeDirectories() creates unnecessary delete markers in a versioned S3 bucket
[ https://issues.apache.org/jira/browse/HADOOP-16090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762281#comment-16762281 ] Dmitri Chmelev commented on HADOOP-16090: - Ok, sounds good. I'll send the patch that performs HEAD checks on upwalks during cleanup for versioned buckets. The rest of the fix that requires operation context can go into 3.x, since we ran into the problem while using Flink 1.6.2 and are thinking of upgrading Flink, and the last time I checked Flink 1.7.1 already uses Hadoop 3.1.0. > deleteUnnecessaryFakeDirectories() creates unnecessary delete markers in a > versioned S3 bucket > -- > > Key: HADOOP-16090 > URL: https://issues.apache.org/jira/browse/HADOOP-16090 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 >Affects Versions: 2.8.1 >Reporter: Dmitri Chmelev >Priority: Minor > > The fix to avoid calls to getFileStatus() for each path component in > deleteUnnecessaryFakeDirectories() (HADOOP-13164) results in accumulation of > delete markers in versioned S3 buckets. The above patch replaced > getFileStatus() checks with a single batch delete request formed by > generating all ancestor keys formed from a given path. Since the delete > request is not checking for existence of fake directories, it will create a > delete marker for every path component that did not exist (or was previously > deleted). Note that issuing a DELETE request without specifying a version ID > will always create a new delete marker, even if one already exists ([AWS S3 > Developer > Guide|https://docs.aws.amazon.com/AmazonS3/latest/dev/RemDelMarker.html]) > Since deleteUnnecessaryFakeDirectories() is called as a callback on > successful writes and on renames, delete markers accumulate rather quickly > and their rate of accumulation is inversely proportional to the depth of the > path. In other words, directories closer to the root will have more delete > markers than the leaves. > This behavior negatively impacts performance of getFileStatus() operation > when it has to issue listObjects() request (especially v1) as the delete > markers have to be examined when the request searches for first current > non-deleted version of an object following a given prefix. > I did a quick comparison against 3.x and the issue is still present: > [https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java#L2947|https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java#L2947] > -- 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-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762230#comment-16762230 ] Íñigo Goiri commented on HADOOP-16073: -- I think the GitHub setup is still in progress. I'm not sure we should do the whole Hadoop in one shot; a little risky to run the unit tests for everything. Is there any particular advantage using StandardCharsets instead of regular Charset? > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Assignee: BELUGA BEHR >Priority: Major > Attachments: HADOOP-16073.1.patch > > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BELUGA BEHR updated HADOOP-16073: - Attachment: HADOOP-16073.1.patch > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement > Components: streaming, tools >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Assignee: BELUGA BEHR >Priority: Major > Attachments: HADOOP-16073.1.patch > > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BELUGA BEHR updated HADOOP-16073: - Status: Patch Available (was: Open) > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement > Components: streaming, tools >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Assignee: BELUGA BEHR >Priority: Major > Attachments: HADOOP-16073.1.patch > > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BELUGA BEHR updated HADOOP-16073: - Component/s: (was: tools) (was: streaming) > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Assignee: BELUGA BEHR >Priority: Major > Attachments: HADOOP-16073.1.patch > > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BELUGA BEHR updated HADOOP-16073: - Status: Open (was: Patch Available) > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement > Components: streaming, tools >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Assignee: BELUGA BEHR >Priority: Major > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-16095) Support impersonation for AuthenticationFilter
[
https://issues.apache.org/jira/browse/HADOOP-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762209#comment-16762209
]
Eric Yang commented on HADOOP-16095:
The reason for this proposal is the existing doas query parameter is written as
part of hdfs logic instead of being part of security filter.
{code:java}
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/web/resources/DoAsParam.java:
public static final String NAME = "doas";
hadoop-hdfs-project/hadoop-hdfs-httpfs/src/main/java/org/apache/hadoop/fs/http/client/HttpFSFileSystem.java:
public static final String DO_AS_PARAM = "doas";{code}
It would be good if this is generalized to be reusable by YARN and Ozone.
> Support impersonation for AuthenticationFilter
> --
>
> Key: HADOOP-16095
> URL: https://issues.apache.org/jira/browse/HADOOP-16095
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
>Reporter: Eric Yang
>Assignee: Eric Yang
>Priority: Major
>
> External services or YARN service may need to call into WebHDFS or YARN REST
> API on behave of the user using web protocols. It would be good to support
> impersonation mechanism in AuthenticationFilter or similar extensions. The
> general design is similar to UserGroupInformation.doAs in RPC layer.
> The calling service credential is verified as a proxy user coming from a
> trusted host verifying Hadoop proxy user ACL on the server side. If proxy
> user ACL allows proxy user to become doAs user. HttpRequest object will
> report REMOTE_USER as doAs user. This feature enables web application logic
> to be written with minimal changes to call Hadoop API with
> UserGroupInformation.doAs() wrapper.
> h2. HTTP Request
> A few possible options:
> 1. Using query parameter to pass doAs user:
> {code:java}
> POST /service?doAs=foobar
> Authorization: [proxy user Kerberos token]
> {code}
> 2. Use HTTP Header to pass doAs user:
> {code:java}
> POST /service
> Authorization: [proxy user Kerberos token]
> x-hadoop-doas: foobar
> {code}
> h2. HTTP Response
> 403 - Forbidden (Including impersonation is not allowed)
> h2. Proxy User ACL requirement
> Proxy user kerberos token maps to a service principal, such as
> yarn/host1.example.com. The host part of the credential and HTTP request
> origin are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user
> group membership or identity is checked with either
> *hadoop.proxyuser.yarn.groups* or *hadoop.proxyuser.yarn.users*. This governs
> the caller is coming from authorized host and belong to authorized group.
--
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] [Assigned] (HADOOP-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BELUGA BEHR reassigned HADOOP-16073: Assignee: BELUGA BEHR > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement > Components: streaming, tools >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Assignee: BELUGA BEHR >Priority: Major > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762207#comment-16762207 ] BELUGA BEHR commented on HADOOP-16073: -- [~goiri] [~giovanni.fumarola] Either of you gents able to take a look at this? > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement > Components: streaming, tools >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Assignee: BELUGA BEHR >Priority: Major > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-15281) Distcp to add no-rename copy option
[
https://issues.apache.org/jira/browse/HADOOP-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762035#comment-16762035
]
Andrew Olson commented on HADOOP-15281:
---
[~ste...@apache.org] Please use 'andrew.ol...@cerner.com'
> Distcp to add no-rename copy option
> ---
>
> Key: HADOOP-15281
> URL: https://issues.apache.org/jira/browse/HADOOP-15281
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.0.0
>Reporter: Steve Loughran
>Assignee: Andrew Olson
>Priority: Major
> Attachments: HADOOP-15281-001.patch, HADOOP-15281-002.patch,
> HADOOP-15281-003.patch, HADOOP-15281-004.patch
>
>
> Currently Distcp uploads a file by two strategies
> # append parts
> # copy to temp then rename
> option 2 executes the following sequence in {{promoteTmpToTarget}}
> {code}
> if ((fs.exists(target) && !fs.delete(target, false))
> || (!fs.exists(target.getParent()) && !fs.mkdirs(target.getParent()))
> || !fs.rename(tmpTarget, target)) {
> throw new IOException("Failed to promote tmp-file:" + tmpTarget
> + " to: " + target);
> }
> {code}
> For any object store, that's a lot of HTTP requests; for S3A you are looking
> at 12+ requests and an O(data) copy call.
> This is not a good upload strategy for any store which manifests its output
> atomically at the end of the write().
> Proposed: add a switch to write directly to the dest path, which can be
> supplied as either a conf option (distcp.direct.write) or a CLI option
> (-direct).
--
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
[GitHub] BELUGABEHR opened a new pull request #480: HDFS-14258: Introduce Java Concurrent Package To DataXceiverServer Class
BELUGABEHR opened a new pull request #480: HDFS-14258: Introduce Java Concurrent Package To DataXceiverServer Class URL: https://github.com/apache/hadoop/pull/480 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16095) Support impersonation for AuthenticationFilter
[
https://issues.apache.org/jira/browse/HADOOP-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated HADOOP-16095:
---
Description:
External services or YARN service may need to call into WebHDFS or YARN REST
API on behave of the user using web protocols. It would be good to support
impersonation mechanism in AuthenticationFilter or similar extensions. The
general design is similar to UserGroupInformation.doAs in RPC layer.
The calling service credential is verified as a proxy user coming from a
trusted host verifying Hadoop proxy user ACL on the server side. If proxy user
ACL allows proxy user to become doAs user. HttpRequest object will report
REMOTE_USER as doAs user. This feature enables web application logic to be
written with minimal changes to call Hadoop API with
UserGroupInformation.doAs() wrapper.
h2. HTTP Request
A few possible options:
1. Using query parameter to pass doAs user:
{code:java}
POST /service?doAs=foobar
Authorization: [proxy user Kerberos token]
{code}
2. Use HTTP Header to pass doAs user:
{code:java}
POST /service
Authorization: [proxy user Kerberos token]
x-hadoop-doas: foobar
{code}
h2. HTTP Response
403 - Forbidden (Including impersonation is not allowed)
h2. Proxy User ACL requirement
Proxy user kerberos token maps to a service principal, such as
yarn/host1.example.com. The host part of the credential and HTTP request origin
are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user group
membership or identity is checked with either *hadoop.proxyuser.yarn.groups* or
*hadoop.proxyuser.yarn.users*. This governs the caller is coming from
authorized host and belong to authorized group.
was:
External services or YARN service may need to call into WebHDFS or YARN REST
API on behave of the user using web protocols. It would be good to support
impersonation mechanism in AuthenticationFilter or similar extensions. The
general design is similar to UserGroupInformation.doAs in RPC layer.
The calling service credential is verified as a proxy user coming from a
trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
This feature enables web application logic to be written with minimal changes
to call Hadoop API with UserGroupInformation.doAs() wrapper.
h2. HTTP Request
A few possible options:
1. Using query parameter to pass doAs user:
{code:java}
POST /service?doAs=foobar
Authorization: [proxy user Kerberos token]
{code}
2. Use HTTP Header to pass doAs user:
{code:java}
POST /service
Authorization: [proxy user Kerberos token]
x-hadoop-doas: foobar
{code}
h2. HTTP Response
403 - Forbidden (Including impersonation is not allowed)
h2. Proxy User ACL requirement
Proxy user kerberos token maps to a service principal, such as
yarn/host1.example.com. The host part of the credential and HTTP request origin
are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user group
membership or identity is checked with either *hadoop.proxyuser.yarn.groups* or
*hadoop.proxyuser.yarn.users*. This governs the caller is coming from
authorized host and belong to authorized group.
> Support impersonation for AuthenticationFilter
> --
>
> Key: HADOOP-16095
> URL: https://issues.apache.org/jira/browse/HADOOP-16095
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
>Reporter: Eric Yang
>Assignee: Eric Yang
>Priority: Major
>
> External services or YARN service may need to call into WebHDFS or YARN REST
> API on behave of the user using web protocols. It would be good to support
> impersonation mechanism in AuthenticationFilter or similar extensions. The
> general design is similar to UserGroupInformation.doAs in RPC layer.
> The calling service credential is verified as a proxy user coming from a
> trusted host verifying Hadoop proxy user ACL on the server side. If proxy
> user ACL allows proxy user to become doAs user. HttpRequest object will
> report REMOTE_USER as doAs user. This feature enables web application logic
> to be written with minimal changes to call Hadoop API with
> UserGroupInformation.doAs() wrapper.
> h2. HTTP Request
> A few possible options:
> 1. Using query parameter to pass doAs user:
> {code:java}
> POST /service?doAs=foobar
> Authorization: [proxy user Kerberos token]
> {code}
> 2. Use HTTP Header to pass doAs user:
> {code:java}
> POST /service
> Authorization: [proxy user Kerberos token]
> x-hadoop-doas: foobar
> {code}
> h2. HTTP Response
> 403 - Forbidden (Including impersonation is not allowed)
> h2. Proxy User ACL requirement
> Proxy user kerberos token maps to a service principal, such as
> yarn/host1.example.com. The host part of the credential and HTTP request
> origin are
[jira] [Updated] (HADOOP-16095) Support impersonation for AuthenticationFilter
[
https://issues.apache.org/jira/browse/HADOOP-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated HADOOP-16095:
---
Description:
External services or YARN service may need to call into WebHDFS or YARN REST
API on behave of the user using web protocols. It would be good to support
impersonation mechanism in AuthenticationFilter or similar extensions. The
general design is similar to UserGroupInformation.doAs in RPC layer.
The calling service credential is verified as a proxy user coming from a
trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
This feature enables web application logic to be written with minimal changes
to call Hadoop API with UserGroupInformation.doAs() wrapper.
h2. HTTP Request
A few possible options:
1. Using query parameter to pass doAs user:
{code:java}
POST /service?doAs=foobar
Authorization: [proxy user Kerberos token]
{code}
2. Use HTTP Header to pass doAs user:
{code:java}
POST /service
Authorization: [proxy user Kerberos token]
x-hadoop-doas: foobar
{code}
h2. HTTP Response
403 - Forbidden (Including impersonation is not allowed)
h2. Proxy User ACL requirement
Proxy user kerberos token maps to a service principal, such as
yarn/host1.example.com. The host part of the credential and HTTP request origin
are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user group
membership or identity is checked with either *hadoop.proxyuser.yarn.groups* or
*hadoop.proxyuser.yarn.users*. This governs the caller is coming from
authorized host and belong to authorized group.
was:
External services or YARN service may need to call into WebHDFS or YARN REST
API on behave of the user using web protocols. It would be good to support
impersonation mechanism in AuthenticationFilter or similar extensions. The
general design is similar to UserGroupInformation.doAs in RPC layer.
The calling service credential is verified as a proxy user coming from a
trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
This feature enables web application logic to be written with minimal changes
to call Hadoop API with UserGroupInformation wrapper.
h2. HTTP Request
A few possible options:
1. Using query parameter to pass doAs user:
{code:java}
POST /service?doAs=foobar
Authorization: [proxy user Kerberos token]
{code}
2. Use HTTP Header to pass doAs user:
{code:java}
POST /service
Authorization: [proxy user Kerberos token]
x-hadoop-doas: foobar
{code}
h2. HTTP Response
403 - Forbidden (Including impersonation is not allowed)
h2. Proxy User ACL requirement
Proxy user kerberos token maps to a service principal, such as
yarn/host1.example.com. The host part of the credential and HTTP request origin
are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user group
membership or identity is checked with either *hadoop.proxyuser.yarn.groups* or
*hadoop.proxyuser.yarn.users*. This governs the caller is coming from
authorized host and belong to authorized group.
> Support impersonation for AuthenticationFilter
> --
>
> Key: HADOOP-16095
> URL: https://issues.apache.org/jira/browse/HADOOP-16095
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
>Reporter: Eric Yang
>Assignee: Eric Yang
>Priority: Major
>
> External services or YARN service may need to call into WebHDFS or YARN REST
> API on behave of the user using web protocols. It would be good to support
> impersonation mechanism in AuthenticationFilter or similar extensions. The
> general design is similar to UserGroupInformation.doAs in RPC layer.
> The calling service credential is verified as a proxy user coming from a
> trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
> to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
> This feature enables web application logic to be written with minimal changes
> to call Hadoop API with UserGroupInformation.doAs() wrapper.
> h2. HTTP Request
> A few possible options:
> 1. Using query parameter to pass doAs user:
> {code:java}
> POST /service?doAs=foobar
> Authorization: [proxy user Kerberos token]
> {code}
> 2. Use HTTP Header to pass doAs user:
> {code:java}
> POST /service
> Authorization: [proxy user Kerberos token]
> x-hadoop-doas: foobar
> {code}
> h2. HTTP Response
> 403 - Forbidden (Including impersonation is not allowed)
> h2. Proxy User ACL requirement
> Proxy user kerberos token maps to a service principal, such as
> yarn/host1.example.com. The host part of the credential and HTTP request
> origin are both validated with *hadoop.proxyuser.yarn.hosts* ACL.
[jira] [Updated] (HADOOP-16095) Support impersonation for AuthenticationFilter
[
https://issues.apache.org/jira/browse/HADOOP-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated HADOOP-16095:
---
Description:
External services or YARN service may need to call into WebHDFS or YARN REST
API on behave of the user using web protocols. It would be good to support
impersonation mechanism in AuthenticationFilter or similar extensions. The
general design is similar to UserGroupInformation.doAs in RPC layer.
The calling service credential is verified as a proxy user coming from a
trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
This feature enables web application logic to be written with minimal changes
to call Hadoop API with UserGroupInformation wrapper.
h2. HTTP Request
A few possible options:
1. Using query parameter to pass doAs user:
{code:java}
POST /service?doAs=foobar
Authorization: [proxy user Kerberos token]
{code}
2. Use HTTP Header to pass doAs user:
{code:java}
POST /service
Authorization: [proxy user Kerberos token]
x-hadoop-doas: foobar
{code}
h2. HTTP Response
403 - Forbidden (Including impersonation is not allowed)
h2. Proxy User ACL requirement
Proxy user kerberos token maps to a service principal, such as
yarn/host1.example.com. The host part of the credential and HTTP request origin
are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user group
membership or identity is checked with either *hadoop.proxyuser.yarn.groups* or
*hadoop.proxyuser.yarn.users*. This governs the caller is coming from
authorized host and belong to authorized group.
was:
External services or YARN service may need to call into WebHDFS or YARN REST
API on behave of the user using web protocols. It would be good to support
impersonation mechanism in AuthenticationFilter or similar extensions. The
general design is similar to UserGroupInformation.doAs in RPC layer.
The calling service credential is verified as a proxy user coming from a
trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
This feature enables web application logic to be written with minimal changes
to call Hadoop API with UserGroupInformation wrapper.
h2. Http Request
A few possible options:
1. Using query parameter to pass doAs user:
{code}
POST /service?doAs=foobar
Authorization: [proxy user Kerberos token]
{code}
2. Use HTTP Header to pass doAs user:
{code}
POST /service
Authorization: [proxy user Kerberos token]
x-hadoop-doas: foobar
{code}
h2. Response
403 - Forbidden (Including impersonation is not allowed)
h2. Proxy User ACL requirement
Proxy user kerberos token maps to a service principal, such as
yarn/host1.example.com. The host part of the credential and HTTP request
origin are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user
group membership or identity is checked with either
*hadoop.proxyuser.yarn.groups* or *hadoop.proxyuser.yarn.users*. This governs
the caller is coming from authorized host and belong to authorized group.
> Support impersonation for AuthenticationFilter
> --
>
> Key: HADOOP-16095
> URL: https://issues.apache.org/jira/browse/HADOOP-16095
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
>Reporter: Eric Yang
>Assignee: Eric Yang
>Priority: Major
>
> External services or YARN service may need to call into WebHDFS or YARN REST
> API on behave of the user using web protocols. It would be good to support
> impersonation mechanism in AuthenticationFilter or similar extensions. The
> general design is similar to UserGroupInformation.doAs in RPC layer.
> The calling service credential is verified as a proxy user coming from a
> trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
> to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
> This feature enables web application logic to be written with minimal changes
> to call Hadoop API with UserGroupInformation wrapper.
> h2. HTTP Request
> A few possible options:
> 1. Using query parameter to pass doAs user:
> {code:java}
> POST /service?doAs=foobar
> Authorization: [proxy user Kerberos token]
> {code}
> 2. Use HTTP Header to pass doAs user:
> {code:java}
> POST /service
> Authorization: [proxy user Kerberos token]
> x-hadoop-doas: foobar
> {code}
> h2. HTTP Response
> 403 - Forbidden (Including impersonation is not allowed)
> h2. Proxy User ACL requirement
> Proxy user kerberos token maps to a service principal, such as
> yarn/host1.example.com. The host part of the credential and HTTP request
> origin are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user
>
[jira] [Commented] (HADOOP-15281) Distcp to add no-rename copy option
[
https://issues.apache.org/jira/browse/HADOOP-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16762025#comment-16762025
]
Steve Loughran commented on HADOOP-15281:
-
LGTM: tested the s3a and ABFS distcp.
+1
Before I commit this: What email address can I use for the --author tag? I want
to make sure github gives you credit for your work, and git blame finds both of
us when it doesnt
> Distcp to add no-rename copy option
> ---
>
> Key: HADOOP-15281
> URL: https://issues.apache.org/jira/browse/HADOOP-15281
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.0.0
>Reporter: Steve Loughran
>Assignee: Andrew Olson
>Priority: Major
> Attachments: HADOOP-15281-001.patch, HADOOP-15281-002.patch,
> HADOOP-15281-003.patch, HADOOP-15281-004.patch
>
>
> Currently Distcp uploads a file by two strategies
> # append parts
> # copy to temp then rename
> option 2 executes the following sequence in {{promoteTmpToTarget}}
> {code}
> if ((fs.exists(target) && !fs.delete(target, false))
> || (!fs.exists(target.getParent()) && !fs.mkdirs(target.getParent()))
> || !fs.rename(tmpTarget, target)) {
> throw new IOException("Failed to promote tmp-file:" + tmpTarget
> + " to: " + target);
> }
> {code}
> For any object store, that's a lot of HTTP requests; for S3A you are looking
> at 12+ requests and an O(data) copy call.
> This is not a good upload strategy for any store which manifests its output
> atomically at the end of the write().
> Proposed: add a switch to write directly to the dest path, which can be
> supplied as either a conf option (distcp.direct.write) or a CLI option
> (-direct).
--
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] [Created] (HADOOP-16095) Support impersonation for AuthenticationFilter
Eric Yang created HADOOP-16095:
--
Summary: Support impersonation for AuthenticationFilter
Key: HADOOP-16095
URL: https://issues.apache.org/jira/browse/HADOOP-16095
Project: Hadoop Common
Issue Type: New Feature
Components: security
Reporter: Eric Yang
Assignee: Eric Yang
External services or YARN service may need to call into WebHDFS or YARN REST
API on behave of the user using web protocols. It would be good to support
impersonation mechanism in AuthenticationFilter or similar extensions. The
general design is similar to UserGroupInformation.doAs in RPC layer.
The calling service credential is verified as a proxy user coming from a
trusted host using Hadoop proxy user ACL. If proxy user ACL allows proxy user
to become doAs user. HttpRequest object will report REMOTE_USER as doAs user.
This feature enables web application logic to be written with minimal changes
to call Hadoop API with UserGroupInformation wrapper.
h2. Http Request
A few possible options:
1. Using query parameter to pass doAs user:
{code}
POST /service?doAs=foobar
Authorization: [proxy user Kerberos token]
{code}
2. Use HTTP Header to pass doAs user:
{code}
POST /service
Authorization: [proxy user Kerberos token]
x-hadoop-doas: foobar
{code}
h2. Response
403 - Forbidden (Including impersonation is not allowed)
h2. Proxy User ACL requirement
Proxy user kerberos token maps to a service principal, such as
yarn/host1.example.com. The host part of the credential and HTTP request
origin are both validated with *hadoop.proxyuser.yarn.hosts* ACL. doAs user
group membership or identity is checked with either
*hadoop.proxyuser.yarn.groups* or *hadoop.proxyuser.yarn.users*. This governs
the caller is coming from authorized host and belong to authorized group.
--
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-11223) Offer a read-only conf alternative to new Configuration()
[
https://issues.apache.org/jira/browse/HADOOP-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761893#comment-16761893
]
Michael Miller commented on HADOOP-11223:
-
[~ste...@apache.org] can you assign this ticket to me? I have a patch but am
unable to attach it.
> Offer a read-only conf alternative to new Configuration()
> -
>
> Key: HADOOP-11223
> URL: https://issues.apache.org/jira/browse/HADOOP-11223
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
>Reporter: Gopal V
>Assignee: Varun Saxena
>Priority: Major
> Labels: Performance
> Attachments: HADOOP-11223.001.patch
>
>
> new Configuration() is called from several static blocks across Hadoop.
> This is incredibly inefficient, since each one of those involves primarily
> XML parsing at a point where the JIT won't be triggered & interpreter mode is
> essentially forced on the JVM.
> The alternate solution would be to offer a {{Configuration::getDefault()}}
> alternative which disallows any modifications.
> At the very least, such a method would need to be called from
> # org.apache.hadoop.io.nativeio.NativeIO::()
> # org.apache.hadoop.security.SecurityUtil::()
> # org.apache.hadoop.yarn.factory.providers.RecordFactoryProvider::
--
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-16073) Use JDK1.7 StandardCharsets
[ https://issues.apache.org/jira/browse/HADOOP-16073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761802#comment-16761802 ] BELUGA BEHR commented on HADOOP-16073: -- OK. I cleaned up my branch a little and rebased on the latest trunk. Please consider for inclusion into the project. Since this touches many files and has a high risk of conflicts with future changes, please review promptly. > Use JDK1.7 StandardCharsets > --- > > Key: HADOOP-16073 > URL: https://issues.apache.org/jira/browse/HADOOP-16073 > Project: Hadoop Common > Issue Type: Improvement > Components: streaming, tools >Affects Versions: 3.2.0 >Reporter: BELUGA BEHR >Priority: Major > > Use Java 1.7 > [StandardCharsets|https://docs.oracle.com/javase/7/docs/api/java/nio/charset/StandardCharsets.html]. > Every JDK must now include support for several common charsets. -- 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-16090) deleteUnnecessaryFakeDirectories() creates unnecessary delete markers in a versioned S3 bucket
[
https://issues.apache.org/jira/browse/HADOOP-16090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761739#comment-16761739
]
Steve Loughran commented on HADOOP-16090:
-
I've been thinking for a while about having an operation context follow those
long-lived ops, one which would get created when the write or read is kicked
off, and which follows it to the end. A number of reasons
# I've promised the flink team a low cost "don't check for existence or delete
parent dirs" option for higher performance IO: essentially a "we know what we
are doing just give us the PUT" operation, accessed by the new createFile()
builder.
# lets us pass down an htrace (successor) context which would then be added to
the UA header of each operation.
There's already an {{S3AReadOpContext}} for reading; a mirror for writing with
some base class for common state (context ID) would go all the way through the
work.
If the existence of the file and parent dir were added to the write context,
they'd know not to worry.
BTW, just been warned this really hurts distcp uploads. We do need to fix this,
though moving any of this stuff back to branch 2 is pretty unlikely, especially
once you get into passing a context around.
An initial patch from you for HEAD of all parent entries is not the lowest
cost, but the only one I could really imagine backporting
> deleteUnnecessaryFakeDirectories() creates unnecessary delete markers in a
> versioned S3 bucket
> --
>
> Key: HADOOP-16090
> URL: https://issues.apache.org/jira/browse/HADOOP-16090
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
>Affects Versions: 2.8.1
>Reporter: Dmitri Chmelev
>Priority: Minor
>
> The fix to avoid calls to getFileStatus() for each path component in
> deleteUnnecessaryFakeDirectories() (HADOOP-13164) results in accumulation of
> delete markers in versioned S3 buckets. The above patch replaced
> getFileStatus() checks with a single batch delete request formed by
> generating all ancestor keys formed from a given path. Since the delete
> request is not checking for existence of fake directories, it will create a
> delete marker for every path component that did not exist (or was previously
> deleted). Note that issuing a DELETE request without specifying a version ID
> will always create a new delete marker, even if one already exists ([AWS S3
> Developer
> Guide|https://docs.aws.amazon.com/AmazonS3/latest/dev/RemDelMarker.html])
> Since deleteUnnecessaryFakeDirectories() is called as a callback on
> successful writes and on renames, delete markers accumulate rather quickly
> and their rate of accumulation is inversely proportional to the depth of the
> path. In other words, directories closer to the root will have more delete
> markers than the leaves.
> This behavior negatively impacts performance of getFileStatus() operation
> when it has to issue listObjects() request (especially v1) as the delete
> markers have to be examined when the request searches for first current
> non-deleted version of an object following a given prefix.
> I did a quick comparison against 3.x and the issue is still present:
> [https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java#L2947|https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java#L2947]
>
--
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-15281) Distcp to add no-rename copy option
[
https://issues.apache.org/jira/browse/HADOOP-15281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761732#comment-16761732
]
Steve Loughran commented on HADOOP-15281:
-
LGTM. Running the s3 and abfs tests to make sure all is well; if they are it'll
get my vote
> Distcp to add no-rename copy option
> ---
>
> Key: HADOOP-15281
> URL: https://issues.apache.org/jira/browse/HADOOP-15281
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tools/distcp
>Affects Versions: 3.0.0
>Reporter: Steve Loughran
>Assignee: Andrew Olson
>Priority: Major
> Attachments: HADOOP-15281-001.patch, HADOOP-15281-002.patch,
> HADOOP-15281-003.patch, HADOOP-15281-004.patch
>
>
> Currently Distcp uploads a file by two strategies
> # append parts
> # copy to temp then rename
> option 2 executes the following sequence in {{promoteTmpToTarget}}
> {code}
> if ((fs.exists(target) && !fs.delete(target, false))
> || (!fs.exists(target.getParent()) && !fs.mkdirs(target.getParent()))
> || !fs.rename(tmpTarget, target)) {
> throw new IOException("Failed to promote tmp-file:" + tmpTarget
> + " to: " + target);
> }
> {code}
> For any object store, that's a lot of HTTP requests; for S3A you are looking
> at 12+ requests and an O(data) copy call.
> This is not a good upload strategy for any store which manifests its output
> atomically at the end of the write().
> Proposed: add a switch to write directly to the dest path, which can be
> supplied as either a conf option (distcp.direct.write) or a CLI option
> (-direct).
--
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
[GitHub] elek removed a comment on issue #458: YARN-8246 winutils - fix failure to retrieve disk and network perf co…
elek removed a comment on issue #458: YARN-8246 winutils - fix failure to retrieve disk and network perf co… URL: https://github.com/apache/hadoop/pull/458#issuecomment-453175556 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #454: Fixing bug : https://issues.apache.org/jira/browse/MAPREDUCE-7089
elek removed a comment on issue #454: Fixing bug : https://issues.apache.org/jira/browse/MAPREDUCE-7089 URL: https://github.com/apache/hadoop/pull/454#issuecomment-453175598 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #447: recovery contaienr exit code not right
elek removed a comment on issue #447: recovery contaienr exit code not right URL: https://github.com/apache/hadoop/pull/447#issuecomment-453175672 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #441: HDFS-14099
elek removed a comment on issue #441: HDFS-14099 URL: https://github.com/apache/hadoop/pull/441#issuecomment-453175771 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #439: YARN-8833 fix compute shares may lock the scheduling process
elek removed a comment on issue #439: YARN-8833 fix compute shares may lock the scheduling process URL: https://github.com/apache/hadoop/pull/439#issuecomment-453175806 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #444: YARN-9093. Remove commented code block from the beginning of TestDefa…
elek removed a comment on issue #444: YARN-9093. Remove commented code block from the beginning of TestDefa… URL: https://github.com/apache/hadoop/pull/444#issuecomment-453175713 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #408: HADOOP-15652. Fix typos SPENGO into SPNEGO
elek removed a comment on issue #408: HADOOP-15652. Fix typos SPENGO into SPNEGO URL: https://github.com/apache/hadoop/pull/408#issuecomment-453176110 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #424: HDFS-13948: provide Regex Based Mount Point In Inode Tree
elek removed a comment on issue #424: HDFS-13948: provide Regex Based Mount Point In Inode Tree URL: https://github.com/apache/hadoop/pull/424#issuecomment-453175989 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #434: HADOOP-15876: Refactoring AzureBlobFileSystemStore.java
elek removed a comment on issue #434: HADOOP-15876: Refactoring AzureBlobFileSystemStore.java URL: https://github.com/apache/hadoop/pull/434#issuecomment-453175912 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #433: HADOOP-15870
elek removed a comment on issue #433: HADOOP-15870 URL: https://github.com/apache/hadoop/pull/433#issuecomment-453175931 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #436: Use print() function in both Python 2 and Python 3
elek removed a comment on issue #436: Use print() function in both Python 2 and Python 3 URL: https://github.com/apache/hadoop/pull/436#issuecomment-453175869 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #416: YARN-8470. Fix a NPE in identifyContainersToPreemptOnNode()
elek removed a comment on issue #416: YARN-8470. Fix a NPE in identifyContainersToPreemptOnNode() URL: https://github.com/apache/hadoop/pull/416#issuecomment-453176034 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #400: HADOOP-15585. Fix passing options via $HADOOP_OPTS
elek removed a comment on issue #400: HADOOP-15585. Fix passing options via $HADOOP_OPTS URL: https://github.com/apache/hadoop/pull/400#issuecomment-453176239 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #399: MAPREDUCE-7120. Make hadoop consider wildcard host as datalocal
elek removed a comment on issue #399: MAPREDUCE-7120. Make hadoop consider wildcard host as datalocal URL: https://github.com/apache/hadoop/pull/399#issuecomment-453176252 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #431: HDFS-13997. Add moment.js to the secondarynamenode web UI
elek removed a comment on issue #431: HDFS-13997. Add moment.js to the secondarynamenode web UI URL: https://github.com/apache/hadoop/pull/431#issuecomment-453175953 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #402: MAPREDUCE-7121. add Abortable so that we can abort output
elek removed a comment on issue #402: MAPREDUCE-7121. add Abortable so that we can abort output URL: https://github.com/apache/hadoop/pull/402#issuecomment-453176197 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #406: HDFS-13775. Add a conf property to retry dns reverse lookups during datanode registration.
elek removed a comment on issue #406: HDFS-13775. Add a conf property to retry dns reverse lookups during datanode registration. URL: https://github.com/apache/hadoop/pull/406#issuecomment-453176138 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #413: Adding EC2ContainerCredentialsProviderWrapper to the credential providers
elek removed a comment on issue #413: Adding EC2ContainerCredentialsProviderWrapper to the credential providers URL: https://github.com/apache/hadoop/pull/413#issuecomment-453176060 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #453: check the buffer size
elek removed a comment on issue #453: check the buffer size URL: https://github.com/apache/hadoop/pull/453#issuecomment-453175612 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #426: correct configuration tag in mapred-site.xml
elek removed a comment on issue #426: correct configuration tag in mapred-site.xml URL: https://github.com/apache/hadoop/pull/426#issuecomment-453175977 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #440: HADOOP-15910 Fixing Javadoc for LdapAuthenticationHandler#ENABLE_START_TLS
elek removed a comment on issue #440: HADOOP-15910 Fixing Javadoc for LdapAuthenticationHandler#ENABLE_START_TLS URL: https://github.com/apache/hadoop/pull/440#issuecomment-453175792 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #432: Update committers.md
elek removed a comment on issue #432: Update committers.md URL: https://github.com/apache/hadoop/pull/432#issuecomment-453175941 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #456: remove the task attempt id from earlier failed map
elek removed a comment on issue #456: remove the task attempt id from earlier failed map URL: https://github.com/apache/hadoop/pull/456#issuecomment-453175569 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #443: recovery contaienr exit code not right
elek removed a comment on issue #443: recovery contaienr exit code not right URL: https://github.com/apache/hadoop/pull/443#issuecomment-453175732 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #427: YARN-6636. Add basic fairscheduler nodelabel support.
elek removed a comment on issue #427: YARN-6636. Add basic fairscheduler nodelabel support. URL: https://github.com/apache/hadoop/pull/427#issuecomment-453175964 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #420: YARN-8785-branch-3.1.002.patch
elek removed a comment on issue #420: YARN-8785-branch-3.1.002.patch URL: https://github.com/apache/hadoop/pull/420#issuecomment-453176015 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #435: Remove extra in documentation for Single Node Cluster
elek removed a comment on issue #435: Remove extra in documentation for Single Node Cluster URL: https://github.com/apache/hadoop/pull/435#issuecomment-453175885 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #460: Hadoop-15994
elek removed a comment on issue #460: Hadoop-15994 URL: https://github.com/apache/hadoop/pull/460#issuecomment-453175517 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #438: YARN-9009: Fix flaky test TestEntityGroupFSTimelineStore.testCleanLogs
elek removed a comment on issue #438: YARN-9009: Fix flaky test TestEntityGroupFSTimelineStore.testCleanLogs URL: https://github.com/apache/hadoop/pull/438#issuecomment-453175826 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #446: HDFS-14147: Back port of HDFS-13056 to the 2.9 branch
elek removed a comment on issue #446: HDFS-14147: Back port of HDFS-13056 to the 2.9 branch URL: https://github.com/apache/hadoop/pull/446#issuecomment-453175699 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #388: Minor spell mistake in comment : Line number 101
elek removed a comment on issue #388: Minor spell mistake in comment : Line number 101 URL: https://github.com/apache/hadoop/pull/388#issuecomment-453176429 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #398: MAPREDUCE-7119. Avoid stopContainer() on dead node
elek removed a comment on issue #398: MAPREDUCE-7119. Avoid stopContainer() on dead node URL: https://github.com/apache/hadoop/pull/398#issuecomment-453176265 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #393: HADOOP-15524 Bounding array size in BytesWritable to Integer.MAX_VALUE - 8
elek removed a comment on issue #393: HADOOP-15524 Bounding array size in BytesWritable to Integer.MAX_VALUE - 8 URL: https://github.com/apache/hadoop/pull/393#issuecomment-453176324 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #389: Change of file name to md
elek removed a comment on issue #389: Change of file name to md URL: https://github.com/apache/hadoop/pull/389#issuecomment-453176417 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #401: YARN-3929. Add uncleaning option for local app log file
elek removed a comment on issue #401: YARN-3929. Add uncleaning option for local app log file URL: https://github.com/apache/hadoop/pull/401#issuecomment-453176220 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #396: classpath description is not full for hadoop cmd
elek removed a comment on issue #396: classpath description is not full for hadoop cmd URL: https://github.com/apache/hadoop/pull/396#issuecomment-453176293 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #403: HDFS-13734. Allow HDFS heapsizes to be configured seperately
elek removed a comment on issue #403: HDFS-13734. Allow HDFS heapsizes to be configured seperately URL: https://github.com/apache/hadoop/pull/403#issuecomment-453176185 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #410: add non-empty folder when test cannot find HADOOP_CONF_DIR [https://i…
elek removed a comment on issue #410: add non-empty folder when test cannot find HADOOP_CONF_DIR [https://i… URL: https://github.com/apache/hadoop/pull/410#issuecomment-453176090 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #384: YARN-8256. Support pluggable node membership manager in YARN.
elek removed a comment on issue #384: YARN-8256. Support pluggable node membership manager in YARN. URL: https://github.com/apache/hadoop/pull/384#issuecomment-453176471 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #414: Prevent OOM on array size over VM limit
elek removed a comment on issue #414: Prevent OOM on array size over VM limit URL: https://github.com/apache/hadoop/pull/414#issuecomment-453176047 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #407: MAPREDUCE-7127. Add aggregated webservice endpoints to fetch all tasks & their taskAttempts
elek removed a comment on issue #407: MAPREDUCE-7127. Add aggregated webservice endpoints to fetch all tasks & their taskAttempts URL: https://github.com/apache/hadoop/pull/407#issuecomment-453176123 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #372: add a pic
elek removed a comment on issue #372: add a pic URL: https://github.com/apache/hadoop/pull/372#issuecomment-453176547 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #391: Add function hdfsGetRemaining to libhdfs
elek removed a comment on issue #391: Add function hdfsGetRemaining to libhdfs URL: https://github.com/apache/hadoop/pull/391#issuecomment-453176339 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #376: HDFS-13514. Avoid edge case where BUFFER_SIZE is 0
elek removed a comment on issue #376: HDFS-13514. Avoid edge case where BUFFER_SIZE is 0 URL: https://github.com/apache/hadoop/pull/376#issuecomment-453176499 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #375: HDFS-13513. Avoid edge case where BUFFER_SIZE is 0
elek removed a comment on issue #375: HDFS-13513. Avoid edge case where BUFFER_SIZE is 0 URL: https://github.com/apache/hadoop/pull/375#issuecomment-453176516 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #397: HADOOP-15584. Move httpcomponents version to their own config
elek removed a comment on issue #397: HADOOP-15584. Move httpcomponents version to their own config URL: https://github.com/apache/hadoop/pull/397#issuecomment-453176280 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #370: HADOOP-15427
elek removed a comment on issue #370: HADOOP-15427 URL: https://github.com/apache/hadoop/pull/370#issuecomment-453176595 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #394: fix the bug of the refresh disk configuration
elek removed a comment on issue #394: fix the bug of the refresh disk configuration URL: https://github.com/apache/hadoop/pull/394#issuecomment-453176308 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #358: Create REad.me
elek removed a comment on issue #358: Create REad.me URL: https://github.com/apache/hadoop/pull/358#issuecomment-453176937 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #367: HADOOP-15409
elek removed a comment on issue #367: HADOOP-15409 URL: https://github.com/apache/hadoop/pull/367#issuecomment-453176647 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #371: HDFS-13515
elek removed a comment on issue #371: HDFS-13515 URL: https://github.com/apache/hadoop/pull/371#issuecomment-453176575 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #361: HADOOP-13617 : Retry requests with updated authentication
elek removed a comment on issue #361: HADOOP-13617 : Retry requests with updated authentication URL: https://github.com/apache/hadoop/pull/361#issuecomment-453176800 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #363: Branch 2.9.1
elek removed a comment on issue #363: Branch 2.9.1 URL: https://github.com/apache/hadoop/pull/363#issuecomment-453176693 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #373: HADOOP-15428
elek removed a comment on issue #373: HADOOP-15428 URL: https://github.com/apache/hadoop/pull/373#issuecomment-453176528 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #369: HADOOP-15418
elek removed a comment on issue #369: HADOOP-15418 URL: https://github.com/apache/hadoop/pull/369#issuecomment-453176613 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #356: YARN-8056. Fix possible NPE when start Application Master
elek removed a comment on issue #356: YARN-8056. Fix possible NPE when start Application Master URL: https://github.com/apache/hadoop/pull/356#issuecomment-453176981 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #355: HDFS-13313. Fix NullPointerException in FSEditLogOp.toString().
elek removed a comment on issue #355: HDFS-13313. Fix NullPointerException in FSEditLogOp.toString(). URL: https://github.com/apache/hadoop/pull/355#issuecomment-453177006 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #368: HADOOP-15380
elek removed a comment on issue #368: HADOOP-15380 URL: https://github.com/apache/hadoop/pull/368#issuecomment-453176636 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #366: HADOOP-15410
elek removed a comment on issue #366: HADOOP-15410 URL: https://github.com/apache/hadoop/pull/366#issuecomment-453176665 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #360: HADOOP-14175 : NPE when ADL store URI contains underscore
elek removed a comment on issue #360: HADOOP-14175 : NPE when ADL store URI contains underscore URL: https://github.com/apache/hadoop/pull/360#issuecomment-453176823 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #350: Fix FileSystem.listStatus javadoc
elek removed a comment on issue #350: Fix FileSystem.listStatus javadoc URL: https://github.com/apache/hadoop/pull/350#issuecomment-453177049 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #343: Add missing description of Namenode format options
elek removed a comment on issue #343: Add missing description of Namenode format options URL: https://github.com/apache/hadoop/pull/343#issuecomment-453177127 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #345: YARN-7926 fix a copy-and-paste error in log messages
elek removed a comment on issue #345: YARN-7926 fix a copy-and-paste error in log messages URL: https://github.com/apache/hadoop/pull/345#issuecomment-453177078 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #328: YARN-7742 - Remove duplicate entries
elek removed a comment on issue #328: YARN-7742 - Remove duplicate entries URL: https://github.com/apache/hadoop/pull/328#issuecomment-453177545 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #314: POC: replace explicit method parameters null-checks by a declarative approach
elek removed a comment on issue #314: POC: replace explicit method parameters null-checks by a declarative approach URL: https://github.com/apache/hadoop/pull/314#issuecomment-453177850 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[GitHub] elek removed a comment on issue #357: HDFS-13321: Inadequate information for handling catch clauses
elek removed a comment on issue #357: HDFS-13321: Inadequate information for handling catch clauses URL: https://github.com/apache/hadoop/pull/357#issuecomment-453176954 Can one of the admins verify this patch? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
