[
https://issues.apache.org/jira/browse/HADOOP-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HADOOP-11223:
Assignee: Michael Miller (was: Varun Saxena)
> Offer a read-only conf alternative to new
[
https://issues.apache.org/jira/browse/HADOOP-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HADOOP-12549:
Assignee: (was: Harsh J)
> Extend HDFS-7456 default generically to all pattern lookups
>
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HADOOP-13694:
Assignee: (was: Harsh J)
> Data transfer encryption with AES 192: Invalid key length.
>
[
https://issues.apache.org/jira/browse/HADOOP-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-6801:
Release Note:
Two new configuration keys, seq.io.sort.mb and seq.io.sort.factor have been
introduced for
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13817:
-
Release Note: A new introduced configuration key
"hadoop.security.groups.shell.command.timeout" allows
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13817:
-
Release Note:
A new introduced configuration key
"hadoop.security.groups.shell.command.timeout" allows
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13817:
-
Resolution: Fixed
Fix Version/s: 3.0.0-beta1
2.9.0
Target
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13817:
-
Hadoop Flags: Reviewed
> Add a finite shell command timeout to ShellBasedUnixGroupsMapping
>
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13817:
-
Target Version/s: 2.9.0, 3.0.0-beta1
> Add a finite shell command timeout to
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13817:
-
Attachment: HADOOP-13817.000.patch
HADOOP-13817-branch-2.000.patch
Uploading direct
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870061#comment-15870061
]
Harsh J commented on HADOOP-13694:
--
[~jojochuang] - Could you help in reviewing this?
> Data transfer
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870058#comment-15870058
]
Harsh J commented on HADOOP-13817:
--
[~jojochuang] - Could you help in reviewing this? Current diff is
[
https://issues.apache.org/jira/browse/HADOOP-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HADOOP-10434.
--
Resolution: Duplicate
> Is it possible to use "df" to calculate the dfs usage instead of "du"
>
[
https://issues.apache.org/jira/browse/HADOOP-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reopened HADOOP-10434:
--
Reopening to close as Duplicate status vs. Fixed.
> Is it possible to use "df" to calculate the dfs
[
https://issues.apache.org/jira/browse/HADOOP-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-10434:
-
Fix Version/s: (was: 2.8.0)
> Is it possible to use "df" to calculate the dfs usage instead of "du"
[
https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-1381:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.0.0-beta1
Release Note: The
[
https://issues.apache.org/jira/browse/HADOOP-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696276#comment-15696276
]
Harsh J commented on HADOOP-6801:
-
Thank you [~ajisakaa], updated the commit with that addressed.
>
[
https://issues.apache.org/jira/browse/HADOOP-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15694990#comment-15694990
]
Harsh J commented on HADOOP-12549:
--
[~daryn] / [~yzhangal] - Could you help take a look at this one?
>
[
https://issues.apache.org/jira/browse/HADOOP-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15694987#comment-15694987
]
Harsh J commented on HADOOP-6801:
-
[~cnauroth] / [~ajisakaa] - Could you help take a look at this one?
>
[
https://issues.apache.org/jira/browse/HADOOP-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-9424:
Assignee: (was: Harsh J)
> The "hadoop jar" invocation should include the passed jar on the classpath
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15694982#comment-15694982
]
Harsh J commented on HADOOP-13817:
--
[~xyao] - Thanks for the reviews so far. Could you take a look at
[
https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15694979#comment-15694979
]
Harsh J commented on HADOOP-1381:
-
[~ajisakaa] / [~ozawa]] - Could you help take a look at this one?
>
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15694976#comment-15694976
]
Harsh J commented on HADOOP-13694:
--
[~cnauroth] / [~hitliuyi] - Would you be able to take a look at
[
https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669509#comment-15669509
]
Harsh J commented on HADOOP-1381:
-
Fixed all javac and checkstyle issues except this one:
{code}
[
https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-1381:
Summary: The distance between sync blocks in SequenceFiles should be
configurable (was: The distance
[
https://issues.apache.org/jira/browse/HADOOP-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-6801:
Affects Version/s: (was: 0.22.0)
2.0.0-alpha
Target Version/s: (was: )
[
https://issues.apache.org/jira/browse/HADOOP-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-6801:
Status: Patch Available (was: Open)
> io.sort.mb and io.sort.factor were renamed and moved to mapreduce
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13694:
-
Status: Open (was: Patch Available)
> Data transfer encryption with AES 192: Invalid key length.
>
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13694:
-
Status: Patch Available (was: Open)
> Data transfer encryption with AES 192: Invalid key length.
>
[
https://issues.apache.org/jira/browse/HADOOP-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13817:
-
Status: Patch Available (was: Open)
> Add a finite shell command timeout to
[
https://issues.apache.org/jira/browse/HADOOP-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625461#comment-15625461
]
Harsh J commented on HADOOP-6801:
-
- Updated patch addresses the checkstyle issues
> io.sort.mb and
[
https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-1381:
Release Note: Made sync interval of sequencefiles configurable and raised
default from 2000 bytes to 100
[
https://issues.apache.org/jira/browse/HADOOP-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-1381:
Target Version/s: (was: )
Status: Patch Available (was: Open)
> The distance between sync
[
https://issues.apache.org/jira/browse/HADOOP-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HADOOP-8134.
-
Resolution: Not A Problem
Assignee: (was: Harsh J)
This hasn't proven as a problem in late.
[
https://issues.apache.org/jira/browse/HADOOP-9424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-9424:
Resolution: Invalid
Target Version/s: (was: )
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/HADOOP-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607784#comment-15607784
]
Harsh J commented on HADOOP-6801:
-
[~cnauroth] - Thanks for reviewing! I added the ordering test as well.
[
https://issues.apache.org/jira/browse/HADOOP-7505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HADOOP-7505.
-
Resolution: Duplicate
Assignee: (was: Harsh J)
This seems to be taken care (in part) via
[
https://issues.apache.org/jira/browse/HADOOP-8579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HADOOP-8579.
-
Resolution: Not A Problem
Assignee: (was: Harsh J)
This does not appear to be a problem after
[
https://issues.apache.org/jira/browse/HADOOP-8863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HADOOP-8863.
-
Resolution: Won't Fix
Assignee: (was: Harsh J)
The eclipse plugin is formally out.
> Eclipse
[
https://issues.apache.org/jira/browse/HADOOP-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607688#comment-15607688
]
Harsh J commented on HADOOP-12549:
--
[~yzhangal] or [~aw] - Could you help review this one? The change
[
https://issues.apache.org/jira/browse/HADOOP-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13056:
-
Target Version/s: (was: 2.9.0)
> Print expected values when rejecting a server's determined principal
[
https://issues.apache.org/jira/browse/HADOOP-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13056:
-
Resolution: Duplicate
Assignee: (was: Harsh J)
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607544#comment-15607544
]
Harsh J commented on HADOOP-13694:
--
[~hitliuyi] or [~jojochuang], could you help review this one? The
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13694:
-
Status: Patch Available (was: Open)
> Data transfer encryption with AES 192: Invalid key length.
>
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13694:
-
Status: Open (was: Patch Available)
> Data transfer encryption with AES 192: Invalid key length.
>
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15571320#comment-15571320
]
Harsh J commented on HADOOP-13694:
--
- Updated patch to address {{cc}} warnings (w.r.t. use of compare
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13694:
-
Status: Patch Available (was: Open)
> Data transfer encryption with AES 192: Invalid key length.
>
[
https://issues.apache.org/jira/browse/HADOOP-13694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J moved HDFS-9878 to HADOOP-13694:
Affects Version/s: (was: 2.7.2)
2.7.2
Harsh J created HADOOP-13515:
Summary: Redundant transitionToActive call can cause a NameNode to
crash
Key: HADOOP-13515
URL: https://issues.apache.org/jira/browse/HADOOP-13515
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15413827#comment-15413827
]
Harsh J commented on HADOOP-13410:
--
There is a use-case that requires something similar, see
[
https://issues.apache.org/jira/browse/HADOOP-13099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272428#comment-15272428
]
Harsh J commented on HADOOP-13099:
--
This looks like a dupe of HADOOP-13051?
> Globbing does not return
[
https://issues.apache.org/jira/browse/HADOOP-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13051:
-
Attachment: HADOOP-13051.000.patch
(Renamed attachment to the right project)
> Test for special
[
https://issues.apache.org/jira/browse/HADOOP-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13051:
-
Attachment: (was: HDFS-13051.000.patch)
> Test for special characters in path being respected
[
https://issues.apache.org/jira/browse/HADOOP-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13056:
-
Status: Patch Available (was: Open)
> Print expected values when rejecting a server's determined
[
https://issues.apache.org/jira/browse/HADOOP-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13056:
-
Attachment: HADOOP-13056.000.patch
> Print expected values when rejecting a server's determined
Harsh J created HADOOP-13056:
Summary: Print expected values when rejecting a server's
determined principal
Key: HADOOP-13056
URL: https://issues.apache.org/jira/browse/HADOOP-13056
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15255017#comment-15255017
]
Harsh J commented on HADOOP-12436:
--
This change subtly fixes the issue described in HADOOP-13051
[
https://issues.apache.org/jira/browse/HADOOP-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13051:
-
Attachment: HDFS-13051.000.patch
Patch that fails in {{branch-2}} but passes in trunk after the
[
https://issues.apache.org/jira/browse/HADOOP-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-13051:
-
Status: Patch Available (was: Open)
> Test for special characters in path being respected during
Harsh J created HADOOP-13051:
Summary: Test for special characters in path being respected
during globPaths
Key: HADOOP-13051
URL: https://issues.apache.org/jira/browse/HADOOP-13051
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222434#comment-15222434
]
Harsh J commented on HADOOP-12990:
--
There does not also seem to be any benefit of using LZ4 Frame
[
https://issues.apache.org/jira/browse/HADOOP-12990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221946#comment-15221946
]
Harsh J commented on HADOOP-12990:
--
I don't think our Lz4Codec implementation actually uses the FRAME
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221793#comment-15221793
]
Harsh J commented on HADOOP-11687:
--
Oops, sorry Steve, I misunderstood the LGTM... Thanks for
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11687:
-
Resolution: Fixed
Fix Version/s: 2.9.0
Target Version/s: (was: 2.9.0)
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11687:
-
Target Version/s: 2.9.0
> Ignore x-* and response headers when copying an Amazon S3 object
>
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15221388#comment-15221388
]
Harsh J commented on HADOOP-11687:
--
Ran the S3A tests a few times more just in case, they still succeed
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15219672#comment-15219672
]
Harsh J commented on HADOOP-11687:
--
I also did a manual "Connection: close" header inject test prior to
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11687:
-
Attachment: HADOOP-11687.004.patch
* Fixes the checkstyle warning
> Ignore x-* and response headers
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15219523#comment-15219523
]
Harsh J commented on HADOOP-11687:
--
All of the S3A tests pass with this change, when running {{mvn
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HADOOP-11687:
Assignee: Harsh J
> Ignore x-* and response headers when copying an Amazon S3 object
>
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11687:
-
Attachment: HADOOP-11687.003.patch
Updated patch
* Added null checks during clone on fields that are
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15219511#comment-15219511
]
Harsh J commented on HADOOP-11687:
--
Thanks [~ste...@apache.org], am running the tests of rename
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11687:
-
Status: Patch Available (was: Open)
> Ignore x-* and response headers when copying an Amazon S3 object
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11687:
-
Attachment: HADOOP-11687.002.patch
Updating patch to address Steve's earlier review comment.
> Ignore
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217513#comment-15217513
]
Harsh J commented on HADOOP-12970:
--
Just for posterity: I did get my upstream patch into aws-sdk-java:
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-12970:
-
Resolution: Duplicate
Status: Resolved (was: Patch Available)
> Intermittent signature match
[
https://issues.apache.org/jira/browse/HADOOP-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15216184#comment-15216184
]
Harsh J commented on HADOOP-11687:
--
Yes this can solve HADOOP-12970 too. I am unsure if skipping all
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15216179#comment-15216179
]
Harsh J commented on HADOOP-12970:
--
Yes it seems to be doing the same thing as this one, but it ignores
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215880#comment-15215880
]
Harsh J commented on HADOOP-12970:
--
Thanks [~ste...@apache.org]!
bq. you do need to use
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-12970:
-
Attachment: HADOOP-12970.patch
> Intermittent signature match failures in S3AFileSystem due connection
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215335#comment-15215335
]
Harsh J commented on HADOOP-12970:
--
bq. Patch generated 1 ASF License warnings.
Unrelated to patch,
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-12970:
-
Status: Patch Available (was: Open)
> Intermittent signature match failures in S3AFileSystem due
[
https://issues.apache.org/jira/browse/HADOOP-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-12970:
-
Attachment: HADOOP-12970.patch
> Intermittent signature match failures in S3AFileSystem due connection
Harsh J created HADOOP-12970:
Summary: Intermittent signature match failures in S3AFileSystem
due connection closure
Key: HADOOP-12970
URL: https://issues.apache.org/jira/browse/HADOOP-12970
Project:
[
https://issues.apache.org/jira/browse/HADOOP-9567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15211143#comment-15211143
]
Harsh J commented on HADOOP-9567:
-
Thanks [~subrotosanyal], that is indeed what handles it automatically
[
https://issues.apache.org/jira/browse/HADOOP-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15198683#comment-15198683
]
Harsh J commented on HADOOP-12559:
--
(We'll need also HADOOP-12682 for tests if backporting BTW)
> KMS
[
https://issues.apache.org/jira/browse/HADOOP-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11404:
-
Resolution: Fixed
Fix Version/s: 2.9.0
Status: Resolved (was: Patch Available)
[
https://issues.apache.org/jira/browse/HADOOP-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189177#comment-15189177
]
Harsh J commented on HADOOP-11404:
--
Thanks [~ste...@apache.org]! Committing shortly.
> Clarify the
[
https://issues.apache.org/jira/browse/HADOOP-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11404:
-
Attachment: HADOOP-11404.003.patch
Fixing the indent issue. Retrying.
> Clarify the "expected client
[
https://issues.apache.org/jira/browse/HADOOP-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-11404:
-
Attachment: HADOOP-11404.002.patch
Resubmitting for jenkins (fixed a 84 line change to clear probable
[
https://issues.apache.org/jira/browse/HADOOP-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188715#comment-15188715
]
Harsh J commented on HADOOP-11404:
--
+1, patch still applies. Will commit in a day unless you have any
Harsh J created HADOOP-12894:
Summary: Add yarn.app.mapreduce.am.log.level to mapred-default.xml
Key: HADOOP-12894
URL: https://issues.apache.org/jira/browse/HADOOP-12894
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052650#comment-15052650
]
Harsh J commented on HADOOP-12559:
--
[~zhz] - I've isolated the issue to a problem with tgt lifetime vs.
[
https://issues.apache.org/jira/browse/HADOOP-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052880#comment-15052880
]
Harsh J commented on HADOOP-12559:
--
Although if its possible for the patch to not be specific to
[
https://issues.apache.org/jira/browse/HADOOP-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046632#comment-15046632
]
Harsh J commented on HADOOP-12559:
--
The reason I ask is that the NameNode also sees the same error
[
https://issues.apache.org/jira/browse/HADOOP-11187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046601#comment-15046601
]
Harsh J commented on HADOOP-11187:
--
This doesn't cover the retries properly if the connection setup
[
https://issues.apache.org/jira/browse/HADOOP-12559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15005962#comment-15005962
]
Harsh J commented on HADOOP-12559:
--
On the client-end, or the server-end BTW?
> KMS connection
Harsh J created HADOOP-12549:
Summary: Extend HDFS-7456 default generically to all pattern
lookups
Key: HADOOP-12549
URL: https://issues.apache.org/jira/browse/HADOOP-12549
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-12549:
-
Status: Patch Available (was: Open)
> Extend HDFS-7456 default generically to all pattern lookups
>
[
https://issues.apache.org/jira/browse/HADOOP-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-12549:
-
Attachment: HADOOP-12549.patch
> Extend HDFS-7456 default generically to all pattern lookups
>
1 - 100 of 1031 matches
Mail list logo
