[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18226: -- Fix Version/s: (was: 3.0.0) > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: New Feature >Reporter: Duo Xu >Assignee: Duo Xu >Priority: Major > Fix For: 1.4.0, 2.0.0-alpha-2, 2.0.0 > > Attachments: 18226.branch-1.txt, HBASE-18226-branch-1.patch, > HBASE-18226.001.patch, HBASE-18226.002.patch, HBASE-18226.003.patch, > HBASE-18226.004.patch, HBASE-18226.005.patch, HBASE-18226.006.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18226: --- Fix Version/s: 1.4.0 > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: New Feature >Reporter: Duo Xu >Assignee: Duo Xu > Fix For: 3.0.0, 1.4.0, 2.0.0-alpha-2 > > Attachments: 18226.branch-1.txt, HBASE-18226.001.patch, > HBASE-18226.002.patch, HBASE-18226.003.patch, HBASE-18226.004.patch, > HBASE-18226.005.patch, HBASE-18226.006.patch, HBASE-18226-branch-1.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Attachment: HBASE-18226-branch-1.patch Attach a patch for branch-1. Local build successfully and passed the tests "org.apache.hadoop.hbase.regionserver.TestRegionServerHostname". > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: New Feature >Reporter: Duo Xu >Assignee: Duo Xu > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: 18226.branch-1.txt, HBASE-18226.001.patch, > HBASE-18226.002.patch, HBASE-18226.003.patch, HBASE-18226.004.patch, > HBASE-18226.005.patch, HBASE-18226.006.patch, HBASE-18226-branch-1.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18226: --- Attachment: 18226.branch-1.txt What I committed to branch-1 > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: New Feature >Reporter: Duo Xu >Assignee: Duo Xu > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: 18226.branch-1.txt, HBASE-18226.001.patch, > HBASE-18226.002.patch, HBASE-18226.003.patch, HBASE-18226.004.patch, > HBASE-18226.005.patch, HBASE-18226.006.patch, HBASE-18226-branch-1.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18226: --- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0-alpha-2 3.0.0 Status: Resolved (was: Patch Available) > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: New Feature >Reporter: Duo Xu >Assignee: Duo Xu > Fix For: 3.0.0, 2.0.0-alpha-2 > > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch, > HBASE-18226.006.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Release Note: The following config is added by this JIRA: hbase.regionserver.hostname.disable.master.reversedns This config is for experts: don't set its value unless you really know what you are doing. When set to true, regionserver will use the current node hostname for the servername and HMaster will skip reverse DNS lookup and use the hostname sent by regionserver instead. Note that this config and hbase.regionserver.hostname are mutually exclusive. See https://issues.apache.org/jira/browse/HBASE-18226 for more details. Caution: please make sure rolling upgrade succeeds before turning on this feature. Update the release note. > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: New Feature >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch, > HBASE-18226.006.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18226: --- Issue Type: New Feature (was: Bug) > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: New Feature >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch, > HBASE-18226.006.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-18226: --- Summary: Disable reverse DNS lookup at HMaster and use the hostname provided by RegionServer (was: Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer) > Disable reverse DNS lookup at HMaster and use the hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch, > HBASE-18226.006.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Attachment: HBASE-18226.006.patch > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch, > HBASE-18226.006.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Patch Available (was: Open) Thanks [~tedyu]! Attache a new patch and trigger the build. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch, > HBASE-18226.006.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Open (was: Patch Available) > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Patch Available (was: In Progress) Trigger a new build. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: In Progress (was: Patch Available) > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu >Assignee: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Patch Available (was: Open) Use the name "hbase.regionserver.hostname.disable.master.reversedns". Trigger a new build. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Open (was: Patch Available) > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Attachment: HBASE-18226.005.patch > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch, HBASE-18226.005.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Patch Available (was: Open) Fix the whitespace and trigger a new build. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Attachment: HBASE-18226.004.patch > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Open (was: Patch Available) > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch, HBASE-18226.004.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.hostname.reported.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Description: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during RS reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble in 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In the other cases (not multihomed), I just want RS to use the hostname return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty(). I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.hostname.reported.to.master", is it a good name? Regarding the hostname returned by the RS node, I read the source code again (including hadoop-common dns.java). By default RS gets hostname by calling InetAddress.getLocalHost().getCanonicalHostName(). If users specify "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or some underlying system configuration changes (eg. modifying /etc/nsswitch.conf), it may first read from DNS or other sources instead of first checking /etc/hosts file. was: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during RS reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble in 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In the other cases (not multihomed), I just want RS to use the hostname return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty(). I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? Regarding the hostname returned by the RS node, I read the source code again (including hadoop-common dns.java). By default RS gets hostname by calling InetAddress.getLocalHost().getCanonicalHostName(). If users specify "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or some underlying system configuration changes (eg. modifying /etc/nsswitch.conf), it may first read from DNS or other sources instead of first checking /etc/hosts file. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Patch Available (was: Open) Trigger a new build. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.report.hostname.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Attachment: HBASE-18226.003.patch Change the configuration name to hbase.regionserver.hostname.reported.to.master. Fix the line format and add two tests: 1. hbase.regionserver.hostname and hbase.regionserver.hostname.reported.to.master are both set and exception should be thrown. 2. Only hbase.regionserver.hostname.reported.to.master is set to true and verify that no duplicate regionservers in zookeeper. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, > HBASE-18226.003.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.report.hostname.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Status: Open (was: Patch Available) > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In the other cases (not multihomed), I > just want RS to use the hostname return by the node and set it in > useThisHostnameInstead and pass to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node. > Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.report.hostname.to.master", is it a good name? > > Regarding the hostname returned by the RS node, I read the source code again > (including hadoop-common dns.java). By default RS gets hostname by calling > InetAddress.getLocalHost().getCanonicalHostName(). If users specify > "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or > some underlying system configuration changes (eg. modifying > /etc/nsswitch.conf), it may first read from DNS or other sources instead of > first checking /etc/hosts file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Description: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during RS reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble in 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In the other cases (not multihomed), I just want RS to use the hostname return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty(). I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? Regarding the hostname returned by the RS node, I read the source code again (including hadoop-common dns.java). By default RS gets hostname by calling InetAddress.getLocalHost().getCanonicalHostName(). If users specify "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or some underlying system configuration changes (eg. modifying /etc/nsswitch.conf), it may first read from DNS or other sources instead of first checking /etc/hosts file. was: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during RS reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble in 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In some cases, I just want RS to use the hostname return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty(). I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? Regarding the hostname returned by the RS node, I read the source code again (including hadoop-common dns.java). By default RS gets hostname by calling InetAddress.getLocalHost().getCanonicalHostName(). If users specify "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or some underlying system configuration changes (eg. modifying /etc/nsswitch.conf), it may first read from DNS or other sources instead of first checking /etc/hosts file. > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Description: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during RS reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble in 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In some cases, I just want RS to use the hostname return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty(). I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? Regarding the hostname returned by the RS node, I read the source code again (including hadoop-common dns.java). By default RS gets hostname by calling InetAddress.getLocalHost().getCanonicalHostName(). If users specify "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver" or some underlying system configuration changes (eg. modifying /etc/nsswitch.conf), it may first read from DNS or other sources instead of first checking /etc/hosts file. was: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during RS reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble in 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In some cases, I just want RS to use the hostname return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty(). I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Description: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during RS reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble in 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In some cases, I just want RS to use the hostname return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty(). I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? was: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble for 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In normal cases, I just want RS to use the hostname return by the node OS system and set it in useThisHostnameInstead and pass to HMaster. I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node OS system. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during > reportForDuty() . This has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during RS > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble in > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In some cases, I just want RS to use > the hostname return by the node and set it in useThisHostnameInstead and pass > to HMaster during reportForDuty(). > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Xu updated HBASE-18226: --- Description: Description updated: In some unusual network environment, forward DNS lookup is supported while reverse DNS lookup may not work properly. This JIRA is to address that HMaster uses the hostname passed from RS instead of doing reverse DNS lookup to tells RS which hostname to use during . This has already been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos. Currently "useThisHostnameInstead" is optional and RS by default only passes port, server start code and server current time info to HMaster during reportForDuty(). In order to use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. This causes some trouble for 1. some deployments managed by some management tools like Ambari, which maintains the same copy of hbase-site.xml across all the nodes. 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname value for each node. In normal cases, I just want RS to use the hostname return by the node OS system and set it in useThisHostnameInstead and pass to HMaster. I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead" will be set to the hostname RS gets from the node OS system. Then HMaster will skip reverse DNS lookup because it sees "useThisHostnameInstead" field is set in the request. "hbase.regionserver.report.hostname.to.master", is it a good name? > Disable reverse DNS lookup at HMaster and use default hostname provided by > RegionServer > --- > > Key: HBASE-18226 > URL: https://issues.apache.org/jira/browse/HBASE-18226 > Project: HBase > Issue Type: Bug >Reporter: Duo Xu > Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch > > > Description updated: > In some unusual network environment, forward DNS lookup is supported while > reverse DNS lookup may not work properly. > This JIRA is to address that HMaster uses the hostname passed from RS instead > of doing reverse DNS lookup to tells RS which hostname to use during . This > has already been implemented by HBASE-12954 by adding > "useThisHostnameInstead" field in RegionServerStatusProtos. > Currently "useThisHostnameInstead" is optional and RS by default only passes > port, server start code and server current time info to HMaster during > reportForDuty(). In order to use this field, users currently need to specify > "hbase.regionserver.hostname" on every regionserver node's hbase-site.xml. > This causes some trouble for > 1. some deployments managed by some management tools like Ambari, which > maintains the same copy of hbase-site.xml across all the nodes. > 2. HBASE-12954 is targeting multihomed hosts, which users want to manually > set the hostname value for each node. In normal cases, I just want RS to use > the hostname return by the node OS system and set it in > useThisHostnameInstead and pass to HMaster. > I would like to introduce a setting that if the setting is set to true, > "useThisHostnameInstead" will be set to the hostname RS gets from the node OS > system. Then HMaster will skip reverse DNS lookup because it sees > "useThisHostnameInstead" field is set in the request. > "hbase.regionserver.report.hostname.to.master", is it a good name? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description: (was: This JIRA is to address the similar problem as
HBASE-12954, but there are some little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. In current implementation when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster as part of RegionServerStartupRequest. HMaster will not do
reverse DNS lookup, which has been implemented in HBASE-12954. If users want to
provide their own hostnames in "*hbase.regionserver.hostname*",
"*hbase.regionserver.hostname.auto*" must be false.
I will submit a patch later today.)
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Attachment: HBASE-18226.002.patch
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. In current implementation when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
> will use the value returned by *rpcServices.isa.getHostName()* as the
> hostname overwriting whatever users specifies in
> "*hbase.regionserver.hostname*" and send to HMaster as part of
> RegionServerStartupRequest. HMaster will not do reverse DNS lookup, which has
> been implemented in HBASE-12954. If users want to provide their own hostnames
> in "*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must
> be false.
> I will submit a patch later today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Status: Patch Available (was: Open)
Remove whitespaces.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. In current implementation when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
> will use the value returned by *rpcServices.isa.getHostName()* as the
> hostname overwriting whatever users specifies in
> "*hbase.regionserver.hostname*" and send to HMaster as part of
> RegionServerStartupRequest. HMaster will not do reverse DNS lookup, which has
> been implemented in HBASE-12954. If users want to provide their own hostnames
> in "*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must
> be false.
> I will submit a patch later today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Status: Open (was: Patch Available)
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. In current implementation when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
> will use the value returned by *rpcServices.isa.getHostName()* as the
> hostname overwriting whatever users specifies in
> "*hbase.regionserver.hostname*" and send to HMaster as part of
> RegionServerStartupRequest. HMaster will not do reverse DNS lookup, which has
> been implemented in HBASE-12954. If users want to provide their own hostnames
> in "*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must
> be false.
> I will submit a patch later today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. In current implementation when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster as part of . HMaster will not do reverse DNS lookup, which has
been implemented in HBASE-12954. If users want to provide their own hostnames
in "*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must
be false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. In current implementation when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. In current implementation when regionserver starts,
> {code}
> String hostName =
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. In current implementation when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster as part of RegionServerStartupRequest. HMaster will not do
reverse DNS lookup, which has been implemented in HBASE-12954. If users want to
provide their own hostnames in "*hbase.regionserver.hostname*",
"*hbase.regionserver.hostname.auto*" must be false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. In current implementation when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster as part of . HMaster will not do reverse DNS lookup, which has
been implemented in HBASE-12954. If users want to provide their own hostnames
in "*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must
be false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. In current implementation when regionserver starts,
> {code}
>
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. In current implementation when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. When regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. In current implementation when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
>
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because HMaster VM's /etc/hosts does not have regionserver VM's FQDN
mappings. When regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because that will not resolves to FQDN we want. When regionserver
starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. When regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node. We do not want HMaster to do reverse
DNS lookup because that will not resolves to FQDN we want. When regionserver
starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node so we do not want HMaster to do
reverse DNS lookup because that will not resolves to FQDN we want. When
regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because that will not resolves to FQDN we want. When
> regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari or other configuration
management tools because each regionserver has a different value of this
setting, which means each node needs a different hbase-site.xml.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node so we do not want HMaster to do
reverse DNS lookup because that will not resolves to FQDN we want. When
regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari because each regionserver has a
different value of this setting.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node, then when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node so we do not want HMaster to do
> reverse DNS lookup because that will not resolves to FQDN we want. When
> regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs =
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Status: Patch Available (was: Open)
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari because each
> regionserver has a different value of this setting.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node, then when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
> will use the value returned by *rpcServices.isa.getHostName()* as the
> hostname overwriting whatever users specifies in
> "*hbase.regionserver.hostname*" and send to HMaster. HMaster will not do
> reverse DNS lookup, which has been implemented in HBASE-12954. If users want
> to provide their own hostnames in "*hbase.regionserver.hostname*",
> "*hbase.regionserver.hostname.auto*" must be false.
> I will submit a patch later today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Attachment: HBASE-18226.001.patch
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
> Attachments: HBASE-18226.001.patch
>
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari because each
> regionserver has a different value of this setting.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node, then when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
> will use the value returned by *rpcServices.isa.getHostName()* as the
> hostname overwriting whatever users specifies in
> "*hbase.regionserver.hostname*" and send to HMaster. HMaster will not do
> reverse DNS lookup, which has been implemented in HBASE-12954. If users want
> to provide their own hostnames in "*hbase.regionserver.hostname*",
> "*hbase.regionserver.hostname.auto*" must be false.
> I will submit a patch later today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Priority: Major (was: Minor)
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari because each
> regionserver has a different value of this setting.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node, then when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
> will use the value returned by *rpcServices.isa.getHostName()* as the
> hostname overwriting whatever users specifies in
> "*hbase.regionserver.hostname*" and send to HMaster. HMaster will not do
> reverse DNS lookup, which has been implemented in HBASE-12954. If users want
> to provide their own hostnames in "*hbase.regionserver.hostname*",
> "*hbase.regionserver.hostname.auto*" must be false.
> I will submit a patch later today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari because each regionserver has a
different value of this setting.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node, then when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
will use the value returned by *rpcServices.isa.getHostName()* as the hostname
overwriting whatever users specifies in "*hbase.regionserver.hostname*" and
send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"*hbase.regionserver.hostname*", "*hbase.regionserver.hostname.auto*" must be
false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari because each regionserver has a
different value of this setting.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node, then when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"hbase.regionserver.hostname.auto". If it is set to true, then Regionserver
will use the value returned by *_rpcServices.isa.getHostName()_* as the
hostname overwriting whatever users specifies in "hbase.regionserver.hostname"
and send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"hbase.regionserver.hostname", "hbase.regionserver.hostname.auto" must be false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
>Priority: Minor
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari because each
> regionserver has a different value of this setting.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node, then when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "*hbase.regionserver.hostname.auto*". If it is set to true, then Regionserver
> will use the value returned by *rpcServices.isa.getHostName()* as the
> hostname overwriting whatever users specifies in
> "*hbase.regionserver.hostname*" and send to HMaster. HMaster will not do
> reverse DNS lookup, which has been implemented in HBASE-12954.
[jira] [Updated] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Xu updated HBASE-18226:
---
Description:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari because each regionserver has a
different value of this setting.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node, then when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"hbase.regionserver.hostname.auto". If it is set to true, then Regionserver
will use the value returned by *_rpcServices.isa.getHostName()_* as the
hostname overwriting whatever users specifies in "hbase.regionserver.hostname"
and send to HMaster. HMaster will not do reverse DNS lookup, which has been
implemented in HBASE-12954. If users want to provide their own hostnames in
"hbase.regionserver.hostname", "hbase.regionserver.hostname.auto" must be false.
I will submit a patch later today.
was:
This JIRA is to address the similar problem as HBASE-12954, but there are some
little differences,
1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
users can configure it on every regionserver with preferred hostnames. However,
this configuration cannot be set through Ambari because each regionserver has a
different value of this setting.
2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a
FQDN by modifying /etc/hosts on that node, then when regionserver starts,
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
which cannot be resolved.
{code}
// if regionserver passed hostname to use,
// then use it instead of doing a reverse DNS lookup
ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}
My proposed fix is to add a new configuration
"hbase.hmaster.skip.reverse.dns.lookup". This is a hard switch. If it is set to
true, then Regionserver will use the value returned by
*_rpcServices.isa.getHostName()_* as the hostname overwriting whatever users
specifies in "hbase.regionserver.hostname" and send to HMaster. HMaster will
not do reverse DNS lookup, which has been implemented in HBASE-12954. If users
want to provide their own hostnames in "hbase.regionserver.hostname",
"hbase.hmaster.skip.reverse.dns.lookup" must be false.
I will submit a patch later today.
> Disable reverse DNS lookup at HMaster and use default hostname provided by
> RegionServer
> ---
>
> Key: HBASE-18226
> URL: https://issues.apache.org/jira/browse/HBASE-18226
> Project: HBase
> Issue Type: Bug
>Reporter: Duo Xu
>Priority: Minor
>
> This JIRA is to address the similar problem as HBASE-12954, but there are
> some little differences,
> 1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so
> users can configure it on every regionserver with preferred hostnames.
> However, this configuration cannot be set through Ambari because each
> regionserver has a different value of this setting.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node, then when regionserver starts,
> {code}
> String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
> rpcServices.isa.getHostName();
> {code}
> it uses FQDN names here but on HMaster side, it will do reverse DNS lookup
> which cannot be resolved.
> {code}
> // if regionserver passed hostname to use,
> // then use it instead of doing a reverse DNS lookup
> ServerName rs = master.getServerManager().regionServerStartup(request, ia);
> {code}
> My proposed fix is to add a new configuration
> "hbase.regionserver.hostname.auto". If it is set to true, then Regionserver
> will use the value returned by *_rpcServices.isa.getHostName()_* as the
> hostname overwriting whatever users specifies in
> "hbase.regionserver.hostname" and send to HMaster. HMaster will not do
> reverse DNS lookup, which has been
