Jinghui Wang created HADOOP-9989:
Summary: Bug introduced in HADOOP-9374, which parses the
-tokenCacheFile as binary file but set it to the configuration as JSON file.
Key: HADOOP-9989
URL: https://issues.apache.o
[
https://issues.apache.org/jira/browse/HADOOP-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe resolved HADOOP-7344.
--
Tags:
Resolution: Fixed
Fix Version/s: 2.3.0
Ass
[
https://issues.apache.org/jira/browse/HADOOP-9988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved HADOOP-9988.
--
Resolution: Duplicate
Release Note: creating JIRA has some issues, closing this d
Lohit Vijayarenu created HADOOP-9988:
Summary: HDFS Compatible ViewFileSystem
Key: HADOOP-9988
URL: https://issues.apache.org/jira/browse/HADOOP-9988
Project: Hadoop Common
Issue Type: Bu
Lohit Vijayarenu created HADOOP-9985:
Summary: HDFS Compatible ViewFileSystem
Key: HADOOP-9985
URL: https://issues.apache.org/jira/browse/HADOOP-9985
Project: Hadoop Common
Issue Type: Bu
Colin Patrick McCabe created HADOOP-9984:
Summary: FileSystem#globStatus and FileSystem#listStatus should
resolve symlinks by default
Key: HADOOP-9984
URL: https://issues.apache.org/jira/browse/HADOOP-9984
Hi Wei,
Yes there is a clear lag between AM requesting resource and satisfying NM
heartbeats (thereby we process the event) are received. Developers in
project Tez ( http://incubator.apache.org/projects/tez.html ) have done
some similar stuff. You can check it there. I hope it helps.
Thanks,
Omka
Hey, Wei:
The nodeHeartBeat is used to let RM knows this NM is still alive. We
only assign containers from alive NM. Another thing is when scheduler
receives the nodeHeartBeat, the scheduler will get the container status
(such as completed, new launched) from NM, and it can use it to update t
Hi, all,
I have a simple question. Currently in YARN, the resource matching is triggered
by the node manager heartbeat. That is, assignContainers() is only invoked when
a new heartbeat comes in. Why we don't use resource request triggered
mechanism? That is, when AM submits allocateRequest, we
[
https://issues.apache.org/jira/browse/HADOOP-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran reopened HADOOP-9963:
> container-executor.c: error: expected expression
> -
[
https://issues.apache.org/jira/browse/HADOOP-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-9963.
Resolution: Duplicate
Fix Version/s: (was: 2.1.1-beta)
Release Note: (was
[
https://issues.apache.org/jira/browse/HADOOP-9983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-9983.
Resolution: Duplicate
Fix Version/s: 2.1.0-beta
> SocketInputStream class (org.
Puneet Srivastava created HADOOP-9983:
-
Summary: SocketInputStream class
(org.apache.hadoop.net.SocketInputStream) is not public class in 2.0.5-alpha
Key: HADOOP-9983
URL: https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/HADOOP-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaopo resolved HADOOP-9963.
Resolution: Fixed
Release Note: patch https://issues.apache.org/jira/browse/HADOOP-9648 thx
> co
Akira AJISAKA created HADOOP-9982:
-
Summary: A hyperlink doesn't work correctly in 'Cluster Setup'
document
Key: HADOOP-9982
URL: https://issues.apache.org/jira/browse/HADOOP-9982
Project: Hadoop Comm
15 matches
Mail list logo