[
https://issues.apache.org/jira/browse/HDFS-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanping Wang updated HDFS-1365:
-------------------------------
Attachment: HDFS1365-branch1052-3.patch
Regarding to
-- newBlockPoolID - if we cannot get new IP , should we use "unknownIP" or
throw an exception?
We decided to throw an exception if we can not get IP address of the default
interface. Not able to get IP address of default interface would indicate some
serious problem. Generating of new blockpoolID will be stopped if we run into
situation like such. We will log a warning message ( to give a clue to users
of what's going on) and throw UnknownHostException. A new patch is attached.
private String newBlockPoolID() throws UnknownHostException{
String ip = "unknownIP";
try {
ip = DNS.getDefaultIP("default");
} catch (UnknownHostException e) {
LOG.warn("Could not find ip address of \"default\" inteface.");
throw e;
}
....
> HDFS federation: propose ClusterID and BlockPoolID format
> ---------------------------------------------------------
>
> Key: HDFS-1365
> URL: https://issues.apache.org/jira/browse/HDFS-1365
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Tanping Wang
> Assignee: Tanping Wang
> Fix For: Federation Branch
>
> Attachments: HDFS1365-branch-HDFS1052.1.patch,
> HDFS1365-branch1052-2.patch, HDFS1365-branch1052-3.patch,
> HDFS1365-branch1052-3.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
