[jira] Updated: (MAPREDUCE-1528) TokenStorage should not be static
[ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-1528: - Attachment: MAPREDUCE-1528_yhadoop20.patch Renamed TestTokenStorage to TestJobCredentials. > TokenStorage should not be static > - > > Key: MAPREDUCE-1528 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Owen O'Malley >Assignee: Arun C Murthy > Attachments: MAPREDUCE-1528_yhadoop20.patch, > MAPREDUCE-1528_yhadoop20.patch, MAPREDUCE-1528_yhadoop20.patch, > MAPREDUCE-1528_yhadoop20.patch, MAPREDUCE-1528_yhadoop20.patch > > > Currently, TokenStorage is a singleton. This doesn't work for some use cases, > such as Oozie. I think that each Job should have a TokenStorage that is > associated it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1528) TokenStorage should not be static
[ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-1528: - Attachment: MAPREDUCE-1528_yhadoop20.patch Pretty-fied patch. > TokenStorage should not be static > - > > Key: MAPREDUCE-1528 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Owen O'Malley >Assignee: Arun C Murthy > Attachments: MAPREDUCE-1528_yhadoop20.patch, > MAPREDUCE-1528_yhadoop20.patch, MAPREDUCE-1528_yhadoop20.patch, > MAPREDUCE-1528_yhadoop20.patch > > > Currently, TokenStorage is a singleton. This doesn't work for some use cases, > such as Oozie. I think that each Job should have a TokenStorage that is > associated it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1528) TokenStorage should not be static
[ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839161#action_12839161 ] Owen O'Malley commented on MAPREDUCE-1528: -- Other than the commented out code, this looks fine for y20. +1 > TokenStorage should not be static > - > > Key: MAPREDUCE-1528 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Owen O'Malley >Assignee: Arun C Murthy > Attachments: MAPREDUCE-1528_yhadoop20.patch, > MAPREDUCE-1528_yhadoop20.patch, MAPREDUCE-1528_yhadoop20.patch > > > Currently, TokenStorage is a singleton. This doesn't work for some use cases, > such as Oozie. I think that each Job should have a TokenStorage that is > associated it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1528) TokenStorage should not be static
[ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-1528: - Attachment: MAPREDUCE-1528_yhadoop20.patch Uh, wrong patch previously... > TokenStorage should not be static > - > > Key: MAPREDUCE-1528 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Owen O'Malley >Assignee: Arun C Murthy > Attachments: MAPREDUCE-1528_yhadoop20.patch, > MAPREDUCE-1528_yhadoop20.patch, MAPREDUCE-1528_yhadoop20.patch > > > Currently, TokenStorage is a singleton. This doesn't work for some use cases, > such as Oozie. I think that each Job should have a TokenStorage that is > associated it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1528) TokenStorage should not be static
[ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-1528: - Attachment: MAPREDUCE-1528_yhadoop20.patch Minor update to y20 branch. > TokenStorage should not be static > - > > Key: MAPREDUCE-1528 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Owen O'Malley >Assignee: Arun C Murthy > Attachments: MAPREDUCE-1528_yhadoop20.patch, > MAPREDUCE-1528_yhadoop20.patch > > > Currently, TokenStorage is a singleton. This doesn't work for some use cases, > such as Oozie. I think that each Job should have a TokenStorage that is > associated it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1528) TokenStorage should not be static
[ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated MAPREDUCE-1528: - Attachment: MAPREDUCE-1528_yhadoop20.patch Summary of changes: # Renamed TokenStorage to Credentials to better reflect it's utility. # Added a Credentials to JobConf (and an accessor: JobConf.getCredentials) since it's the only per-job identifier in an MR application for the old apis, added a JobContext.getCredentials for the new, context-objects api. # Removed as much cruft as possible from TokenCache, without really going overboard - we need to keep TokenCache since it's Hadoop MapReduce specific and I can't really put everything into Credentials as it's in Hadoop Common. > TokenStorage should not be static > - > > Key: MAPREDUCE-1528 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Owen O'Malley > Attachments: MAPREDUCE-1528_yhadoop20.patch > > > Currently, TokenStorage is a singleton. This doesn't work for some use cases, > such as Oozie. I think that each Job should have a TokenStorage that is > associated it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (MAPREDUCE-1528) TokenStorage should not be static
[ https://issues.apache.org/jira/browse/MAPREDUCE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned MAPREDUCE-1528: Assignee: Arun C Murthy > TokenStorage should not be static > - > > Key: MAPREDUCE-1528 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1528 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Owen O'Malley >Assignee: Arun C Murthy > Attachments: MAPREDUCE-1528_yhadoop20.patch > > > Currently, TokenStorage is a singleton. This doesn't work for some use cases, > such as Oozie. I think that each Job should have a TokenStorage that is > associated it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1538) TrackerDistributedCacheManager can fail because the number of subdirectories reaches system limit
[ https://issues.apache.org/jira/browse/MAPREDUCE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839136#action_12839136 ] Scott Chen commented on MAPREDUCE-1538: --- In the patch, we track the number of subdirectories and if it goes up to a threshold, we delete the released cache. Similar mechanism is there for the total size. So we just adapt from that. > TrackerDistributedCacheManager can fail because the number of subdirectories > reaches system limit > - > > Key: MAPREDUCE-1538 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1538 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: tasktracker >Affects Versions: 0.22.0 >Reporter: Scott Chen >Assignee: Scott Chen > Fix For: 0.22.0 > > Attachments: MAPREDUCE-1538.patch > > > TrackerDistributedCacheManager deletes the cached files when the size goes up > to a configured number. > But there is no such limit for the number of subdirectories. Therefore the > number of subdirectories may grow large and exceed system limit. > This will make TT cannot create directory when getLocalCache and fails the > tasks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1304) Add counters for task time spent in GC
[ https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated MAPREDUCE-1304: - Attachment: MAPREDUCE-1304.2.patch New patch moves this logic into TaskReporter so that it happens every status update interval. > Add counters for task time spent in GC > -- > > Key: MAPREDUCE-1304 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task >Reporter: Todd Lipcon >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1304.2.patch, MAPREDUCE-1304.patch > > > It's easy to grab the number of millis spent in GC (see JvmMetrics for > example). Exposing these as task counters would be handy - occasionally I've > seen user jobs where long GC pauses cause big "unexplainable" performance > problems, and a large counter would make it obvious to the user what's going > on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1538) TrackerDistributedCacheManager can fail because the number of subdirectories reaches system limit
[ https://issues.apache.org/jira/browse/MAPREDUCE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839131#action_12839131 ] Zheng Shao commented on MAPREDUCE-1538: --- +1 > TrackerDistributedCacheManager can fail because the number of subdirectories > reaches system limit > - > > Key: MAPREDUCE-1538 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1538 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: tasktracker >Affects Versions: 0.22.0 >Reporter: Scott Chen >Assignee: Scott Chen > Fix For: 0.22.0 > > Attachments: MAPREDUCE-1538.patch > > > TrackerDistributedCacheManager deletes the cached files when the size goes up > to a configured number. > But there is no such limit for the number of subdirectories. Therefore the > number of subdirectories may grow large and exceed system limit. > This will make TT cannot create directory when getLocalCache and fails the > tasks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1538) TrackerDistributedCacheManager can fail because the number of subdirectories reaches system limit
[ https://issues.apache.org/jira/browse/MAPREDUCE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Chen updated MAPREDUCE-1538: -- Attachment: MAPREDUCE-1538.patch > TrackerDistributedCacheManager can fail because the number of subdirectories > reaches system limit > - > > Key: MAPREDUCE-1538 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1538 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: tasktracker >Affects Versions: 0.22.0 >Reporter: Scott Chen >Assignee: Scott Chen > Fix For: 0.22.0 > > Attachments: MAPREDUCE-1538.patch > > > TrackerDistributedCacheManager deletes the cached files when the size goes up > to a configured number. > But there is no such limit for the number of subdirectories. Therefore the > number of subdirectories may grow large and exceed system limit. > This will make TT cannot create directory when getLocalCache and fails the > tasks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1538) TrackerDistributedCacheManager can fail because the number of subdirectories reaches system limit
[ https://issues.apache.org/jira/browse/MAPREDUCE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839129#action_12839129 ] Scott Chen commented on MAPREDUCE-1538: --- When this happens, the log will actually show the follwing. 2010-02-25 12:45:41,022 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_201002230013_22452_m_003831_0 on tracker_hadoop0143.snc3.facebook.com.:localhost.localdomain/127.0.0.1:37489: java.io.FileNotFoundException: /mnt/d3/SILVER/local/taskTracker/jobcache/job_201002230013_22452/attempt_201002230013_22452_m_003831_0/output/file.out (No space left on device) But if we do df on the machine, we found the space is not an issue. It is because of the number of subdirectories are too high. > TrackerDistributedCacheManager can fail because the number of subdirectories > reaches system limit > - > > Key: MAPREDUCE-1538 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1538 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: tasktracker >Affects Versions: 0.22.0 >Reporter: Scott Chen >Assignee: Scott Chen > Fix For: 0.22.0 > > > TrackerDistributedCacheManager deletes the cached files when the size goes up > to a configured number. > But there is no such limit for the number of subdirectories. Therefore the > number of subdirectories may grow large and exceed system limit. > This will make TT cannot create directory when getLocalCache and fails the > tasks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1304) Add counters for task time spent in GC
[ https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839115#action_12839115 ] Todd Lipcon commented on MAPREDUCE-1304: bq. I think something like this should actually go into the TaskReporter itself Seems reasonable enough to me. > Add counters for task time spent in GC > -- > > Key: MAPREDUCE-1304 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task >Reporter: Todd Lipcon >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1304.patch > > > It's easy to grab the number of millis spent in GC (see JvmMetrics for > example). Exposing these as task counters would be handy - occasionally I've > seen user jobs where long GC pauses cause big "unexplainable" performance > problems, and a large counter would make it obvious to the user what's going > on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1304) Add counters for task time spent in GC
[ https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839114#action_12839114 ] Aaron Kimball commented on MAPREDUCE-1304: -- You're right that if a task throws an exception, I think that it will probably not set the counter. I could put the increment in a finally block and that would fix that issue. Based on a quick look at the code in Counters and Counter, I think that there wouldn't be major issues with thread safety or performance (every operation on a Counter is already synchronized). An extra thread is pretty heavy-weight, though. I think something like this should actually go into the TaskReporter itself; it could just increment the gc counter itself right before sending a status every 3 seconds. I ran a quick benchmark test which got a handle to the GarbageCollectorMXBean list and polled them; I put all of this in a loop and ran it a million times in about a half-second, so I don't think this would negatively impact performance. > Add counters for task time spent in GC > -- > > Key: MAPREDUCE-1304 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task >Reporter: Todd Lipcon >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1304.patch > > > It's easy to grab the number of millis spent in GC (see JvmMetrics for > example). Exposing these as task counters would be handy - occasionally I've > seen user jobs where long GC pauses cause big "unexplainable" performance > problems, and a large counter would make it obvious to the user what's going > on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1304) Add counters for task time spent in GC
[ https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839108#action_12839108 ] Todd Lipcon commented on MAPREDUCE-1304: Two questions: - I don't know the Task code quite well enough, but will this still be set in the case that the task fails? - Is it worth putting this in a separate thread in the Child interface so it actually gets incremented as the task goes, with each umbilical heartbeat? It would be nice to see this on a per-task basis when a task appears to be "stuck". > Add counters for task time spent in GC > -- > > Key: MAPREDUCE-1304 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task >Reporter: Todd Lipcon >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1304.patch > > > It's easy to grab the number of millis spent in GC (see JvmMetrics for > example). Exposing these as task counters would be handy - occasionally I've > seen user jobs where long GC pauses cause big "unexplainable" performance > problems, and a large counter would make it obvious to the user what's going > on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1510) RAID should regenerate parity files if they get deleted
[ https://issues.apache.org/jira/browse/MAPREDUCE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodrigo Schmidt updated MAPREDUCE-1510: --- Status: Open (was: Patch Available) > RAID should regenerate parity files if they get deleted > --- > > Key: MAPREDUCE-1510 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1510 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: contrib/raid >Reporter: Rodrigo Schmidt >Assignee: Rodrigo Schmidt > Attachments: MAPREDUCE-1510.1.patch, MAPREDUCE-1510.2.patch, > MAPREDUCE-1510.patch > > > Currently, if a source file has a replication factor lower or equal to that > expected by RAID, the file is skipped and no parity file is generated. I > don't think this is a good behavior since parity files can get wrongly > deleted, leaving the source file with a low replication factor. In that case, > raid should be able to recreate the parity file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1510) RAID should regenerate parity files if they get deleted
[ https://issues.apache.org/jira/browse/MAPREDUCE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodrigo Schmidt updated MAPREDUCE-1510: --- Status: Patch Available (was: Open) > RAID should regenerate parity files if they get deleted > --- > > Key: MAPREDUCE-1510 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1510 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: contrib/raid >Reporter: Rodrigo Schmidt >Assignee: Rodrigo Schmidt > Attachments: MAPREDUCE-1510.1.patch, MAPREDUCE-1510.2.patch, > MAPREDUCE-1510.patch > > > Currently, if a source file has a replication factor lower or equal to that > expected by RAID, the file is skipped and no parity file is generated. I > don't think this is a good behavior since parity files can get wrongly > deleted, leaving the source file with a low replication factor. In that case, > raid should be able to recreate the parity file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1510) RAID should regenerate parity files if they get deleted
[ https://issues.apache.org/jira/browse/MAPREDUCE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodrigo Schmidt updated MAPREDUCE-1510: --- Attachment: MAPREDUCE-1510.2.patch In an offline discussion, Dhruba made me realize that the fact that the RaidNode binds to a fixed port is probably the reason why the tests were failing on Hudson. I'm submitting this new patch that also changes the unit tests so that now they bind to any available port. > RAID should regenerate parity files if they get deleted > --- > > Key: MAPREDUCE-1510 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1510 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: contrib/raid >Reporter: Rodrigo Schmidt >Assignee: Rodrigo Schmidt > Attachments: MAPREDUCE-1510.1.patch, MAPREDUCE-1510.2.patch, > MAPREDUCE-1510.patch > > > Currently, if a source file has a replication factor lower or equal to that > expected by RAID, the file is skipped and no parity file is generated. I > don't think this is a good behavior since parity files can get wrongly > deleted, leaving the source file with a low replication factor. In that case, > raid should be able to recreate the parity file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1454) The servlets should quote server generated strings sent in the response
[ https://issues.apache.org/jira/browse/MAPREDUCE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu updated MAPREDUCE-1454: --- Affects Version/s: 0.22.0 Release Note: Servlets should quote server generated strings sent in the response Status: Patch Available (was: Open) > The servlets should quote server generated strings sent in the response > --- > > Key: MAPREDUCE-1454 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1454 > Project: Hadoop Map/Reduce > Issue Type: Sub-task >Affects Versions: 0.22.0 >Reporter: Devaraj Das >Assignee: Chris Douglas > Fix For: 0.22.0 > > Attachments: M1454-0y20.patch, mr-1454-trunk-v1.patch > > > This is related to HADOOP-6151 but for output. We need to go through all the > servlets/jsps and pass all the response strings that could be based on the > incoming request or user's data through a filter (implemented in HADOOP-6151). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1454) The servlets should quote server generated strings sent in the response
[ https://issues.apache.org/jira/browse/MAPREDUCE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu updated MAPREDUCE-1454: --- Attachment: mr-1454-trunk-v1.patch Ported to trunk. Removed dead link in jobtracker.jsp for scheduling info. > The servlets should quote server generated strings sent in the response > --- > > Key: MAPREDUCE-1454 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1454 > Project: Hadoop Map/Reduce > Issue Type: Sub-task >Reporter: Devaraj Das >Assignee: Chris Douglas > Fix For: 0.22.0 > > Attachments: M1454-0y20.patch, mr-1454-trunk-v1.patch > > > This is related to HADOOP-6151 but for output. We need to go through all the > servlets/jsps and pass all the response strings that could be based on the > incoming request or user's data through a filter (implemented in HADOOP-6151). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (MAPREDUCE-1304) Add counters for task time spent in GC
[ https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball reassigned MAPREDUCE-1304: Assignee: Aaron Kimball > Add counters for task time spent in GC > -- > > Key: MAPREDUCE-1304 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task >Reporter: Todd Lipcon >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1304.patch > > > It's easy to grab the number of millis spent in GC (see JvmMetrics for > example). Exposing these as task counters would be handy - occasionally I've > seen user jobs where long GC pauses cause big "unexplainable" performance > problems, and a large counter would make it obvious to the user what's going > on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1304) Add counters for task time spent in GC
[ https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated MAPREDUCE-1304: - Attachment: MAPREDUCE-1304.patch Added a new TaskCounter, GC_TIME_MILLIS, which tracks this information. Patch also includes a testcase. > Add counters for task time spent in GC > -- > > Key: MAPREDUCE-1304 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task >Reporter: Todd Lipcon >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1304.patch > > > It's easy to grab the number of millis spent in GC (see JvmMetrics for > example). Exposing these as task counters would be handy - occasionally I've > seen user jobs where long GC pauses cause big "unexplainable" performance > problems, and a large counter would make it obvious to the user what's going > on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1304) Add counters for task time spent in GC
[ https://issues.apache.org/jira/browse/MAPREDUCE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Kimball updated MAPREDUCE-1304: - Status: Patch Available (was: Open) > Add counters for task time spent in GC > -- > > Key: MAPREDUCE-1304 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1304 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task >Reporter: Todd Lipcon >Assignee: Aaron Kimball > Attachments: MAPREDUCE-1304.patch > > > It's easy to grab the number of millis spent in GC (see JvmMetrics for > example). Exposing these as task counters would be handy - occasionally I've > seen user jobs where long GC pauses cause big "unexplainable" performance > problems, and a large counter would make it obvious to the user what's going > on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1516) JobTracker should issue a delegation token only for kerberos authenticated client
[ https://issues.apache.org/jira/browse/MAPREDUCE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated MAPREDUCE-1516: Attachment: MR-1516.3.patch New patch uploaded accommodating the interface changes in HADOOP-6580 > JobTracker should issue a delegation token only for kerberos authenticated > client > - > > Key: MAPREDUCE-1516 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1516 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1516.1.patch, MR-1516.2.patch, MR-1516.3.patch > > > Delegation tokens should be issued only if the client is kerberos > authenticated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1539) authorization checks for inter-server protocol (based on HADOOP-6600)
[ https://issues.apache.org/jira/browse/MAPREDUCE-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated MAPREDUCE-1539: -- Attachment: MAPREDUCE-1539-2.patch merged with trunk > authorization checks for inter-server protocol (based on HADOOP-6600) > - > > Key: MAPREDUCE-1539 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1539 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Attachments: MAPREDUCE-1539-1.patch, MAPREDUCE-1539-2.patch > > > authorization checks for inter-server protocol (based on HADOOP-6600) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das updated MAPREDUCE-1537: --- Resolution: Fixed Fix Version/s: 0.22.0 Status: Resolved (was: Patch Available) +1 I just committed this. Thanks, Jitendra! > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Fix For: 0.22.0 > > Attachments: MR-1537.1.patch, MR-1537.2.patch, MR-1537.3.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1482) Better handling of task diagnostic information stored in the TaskInProgress
[ https://issues.apache.org/jira/browse/MAPREDUCE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated MAPREDUCE-1482: -- Assignee: Amar Kamat Hadoop Flags: [Reviewed] +1 patch looks good. > Better handling of task diagnostic information stored in the TaskInProgress > --- > > Key: MAPREDUCE-1482 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1482 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Reporter: Amar Kamat >Assignee: Amar Kamat > Attachments: mapreduce-1482-v1.1.patch > > > Task diagnostic information can be very large at times eating up Jobtracker's > memory. There should be some way to avoid storing large error strings in > JobTracker. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839013#action_12839013 ] Jitendra Nath Pandey commented on MAPREDUCE-1537: - ant test results: 4 failures due to unrelated reasons 1. TestJobHistory: succeeds when run from command line 2. TestMiniMRLocalFS: File QuasiMonteCarlo_TMP_3_141592654/out/reduce-out does not exist. java.io.FileNotFoundException: File QuasiMonteCarlo_TMP_3_141592654/out/reduce-out does not exist. at org.apache.hadoop.fs.RawLocalFileSystem.getFileStatus(RawLocalFileSystem.java:420) 3. TestDelegationTokenRenewal: It is a flaky test (MR-1532 addresses it) 4. TestMiniMRChildTask: junit.framework.AssertionFailedError: Exception in testing temp dir junit.framework.AssertionFailedError: Exception in testing child env junit.framework.AssertionFailedError: Exception in testing child env > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch, MR-1537.2.patch, MR-1537.3.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839011#action_12839011 ] Jitendra Nath Pandey commented on MAPREDUCE-1537: - test-patch results: [exec] +1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch, MR-1537.2.patch, MR-1537.3.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1539) authorization checks for inter-server protocol (based on HADOOP-6600)
[ https://issues.apache.org/jira/browse/MAPREDUCE-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik updated MAPREDUCE-1539: -- Attachment: MAPREDUCE-1539-1.patch > authorization checks for inter-server protocol (based on HADOOP-6600) > - > > Key: MAPREDUCE-1539 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1539 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > Attachments: MAPREDUCE-1539-1.patch > > > authorization checks for inter-server protocol (based on HADOOP-6600) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MAPREDUCE-1541) JobHistory page should list job start time rather than job-tracker start time
JobHistory page should list job start time rather than job-tracker start time - Key: MAPREDUCE-1541 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1541 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobtracker Reporter: Arun C Murthy Assignee: Arun C Murthy Fix For: 0.22.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MAPREDUCE-1540) Sometimes JobTracker holds stale refrence of JobInProgress even after Job gets retired
[ https://issues.apache.org/jira/browse/MAPREDUCE-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amar Kamat resolved MAPREDUCE-1540. --- Resolution: Cannot Reproduce This doesnt occur in 0.20, 0.21 and trunk. > Sometimes JobTracker holds stale refrence of JobInProgress even after Job > gets retired > -- > > Key: MAPREDUCE-1540 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.2 >Reporter: Karam Singh >Assignee: Amar Kamat > > Ran random writer, sort and sort validate job. Checked the jmap -histo:live > and verified that there is no reference of JobInProgress after Jobs are > retired > Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed > all the job when jobs got retired. again checked jmap -histo:live for > JobInProgress for JT process found 2 references were there. > Found this while doing sanity testing of 1316 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1407) Invalid example in the documentation of org.apache.hadoop.mapreduce.{Mapper,Reducer}
[
https://issues.apache.org/jira/browse/MAPREDUCE-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Sigoure updated MAPREDUCE-1407:
--
Status: Patch Available (was: Open)
> Invalid example in the documentation of
> org.apache.hadoop.mapreduce.{Mapper,Reducer}
>
>
> Key: MAPREDUCE-1407
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1407
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: documentation
>Affects Versions: 0.20.1
>Reporter: Benoit Sigoure
>Priority: Trivial
> Attachments: MAPREDUCE-1407.patch, MAPREDUCE-1407.patch
>
>
> Both examples are using context.collect instead of context.write
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1523) Sometimes rumen trace generator fails to extract the job finish time.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838980#action_12838980 ] Hong Tang commented on MAPREDUCE-1523: -- Patch looks good to me. +1. > Sometimes rumen trace generator fails to extract the job finish time. > - > > Key: MAPREDUCE-1523 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1523 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Hong Tang >Assignee: Dick King > Attachments: mapreduce-1523--2010-02-24.patch, > mapreduce-1523--2010-02-25.patch > > > We saw sometimes (not very often) that rumen may fail to extract the job > finish time from Hadoop 0.20 history log. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated MAPREDUCE-1537: Status: Patch Available (was: Reopened) > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch, MR-1537.2.patch, MR-1537.3.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1502) Sqoop should run mysqldump in a mapper as opposed to a user-side process
[
https://issues.apache.org/jira/browse/MAPREDUCE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838963#action_12838963
]
Aaron Kimball commented on MAPREDUCE-1502:
--
To be clear, the JDBC-based import mechanisms available in Sqoop have always
been accessing non-distributed resources from within map tasks. This just puts
mysqldump on an equal footing, eliminates an extra machine (the client) from
the main transfer path in the network, and allows mysqldump to take advantage
of Hadoop's ability to monitor and restart long-running processes that get
interrupted.
Sqoop provides users with explicit parallelism control; it will default to
using 4 mappers, and allows users to select a different number of tasks with
the {{\-\-num-mappers}} argument.
> Sqoop should run mysqldump in a mapper as opposed to a user-side process
>
>
> Key: MAPREDUCE-1502
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1502
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
>Reporter: Aaron Kimball
>Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1502.patch
>
>
> Sqoop currently runs mysqldump ("direct import mode") in the local user
> process with a single thread. Better system performance and reliability could
> be achieved by running this in a parallel set of mapper tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1523) Sometimes rumen trace generator fails to extract the job finish time.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick King updated MAPREDUCE-1523: - Attachment: mapreduce-1523--2010-02-25.patch This addresses the issue of an unparseable counter string. > Sometimes rumen trace generator fails to extract the job finish time. > - > > Key: MAPREDUCE-1523 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1523 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Hong Tang >Assignee: Dick King > Attachments: mapreduce-1523--2010-02-24.patch, > mapreduce-1523--2010-02-25.patch > > > We saw sometimes (not very often) that rumen may fail to extract the job > finish time from Hadoop 0.20 history log. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1523) Sometimes rumen trace generator fails to extract the job finish time.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dick King updated MAPREDUCE-1523: - Status: Patch Available (was: Open) > Sometimes rumen trace generator fails to extract the job finish time. > - > > Key: MAPREDUCE-1523 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1523 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Hong Tang >Assignee: Dick King > Attachments: mapreduce-1523--2010-02-24.patch, > mapreduce-1523--2010-02-25.patch > > > We saw sometimes (not very often) that rumen may fail to extract the job > finish time from Hadoop 0.20 history log. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated MAPREDUCE-1537: Attachment: MR-1537.3.patch > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch, MR-1537.2.patch, MR-1537.3.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1540) Sometimes JobTracker holds stale refrence of JobInProgress even after Job gets retired
[ https://issues.apache.org/jira/browse/MAPREDUCE-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838932#action_12838932 ] Arun C Murthy commented on MAPREDUCE-1540: -- Thanks for the quick update Amar. > Sometimes JobTracker holds stale refrence of JobInProgress even after Job > gets retired > -- > > Key: MAPREDUCE-1540 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.2 >Reporter: Karam Singh >Assignee: Amar Kamat > > Ran random writer, sort and sort validate job. Checked the jmap -histo:live > and verified that there is no reference of JobInProgress after Jobs are > retired > Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed > all the job when jobs got retired. again checked jmap -histo:live for > JobInProgress for JT process found 2 references were there. > Found this while doing sanity testing of 1316 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1502) Sqoop should run mysqldump in a mapper as opposed to a user-side process
[
https://issues.apache.org/jira/browse/MAPREDUCE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838902#action_12838902
]
Owen O'Malley commented on MAPREDUCE-1502:
--
I haven't looked at the patch, but you should be careful when pushing access to
non-distributed servers into the cluster. In particular, you probably want an
upper bound on the number of maps
> Sqoop should run mysqldump in a mapper as opposed to a user-side process
>
>
> Key: MAPREDUCE-1502
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1502
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
>Reporter: Aaron Kimball
>Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1502.patch
>
>
> Sqoop currently runs mysqldump ("direct import mode") in the local user
> process with a single thread. Better system performance and reliability could
> be achieved by running this in a parallel set of mapper tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1493) Authorization for job-history pages
[ https://issues.apache.org/jira/browse/MAPREDUCE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Gummadi updated MAPREDUCE-1493: Status: Open (was: Patch Available) Hudson can apply this patch only after MAPREDUCE-1455 gets committed. So cancelling submission of this patch to Hudson. > Authorization for job-history pages > --- > > Key: MAPREDUCE-1493 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1493 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobtracker, security >Reporter: Vinod K V >Assignee: Vinod K V > Fix For: 0.22.0 > > Attachments: MAPREDUCE-1493-20100222.1.txt, > MAPREDUCE-1493-20100225.2.txt, MAPREDUCE-1493-20100226.1.txt > > > MAPREDUCE-1455 introduces authorization for most of the Map/Reduce jsp pages > and servlets, but left history pages. This JIRA will make sure that > authorization checks are made while accessing job-history pages also. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1493) Authorization for job-history pages
[ https://issues.apache.org/jira/browse/MAPREDUCE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Gummadi updated MAPREDUCE-1493: Status: Patch Available (was: Open) > Authorization for job-history pages > --- > > Key: MAPREDUCE-1493 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1493 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobtracker, security >Reporter: Vinod K V >Assignee: Vinod K V > Fix For: 0.22.0 > > Attachments: MAPREDUCE-1493-20100222.1.txt, > MAPREDUCE-1493-20100225.2.txt, MAPREDUCE-1493-20100226.1.txt > > > MAPREDUCE-1455 introduces authorization for most of the Map/Reduce jsp pages > and servlets, but left history pages. This JIRA will make sure that > authorization checks are made while accessing job-history pages also. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1493) Authorization for job-history pages
[ https://issues.apache.org/jira/browse/MAPREDUCE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1283#action_1283 ] Ravi Gummadi commented on MAPREDUCE-1493: - Patch looks good. +1 > Authorization for job-history pages > --- > > Key: MAPREDUCE-1493 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1493 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobtracker, security >Reporter: Vinod K V >Assignee: Vinod K V > Fix For: 0.22.0 > > Attachments: MAPREDUCE-1493-20100222.1.txt, > MAPREDUCE-1493-20100225.2.txt, MAPREDUCE-1493-20100226.1.txt > > > MAPREDUCE-1455 introduces authorization for most of the Map/Reduce jsp pages > and servlets, but left history pages. This JIRA will make sure that > authorization checks are made while accessing job-history pages also. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated MAPREDUCE-1537: Attachment: MR-1537.2.patch A new patch added. It fetches delegation tokens from namenode only if security is enabled. > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch, MR-1537.2.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1493) Authorization for job-history pages
[ https://issues.apache.org/jira/browse/MAPREDUCE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod K V updated MAPREDUCE-1493: - Attachment: MAPREDUCE-1493-20100226.1.txt Updated patch sync'ing with the latest one at MAPREDUCE-1455. > Authorization for job-history pages > --- > > Key: MAPREDUCE-1493 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1493 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobtracker, security >Reporter: Vinod K V >Assignee: Vinod K V > Fix For: 0.22.0 > > Attachments: MAPREDUCE-1493-20100222.1.txt, > MAPREDUCE-1493-20100225.2.txt, MAPREDUCE-1493-20100226.1.txt > > > MAPREDUCE-1455 introduces authorization for most of the Map/Reduce jsp pages > and servlets, but left history pages. This JIRA will make sure that > authorization checks are made while accessing job-history pages also. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838796#action_12838796 ] Ravi Gummadi commented on MAPREDUCE-1537: - Yes. That is the stack trace from the other tests failures also. This JIRA is reopened to address that. As Devaraj pointed out, the actual fix could be in HDFS and/or COMMON. > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838788#action_12838788 ] Rodrigo Schmidt commented on MAPREDUCE-1537: If it helps, this is the error that I'm getting in TestRaidHar inside contrib/raid: [junit] java.io.IOException: java.lang.NullPointerException [junit] at org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.createPassword(AbstractDelegationTokenSecretManager.java:189) [junit] at org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.createPassword(AbstractDelegationTokenSecretManager.java:45) [junit] at org.apache.hadoop.security.token.Token.(Token.java:51) [junit] at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getDelegationToken(FSNamesystem.java:4445) [junit] at org.apache.hadoop.hdfs.server.namenode.NameNode.getDelegationToken(NameNode.java:563) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.apache.hadoop.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:342) [junit] at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1224) [junit] at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1220) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at javax.security.auth.Subject.doAs(Subject.java:396) [junit] at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:706) [junit] at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1218) [junit] 10/02/26 01:37:46 INFO mapreduce.JobSubmitter: Cleaning up the staging area hdfs://localhost:56663/tmp/hadoop-rschmidt/mapred/staging/rschmidt/.staging/job_20100226013723998_0002 [junit] 10/02/26 01:37:46 INFO security.Groups: Returning cached groups for 'rschmidt' [junit] java.io.IOException: java.lang.NullPointerException [junit] at org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.createPassword(AbstractDelegationTokenSecretManager.java:189) [junit] at org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager.createPassword(AbstractDelegationTokenSecretManager.java:45) [junit] at org.apache.hadoop.security.token.Token.(Token.java:51) [junit] at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getDelegationToken(FSNamesystem.java:4445) [junit] at org.apache.hadoop.hdfs.server.namenode.NameNode.getDelegationToken(NameNode.java:563) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.apache.hadoop.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:342) [junit] at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1224) [junit] at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1220) [junit] at java.security.AccessController.doPrivileged(Native Method) [junit] at javax.security.auth.Subject.doAs(Subject.java:396) [junit] at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:706) [junit] at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1218) > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1537) TestDelegationTokenRenewal fails
[ https://issues.apache.org/jira/browse/MAPREDUCE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838789#action_12838789 ] Rodrigo Schmidt commented on MAPREDUCE-1537: Can you please confirm the error I'm seeing is related to this issue? Thanks! > TestDelegationTokenRenewal fails > > > Key: MAPREDUCE-1537 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1537 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Jitendra Nath Pandey >Assignee: Jitendra Nath Pandey > Attachments: MR-1537.1.patch > > > TestDelegationTokenRenewal does not compile in trunk. > The reason is that DelegationTokenSecretManager in hdfs requires namesystem > in constructor. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1455) Authorization for servlets
[ https://issues.apache.org/jira/browse/MAPREDUCE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod K V updated MAPREDUCE-1455: - Status: Patch Available (was: Open) The latest one looks good. +1 for the patch. Letting Hudson hammer it. > Authorization for servlets > -- > > Key: MAPREDUCE-1455 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1455 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobtracker, security, tasktracker >Reporter: Devaraj Das >Assignee: Ravi Gummadi > Fix For: 0.22.0 > > Attachments: 1455.patch, 1455.v1.patch, 1455.v2.patch, 1455.v3.patch, > 1455.v4.1.patch, 1455.v4.patch > > > This jira is about building the authorization for servlets (on top of > MAPREDUCE-1307). That is, the JobTracker/TaskTracker runs authorization > checks on web requests based on the configured job permissions. For e.g., if > the job permission is 600, then no one except the authenticated user can look > at the job details via the browser. The authenticated user in the servlet can > be obtained using the HttpServletRequest method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1455) Authorization for servlets
[ https://issues.apache.org/jira/browse/MAPREDUCE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Gummadi updated MAPREDUCE-1455: Attachment: 1455.v4.1.patch Attaching new patch by removing some unused imports from jsps and removing ^M characters from testcase. > Authorization for servlets > -- > > Key: MAPREDUCE-1455 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1455 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobtracker, security, tasktracker >Reporter: Devaraj Das >Assignee: Ravi Gummadi > Fix For: 0.22.0 > > Attachments: 1455.patch, 1455.v1.patch, 1455.v2.patch, 1455.v3.patch, > 1455.v4.1.patch, 1455.v4.patch > > > This jira is about building the authorization for servlets (on top of > MAPREDUCE-1307). That is, the JobTracker/TaskTracker runs authorization > checks on web requests based on the configured job permissions. For e.g., if > the job permission is 600, then no one except the authenticated user can look > at the job details via the browser. The authenticated user in the servlet can > be obtained using the HttpServletRequest method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1455) Authorization for servlets
[ https://issues.apache.org/jira/browse/MAPREDUCE-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838779#action_12838779 ] Vinod K V commented on MAPREDUCE-1455: -- Patch looks good. The test TestWebUIAuthorization has ^M characters. Can you reupload the patch? > Authorization for servlets > -- > > Key: MAPREDUCE-1455 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1455 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: jobtracker, security, tasktracker >Reporter: Devaraj Das >Assignee: Ravi Gummadi > Fix For: 0.22.0 > > Attachments: 1455.patch, 1455.v1.patch, 1455.v2.patch, 1455.v3.patch, > 1455.v4.patch > > > This jira is about building the authorization for servlets (on top of > MAPREDUCE-1307). That is, the JobTracker/TaskTracker runs authorization > checks on web requests based on the configured job permissions. For e.g., if > the job permission is 600, then no one except the authenticated user can look > at the job details via the browser. The authenticated user in the servlet can > be obtained using the HttpServletRequest method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1307) Introduce the concept of Job Permissions
[ https://issues.apache.org/jira/browse/MAPREDUCE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod K V updated MAPREDUCE-1307: - Attachment: MAPREDUCE-1307-20100226.1-ydist.txt Patch for previous versions of the repo. Not for commit here. > Introduce the concept of Job Permissions > > > Key: MAPREDUCE-1307 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1307 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: security >Reporter: Devaraj Das >Assignee: Vinod K V > Fix For: 0.22.0 > > Attachments: 1307-early-1.patch, MAPREDUCE-1307-20100210.txt, > MAPREDUCE-1307-20100211.txt, MAPREDUCE-1307-20100215.txt, > MAPREDUCE-1307-20100217.txt, MAPREDUCE-1307-20100226.1-ydist.txt > > > It would be good to define the notion of job permissions analogous to file > permissions. Then the JobTracker can restrict who can "read" (e.g. look at > the job page) or "modify" (e.g. kill) jobs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (MAPREDUCE-1540) Sometimes JobTracker holds stale refrence of JobInProgress even after Job gets retired
[ https://issues.apache.org/jira/browse/MAPREDUCE-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amar Kamat reassigned MAPREDUCE-1540: - Assignee: Amar Kamat > Sometimes JobTracker holds stale refrence of JobInProgress even after Job > gets retired > -- > > Key: MAPREDUCE-1540 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.2 >Reporter: Karam Singh >Assignee: Amar Kamat > > Ran random writer, sort and sort validate job. Checked the jmap -histo:live > and verified that there is no reference of JobInProgress after Jobs are > retired > Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed > all the job when jobs got retired. again checked jmap -histo:live for > JobInProgress for JT process found 2 references were there. > Found this while doing sanity testing of 1316 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-1540) Sometimes JobTracker holds stale refrence of JobInProgress even after Job gets retired
[ https://issues.apache.org/jira/browse/MAPREDUCE-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838774#action_12838774 ] Amar Kamat commented on MAPREDUCE-1540: --- What actually happened was that these jobs failed during submission itself. As a result, _job.fail()_ was invoked to cleanup the job files on the local-fs, which inturn invokes JobTracker.finalizeJob(). JobTracker.finalizeJob() goes ahead and adds them to _userToJobsMap_. Note that the JIP is not present in the _jobs_ structure of the JobTracker but somehow found its way in _userToJobsMap_. Later the _RetireJobs_ thread runs and tries to claim these jobs. But the condition, _minConditionToRetire()_, waits until the history file gets copied, which in this case never happens as the history file was never created. As a result of this, the jobs will be held up in the memory forever. Note that these jobs are not initialized and hence wont affect JobTracker's memory. > Sometimes JobTracker holds stale refrence of JobInProgress even after Job > gets retired > -- > > Key: MAPREDUCE-1540 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.2 >Reporter: Karam Singh > > Ran random writer, sort and sort validate job. Checked the jmap -histo:live > and verified that there is no reference of JobInProgress after Jobs are > retired > Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed > all the job when jobs got retired. again checked jmap -histo:live for > JobInProgress for JT process found 2 references were there. > Found this while doing sanity testing of 1316 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1540) Sometimes JobTracker holds stale refrence of JobInProgress even after Job gets retired
[ https://issues.apache.org/jira/browse/MAPREDUCE-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karam Singh updated MAPREDUCE-1540: --- Description: Ran random writer, sort and sort validate job. Checked the jmap -histo:live and verified that there is no reference of JobInProgress after Jobs are retired Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed all the job when jobs got retired. again checked jmap -histo:live for JobInProgress for JT process found 2 references were there. Found this while doing sanity testing of 1316 was: Ran random writer, sort and sort validate job. Checked the jmap -histo:live and verified that there is no reference of JobInProgress after Jobs are retired Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed all the job when jobs got retired. again checked jmap -histo:live for JobInProgress for JT process found 2 references were there. Found this while doing snaity testing of 1316 > Sometimes JobTracker holds stale refrence of JobInProgress even after Job > gets retired > -- > > Key: MAPREDUCE-1540 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.2 >Reporter: Karam Singh > > Ran random writer, sort and sort validate job. Checked the jmap -histo:live > and verified that there is no reference of JobInProgress after Jobs are > retired > Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed > all the job when jobs got retired. again checked jmap -histo:live for > JobInProgress for JT process found 2 references were there. > Found this while doing sanity testing of 1316 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1540) Sometimes JobTracker holds stale refrence of JobInProgress even after Job gets retired
[ https://issues.apache.org/jira/browse/MAPREDUCE-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karam Singh updated MAPREDUCE-1540: --- Summary: Sometimes JobTracker holds stale refrence of JobInProgress even after Job gets retired (was: Sometime JobTracker holds stale refrence of JobInProgress.) > Sometimes JobTracker holds stale refrence of JobInProgress even after Job > gets retired > -- > > Key: MAPREDUCE-1540 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Affects Versions: 0.20.2 >Reporter: Karam Singh > > Ran random writer, sort and sort validate job. Checked the jmap -histo:live > and verified that there is no reference of JobInProgress after Jobs are > retired > Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed > all the job when jobs got retired. again checked jmap -histo:live for > JobInProgress for JT process found 2 references were there. > Found this while doing snaity testing of 1316 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1482) Better handling of task diagnostic information stored in the TaskInProgress
[ https://issues.apache.org/jira/browse/MAPREDUCE-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amar Kamat updated MAPREDUCE-1482: -- Attachment: mapreduce-1482-v1.1.patch Attaching a patch that caps the task-diagnostic-info and state-string to 1024 chars. test-patch passed. All ant tests except the following have passed : - TestMiniMRLocalFS - TestSubmitJob - TestTTResourceReporting All these failed on trunk too. > Better handling of task diagnostic information stored in the TaskInProgress > --- > > Key: MAPREDUCE-1482 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1482 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: jobtracker >Reporter: Amar Kamat > Attachments: mapreduce-1482-v1.1.patch > > > Task diagnostic information can be very large at times eating up Jobtracker's > memory. There should be some way to avoid storing large error strings in > JobTracker. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MAPREDUCE-1540) Sometime JobTracker holds stale refrence of JobInProgress.
Sometime JobTracker holds stale refrence of JobInProgress. -- Key: MAPREDUCE-1540 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1540 Project: Hadoop Map/Reduce Issue Type: Bug Components: jobtracker Affects Versions: 0.20.2 Reporter: Karam Singh Ran random writer, sort and sort validate job. Checked the jmap -histo:live and verified that there is no reference of JobInProgress after Jobs are retired Now submitter around 77 sleeps of around 1 maps. then after 1 hr killed all the job when jobs got retired. again checked jmap -histo:live for JobInProgress for JT process found 2 references were there. Found this while doing snaity testing of 1316 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (MAPREDUCE-1539) authorization checks for inter-server protocol (based on HADOOP-6600)
[ https://issues.apache.org/jira/browse/MAPREDUCE-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Shkolnik reassigned MAPREDUCE-1539: - Assignee: Boris Shkolnik > authorization checks for inter-server protocol (based on HADOOP-6600) > - > > Key: MAPREDUCE-1539 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1539 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Boris Shkolnik >Assignee: Boris Shkolnik > > authorization checks for inter-server protocol (based on HADOOP-6600) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MAPREDUCE-1539) authorization checks for inter-server protocol (based on HADOOP-6600)
authorization checks for inter-server protocol (based on HADOOP-6600) - Key: MAPREDUCE-1539 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1539 Project: Hadoop Map/Reduce Issue Type: New Feature Reporter: Boris Shkolnik authorization checks for inter-server protocol (based on HADOOP-6600) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
