[
https://issues.apache.org/jira/browse/HADOOP-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad Agarwal updated HADOOP-3829:
---
Release Note: If the number of skipped records in the neighborhood of a bad
record are not a
[
https://issues.apache.org/jira/browse/HADOOP-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad Agarwal updated HADOOP-3828:
---
Release Note: Skipped records can optionally be written to the HDFS. Refer
org.apache.hadoop
[
https://issues.apache.org/jira/browse/HADOOP-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sharad Agarwal updated HADOOP-153:
--
Release Note: If there are bugs in user code which lead to failure of Tasks
on certain records,
[
https://issues.apache.org/jira/browse/HADOOP-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala resolved HADOOP-4211.
--
Resolution: Duplicate
Based on Karam's testing, which confirms the diagnosis, I am mar
[
https://issues.apache.org/jira/browse/HADOOP-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640077#action_12640077
]
Karam Singh commented on HADOOP-4211:
-
Checked and verified that after applying patch
[
https://issues.apache.org/jira/browse/HADOOP-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-249:
---
Release Note: Jobs can enable task JVMs to be reused via the job config
mapred.job.reuse.jvm.num.task
[
https://issues.apache.org/jira/browse/HADOOP-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-3155:
Component/s: mapred
> reducers stuck at shuffling
>
>
>
[
https://issues.apache.org/jira/browse/HADOOP-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-4426:
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks,
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-4358:
-
Status: Patch Available (was: Open)
> NPE from CreateEditsLog
> ---
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640075#action_12640075
]
dhruba borthakur commented on HADOOP-4358:
--
I agree with Konstantin that the usin
[
https://issues.apache.org/jira/browse/HADOOP-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640074#action_12640074
]
Vivek Ratan commented on HADOOP-3674:
-
There's definitely an advantage, in some cases,
[
https://issues.apache.org/jira/browse/HADOOP-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640071#action_12640071
]
Hemanth Yamijala commented on HADOOP-4426:
--
Results of ant test-patch:
[exe
[
https://issues.apache.org/jira/browse/HADOOP-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640069#action_12640069
]
Amar Kamat commented on HADOOP-4426:
bq. testJobRunStateChange was setting the guarant
[
https://issues.apache.org/jira/browse/HADOOP-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-4426:
-
Attachment: HADOOP-4426.patch
{{testJobRunStateChange}} was setting the guaranteed capac
[
https://issues.apache.org/jira/browse/HADOOP-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-4426:
-
Status: Patch Available (was: Open)
> TestCapacityScheduler is broken
> ---
TestCapacityScheduler is broken
---
Key: HADOOP-4426
URL: https://issues.apache.org/jira/browse/HADOOP-4426
Project: Hadoop Core
Issue Type: Test
Components: contrib/capacity-sched
Affects Versions:
[
https://issues.apache.org/jira/browse/HADOOP-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas reassigned HADOOP-4408:
-
Assignee: Chris Douglas
> FsAction operations shouldn't create new Objects
> ---
[
https://issues.apache.org/jira/browse/HADOOP-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640054#action_12640054
]
Hadoop QA commented on HADOOP-4425:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640053#action_12640053
]
Hemanth Yamijala commented on HADOOP-3786:
--
Request to committers. Can you please
[
https://issues.apache.org/jira/browse/HADOOP-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640052#action_12640052
]
Hemanth Yamijala commented on HADOOP-3786:
--
+1 for the patch. Core test failure i
[
https://issues.apache.org/jira/browse/HADOOP-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640051#action_12640051
]
Amareshwari Sriramadasu commented on HADOOP-4421:
-
+1 for separate map, re
[
https://issues.apache.org/jira/browse/HADOOP-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4335:
--
Resolution: Fixed
Fix Version/s: 0.19.0
Assignee: David Phillips
Hadoop Fl
[
https://issues.apache.org/jira/browse/HADOOP-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4408:
--
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Availa
[
https://issues.apache.org/jira/browse/HADOOP-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4425:
--
Attachment: 4425-0.patch
FSEditLog.EditLogFileInputStream doesn't overload the read(byte[]) me
[
https://issues.apache.org/jira/browse/HADOOP-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4425:
--
Assignee: Chris Douglas
Status: Patch Available (was: Open)
> Edits log takes much long
[
https://issues.apache.org/jira/browse/HADOOP-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640032#action_12640032
]
Mac Yang commented on HADOOP-4413:
--
For the scheduler log entries that are meant for huma
Edits log takes much longer to load
---
Key: HADOOP-4425
URL: https://issues.apache.org/jira/browse/HADOOP-4425
Project: Hadoop Core
Issue Type: Bug
Components: dfs
Affects Versions: 0.19.0
[
https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640031#action_12640031
]
Hadoop QA commented on HADOOP-4398:
---
-1 overall. Here are the results of testing the la
menu layout change for Hadoop documentation
---
Key: HADOOP-4424
URL: https://issues.apache.org/jira/browse/HADOOP-4424
Project: Hadoop Core
Issue Type: Improvement
Components: documentation
Is there a way to change number of mappers in Hadoop streaming command line?
I know I can change hadoop-default.xml:
mapred.map.tasks
10
The default number of map tasks per job. Typically set
to a prime several times greater than number of available hosts.
Ignored when mapred.job.track
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1263#action_1263
]
Raghu Angadi commented on HADOOP-4358:
--
> I don't think we can achieve this if we do
[
https://issues.apache.org/jira/browse/HADOOP-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639998#action_12639998
]
Hadoop QA commented on HADOOP-4422:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639993#action_12639993
]
Hadoop QA commented on HADOOP-3155:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639991#action_12639991
]
Arun C Murthy commented on HADOOP-4421:
---
I propose we bite the bullet and introduce
[
https://issues.apache.org/jira/browse/HADOOP-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-4053:
--
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Availa
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639988#action_12639988
]
Konstantin Shvachko commented on HADOOP-4358:
-
Yes, the image stores the long
[
https://issues.apache.org/jira/browse/HADOOP-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-4423:
---
Fix Version/s: 0.18.2
Summary: FSDataset.getStoredBlock(id) should
[
https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Wyckoff updated HADOOP-4398:
-
Assignee: Pete Wyckoff
Status: Patch Available (was: Open)
> fuse-dfs per FD context is n
[
https://issues.apache.org/jira/browse/HADOOP-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Wyckoff updated HADOOP-4398:
-
Attachment: HADOOP-4398.1.txt
this patch fixes all threading issues
> fuse-dfs per FD context
FSDataset.getStoredBlock(id) should not revert corrupted information
Key: HADOOP-4423
URL: https://issues.apache.org/jira/browse/HADOOP-4423
Project: Hadoop Core
Issue Type
[
https://issues.apache.org/jira/browse/HADOOP-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Phillips updated HADOOP-4422:
---
Attachment: hadoop-s3n-nocreate.patch
Simple patch that removes bucket creation.
> S3 nativ
S3 native fs should not create bucket
-
Key: HADOOP-4422
URL: https://issues.apache.org/jira/browse/HADOOP-4422
Project: Hadoop Core
Issue Type: Bug
Components: fs/s3
Affects Versions: 0.18.1
[
https://issues.apache.org/jira/browse/HADOOP-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Phillips updated HADOOP-4422:
---
Status: Patch Available (was: Open)
> S3 native fs should not create bucket
> -
[
https://issues.apache.org/jira/browse/HADOOP-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639965#action_12639965
]
Sameer Paranjpye commented on HADOOP-4278:
--
@Dhruba: I agree that this is not a b
[
https://issues.apache.org/jira/browse/HADOOP-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Wyckoff updated HADOOP-4397:
-
Attachment: HADOOP-4397.3.txt
sorry - this one includes the TestFuseDFS.java in the right place.
[
https://issues.apache.org/jira/browse/HADOOP-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pete Wyckoff updated HADOOP-4397:
-
Attachment: HADOOP-4397.2.txt
I suggest we use this patch which fixes both bugs and is the versi
Rework job-setup and job-cleanup tasks
--
Key: HADOOP-4421
URL: https://issues.apache.org/jira/browse/HADOOP-4421
Project: Hadoop Core
Issue Type: Bug
Components: mapred
Affects Versions: 0.1
[
https://issues.apache.org/jira/browse/HADOOP-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639958#action_12639958
]
Tsz Wo (Nicholas), SZE commented on HADOOP-2658:
TC7 failed is because Dat
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-4358:
-
Attachment: HADOOP-4358.patch
Does the attached patch fix this issue and 'precision' related con
[
https://issues.apache.org/jira/browse/HADOOP-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-4373:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Than
[
https://issues.apache.org/jira/browse/HADOOP-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639944#action_12639944
]
Hadoop QA commented on HADOOP-4053:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639942#action_12639942
]
Runping Qi commented on HADOOP-4396:
Can you capture the stacktraces of those straggle
[
https://issues.apache.org/jira/browse/HADOOP-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639940#action_12639940
]
Hadoop QA commented on HADOOP-4373:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639939#action_12639939
]
Raghu Angadi commented on HADOOP-4358:
--
Fortunately, fsimage does not depend on preci
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639935#action_12639935
]
Raghu Angadi commented on HADOOP-4358:
--
It seems like getAccessTime() is unnecessari
Folks, can we shoot to have all the blockers fixed and committed by
end-of-day on Tuesday, Oct 20? I'll then call of vote Wednesday
morning.
Nige
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639932#action_12639932
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4358:
Konstantin> This will be
[
https://issues.apache.org/jira/browse/HADOOP-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639929#action_12639929
]
Raghu Angadi commented on HADOOP-4278:
--
The fact that TestDatanodeDeath is unpredicta
[
https://issues.apache.org/jira/browse/HADOOP-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639924#action_12639924
]
dhruba borthakur commented on HADOOP-4404:
--
+1 for a fix in 0.19.
> saveFSImage
[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639927#action_12639927
]
dhruba borthakur commented on HADOOP-4358:
--
Is it possible to come up with a solu
[
https://issues.apache.org/jira/browse/HADOOP-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-4236.
---
Resolution: Fixed
I just committed this. Thanks, Sharad!
> JobTracker.killJob() fails to ki
[
https://issues.apache.org/jira/browse/HADOOP-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639925#action_12639925
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4278:
It seems that it will be
[
https://issues.apache.org/jira/browse/HADOOP-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639923#action_12639923
]
dhruba borthakur commented on HADOOP-4278:
--
@Sameer: I agree that out test is tri
[
https://issues.apache.org/jira/browse/HADOOP-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-3155:
-
Priority: Blocker (was: Major)
I am marking this as a blocker for 0.19.
> reducers stu
[
https://issues.apache.org/jira/browse/HADOOP-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-3155:
-
Status: Patch Available (was: Open)
> reducers stuck at shuffling
> --
[
https://issues.apache.org/jira/browse/HADOOP-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-3155:
-
Attachment: fetcherThread.patch
Fix findbugs issue.
> reducers stuck at shuffling
> --
[
https://issues.apache.org/jira/browse/HADOOP-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-3155:
-
Status: Open (was: Patch Available)
Fix findbugs error.
> reducers stuck at shuffling
[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639908#action_12639908
]
Raghu Angadi commented on HADOOP-4044:
--
One of the issues with 'resolve then open' ap
[
https://issues.apache.org/jira/browse/HADOOP-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639907#action_12639907
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4416:
+1 for trimming in getCla
[
https://issues.apache.org/jira/browse/HADOOP-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639902#action_12639902
]
Hadoop QA commented on HADOOP-4236:
---
-1 overall. Here are the results of testing the la
[
https://issues.apache.org/jira/browse/HADOOP-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-4053:
---
Status: Open (was: Patch Available)
> Schedulers need to know when a job has completed
> --
[
https://issues.apache.org/jira/browse/HADOOP-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-4053:
---
Attachment: HADOOP-4053-v5.5.patch
Attaching a patch that fixes {{TestJobQueueInformation}}.
{{Test
[
https://issues.apache.org/jira/browse/HADOOP-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-4053:
---
Status: Patch Available (was: Open)
> Schedulers need to know when a job has completed
> --
[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639892#action_12639892
]
Raghu Angadi commented on HADOOP-4044:
--
>First, we implement the naive approach, benc
[
https://issues.apache.org/jira/browse/HADOOP-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639889#action_12639889
]
Hemanth Yamijala commented on HADOOP-4419:
--
One thing to consider is how to infor
[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639888#action_12639888
]
Doug Cutting commented on HADOOP-4044:
--
Sanjay> I really don't like the extra rpc [ .
[
https://issues.apache.org/jira/browse/HADOOP-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639887#action_12639887
]
Hemanth Yamijala commented on HADOOP-4419:
--
I verified that when the setJobPriori
[
https://issues.apache.org/jira/browse/HADOOP-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639869#action_12639869
]
Nigel Daley commented on HADOOP-4416:
-
If this isn't a regression, then this isn't for
[
https://issues.apache.org/jira/browse/HADOOP-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639867#action_12639867
]
Sameer Paranjpye commented on HADOOP-4278:
--
> It is likely to be a problem with t
See http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/634/changes
[
https://issues.apache.org/jira/browse/HADOOP-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639856#action_12639856
]
Hudson commented on HADOOP-4150:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639854#action_12639854
]
Hudson commented on HADOOP-4361:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639858#action_12639858
]
Hudson commented on HADOOP-4410:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639855#action_12639855
]
Hudson commented on HADOOP-3790:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639861#action_12639861
]
Hudson commented on HADOOP-4400:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639860#action_12639860
]
Hudson commented on HADOOP-4403:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639859#action_12639859
]
Hudson commented on HADOOP-4287:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639852#action_12639852
]
Hudson commented on HADOOP-4376:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639848#action_12639848
]
Hudson commented on HADOOP-4395:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639857#action_12639857
]
Hudson commented on HADOOP-3814:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639853#action_12639853
]
Hudson commented on HADOOP-4351:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639850#action_12639850
]
Hudson commented on HADOOP-4393:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639851#action_12639851
]
Hudson commented on HADOOP-4378:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639849#action_12639849
]
Hudson commented on HADOOP-4014:
Integrated in Hadoop-trunk #634 (See
[http://hudson.zone
[
https://issues.apache.org/jira/browse/HADOOP-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-3217:
-
Attachment: HADOOP-3217
Patch for Hadoop 0.18. I've verified this also applies to 0.19 a
[
https://issues.apache.org/jira/browse/HADOOP-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639844#action_12639844
]
Hemanth Yamijala commented on HADOOP-3217:
--
I found a bug while testing the previ
[
https://issues.apache.org/jira/browse/HADOOP-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-3217:
-
Attachment: HADOOP-3217.patch.0.17
> [HOD] Be less agressive when querying job status fr
[
https://issues.apache.org/jira/browse/HADOOP-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639839#action_12639839
]
Hemanth Yamijala commented on HADOOP-4373:
--
Since this patch touches only capacit
[
https://issues.apache.org/jira/browse/HADOOP-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639836#action_12639836
]
Hemanth Yamijala commented on HADOOP-4035:
--
bq. This patch is a big risky patch t
JobTracker.killJob() doesn't check for the JobID being valid
Key: HADOOP-4420
URL: https://issues.apache.org/jira/browse/HADOOP-4420
Project: Hadoop Core
Issue Type: Bug
1 - 100 of 133 matches
Mail list logo
