getDatanodeReport can be moved to NameNodeProtocol from ClientProtocol
--
Key: HDFS-1155
URL: https://issues.apache.org/jira/browse/HDFS-1155
Project: Hadoop HDFS
Issue Type
Make Balancer run on the service port
-
Key: HDFS-1156
URL: https://issues.apache.org/jira/browse/HDFS-1156
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Dmytro Molkov
The balancer s
[
https://issues.apache.org/jira/browse/HDFS-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved HDFS-1002.
---
Resolution: Invalid
> Secondary Name Node crash, NPE in edit log replay
>
HDFS-1150 (https://issues.apache.org/jira/browse/Hdfs-1150), part of the
security initiative, is a rather big change to the way Datanodes are
started in a secure environment and the resources needed to start one.
I want to make sure the community gets a chance to review the approach
we're takin
Hey Jakob,
If I understand correctly, then two plausible ways of attacking a client are
then:
1) Screw up the client's DNS resolution somehow (reference the rather serious
DNS hijack that have gone on) and trick it to talk to an attacker's node.
2) Perform a MITM attack.
Since we are basing this
[
https://issues.apache.org/jira/browse/HDFS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved HDFS-417.
--
Resolution: Won't Fix
Yes, I agree - it seems the demand in the community isn't high for this at the
mom
[
https://issues.apache.org/jira/browse/HDFS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved HDFS-419.
--
Resolution: Won't Fix
> Add Thrift interface to JobTracker/TaskTracker
>
