hdfs datanode can not register to namenode due to L2TP with NAT( not sure )
up vote
0
down vote
favorite
Hi everyone i v come up with a problem which involves lots of techs and i m not sure i can describe it properly..
first my network topology:
lab 1 (datanode1~5)
< client - L2TP vpn ( with NAT on ) - server >
lab 2 (datanode 6~8 and namenode 1~2)
lab 1 datanode IP 192.169.88.x
lab 2 datanode IP 192.168.77.x
L2TP : lab 1 77.77.77.254 -> 77.77.77.1 lab 2
when i start a datanode in lab1 , in lab 2's namenode, i can see register request came up , but with wrong IP address ( 77.77.77.254 which is VPN client, or NAT IP ) not then exact datanode IP.
in my knowledge tunnel tranportation should not be awared by applications , but why hdfs get this IP address . ?
BTW , in the same topo, YARN cluster works just fine with all the node active.
( yarn resorcemanager is located in lab2, and nodemanager located in lab1)
it confused me for a bit long time, so very appreciate any help , thanks !
hdfs l2tp
asked Nov 20 at 7:26
knight.tong
12
add a comment |
up vote
0
down vote
favorite
Hi everyone i v come up with a problem which involves lots of techs and i m not sure i can describe it properly..
first my network topology:
lab 1 (datanode1~5)
< client - L2TP vpn ( with NAT on ) - server >
lab 2 (datanode 6~8 and namenode 1~2)
lab 1 datanode IP 192.169.88.x
lab 2 datanode IP 192.168.77.x
L2TP : lab 1 77.77.77.254 -> 77.77.77.1 lab 2
when i start a datanode in lab1 , in lab 2's namenode, i can see register request came up , but with wrong IP address ( 77.77.77.254 which is VPN client, or NAT IP ) not then exact datanode IP.
in my knowledge tunnel tranportation should not be awared by applications , but why hdfs get this IP address . ?
BTW , in the same topo, YARN cluster works just fine with all the node active.
( yarn resorcemanager is located in lab2, and nodemanager located in lab1)
it confused me for a bit long time, so very appreciate any help , thanks !
hdfs l2tp
asked Nov 20 at 7:26
knight.tong
12
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Hi everyone i v come up with a problem which involves lots of techs and i m not sure i can describe it properly..
first my network topology:
lab 1 (datanode1~5)
< client - L2TP vpn ( with NAT on ) - server >
lab 2 (datanode 6~8 and namenode 1~2)
lab 1 datanode IP 192.169.88.x
lab 2 datanode IP 192.168.77.x
L2TP : lab 1 77.77.77.254 -> 77.77.77.1 lab 2
when i start a datanode in lab1 , in lab 2's namenode, i can see register request came up , but with wrong IP address ( 77.77.77.254 which is VPN client, or NAT IP ) not then exact datanode IP.
in my knowledge tunnel tranportation should not be awared by applications , but why hdfs get this IP address . ?
BTW , in the same topo, YARN cluster works just fine with all the node active.
( yarn resorcemanager is located in lab2, and nodemanager located in lab1)
it confused me for a bit long time, so very appreciate any help , thanks !
hdfs l2tp
asked Nov 20 at 7:26
knight.tong
12
Hi everyone i v come up with a problem which involves lots of techs and i m not sure i can describe it properly..
first my network topology:
lab 1 (datanode1~5)
< client - L2TP vpn ( with NAT on ) - server >
lab 2 (datanode 6~8 and namenode 1~2)
lab 1 datanode IP 192.169.88.x
lab 2 datanode IP 192.168.77.x
L2TP : lab 1 77.77.77.254 -> 77.77.77.1 lab 2
when i start a datanode in lab1 , in lab 2's namenode, i can see register request came up , but with wrong IP address ( 77.77.77.254 which is VPN client, or NAT IP ) not then exact datanode IP.
in my knowledge tunnel tranportation should not be awared by applications , but why hdfs get this IP address . ?
BTW , in the same topo, YARN cluster works just fine with all the node active.
( yarn resorcemanager is located in lab2, and nodemanager located in lab1)
it confused me for a bit long time, so very appreciate any help , thanks !
hdfs l2tp
hdfs l2tp
asked Nov 20 at 7:26
knight.tong
12
asked Nov 20 at 7:26
knight.tong
12
asked Nov 20 at 7:26
knight.tong
12
asked Nov 20 at 7:26
knight.tong
12
asked Nov 20 at 7:26
knight.tong
12
12
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53388125%2fhdfs-datanode-can-not-register-to-namenode-due-to-l2tp-with-nat-not-sure%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
