[jira] [Commented] (HADOOP-7967) Need generalized multi-token filesystem support
[
https://issues.apache.org/jira/browse/HADOOP-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420882#comment-13420882
]
Sanjay Radia commented on HADOOP-7967:
--
I think you are right: (getCanonicalName() != null) = FS has token
Need generalized multi-token filesystem support
---
Key: HADOOP-7967
URL: https://issues.apache.org/jira/browse/HADOOP-7967
Project: Hadoop Common
Issue Type: Bug
Components: fs, security
Affects Versions: 0.23.1, 0.24.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-7967-2.patch, HADOOP-7967-3.patch,
HADOOP-7967-4.patch, HADOOP-7967-compat.patch, HADOOP-7967.newapi.patch,
HADOOP-7967.patch
Multi-token filesystem support and its interactions with the MR
{{TokenCache}} is problematic. The {{TokenCache}} tries to assume it has the
knowledge to know if the tokens for a filesystem are available, which it
can't possibly know for multi-token filesystems. Filtered filesystems are
also problematic, such as har on viewfs. When mergeFs is implemented, it too
will become a problem with the current implementation. Currently
{{FileSystem}} will leak tokens even when some tokens are already present.
The decision for token acquisition, and which tokens, should be pushed all
the way down into the {{FileSystem}} level. The {{TokenCache}} should be
ignorant and simply request tokens from each {{FileSystem}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7967) Need generalized multi-token filesystem support
[
https://issues.apache.org/jira/browse/HADOOP-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418608#comment-13418608
]
Sanjay Radia commented on HADOOP-7967:
--
Some early comments:
A suggestion: center the code around FileSystem#getChildFileSystems()
* FileSystems which embed others such as ViewFS will only need to implement
getChildFileSystems()
* the default impl of getCanaonicalName will return null if
getChildFileSystems() returns null
* the defaul impl of getDelegationToken will return null if
getChildFileSystems() returns null
* In collectDelegationTokens use if (getChildFileSystems()==null) rather than
if (getCanaonicalName() == null)
{code}
collectDelegationTokens() {
children = getChildFileSystems();
if (children == null) { // get token directly from FS
... your code ...
} else { // get the tokens from the children
... your code
}
}
{code}
Need generalized multi-token filesystem support
---
Key: HADOOP-7967
URL: https://issues.apache.org/jira/browse/HADOOP-7967
Project: Hadoop Common
Issue Type: Bug
Components: fs, security
Affects Versions: 0.23.1, 0.24.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-7967-2.patch, HADOOP-7967-3.patch,
HADOOP-7967-4.patch, HADOOP-7967-compat.patch, HADOOP-7967.newapi.patch,
HADOOP-7967.patch
Multi-token filesystem support and its interactions with the MR
{{TokenCache}} is problematic. The {{TokenCache}} tries to assume it has the
knowledge to know if the tokens for a filesystem are available, which it
can't possibly know for multi-token filesystems. Filtered filesystems are
also problematic, such as har on viewfs. When mergeFs is implemented, it too
will become a problem with the current implementation. Currently
{{FileSystem}} will leak tokens even when some tokens are already present.
The decision for token acquisition, and which tokens, should be pushed all
the way down into the {{FileSystem}} level. The {{TokenCache}} should be
ignorant and simply request tokens from each {{FileSystem}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7967) Need generalized multi-token filesystem support
[
https://issues.apache.org/jira/browse/HADOOP-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13417352#comment-13417352
]
Sanjay Radia commented on HADOOP-7967:
--
@daryn I'd like to separate out FileContext and AbstractFileSystem changes into
a separate jira
That sounds good since there is not code share as you state.
Need generalized multi-token filesystem support
---
Key: HADOOP-7967
URL: https://issues.apache.org/jira/browse/HADOOP-7967
Project: Hadoop Common
Issue Type: Bug
Components: fs, security
Affects Versions: 0.23.1, 0.24.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-7967-2.patch, HADOOP-7967-3.patch,
HADOOP-7967-4.patch, HADOOP-7967-compat.patch, HADOOP-7967.newapi.patch,
HADOOP-7967.patch
Multi-token filesystem support and its interactions with the MR
{{TokenCache}} is problematic. The {{TokenCache}} tries to assume it has the
knowledge to know if the tokens for a filesystem are available, which it
can't possibly know for multi-token filesystems. Filtered filesystems are
also problematic, such as har on viewfs. When mergeFs is implemented, it too
will become a problem with the current implementation. Currently
{{FileSystem}} will leak tokens even when some tokens are already present.
The decision for token acquisition, and which tokens, should be pushed all
the way down into the {{FileSystem}} level. The {{TokenCache}} should be
ignorant and simply request tokens from each {{FileSystem}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8607) Replace references to Dr Who in codebase with @BigDataBorat
[
https://issues.apache.org/jira/browse/HADOOP-8607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Radia updated HADOOP-8607:
-
Hadoop Flags: Incompatible change
Replace references to Dr Who in codebase with @BigDataBorat
-
Key: HADOOP-8607
URL: https://issues.apache.org/jira/browse/HADOOP-8607
Project: Hadoop Common
Issue Type: Improvement
Components: util
Affects Versions: 1.0.3, 2.0.0-alpha
Reporter: Steve Loughran
Assignee: Sanjay Radia
Priority: Minor
Original Estimate: 0.5h
Remaining Estimate: 0.5h
People complain that having Dr Who in the code causes confusion and isn't
appropriate in Hadoop now that it has matured.
I propose that we replace this anonymous user ID with {{@BigDataBorat}}. This
will
# Increase brand awareness of @BigDataBorat and their central role in the Big
Data ecosystem.
# Drive traffic to twitter, and increase their revenue. As contributors to
the Hadoop platform, this will fund further Hadoop development.
Patching the code is straightforward; no easy tests, though we could monitor
twitter followers to determine rollout of the patch in the field.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8457) Address file ownership issue for users in Administrators group on Windows.
[ https://issues.apache.org/jira/browse/HADOOP-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413859#comment-13413859 ] Sanjay Radia commented on HADOOP-8457: -- The two approaches explored in this jira are # When a local file is created, change the owner to the creator of the file # Leave the owner of local file to policies of local file (ie Admin in the case of Windows if the owner is an Admin). Add a method in FileStatus to check if the owner is current user (so that it can match the behavior of the local file system for local files) - current patch Approach (2) seems reasonable except given the Hadoop APIs, apps are justified to do fileStatus.getOwner().equals(currentUser). Such code is probably all over the place and can't be avoided. Good news is that LocalFs is used only for emulating Hadoop or for copying files back and forth. Hard call on which is the right approach. Address file ownership issue for users in Administrators group on Windows. -- Key: HADOOP-8457 URL: https://issues.apache.org/jira/browse/HADOOP-8457 Project: Hadoop Common Issue Type: Bug Components: native Affects Versions: 1.1.0, 0.24.0 Reporter: Chuan Liu Assignee: Ivan Mitic Priority: Minor Attachments: HADOOP-8457-branch-1-win_Admins(2).patch, HADOOP-8457-branch-1-win_Admins.patch On Linux, the initial file owners are the creators. (I think this is true in general. If there are exceptions, please let me know.) On Windows, the file created by a user in the Administrators group has the initial owner ‘Administrators’, i.e. the the Administrators group is the initial owner of the file. As a result, this leads to an exception when we check file ownership in SecureIOUtils .checkStat() method. As a result, this method is disabled right now. We need to address this problem and enable the method on Windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8457) Address file ownership issue for users in Administrators group on Windows.
[ https://issues.apache.org/jira/browse/HADOOP-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413429#comment-13413429 ] Sanjay Radia commented on HADOOP-8457: -- Patch adds public method FileStatus#isOwnedByUser(UserGroupInformation ugi) * Does not make sense to expose a low level structure like ugi through a fundamental class like FileStatus. Make the parameter String user. * I hate the idea of adding a public method when getOwener().equals(user) is good enough - but FileStatus is subclassed and is useful for the RawFileSystem's FileStatus. Is there another way to solve the problem in a simple way without adding such a method? ** e.g. put in a util? May not work since the new code applies to FileStatus of RawLocalFileSystem of windows-filesystem and not to FileStatus of hdfs where the client is running on a windows box. Address file ownership issue for users in Administrators group on Windows. -- Key: HADOOP-8457 URL: https://issues.apache.org/jira/browse/HADOOP-8457 Project: Hadoop Common Issue Type: Bug Components: native Affects Versions: 1.1.0, 0.24.0 Reporter: Chuan Liu Assignee: Ivan Mitic Priority: Minor Attachments: HADOOP-8457-branch-1-win_Admins(2).patch, HADOOP-8457-branch-1-win_Admins.patch On Linux, the initial file owners are the creators. (I think this is true in general. If there are exceptions, please let me know.) On Windows, the file created by a user in the Administrators group has the initial owner ‘Administrators’, i.e. the the Administrators group is the initial owner of the file. As a result, this leads to an exception when we check file ownership in SecureIOUtils .checkStat() method. As a result, this method is disabled right now. We need to address this problem and enable the method on Windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8414) Address problems related to localhost resolving to 127.0.0.1 on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8414. -- Resolution: Fixed Thanks Ivan, committed to branch-1 windows. Address problems related to localhost resolving to 127.0.0.1 on Windows --- Key: HADOOP-8414 URL: https://issues.apache.org/jira/browse/HADOOP-8414 Project: Hadoop Common Issue Type: Bug Components: fs, test Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8414-branch-1-win(2).patch, HADOOP-8414-branch-1-win(3).patch, HADOOP-8414-branch-1-win.patch, HADOOP-8414-branch-1-win.patch Localhost resolves to 127.0.0.1 on Windows and that causes the following tests to fail: - TestHarFileSystem - TestCLI - TestSaslRPC This Jira tracks fixing these tests and other possible places that have similar issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8487) Many HDFS tests use a test path intended for local file system tests
[
https://issues.apache.org/jira/browse/HADOOP-8487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Radia updated HADOOP-8487:
-
Description:
Many tests use a test path intended for local tests setup by build environment.
In some cases the tests fails on platforms such as windows because the path
contains a c:
was:
There is a number of tests that fail on Windows because Hadoop's distributed
file system does not allow colon character in DFS paths. Specifically, passing
in the following path to DFS:
{code}/c:/some/path{code}
would fail DFSUtil#isValidName check and cause the current operation to fail.
Any test that is using local absolute path in the context of the DFS will fail
because of this.
Assignee: Ivan Mitic
Summary: Many HDFS tests use a test path intended for local file system
tests (was: Address test failures related to Windows paths not being valid DFS
paths)
Many HDFS tests use a test path intended for local file system tests
Key: HADOOP-8487
URL: https://issues.apache.org/jira/browse/HADOOP-8487
Project: Hadoop Common
Issue Type: Bug
Components: test
Reporter: Ivan Mitic
Assignee: Ivan Mitic
Attachments: HADOOP-8487-branch-1-win(2).patch,
HADOOP-8487-branch-1-win(3).patch, HADOOP-8487-branch-1-win.alternate.patch,
HADOOP-8487-branch-1-win.patch
Many tests use a test path intended for local tests setup by build
environment. In some cases the tests fails on platforms such as windows
because the path contains a c:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8487) Many HDFS tests use a test path intended for local file system tests
[ https://issues.apache.org/jira/browse/HADOOP-8487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406639#comment-13406639 ] Sanjay Radia commented on HADOOP-8487: -- I have committed this to Hadoop-1 windows branch. Thanks Ivan. Ivan, please provide a patch for trunk and I will commit this to trunk. Many HDFS tests use a test path intended for local file system tests Key: HADOOP-8487 URL: https://issues.apache.org/jira/browse/HADOOP-8487 Project: Hadoop Common Issue Type: Bug Components: test Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8487-branch-1-win(2).patch, HADOOP-8487-branch-1-win(3).patch, HADOOP-8487-branch-1-win.alternate.patch, HADOOP-8487-branch-1-win.patch Many tests use a test path intended for local tests setup by build environment. In some cases the tests fails on platforms such as windows because the path contains a c: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8487) Address test failures related to Windows paths not being valid DFS paths
[
https://issues.apache.org/jira/browse/HADOOP-8487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406103#comment-13406103
]
Sanjay Radia commented on HADOOP-8487:
--
For a few places, if you leave the the variable name to TEST_DIR, rather than
change it to DFS_TEST_PATH, the patch becomes a lot smaller. TEST_DIR is a good
enough variable name.
Address test failures related to Windows paths not being valid DFS paths
Key: HADOOP-8487
URL: https://issues.apache.org/jira/browse/HADOOP-8487
Project: Hadoop Common
Issue Type: Bug
Components: test
Reporter: Ivan Mitic
Attachments: HADOOP-8487-branch-1-win(2).patch,
HADOOP-8487-branch-1-win.alternate.patch, HADOOP-8487-branch-1-win.patch
There is a number of tests that fail on Windows because Hadoop's distributed
file system does not allow colon character in DFS paths. Specifically,
passing in the following path to DFS:
{code}/c:/some/path{code}
would fail DFSUtil#isValidName check and cause the current operation to fail.
Any test that is using local absolute path in the context of the DFS will
fail because of this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8534) Some tests leave a config file open causing failure on windows
[
https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Radia updated HADOOP-8534:
-
Summary: Some tests leave a config file open causing failure on windows
(was: TestQueueManagerForJobKillAndJobPriority and
TestQueueManagerForJobKillAndNonDefaultQueue fail on Windows)
Some tests leave a config file open causing failure on windows
--
Key: HADOOP-8534
URL: https://issues.apache.org/jira/browse/HADOOP-8534
Project: Hadoop Common
Issue Type: Bug
Components: conf
Affects Versions: 1.0.0
Reporter: Ivan Mitic
Assignee: Ivan Mitic
Attachments: HADOOP-8534-branch-1-win_Parser(2).patch,
HADOOP-8534-branch-1-win_Parser.patch
Java xml parser keeps file locked after SAXException, causing the following
tests to fail:
- TestQueueManagerForJobKillAndJobPriority
- TestQueueManagerForJobKillAndNonDefaultQueue
{{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}}
is creating a temp config file with incorrect syntax. Later, the test tries
to delete/cleanup this file and this operation fails on Windows (as the file
is still open). From this point on, all subsequent tests fail because they
try to use the incorrect config file.
Forum references on the problem and the fix:
http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
https://forums.oracle.com/forums/thread.jspa?threadID=2046505start=0tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8534) Some tests leave a config file open causing failure on windows
[
https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjay Radia resolved HADOOP-8534.
--
Resolution: Fixed
Committed to Hadoop-1 windows branch. Thanks Ivan.
Some tests leave a config file open causing failure on windows
--
Key: HADOOP-8534
URL: https://issues.apache.org/jira/browse/HADOOP-8534
Project: Hadoop Common
Issue Type: Bug
Components: conf
Affects Versions: 1.0.0
Reporter: Ivan Mitic
Assignee: Ivan Mitic
Attachments: HADOOP-8534-branch-1-win_Parser(2).patch,
HADOOP-8534-branch-1-win_Parser.patch
Java xml parser keeps file locked after SAXException, causing the following
tests to fail:
- TestQueueManagerForJobKillAndJobPriority
- TestQueueManagerForJobKillAndNonDefaultQueue
{{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}}
is creating a temp config file with incorrect syntax. Later, the test tries
to delete/cleanup this file and this operation fails on Windows (as the file
is still open). From this point on, all subsequent tests fail because they
try to use the incorrect config file.
Forum references on the problem and the fix:
http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/
https://forums.oracle.com/forums/thread.jspa?threadID=2046505start=0tstart=0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7967) Need generalized multi-token filesystem support
[
https://issues.apache.org/jira/browse/HADOOP-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398740#comment-13398740
]
Sanjay Radia commented on HADOOP-7967:
--
Daryn, rather than do this in two or three steps, let us do a single patch to
address this problem completely. I have summarized our discussion in
MAPREDUCE-3825 in this
[comment.|https://issues.apache.org/jira/browse/MAPREDUCE-3825?focusedCommentId=13398726page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13398726]
Need generalized multi-token filesystem support
---
Key: HADOOP-7967
URL: https://issues.apache.org/jira/browse/HADOOP-7967
Project: Hadoop Common
Issue Type: Bug
Components: fs, security
Affects Versions: 0.23.1, 0.24.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-7967-2.patch, HADOOP-7967-3.patch,
HADOOP-7967-4.patch, HADOOP-7967-compat.patch, HADOOP-7967.patch
Multi-token filesystem support and its interactions with the MR
{{TokenCache}} is problematic. The {{TokenCache}} tries to assume it has the
knowledge to know if the tokens for a filesystem are available, which it
can't possibly know for multi-token filesystems. Filtered filesystems are
also problematic, such as har on viewfs. When mergeFs is implemented, it too
will become a problem with the current implementation. Currently
{{FileSystem}} will leak tokens even when some tokens are already present.
The decision for token acquisition, and which tokens, should be pushed all
the way down into the {{FileSystem}} level. The {{TokenCache}} should be
ignorant and simply request tokens from each {{FileSystem}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8486) Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor
[ https://issues.apache.org/jira/browse/HADOOP-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398895#comment-13398895 ] Sanjay Radia commented on HADOOP-8486: -- This patch also directly applies to trunk - can you please provide a trunk patch. Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor -- Key: HADOOP-8486 URL: https://issues.apache.org/jira/browse/HADOOP-8486 Project: Hadoop Common Issue Type: Bug Components: fs, io Affects Versions: 1.0.2, 1-win Reporter: Kanna Karanam Assignee: Kanna Karanam Fix For: 1-win Attachments: HADOOP-8486-branch-1-win-(2).patch, HADOOP-8486-branch-1-win-(3).patch, HADOOP-8486-branch-1-win-(4).patch, HADOOP-8486-branch-1-win-(5).patch, HADOOP-8486-branch-1-win.patch I noticed this problem while I am working on porting HIVE to work on windows. Hive is attempting to create this class object to validate the file format and end up with resource leak. Because of this leak, we can’t move, rename or delete the files on windows when there is an open file handle whereas in UNIX we can perform all these operation with no issues even with open file handles. Please suggest me if you similar issues in any other places. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8440) HarFileSystem.decodeHarURI fails for URIs whose host contains numbers
[ https://issues.apache.org/jira/browse/HADOOP-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397913#comment-13397913 ] Sanjay Radia commented on HADOOP-8440: -- Review and committed (HADOOP-8440-branch-1-win.2.patch) to hadoop-1 windows branch. HarFileSystem.decodeHarURI fails for URIs whose host contains numbers - Key: HADOOP-8440 URL: https://issues.apache.org/jira/browse/HADOOP-8440 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Priority: Minor Attachments: HADOOP-8440-2-branch-1-win.patch, HADOOP-8440-branch-1-win.2.patch, HADOOP-8440-branch-1-win.patch, HADOOP-8440-branch-1-win.patch, HADOOP-8440-trunk.patch, HADOOP-8440-trunk.patch For example, HarFileSystem.decodeHarURI will fail for the following URI: har://hdfs-127.0.0.1:51040/user -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8409) Fix TestCommandLineJobSubmission and TestGenericOptionsParser to work for windows
[ https://issues.apache.org/jira/browse/HADOOP-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8409: - Summary: Fix TestCommandLineJobSubmission and TestGenericOptionsParser to work for windows (was: Address Hadoop path related issues on Windows) Rename title to reflect the narrower scope. Fix TestCommandLineJobSubmission and TestGenericOptionsParser to work for windows - Key: HADOOP-8409 URL: https://issues.apache.org/jira/browse/HADOOP-8409 Project: Hadoop Common Issue Type: Bug Components: fs, test, util Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8409-branch-1-win.2.patch, HADOOP-8409-branch-1-win.3.patch, HADOOP-8409-branch-1-win.4.patch, HADOOP-8409-branch-1-win.patch Original Estimate: 168h Remaining Estimate: 168h There are multiple places in prod and test code where Windows paths are not handled properly. From a high level this could be summarized with: 1. Windows paths are not necessarily valid DFS paths (while Unix paths are) 2. Windows paths are not necessarily valid URIs (while Unix paths are) #1 causes a number of tests to fail because they implicitly assume that local paths are valid DFS paths (by extracting the DFS test path from for example test.build.data property) #2 causes issues when URIs are directly created on path strings passed in by the user -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8409) Fix TestCommandLineJobSubmission and TestGenericOptionsParser to work for windows
[ https://issues.apache.org/jira/browse/HADOOP-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398029#comment-13398029 ] Sanjay Radia commented on HADOOP-8409: -- Committed to hadoop-1 windows branch. Thanks Ivan. Fix TestCommandLineJobSubmission and TestGenericOptionsParser to work for windows - Key: HADOOP-8409 URL: https://issues.apache.org/jira/browse/HADOOP-8409 Project: Hadoop Common Issue Type: Bug Components: fs, test, util Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8409-branch-1-win.2.patch, HADOOP-8409-branch-1-win.3.patch, HADOOP-8409-branch-1-win.4.patch, HADOOP-8409-branch-1-win.patch Original Estimate: 168h Remaining Estimate: 168h There are multiple places in prod and test code where Windows paths are not handled properly. From a high level this could be summarized with: 1. Windows paths are not necessarily valid DFS paths (while Unix paths are) 2. Windows paths are not necessarily valid URIs (while Unix paths are) #1 causes a number of tests to fail because they implicitly assume that local paths are valid DFS paths (by extracting the DFS test path from for example test.build.data property) #2 causes issues when URIs are directly created on path strings passed in by the user -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8454) Fix the ‘chmod =[perm]’ bug in winutils
[ https://issues.apache.org/jira/browse/HADOOP-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8454: - Attachment: HADOOP-8454-2-branch-1-win.patch ran patch through dos2unix Fix the ‘chmod =[perm]’ bug in winutils --- Key: HADOOP-8454 URL: https://issues.apache.org/jira/browse/HADOOP-8454 Project: Hadoop Common Issue Type: Bug Components: native Affects Versions: 1.1.0, 0.24.0 Reporter: Chuan Liu Assignee: Chuan Liu Priority: Minor Attachments: HADOOP-8454-2-branch-1-win.patch, HADOOP-8454-branch-1-win.patch The original patch for [Hadoop-8235|https://issues.apache.org/jira/browse/HADOOP-8235] contained a bug for ‘chmod’ implantation. The logic to compute new access mask when ‘chmod’ mode string has ‘=’ in them is incorrect. For example, ‘winutils chmod o=g foo’ will result wrong permission settings for the file ‘foo’. The Jira is created to track the bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8454) Fix the ‘chmod =[perm]’ bug in winutils
[ https://issues.apache.org/jira/browse/HADOOP-8454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8454. -- Resolution: Fixed Reviewed and committed patch to Hadoop-1 windows branch. Thanks Chuan Lin. Fix the ‘chmod =[perm]’ bug in winutils --- Key: HADOOP-8454 URL: https://issues.apache.org/jira/browse/HADOOP-8454 Project: Hadoop Common Issue Type: Bug Components: native Affects Versions: 1.1.0, 0.24.0 Reporter: Chuan Liu Assignee: Chuan Liu Priority: Minor Attachments: HADOOP-8454-2-branch-1-win.patch, HADOOP-8454-branch-1-win.patch The original patch for [Hadoop-8235|https://issues.apache.org/jira/browse/HADOOP-8235] contained a bug for ‘chmod’ implantation. The logic to compute new access mask when ‘chmod’ mode string has ‘=’ in them is incorrect. For example, ‘winutils chmod o=g foo’ will result wrong permission settings for the file ‘foo’. The Jira is created to track the bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8486) Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor
[ https://issues.apache.org/jira/browse/HADOOP-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8486: - Attachment: HADOOP-8486-branch-1-win-(4).patch Ran patch through dos2unix Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor -- Key: HADOOP-8486 URL: https://issues.apache.org/jira/browse/HADOOP-8486 Project: Hadoop Common Issue Type: Bug Components: fs, io Affects Versions: 1.0.2, 1-win Reporter: Kanna Karanam Assignee: Kanna Karanam Fix For: 1-win Attachments: HADOOP-8486-branch-1-win-(2).patch, HADOOP-8486-branch-1-win-(3).patch, HADOOP-8486-branch-1-win-(4).patch, HADOOP-8486-branch-1-win.patch I noticed this problem while I am working on porting HIVE to work on windows. Hive is attempting to create this class object to validate the file format and end up with resource leak. Because of this leak, we can’t move, rename or delete the files on windows when there is an open file handle whereas in UNIX we can perform all these operation with no issues even with open file handles. Please suggest me if you similar issues in any other places. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8486) Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor
[ https://issues.apache.org/jira/browse/HADOOP-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8486: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to Hadoop-1 windows branch. Thanks Kanna. Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor -- Key: HADOOP-8486 URL: https://issues.apache.org/jira/browse/HADOOP-8486 Project: Hadoop Common Issue Type: Bug Components: fs, io Affects Versions: 1.0.2, 1-win Reporter: Kanna Karanam Assignee: Kanna Karanam Fix For: 1-win Attachments: HADOOP-8486-branch-1-win-(2).patch, HADOOP-8486-branch-1-win-(3).patch, HADOOP-8486-branch-1-win-(4).patch, HADOOP-8486-branch-1-win.patch I noticed this problem while I am working on porting HIVE to work on windows. Hive is attempting to create this class object to validate the file format and end up with resource leak. Because of this leak, we can’t move, rename or delete the files on windows when there is an open file handle whereas in UNIX we can perform all these operation with no issues even with open file handles. Please suggest me if you similar issues in any other places. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7967) Need generalized multi-token filesystem support
[
https://issues.apache.org/jira/browse/HADOOP-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291143#comment-13291143
]
Sanjay Radia commented on HADOOP-7967:
--
@Daryn ... so would it be reasonable to commit this backward-compatible change,
with an immediate followup jira for the new apis?..
Can you please describe what the patch does and if it is proper subset of the
the originally agreed solution and what will remain for the follow up jira?
Need generalized multi-token filesystem support
---
Key: HADOOP-7967
URL: https://issues.apache.org/jira/browse/HADOOP-7967
Project: Hadoop Common
Issue Type: Bug
Components: fs, security
Affects Versions: 0.23.1, 0.24.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
Attachments: HADOOP-7967-2.patch, HADOOP-7967-3.patch,
HADOOP-7967-4.patch, HADOOP-7967-compat.patch, HADOOP-7967.patch
Multi-token filesystem support and its interactions with the MR
{{TokenCache}} is problematic. The {{TokenCache}} tries to assume it has the
knowledge to know if the tokens for a filesystem are available, which it
can't possibly know for multi-token filesystems. Filtered filesystems are
also problematic, such as har on viewfs. When mergeFs is implemented, it too
will become a problem with the current implementation. Currently
{{FileSystem}} will leak tokens even when some tokens are already present.
The decision for token acquisition, and which tokens, should be pushed all
the way down into the {{FileSystem}} level. The {{TokenCache}} should be
ignorant and simply request tokens from each {{FileSystem}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8473) Update Balancer to support new NetworkTopology with NodeGroup
[ https://issues.apache.org/jira/browse/HADOOP-8473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288676#comment-13288676 ] Sanjay Radia commented on HADOOP-8473: -- There are two separate problems here as mentioned in your description - please split into two separate jiras: * correctness - two replicas are not on the same node * performance optimization - choose the target and source node on the same node group for balancing as the first priority. Update Balancer to support new NetworkTopology with NodeGroup - Key: HADOOP-8473 URL: https://issues.apache.org/jira/browse/HADOOP-8473 Project: Hadoop Common Issue Type: Sub-task Components: util Affects Versions: 1.0.0, 2.0.0-alpha Reporter: Junping Du Assignee: Junping Du Attachments: HADOOP-8473-Balancer-NodeGroup-aware.patch Since the Balancer is a Hadoop Tool, it was updated to be directly aware of four-layer hierarchy instead of creating an alternative Balancer implementation. To accommodate extensibility, a new protected method, doChooseNodesForCustomFaultDomain is now called from the existing chooseNodes method so that a subclass of the Balancer could customize the balancer algotirhm for other failure and locality topologies. An alternative option is to encapsulate the algorithm used for the four-layer hierarchy into a collaborating strategy class. The key changes introduced to support a four-layer hierarchy were to override the algorithm of choosing source, target pairs for balancing. Unit tests were created to test the new algorithm. The algorithm now makes sure to choose the target and source node on the same node group for balancing as the first priority. Then the overall balancing policy is: first doing balancing between nodes within the same nodegroup then the same rack and off rack at last. Also, we need to check no duplicated replicas live in the same node group after balancing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8101) Access Control support for Non-secure deployment of Hadoop on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8101. -- Resolution: Fixed Target Version/s: HADOOP-1-Windows (was: 1.1.0, 0.24.0) Access Control support for Non-secure deployment of Hadoop on Windows - Key: HADOOP-8101 URL: https://issues.apache.org/jira/browse/HADOOP-8101 Project: Hadoop Common Issue Type: Improvement Components: native Reporter: Sanjay Radia Attachments: security.patch, security1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8411) TestStorageDirecotyFailure, TestTaskLogsTruncater, TestWebHdfsUrl and TestSecurityUtil fail on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8411: - Attachment: HADOOP-8411-2-branch-1-win.patch Updated patch run through dos2unix TestStorageDirecotyFailure, TestTaskLogsTruncater, TestWebHdfsUrl and TestSecurityUtil fail on Windows -- Key: HADOOP-8411 URL: https://issues.apache.org/jira/browse/HADOOP-8411 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 1.1.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8411-2-branch-1-win.patch, HADOOP-8411-branch-1-win.patch, HADOOP-8411-branch-1-win.patch, HADOOP-8411-branch-1-win.patch Original Estimate: 48h Remaining Estimate: 48h Jira tracking failures from the summary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8411) TestStorageDirecotyFailure, TestTaskLogsTruncater, TestWebHdfsUrl and TestSecurityUtil fail on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8411. -- Resolution: Fixed Target Version/s: HADOOP-1-Windows (was: 1.1.0) Committed patch. Thanks Ivan. TestStorageDirecotyFailure, TestTaskLogsTruncater, TestWebHdfsUrl and TestSecurityUtil fail on Windows -- Key: HADOOP-8411 URL: https://issues.apache.org/jira/browse/HADOOP-8411 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 1.1.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8411-2-branch-1-win.patch, HADOOP-8411-branch-1-win.patch, HADOOP-8411-branch-1-win.patch, HADOOP-8411-branch-1-win.patch Original Estimate: 48h Remaining Estimate: 48h Jira tracking failures from the summary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8440) HarFileSystem.decodeHarURI fails for URIs whose host contains numbers
[ https://issues.apache.org/jira/browse/HADOOP-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8440: - Attachment: HADOOP-8440-2-branch-1-win.patch Updated patch - ran through dos2unix HarFileSystem.decodeHarURI fails for URIs whose host contains numbers - Key: HADOOP-8440 URL: https://issues.apache.org/jira/browse/HADOOP-8440 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Priority: Minor Attachments: HADOOP-8440-2-branch-1-win.patch, HADOOP-8440-branch-1-win.patch For example, HarFileSystem.decodeHarURI will fail for the following URI: har://hdfs-127.0.0.1:51040/user -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8440) HarFileSystem.decodeHarURI fails for URIs whose host contains numbers
[ https://issues.apache.org/jira/browse/HADOOP-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8440. -- Resolution: Fixed Target Version/s: HADOOP-1-Windows (was: 1.1.0) Committed to the Windows branch. Thanks Ivan. HarFileSystem.decodeHarURI fails for URIs whose host contains numbers - Key: HADOOP-8440 URL: https://issues.apache.org/jira/browse/HADOOP-8440 Project: Hadoop Common Issue Type: Bug Components: fs Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Priority: Minor Attachments: HADOOP-8440-2-branch-1-win.patch, HADOOP-8440-branch-1-win.patch For example, HarFileSystem.decodeHarURI will fail for the following URI: har://hdfs-127.0.0.1:51040/user -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8374) Improve support for hard link manipulation on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13287083#comment-13287083 ] Sanjay Radia commented on HADOOP-8374: -- +1 on patch Improve support for hard link manipulation on Windows - Key: HADOOP-8374 URL: https://issues.apache.org/jira/browse/HADOOP-8374 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.0 Reporter: Bikas Saha Assignee: Bikas Saha Attachments: HADOOP-8374-1.patch, HADOOP-8374-branch-1-win_hardlinks.patch, HADOOP-8374-branch-1-win_hardlinks.patch Hard link support for Windows does not work properly. There is some refactoring needed in the code. Also, the code currently executes the fsutil command to manipulate hard links. fsutil requires admin privileges on recent versions of Windows. The main features needed are the ability to create hard links to a file and count the number of hard links to a file. So we could use mklink to create hard links and write a custom executable to count hard links. Or use a custom executable to do both using Windows API's. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8374) Improve support for hard link manipulation on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8374. -- Resolution: Fixed Target Version/s: HADOOP-1-Windows (was: 1.1.0) Committed to windows branch. Improve support for hard link manipulation on Windows - Key: HADOOP-8374 URL: https://issues.apache.org/jira/browse/HADOOP-8374 Project: Hadoop Common Issue Type: Bug Affects Versions: 1.0.0 Reporter: Bikas Saha Assignee: Bikas Saha Attachments: HADOOP-8374-1.patch, HADOOP-8374-branch-1-win_hardlinks.patch, HADOOP-8374-branch-1-win_hardlinks.patch Hard link support for Windows does not work properly. There is some refactoring needed in the code. Also, the code currently executes the fsutil command to manipulate hard links. fsutil requires admin privileges on recent versions of Windows. The main features needed are the ability to create hard links to a file and count the number of hard links to a file. So we could use mklink to create hard links and write a custom executable to count hard links. Or use a custom executable to do both using Windows API's. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8223) Initial patch for branch-1-win
[ https://issues.apache.org/jira/browse/HADOOP-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8223. -- Resolution: Fixed Target Version/s: HADOOP-1-Windows Initial patch for branch-1-win -- Key: HADOOP-8223 URL: https://issues.apache.org/jira/browse/HADOOP-8223 Project: Hadoop Common Issue Type: Sub-task Components: native Reporter: Sanjay Radia Attachments: hadoop-8223-2.patch, hadoop-8223.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8234) Enable user group mappings on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8234. -- Resolution: Fixed Target Version/s: HADOOP-1-Windows (was: 1.1.0, 0.24.0) Enable user group mappings on Windows - Key: HADOOP-8234 URL: https://issues.apache.org/jira/browse/HADOOP-8234 Project: Hadoop Common Issue Type: Sub-task Components: native Affects Versions: 1.0.0 Reporter: Bikas Saha Assignee: Bikas Saha Attachments: HADOOP-8234.branch-1-win.patch, HADOOP-8234.branch-1-win.patch The initial patch submitted is missing mapping of users to groups. A number of test failures are related to this. The jira tracks adding this support. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8235) Support file permissions and ownership on Windows for RawLocalFileSystem
[ https://issues.apache.org/jira/browse/HADOOP-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8235: - Resolution: Fixed Target Version/s: HADOOP-1-Windows (was: 1.1.0, 0.24.0) Status: Resolved (was: Patch Available) Support file permissions and ownership on Windows for RawLocalFileSystem Key: HADOOP-8235 URL: https://issues.apache.org/jira/browse/HADOOP-8235 Project: Hadoop Common Issue Type: Sub-task Components: native Affects Versions: 1.1.0 Reporter: Bikas Saha Assignee: Chuan Liu Attachments: HADOOP-8235-2-branch-1-win.patch, HADOOP-8235-branch-1-win.patch The initial patch submitted on HADOOP-8223 does not have ability to set file permissions on Windows. This is causing tests to fail. Jira tracks adding support to enable file permissions and ownership changes on Windows -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8412) TestModTime, TestDelegationToken and TestAuthenticationToken fail intermittently on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8412: - Resolution: Fixed Target Version/s: HADOOP-1-Windows (was: 1.1.0) Status: Resolved (was: Patch Available) TestModTime, TestDelegationToken and TestAuthenticationToken fail intermittently on Windows --- Key: HADOOP-8412 URL: https://issues.apache.org/jira/browse/HADOOP-8412 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8412-branch-1-win.patch Jira tracking failures from the summary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8235) Support file permissions and ownership on Windows for RawLocalFileSystem
[ https://issues.apache.org/jira/browse/HADOOP-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8235: - Attachment: HADOOP-8235-2-branch-1-win.patch Please use dos2unix to convert patch files to unix format - it deals with the ^Ms Uploaded converted patch. Support file permissions and ownership on Windows for RawLocalFileSystem Key: HADOOP-8235 URL: https://issues.apache.org/jira/browse/HADOOP-8235 Project: Hadoop Common Issue Type: Sub-task Components: native Affects Versions: 1.1.0 Reporter: Bikas Saha Assignee: Chuan Liu Attachments: HADOOP-8235-2-branch-1-win.patch, HADOOP-8235-branch-1-win.patch The initial patch submitted on HADOOP-8223 does not have ability to set file permissions on Windows. This is causing tests to fail. Jira tracks adding support to enable file permissions and ownership changes on Windows -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8235) Support file permissions and ownership on Windows for RawLocalFileSystem
[ https://issues.apache.org/jira/browse/HADOOP-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13286256#comment-13286256 ] Sanjay Radia commented on HADOOP-8235: -- Please file jiras to addresses the issues Bikas has raised if needed. In the meantime I will commit the patch to the branch because this patch fixes a large number of tests. Support file permissions and ownership on Windows for RawLocalFileSystem Key: HADOOP-8235 URL: https://issues.apache.org/jira/browse/HADOOP-8235 Project: Hadoop Common Issue Type: Sub-task Components: native Affects Versions: 1.1.0 Reporter: Bikas Saha Assignee: Chuan Liu Attachments: HADOOP-8235-2-branch-1-win.patch, HADOOP-8235-branch-1-win.patch The initial patch submitted on HADOOP-8223 does not have ability to set file permissions on Windows. This is causing tests to fail. Jira tracks adding support to enable file permissions and ownership changes on Windows -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8367) Better document the declaringClassProtocolName in the rpc headers better
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8367: - Attachment: hadoop-8367-2.patch Better document the declaringClassProtocolName in the rpc headers better Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8367-1.patch, hadoop-8367-2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8367) Better document the declaringClassProtocolName in the rpc headers better
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8367: - Status: Open (was: Patch Available) Better document the declaringClassProtocolName in the rpc headers better Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8367-1.patch, hadoop-8367-2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8367) Improve documentation of declaringClassProtocolName in rpc headers
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8367: - Summary: Improve documentation of declaringClassProtocolName in rpc headers (was: Better document the declaringClassProtocolName in the rpc headers better) Improve documentation of declaringClassProtocolName in rpc headers --- Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0-alpha Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8367-1.patch, hadoop-8367-2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8367) Improve documentation of declaringClassProtocolName in rpc headers
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8367: - Resolution: Fixed Fix Version/s: 2.0.1-alpha Status: Resolved (was: Patch Available) New tests not needed - javadoc improvements. Committed. Improve documentation of declaringClassProtocolName in rpc headers --- Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0-alpha Reporter: Sanjay Radia Assignee: Sanjay Radia Fix For: 2.0.1-alpha Attachments: hadoop-8367-1.patch, hadoop-8367-2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8409) Address Hadoop path related issues on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13280756#comment-13280756 ] Sanjay Radia commented on HADOOP-8409: -- Path(URI) should continue to be supported. getUriPath: The problematic URI would be the following: file://test:8000/c:/some/path file:/// should not allow authority or port - it is for local file systems. System.getProperty(test.build.dir, build/test) Agree with Daryn. However I am fine with letting this into the *branch* *temporarily* so that you can get most unit tests pass. But it will have to be fixed before we merge with and of the mainlines. (This is commit then review branch.) Address Hadoop path related issues on Windows - Key: HADOOP-8409 URL: https://issues.apache.org/jira/browse/HADOOP-8409 Project: Hadoop Common Issue Type: Bug Components: fs, test, util Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8409-branch-1-win.patch Original Estimate: 168h Remaining Estimate: 168h There are multiple places in prod and test code where Windows paths are not handled properly. From a high level this could be summarized with: 1. Windows paths are not necessarily valid DFS paths (while Unix paths are) 2. Windows paths are not necessarily valid URIs (while Unix paths are) #1 causes a number of tests to fail because they implicitly assume that local paths are valid DFS paths (by extracting the DFS test path from for example test.build.data property) #2 causes issues when URIs are directly created on path strings passed in by the user -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8412) TestModTime, TestDelegationToken and TestAuthenticationToken fail intermittently on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13280773#comment-13280773 ] Sanjay Radia commented on HADOOP-8412: -- Thanks Ivan, I have commit this to branch hadoop-1-windows. TestModTime, TestDelegationToken and TestAuthenticationToken fail intermittently on Windows --- Key: HADOOP-8412 URL: https://issues.apache.org/jira/browse/HADOOP-8412 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8412-branch-1-win.patch Jira tracking failures from the summary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8409) Address Hadoop path related issues on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8409: - Assignee: Ivan Mitic Address Hadoop path related issues on Windows - Key: HADOOP-8409 URL: https://issues.apache.org/jira/browse/HADOOP-8409 Project: Hadoop Common Issue Type: Bug Components: fs, test, util Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8409-branch-1-win.patch Original Estimate: 168h Remaining Estimate: 168h There are multiple places in prod and test code where Windows paths are not handled properly. From a high level this could be summarized with: 1. Windows paths are not necessarily valid DFS paths (while Unix paths are) 2. Windows paths are not necessarily valid URIs (while Unix paths are) #1 causes a number of tests to fail because they implicitly assume that local paths are valid DFS paths (by extracting the DFS test path from for example test.build.data property) #2 causes issues when URIs are directly created on path strings passed in by the user -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8414) Address problems related to localhost resolving to 127.0.0.1 on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8414: - Assignee: Ivan Mitic Address problems related to localhost resolving to 127.0.0.1 on Windows --- Key: HADOOP-8414 URL: https://issues.apache.org/jira/browse/HADOOP-8414 Project: Hadoop Common Issue Type: Bug Components: fs, test Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Localhost resolves to 127.0.0.1 on Windows and that causes the following tests to fail: - TestHarFileSystem - TestCLI - TestSaslRPC This Jira tracks fixing these tests and other possible places that have similar issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8411) TestStorageDirecotyFailure, TestTaskLogsTruncater, TestWebHdfsUrl and TestSecurityUtil fail on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8411: - Assignee: Ivan Mitic TestStorageDirecotyFailure, TestTaskLogsTruncater, TestWebHdfsUrl and TestSecurityUtil fail on Windows -- Key: HADOOP-8411 URL: https://issues.apache.org/jira/browse/HADOOP-8411 Project: Hadoop Common Issue Type: Bug Components: util Affects Versions: 1.1.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Original Estimate: 48h Remaining Estimate: 48h Jira tracking failures from the summary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8412) TestModTime, TestDelegationToken and TestAuthenticationToken fail intermittently on Windows
[ https://issues.apache.org/jira/browse/HADOOP-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8412: - Assignee: Ivan Mitic TestModTime, TestDelegationToken and TestAuthenticationToken fail intermittently on Windows --- Key: HADOOP-8412 URL: https://issues.apache.org/jira/browse/HADOOP-8412 Project: Hadoop Common Issue Type: Bug Components: test Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8412-branch-1-win.patch Jira tracking failures from the summary. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Attachment: hadoop-8366-4.patch Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch, hadoop-8366-2.patch, hadoop-8366-3.patch, hadoop-8366-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Status: Patch Available (was: Open) Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch, hadoop-8366-2.patch, hadoop-8366-3.patch, hadoop-8366-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Status: Open (was: Patch Available) Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch, hadoop-8366-2.patch, hadoop-8366-3.patch, hadoop-8366-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Resolution: Fixed Status: Resolved (was: Patch Available) Addressed the comments. Committed. Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch, hadoop-8366-2.patch, hadoop-8366-3.patch, hadoop-8366-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8367) Better document the declaringClassProtocolName in the rpc headers better
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8367: - Summary: Better document the declaringClassProtocolName in the rpc headers better (was: ProtoBufRpcEngine's rpc request header does not need declaringClass name) Better document the declaringClassProtocolName in the rpc headers better Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8367-1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8367) Better document the declaringClassProtocolName in the rpc headers better
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8367: - Status: Patch Available (was: Open) Better document the declaringClassProtocolName in the rpc headers better Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8367-1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8367) ProtoBufRpcEngine's rpc request header does not need declaringClass name
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273757#comment-13273757 ] Sanjay Radia commented on HADOOP-8367: -- I was wrong here. Since the connection is reused, the declaringClassProtocolName is needed. Will better document this in the code; will change the jira title to do this. ProtoBufRpcEngine's rpc request header does not need declaringClass name Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8367-1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Target Version/s: 2.0.0 Affects Version/s: (was: 0.3.0) (was: 0.2.0) 2.0.0 Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch, hadoop-8366-2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Attachment: hadoop-8366-3.patch Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch, hadoop-8366-2.patch, hadoop-8366-3.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
Sanjay Radia created HADOOP-8366: Summary: Use ProtoBuf for RpcResponseHeader Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: HA Branch (HDFS-1623) Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Status: Patch Available (was: Open) Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: HA Branch (HDFS-1623) Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Attachment: hadoop-8366-1.patch Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: HA Branch (HDFS-1623) Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-7775) RPC Layer improvements to support protocol compatibility
[ https://issues.apache.org/jira/browse/HADOOP-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-7775. -- Resolution: Fixed All subtasks done. RPC Layer improvements to support protocol compatibility Key: HADOOP-7775 URL: https://issues.apache.org/jira/browse/HADOOP-7775 Project: Hadoop Common Issue Type: Improvement Reporter: Sanjay Radia Assignee: Sanjay Radia -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8367) ProtoBufRpcEngine's rpc request header does not need declaringClass name
Sanjay Radia created HADOOP-8367: Summary: ProtoBufRpcEngine's rpc request header does not need declaringClass name Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8367) ProtoBufRpcEngine's rpc request header does not need declaringClass name
[ https://issues.apache.org/jira/browse/HADOOP-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269881#comment-13269881 ] Sanjay Radia commented on HADOOP-8367: -- The declaring-class name was added to the writable rpc engine's header to deal with the VersionedProtocol. Not needed for PB since version number is handled differently. ProtoBufRpcEngine's rpc request header does not need declaringClass name Key: HADOOP-8367 URL: https://issues.apache.org/jira/browse/HADOOP-8367 Project: Hadoop Common Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Sanjay Radia Assignee: Sanjay Radia -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8366) Use ProtoBuf for RpcResponseHeader
[ https://issues.apache.org/jira/browse/HADOOP-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8366: - Attachment: hadoop-8366-2.patch Use ProtoBuf for RpcResponseHeader -- Key: HADOOP-8366 URL: https://issues.apache.org/jira/browse/HADOOP-8366 Project: Hadoop Common Issue Type: Improvement Affects Versions: 0.2.0, 0.3.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Priority: Blocker Attachments: hadoop-8366-1.patch, hadoop-8366-2.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8230) Enable sync by default and disable append
[ https://issues.apache.org/jira/browse/HADOOP-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13269286#comment-13269286 ] Sanjay Radia commented on HADOOP-8230: -- Couldn't the same be said for any new feature? Given that sync was fixed prior to the 1.0 release, I don't see why this should be considered an incompatible change. This was turned on in the 20 originally and then we had to turn it off due bugs. Given that the default in Hadoop 1 is off, why not leave it off and give a way to turn it on. The current default is off and I don't see a reason to change that default in 1.1. There are installations have that are using the current default. Can you please explain the reason the make this change? Enable sync by default and disable append - Key: HADOOP-8230 URL: https://issues.apache.org/jira/browse/HADOOP-8230 Project: Hadoop Common Issue Type: Improvement Affects Versions: 1.0.0 Reporter: Eli Collins Assignee: Eli Collins Fix For: 1.1.0 Attachments: hadoop-8230.txt Per HDFS-3120 for 1.x let's: - Always enable the sync path, which is currently only enabled if dfs.support.append is set - Remove the dfs.support.append configuration option. We'll keep the code paths though in case we ever fix append on branch-1, in which case we can add the config option back -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-8230) Enable sync by default and disable append
[ https://issues.apache.org/jira/browse/HADOOP-8230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13267596#comment-13267596 ] Sanjay Radia commented on HADOOP-8230: -- The sync fixes were a large number of individual fixes. They added risk for users that were not using the sync feature. Hence Sync was kept off by default for such users - this was a very conscious decision. Sync should be left off by default with an option to turn it on. This is an incompatible change. Enable sync by default and disable append - Key: HADOOP-8230 URL: https://issues.apache.org/jira/browse/HADOOP-8230 Project: Hadoop Common Issue Type: Improvement Affects Versions: 1.0.0 Reporter: Eli Collins Assignee: Eli Collins Fix For: 1.1.0 Attachments: hadoop-8230.txt Per HDFS-3120 for 1.x let's: - Always enable the sync path, which is currently only enabled if dfs.support.append is set - Remove the dfs.support.append configuration option. We'll keep the code paths though in case we ever fix append on branch-1, in which case we can add the config option back -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-5.patch Update patch against current trunk Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch, hadoop-8285-5.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-5-common.patch Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch, hadoop-8285-5-common.patch, hadoop-8285-5.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Status: Open (was: Patch Available) Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch, hadoop-8285-5-common.patch, hadoop-8285-5.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Resolution: Fixed Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Status: Resolved (was: Patch Available) COmmitted Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch, hadoop-8285-5-common.patch, hadoop-8285-5.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-4.patch Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Status: Patch Available (was: Open) Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Target Version/s: 2.0.0, 3.0.0 (was: 3.0.0, 2.0.0) Status: Open (was: Patch Available) Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-8285) Use ProtoBuf for RpcPayLoadHeader
[ https://issues.apache.org/jira/browse/HADOOP-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-8285: - Attachment: hadoop-8285-4-common.patch Use ProtoBuf for RpcPayLoadHeader - Key: HADOOP-8285 URL: https://issues.apache.org/jira/browse/HADOOP-8285 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: hadoop-8285-1-common.patch, hadoop-8285-1.patch, hadoop-8285-2-common.patch, hadoop-8285-2.patch, hadoop-8285-3-common.patch, hadoop-8285-3.patch, hadoop-8285-4-common.patch, hadoop-8285-4.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-7119) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles
[ https://issues.apache.org/jira/browse/HADOOP-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-7119. -- Resolution: Fixed committed to branch-0.20-security to go into 20.205 add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles -- Key: HADOOP-7119 URL: https://issues.apache.org/jira/browse/HADOOP-7119 Project: Hadoop Common Issue Type: New Feature Components: security Affects Versions: 0.23.0 Environment: all Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.20.205.0, 0.23.0 Attachments: HADOOP-7119v3.patch, HADOOP-7119v4-amendment.patch, HADOOP-7119v4.patch, HADOOP-7119v5.patch, HADOOP-7119v6.patch, ha-common-01.patch, ha-common-02.patch, ha-commons.patch, spnego-20-security.patch, spnego-20-security2.patch, spnego-20-security3.patch, spnego-20-security4.patch Currently the JT/NN/DN/TT web-consoles don't support any form of authentication. Hadoop RPC API already supports Kerberos authentication. Kerberos enables single sign-on. Popular browsers (Firefox and Internet Explorer) have support for Kerberos HTTP SPNEGO. Adding support for Kerberos HTTP SPNEGO to Hadoop web consoles would provide a unified authentication mechanism and single sign-on for Hadoop web UI and Hadoop RPC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7119) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles
[ https://issues.apache.org/jira/browse/HADOOP-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7119: - Attachment: spnego-20-security2.patch Updated path with AuthenticationFilterInitializer.java add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles -- Key: HADOOP-7119 URL: https://issues.apache.org/jira/browse/HADOOP-7119 Project: Hadoop Common Issue Type: New Feature Components: security Affects Versions: 0.23.0 Environment: all Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.20.205.0, 0.23.0 Attachments: HADOOP-7119v3.patch, HADOOP-7119v4-amendment.patch, HADOOP-7119v4.patch, HADOOP-7119v5.patch, HADOOP-7119v6.patch, ha-common-01.patch, ha-common-02.patch, ha-commons.patch, spnego-20-security.patch, spnego-20-security2.patch Currently the JT/NN/DN/TT web-consoles don't support any form of authentication. Hadoop RPC API already supports Kerberos authentication. Kerberos enables single sign-on. Popular browsers (Firefox and Internet Explorer) have support for Kerberos HTTP SPNEGO. Adding support for Kerberos HTTP SPNEGO to Hadoop web consoles would provide a unified authentication mechanism and single sign-on for Hadoop web UI and Hadoop RPC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7119) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles
[ https://issues.apache.org/jira/browse/HADOOP-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7119: - Attachment: spnego-20-security3.patch updated patch Still working on site.xml - this is in apt and will need to be ported to forrest for 20. add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles -- Key: HADOOP-7119 URL: https://issues.apache.org/jira/browse/HADOOP-7119 Project: Hadoop Common Issue Type: New Feature Components: security Affects Versions: 0.23.0 Environment: all Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.20.205.0, 0.23.0 Attachments: HADOOP-7119v3.patch, HADOOP-7119v4-amendment.patch, HADOOP-7119v4.patch, HADOOP-7119v5.patch, HADOOP-7119v6.patch, ha-common-01.patch, ha-common-02.patch, ha-commons.patch, spnego-20-security.patch, spnego-20-security2.patch, spnego-20-security3.patch Currently the JT/NN/DN/TT web-consoles don't support any form of authentication. Hadoop RPC API already supports Kerberos authentication. Kerberos enables single sign-on. Popular browsers (Firefox and Internet Explorer) have support for Kerberos HTTP SPNEGO. Adding support for Kerberos HTTP SPNEGO to Hadoop web consoles would provide a unified authentication mechanism and single sign-on for Hadoop web UI and Hadoop RPC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7119) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles
[ https://issues.apache.org/jira/browse/HADOOP-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7119: - Attachment: spnego-20-security4.patch add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles -- Key: HADOOP-7119 URL: https://issues.apache.org/jira/browse/HADOOP-7119 Project: Hadoop Common Issue Type: New Feature Components: security Affects Versions: 0.23.0 Environment: all Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.20.205.0, 0.23.0 Attachments: HADOOP-7119v3.patch, HADOOP-7119v4-amendment.patch, HADOOP-7119v4.patch, HADOOP-7119v5.patch, HADOOP-7119v6.patch, ha-common-01.patch, ha-common-02.patch, ha-commons.patch, spnego-20-security.patch, spnego-20-security2.patch, spnego-20-security3.patch, spnego-20-security4.patch Currently the JT/NN/DN/TT web-consoles don't support any form of authentication. Hadoop RPC API already supports Kerberos authentication. Kerberos enables single sign-on. Popular browsers (Firefox and Internet Explorer) have support for Kerberos HTTP SPNEGO. Adding support for Kerberos HTTP SPNEGO to Hadoop web consoles would provide a unified authentication mechanism and single sign-on for Hadoop web UI and Hadoop RPC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7119) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles
[ https://issues.apache.org/jira/browse/HADOOP-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13101727#comment-13101727 ] Sanjay Radia commented on HADOOP-7119: -- Last patch has the site stuff. Ignore my previous comment about apt and forrest; I misunderstood Alejandro. add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles -- Key: HADOOP-7119 URL: https://issues.apache.org/jira/browse/HADOOP-7119 Project: Hadoop Common Issue Type: New Feature Components: security Affects Versions: 0.23.0 Environment: all Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.20.205.0, 0.23.0 Attachments: HADOOP-7119v3.patch, HADOOP-7119v4-amendment.patch, HADOOP-7119v4.patch, HADOOP-7119v5.patch, HADOOP-7119v6.patch, ha-common-01.patch, ha-common-02.patch, ha-commons.patch, spnego-20-security.patch, spnego-20-security2.patch, spnego-20-security3.patch, spnego-20-security4.patch Currently the JT/NN/DN/TT web-consoles don't support any form of authentication. Hadoop RPC API already supports Kerberos authentication. Kerberos enables single sign-on. Popular browsers (Firefox and Internet Explorer) have support for Kerberos HTTP SPNEGO. Adding support for Kerberos HTTP SPNEGO to Hadoop web consoles would provide a unified authentication mechanism and single sign-on for Hadoop web UI and Hadoop RPC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100522#comment-13100522 ] Sanjay Radia commented on HADOOP-7524: -- It is incompatible only wrt to wire protocol, public APIs apis are compatible. Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 0.24.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Fix For: 0.24.0 Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch, rpcCommitted.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100523#comment-13100523 ] Sanjay Radia commented on HADOOP-7524: -- we should backport this to 0.23 Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Affects Versions: 0.24.0 Reporter: Sanjay Radia Assignee: Sanjay Radia Fix For: 0.24.0 Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch, rpcCommitted.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Attachment: rpcCommitted.patch Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch, rpcCommitted.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7119) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles
[ https://issues.apache.org/jira/browse/HADOOP-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7119: - Attachment: spnego-20-security.patch Ported patch to 20-security (after the renames of HADOOP-7579) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles -- Key: HADOOP-7119 URL: https://issues.apache.org/jira/browse/HADOOP-7119 Project: Hadoop Common Issue Type: New Feature Components: security Affects Versions: 0.23.0 Environment: all Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.20.205.0, 0.23.0 Attachments: HADOOP-7119v3.patch, HADOOP-7119v4-amendment.patch, HADOOP-7119v4.patch, HADOOP-7119v5.patch, HADOOP-7119v6.patch, ha-common-01.patch, ha-common-02.patch, ha-commons.patch, spnego-20-security.patch Currently the JT/NN/DN/TT web-consoles don't support any form of authentication. Hadoop RPC API already supports Kerberos authentication. Kerberos enables single sign-on. Popular browsers (Firefox and Internet Explorer) have support for Kerberos HTTP SPNEGO. Adding support for Kerberos HTTP SPNEGO to Hadoop web consoles would provide a unified authentication mechanism and single sign-on for Hadoop web UI and Hadoop RPC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7119) add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles
[ https://issues.apache.org/jira/browse/HADOOP-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7119: - Fix Version/s: 0.20.205.0 add Kerberos HTTP SPNEGO authentication support to Hadoop JT/NN/DN/TT web-consoles -- Key: HADOOP-7119 URL: https://issues.apache.org/jira/browse/HADOOP-7119 Project: Hadoop Common Issue Type: New Feature Components: security Affects Versions: 0.23.0 Environment: all Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.20.205.0, 0.23.0 Attachments: HADOOP-7119v3.patch, HADOOP-7119v4-amendment.patch, HADOOP-7119v4.patch, HADOOP-7119v5.patch, HADOOP-7119v6.patch, ha-common-01.patch, ha-common-02.patch, ha-commons.patch, spnego-20-security.patch Currently the JT/NN/DN/TT web-consoles don't support any form of authentication. Hadoop RPC API already supports Kerberos authentication. Kerberos enables single sign-on. Popular browsers (Firefox and Internet Explorer) have support for Kerberos HTTP SPNEGO. Adding support for Kerberos HTTP SPNEGO to Hadoop web consoles would provide a unified authentication mechanism and single sign-on for Hadoop web UI and Hadoop RPC. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed the patch (together with MapReduce-2887) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Hadoop Flags: [Incompatible change] writableRpcVersion has changed. Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7579) Rename package names from alfredo to auth
[ https://issues.apache.org/jira/browse/HADOOP-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094791#comment-13094791 ] Sanjay Radia commented on HADOOP-7579: -- It also applied fine for me. Rename package names from alfredo to auth - Key: HADOOP-7579 URL: https://issues.apache.org/jira/browse/HADOOP-7579 Project: Hadoop Common Issue Type: Task Components: security Affects Versions: 0.23.0, 0.24.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.23.0, 0.24.0 Attachments: HADOOP-7579v1.patch, HADOOP-7579v2.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Attachment: rpc8WithoutMR.patch Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Patch Available (was: Open) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Open (was: Patch Available) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch, rpc8WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Patch Available (was: Open) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Attachment: rpc7WithoutMR.patch New patch: Minor improvements to logging. Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Open (was: Patch Available) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch, rpc7WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Attachment: rpc6.patch Updated patch: * Incorporates Todd's nits * Fixes the HDFS test failure - added code to ignore protocol interfaces that throw exception on getProtocolVersion() as does NamenodeProotocol. * Minor fixes to make MR2's rpc work. Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Open (was: Patch Available) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Patch Available (was: Open) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Attachment: rpc6WithoutMR.patch rpc6WithoutMR.path removes the MR related changes which need to be submitted as a MR jira. Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Open (was: Patch Available) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Patch Available (was: Open) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt, rpc6.patch, rpc6WithoutMR.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7380) Add client failover functionality to o.a.h.io.(ipc|retry)
[
https://issues.apache.org/jira/browse/HADOOP-7380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091452#comment-13091452
]
Sanjay Radia commented on HADOOP-7380:
--
Thanks for the doc.
- Any suggestions for an alternate name to StandbyException - the IPC layer
should not know about Standby or Active. Perhaps RedirectException?
- Clearly one cannot the server to always respond with an exception (it won't
in a split brain situation).
Looks good otherwise. Please move to HA branch.
Add client failover functionality to o.a.h.io.(ipc|retry)
-
Key: HADOOP-7380
URL: https://issues.apache.org/jira/browse/HADOOP-7380
Project: Hadoop Common
Issue Type: Sub-task
Components: ipc
Affects Versions: 0.23.0
Reporter: Aaron T. Myers
Assignee: Aaron T. Myers
Fix For: 0.23.0
Attachments: hadoop-7380-hdfs-example.patch, hadoop-7380.0.patch,
hadoop-7380.1.patch, hadoop-7380.2.patch, hdfs-7380.3.patch
Implementing client failover will likely require changes to {{o.a.h.io.ipc}}
and/or {{o.a.h.io.retry}}. This JIRA is to track those changes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13090352#comment-13090352 ] Sanjay Radia commented on HADOOP-7524: -- I have the fix for the above. However I another test fails in HDFS that I am investigating - it appears unrelated. Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, nits.txt, rpc2.patch, rpc2_trunk.patch, rpc3.patch, rpc4.txt -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7524) Change RPC to allow multiple protocols including multuple versions of the same protocol
[ https://issues.apache.org/jira/browse/HADOOP-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia updated HADOOP-7524: - Status: Patch Available (was: Open) Change RPC to allow multiple protocols including multuple versions of the same protocol --- Key: HADOOP-7524 URL: https://issues.apache.org/jira/browse/HADOOP-7524 Project: Hadoop Common Issue Type: Improvement Components: ipc Reporter: Sanjay Radia Assignee: Sanjay Radia Attachments: newPatchFindbugsWarnings.html, rpc2.patch, rpc2_trunk.patch, rpc3.patch -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
