DFS client lost lease during writing into DFS files
---
Key: HADOOP-2669
URL: https://issues.apache.org/jira/browse/HADOOP-2669
Project: Hadoop
Issue Type: Bug
Components: dfs
[
https://issues.apache.org/jira/browse/HADOOP-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560637#action_12560637
]
Runping Qi commented on HADOOP-2663:
On the flip side, the Buffer should provide a co
Buffer class' toString method should accept a code name for "true" utf-8
codeName
--
Key: HADOOP-2663
URL: https://issues.apache.org/jira/browse/HADOOP-2663
Project: Had
[
https://issues.apache.org/jira/browse/HADOOP-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559815#action_12559815
]
Runping Qi commented on HADOOP-2608:
Forgot one point: when scanning sequence files wi
[
https://issues.apache.org/jira/browse/HADOOP-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559812#action_12559812
]
Runping Qi commented on HADOOP-2608:
I profiled the program of reading sequence files
Reading sequence file consumes 100% cpu with maximum throughput being about
5MB/sec per process
---
Key: HADOOP-2608
URL: https://issues.apache.org/jira/browse/HADOOP-2608
[
https://issues.apache.org/jira/browse/HADOOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558749#action_12558749
]
Runping Qi commented on HADOOP-2491:
A great analysis.
+2
Especially like the conce
[
https://issues.apache.org/jira/browse/HADOOP-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558147#action_12558147
]
Runping Qi commented on HADOOP-2581:
Cool.
That will address the first 2 items.
Is
Counters and other useful stats should be logged into Job History log
-
Key: HADOOP-2581
URL: https://issues.apache.org/jira/browse/HADOOP-2581
Project: Hadoop
Issue Type: I
[
https://issues.apache.org/jira/browse/HADOOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558029#action_12558029
]
Runping Qi commented on HADOOP-2178:
Even with hod JT, we still need to address case
[
https://issues.apache.org/jira/browse/HADOOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557720#action_12557720
]
Runping Qi commented on HADOOP-2570:
Lohit's suggestion should work.
> streaming
Combining multiple input blocks into one mapper
---
Key: HADOOP-2560
URL: https://issues.apache.org/jira/browse/HADOOP-2560
Project: Hadoop
Issue Type: Bug
Reporter: Runping Qi
Curre
DFS should place one replica per rack
-
Key: HADOOP-2559
URL: https://issues.apache.org/jira/browse/HADOOP-2559
Project: Hadoop
Issue Type: Improvement
Components: dfs
Reporter: Runpi
[
https://issues.apache.org/jira/browse/HADOOP-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557292#action_12557292
]
Runping Qi commented on HADOOP-1876:
I am fine with the approach of this patch if it
[
https://issues.apache.org/jira/browse/HADOOP-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi reassigned HADOOP-2094:
--
Assignee: dhruba borthakur
> DFS should not use round robin policy in determing on which volum
[
https://issues.apache.org/jira/browse/HADOOP-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi reassigned HADOOP-2014:
--
Assignee: Devaraj Das
> Job Tracker should not clobber the data locality of tasks
> --
[
https://issues.apache.org/jira/browse/HADOOP-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi reassigned HADOOP-2144:
--
Assignee: dhruba borthakur
> Data node process consumes 180% cpu
> --
[
https://issues.apache.org/jira/browse/HADOOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556914#action_12556914
]
Runping Qi commented on HADOOP-2178:
+1.
This is much clearer.
Need coordination in
[
https://issues.apache.org/jira/browse/HADOOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556630#action_12556630
]
Runping Qi commented on HADOOP-2178:
BTW, Is this issue the same as H-1876
(https://
[
https://issues.apache.org/jira/browse/HADOOP-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556584#action_12556584
]
Runping Qi commented on HADOOP-1876:
The point is that you don't need to write Runnin
[
https://issues.apache.org/jira/browse/HADOOP-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556498#action_12556498
]
Runping Qi commented on HADOOP-1876:
You can add counter information to JobHistory dat
[
https://issues.apache.org/jira/browse/HADOOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555439#action_12555439
]
Runping Qi commented on HADOOP-2178:
The output data may be deleted anytime when it i
[
https://issues.apache.org/jira/browse/HADOOP-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555372#action_12555372
]
Runping Qi commented on HADOOP-2501:
bin/hadoop seq -head assumes the key/value class
[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553958
]
Runping Qi commented on HADOOP-1298:
Since the file sizes to read/write are very small, the NNBench should not
[
https://issues.apache.org/jira/browse/HADOOP-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552244
]
Runping Qi commented on HADOOP-2437:
Similar problem due to round robin placement policy happens in DFS data n
[
https://issues.apache.org/jira/browse/HADOOP-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552074
]
Runping Qi commented on HADOOP-1336:
Speculative execution does not work well without the patch for hadoop-1281
[
https://issues.apache.org/jira/browse/HADOOP-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552033
]
Runping Qi commented on HADOOP-2433:
There is already a proper input format class: KeyValueTextInputFormat for
[
https://issues.apache.org/jira/browse/HADOOP-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551923
]
Runping Qi commented on HADOOP-2429:
+1
To enforce that, the API should use concrete classes (such as Buffer) i
[
https://issues.apache.org/jira/browse/HADOOP-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550763
]
Runping Qi commented on HADOOP-2369:
+1
> Representative mix of jobs for large cluster throughput benchmarking
JobHistory log files contain data that cannot be parsed by
org.apache.hadoop.mapred.JobHistory
--
Key: HADOOP-2403
URL: https://issues.apache.org/jira/browse/HADOOP-2403
[
https://issues.apache.org/jira/browse/HADOOP-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542896
]
Runping Qi commented on HADOOP-2141:
I don't think this Jira is that urgent and we have to have a quick patch
[
https://issues.apache.org/jira/browse/HADOOP-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542861
]
Runping Qi commented on HADOOP-2141:
The above proposal sounds reasonable.
Here are some points to consider:
1
[
https://issues.apache.org/jira/browse/HADOOP-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541828
]
Runping Qi commented on HADOOP-1984:
It will be really helpful if we know the overall job progress status,
and
[
https://issues.apache.org/jira/browse/HADOOP-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541817
]
Runping Qi commented on HADOOP-1984:
Ten minutes waiting interval seems too much.
When the interval reach a few
[
https://issues.apache.org/jira/browse/HADOOP-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541388
]
Runping Qi commented on HADOOP-2141:
+1
Speculative execution should start of the original execution is a lot
[
https://issues.apache.org/jira/browse/HADOOP-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541386
]
Runping Qi commented on HADOOP-2175:
The criteria for starting a speculative execution should also include
how
Each task tracker should not execute more than one speculative task
---
Key: HADOOP-2180
URL: https://issues.apache.org/jira/browse/HADOOP-2180
Project: Hadoop
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541350
]
Runping Qi commented on HADOOP-2175:
then we need to try the patch for hadoop-1984.
Currently, a job may stall f
[
https://issues.apache.org/jira/browse/HADOOP-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541240
]
Runping Qi commented on HADOOP-2175:
I was using hadoop 0.15.0.
is the patch for hadoop-1158 in 0.15.0?
if so,
Speculative execution does not work properly
Key: HADOOP-2177
URL: https://issues.apache.org/jira/browse/HADOOP-2177
Project: Hadoop
Issue Type: Bug
Components: mapred
Report
Blacklisted hosts may not be able to serve map outputs
--
Key: HADOOP-2175
URL: https://issues.apache.org/jira/browse/HADOOP-2175
Project: Hadoop
Issue Type: Bug
Components: mapre
[
https://issues.apache.org/jira/browse/HADOOP-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540774
]
Runping Qi commented on HADOOP-2164:
My input data is in SequenceFile.
Only one map outputt segment file had th
[
https://issues.apache.org/jira/browse/HADOOP-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540772
]
Runping Qi commented on HADOOP-2164:
All attempts failed. The job failed eventually.
> Reducer sort failed d
Reducer sort failed due to wrong key class
--
Key: HADOOP-2164
URL: https://issues.apache.org/jira/browse/HADOOP-2164
Project: Hadoop
Issue Type: Bug
Components: mapred
Reporter:
mapper failed due to exceptions
---
Key: HADOOP-2163
URL: https://issues.apache.org/jira/browse/HADOOP-2163
Project: Hadoop
Issue Type: Bug
Components: mapred
Reporter: Runping Qi
>From t
[
https://issues.apache.org/jira/browse/HADOOP-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539635
]
Runping Qi commented on HADOOP-2144:
Overall cpu usage is 90+%.
It is easy to reproduce.
> Data node process
Data node process consumes 180% cpu
Key: HADOOP-2144
URL: https://issues.apache.org/jira/browse/HADOOP-2144
Project: Hadoop
Issue Type: Improvement
Reporter: Runping Qi
I did a test on DFS
[
https://issues.apache.org/jira/browse/HADOOP-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2144:
---
Component/s: dfs
Description:
I did a test on DFS read throughput and found that the data node
[
https://issues.apache.org/jira/browse/HADOOP-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi resolved HADOOP-2060.
Resolution: Invalid
The suggested feature is already in.
> DFSClient should choose a block that
[
https://issues.apache.org/jira/browse/HADOOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539581
]
Runping Qi commented on HADOOP-2086:
+1
Looks good.
> ability to add dependencies to a job after constructio
[
https://issues.apache.org/jira/browse/HADOOP-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538678
]
Runping Qi commented on HADOOP-2119:
Yes, the #running-mappers kept on going up and went beyond the actual numb
JobTracker becomes non-responsive if the task trackers finish task too fast
---
Key: HADOOP-2119
URL: https://issues.apache.org/jira/browse/HADOOP-2119
Project: Hadoop
I
[
https://issues.apache.org/jira/browse/HADOOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538534
]
Runping Qi commented on HADOOP-2086:
There is no real harm to make getState synchronized,
although either way i
[
https://issues.apache.org/jira/browse/HADOOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538051
]
Runping Qi commented on HADOOP-2086:
+1.
> ability to add dependencies to a job after construction
>
[
https://issues.apache.org/jira/browse/HADOOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538017
]
Runping Qi commented on HADOOP-2086:
Right. WAITING is the only valid state we can add a dependending job.
sub
[
https://issues.apache.org/jira/browse/HADOOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537706
]
runping edited comment on HADOOP-2086 at 10/25/07 1:54 PM:
--
I like 1).
Yes, there is a
[
https://issues.apache.org/jira/browse/HADOOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537706
]
Runping Qi commented on HADOOP-2086:
I like 1).
Yes, there is a possibility of race condition when the JobCont
[
https://issues.apache.org/jira/browse/HADOOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537653
]
Runping Qi commented on HADOOP-2086:
+0 the code looks good.
However, the semantics of the new api addDepending
[
https://issues.apache.org/jira/browse/HADOOP-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537492
]
Runping Qi commented on HADOOP-2095:
Yes.
> Reducer failed due to Out ofMemory
> -
[
https://issues.apache.org/jira/browse/HADOOP-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537162
]
Runping Qi commented on HADOOP-2095:
The problem was gone after I set the compressMapOutput attribute to false.
[
https://issues.apache.org/jira/browse/HADOOP-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2095:
---
Component/s: mapred
Fix Version/s: 0.15.0
Description:
One of the reducers of my job fa
Reducer failed due to Out ofMemory
--
Key: HADOOP-2095
URL: https://issues.apache.org/jira/browse/HADOOP-2095
Project: Hadoop
Issue Type: Bug
Reporter: Runping Qi
One of the reducers of my job
[
https://issues.apache.org/jira/browse/HADOOP-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi reassigned HADOOP-2094:
--
Assignee: (was: Runping Qi)
> DFS should not use round robin policy in determing on which
DFS should not use round robin policy in determing on which volume (file system
partition) to allocate for the next block
--
Key: HADOOP-2094
[
https://issues.apache.org/jira/browse/HADOOP-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2093:
---
Component/s: mapred
dfs
Description:
The summary is a bit of long. But the basi
DFS should provide partition information for blocks, and map/reduce should
schedule avoid schedule mappers with the splits off the same file system
partition at the same time
--
[
https://issues.apache.org/jira/browse/HADOOP-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535529
]
Runping Qi commented on HADOOP-1965:
It seems clear that threaded spill performed much better than sequence spi
[
https://issues.apache.org/jira/browse/HADOOP-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534962
]
Runping Qi commented on HADOOP-2060:
OK, that is the part I didn't get.
I'll examine the location list to confi
DFSClient should choose a block that is local to the node where the client is
running
-
Key: HADOOP-2060
URL: https://issues.apache.org/jira/browse/HADOOP-2060
Projec
[
https://issues.apache.org/jira/browse/HADOOP-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534716
]
Runping Qi commented on HADOOP-2050:
It turned out to be a problem in CopyFile class.
After a mapper got killed
[
https://issues.apache.org/jira/browse/HADOOP-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2050:
---
Component/s: (was: dfs)
mapred
> distcp failed due to problem in creating files
[
https://issues.apache.org/jira/browse/HADOOP-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534570
]
Runping Qi commented on HADOOP-2050:
This problem does not happen if the dfs write load is low.
When a few mappe
[
https://issues.apache.org/jira/browse/HADOOP-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2050:
---
Description:
When I run a distcp program to copy files from one dfs to another, my job
failed with
[
https://issues.apache.org/jira/browse/HADOOP-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2052:
---
Description:
When the mappers of distcp finish, the status page in the web gui reports the
data cop
[
https://issues.apache.org/jira/browse/HADOOP-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2052:
---
Component/s: mapred
Description:
When the mappers of distcp finish, the status page in the web g
distcp mapper's status report misleading
Key: HADOOP-2052
URL: https://issues.apache.org/jira/browse/HADOOP-2052
Project: Hadoop
Issue Type: Bug
Reporter: Runping Qi
When the mappers of
[
https://issues.apache.org/jira/browse/HADOOP-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534462
]
Runping Qi commented on HADOOP-2050:
Some mappers failed with the following exception:
org.apache.hadoop.ipc.R
[
https://issues.apache.org/jira/browse/HADOOP-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2050:
---
Component/s: dfs
I suspect this is a problem in dfs.
> distcp failed due to problem in creating f
distcp failed due to problem in creating files
--
Key: HADOOP-2050
URL: https://issues.apache.org/jira/browse/HADOOP-2050
Project: Hadoop
Issue Type: Bug
Reporter: Runping Qi
When I
[
https://issues.apache.org/jira/browse/HADOOP-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2050:
---
Description:
When I run a distcp program to copy files from one dfs to another, my job
failed
DISTCP mapper should report progress more often
---
Key: HADOOP-2048
URL: https://issues.apache.org/jira/browse/HADOOP-2048
Project: Hadoop
Issue Type: Bug
Reporter: Runping Qi
When
[
https://issues.apache.org/jira/browse/HADOOP-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534401
]
Runping Qi commented on HADOOP-2042:
The current trunk. I guess it is 0.15
> distcp job failed
> -
[
https://issues.apache.org/jira/browse/HADOOP-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2042:
---
Component/s: dfs
Description:
I was running distcp to copy data from one dfs to another.
The job
distcp job failed
-
Key: HADOOP-2042
URL: https://issues.apache.org/jira/browse/HADOOP-2042
Project: Hadoop
Issue Type: Bug
Affects Versions: 0.15.0
Reporter: Runping Qi
I was running distcp to copy data fr
distcp split generation does not work correctly
---
Key: HADOOP-2032
URL: https://issues.apache.org/jira/browse/HADOOP-2032
Project: Hadoop
Issue Type: Bug
Components: util
Re
[
https://issues.apache.org/jira/browse/HADOOP-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533904
]
Runping Qi commented on HADOOP-2028:
the job fails too if the specified log dir is not empty
> distcp fails if
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Status: Patch Available (was: Open)
> Job tracker should report the number of splits that are local
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Attachment: (was: hadoop-2015.txt)
> Job tracker should report the number of splits that are loc
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Status: Open (was: Patch Available)
a more optimized patch is available
> Job tracker should repo
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Attachment: hadoop-2015.txt
a better one
> Job tracker should report the number of splits that are
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Attachment: hadoop-2015.txt
Fix a bug in the patch
> Job tracker should report the number of split
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Status: Patch Available (was: Open)
> Job tracker should report the number of splits that are local
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Attachment: (was: hadoop-2015.txt)
> Job tracker should report the number of splits that are loc
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Status: Open (was: Patch Available)
Need some more change
> Job tracker should report the number
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Status: Patch Available (was: Open)
> Job tracker should report the number of splits that are local
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2015:
---
Attachment: hadoop-2015.txt
a patch that adds a counter for the total number of tasks
that may be
[
https://issues.apache.org/jira/browse/HADOOP-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi reassigned HADOOP-2015:
--
Assignee: Runping Qi
> Job tracker should report the number of splits that are local to some t
Job tracker should report the number of splits that are local to some task
trackers
---
Key: HADOOP-2015
URL: https://issues.apache.org/jira/browse/HADOOP-2015
Project: H
[
https://issues.apache.org/jira/browse/HADOOP-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-2014:
---
Component/s: mapred
Description:
Currently, when the Job Tracker assigns a mapper task to a task
Job Tracker should not clobber the data locality of tasks
-
Key: HADOOP-2014
URL: https://issues.apache.org/jira/browse/HADOOP-2014
Project: Hadoop
Issue Type: Bug
Reporter:
1 - 100 of 427 matches
Mail list logo
