[
https://issues.apache.org/jira/browse/HBASE-29534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Y. SREENIVASULU REDDY updated HBASE-29534:
------------------------------------------
Description:
Currently, HBase may primarily rely on hostnames for server identification and
network communication. However, in environments where only IPv6 is available or
preferred, it is critical for cluster stability and accessibility that HBase
fully supports initialization and connection using IPv6 IPs.
*Key Points:*
•HBase server components (e.g., RegionServer, Master) should be able to start,
bind, and register using an IPv6 address (such as `2001:db8::1`) as their
identity, not relying exclusively on a DNS-resolvable hostname.
•WAL (Write Ahead Log) paths, ZooKeeper registration, and inter-node
communications should safely encode and decode IPv6 addresses to avoid
filesystem incompatibilities (e.g., colons in paths).
•IPv6 addresses may include shorthand notation (compressed zeroes) and should
be handled using standard networking libraries to ensure robust identification
and compatibility.
•Configuration options and startup scripts should accept and correctly process
IPv6 IP addresses wherever a server name or host is expected.
•The cluster should properly recognize, route, and validate IPv6 addresses
during discovery, registration, health checks, and client data operations.
*Impact:*
Supporting HBase startup and communication using IPv6 IP addresses improves
compatibility with modern network infrastructures, facilitates deployment in
cloud and enterprise environments mandating IPv6, and resolves scenarios where
hostnames are not available or not preferred.
Resolution:
•Update server identification, registration, and communication logic to accept,
encode/decode, and validate IPv6 IP addresses using Java’s standard networking
API.
•Ensure all paths, config entries, and network-dependent features are fully
compatible and secure with raw IPv6 IP usage.
This change is vital for long-term compatibility and seamless HBase operation
in IPv6-based setups.
was:
Support using IP to set up HBase Instances developed in HBASE-27304 .
Need to support for IPV6 also.
> Support IPV6 HBase cluster set up using UseIP feature
> -----------------------------------------------------
>
> Key: HBASE-29534
> URL: https://issues.apache.org/jira/browse/HBASE-29534
> Project: HBase
> Issue Type: Umbrella
> Reporter: Y. SREENIVASULU REDDY
> Assignee: Y. SREENIVASULU REDDY
> Priority: Major
>
> Currently, HBase may primarily rely on hostnames for server identification
> and network communication. However, in environments where only IPv6 is
> available or preferred, it is critical for cluster stability and
> accessibility that HBase fully supports initialization and connection using
> IPv6 IPs.
>
> *Key Points:*
> •HBase server components (e.g., RegionServer, Master) should be able to
> start, bind, and register using an IPv6 address (such as `2001:db8::1`) as
> their identity, not relying exclusively on a DNS-resolvable hostname.
> •WAL (Write Ahead Log) paths, ZooKeeper registration, and inter-node
> communications should safely encode and decode IPv6 addresses to avoid
> filesystem incompatibilities (e.g., colons in paths).
> •IPv6 addresses may include shorthand notation (compressed zeroes) and should
> be handled using standard networking libraries to ensure robust
> identification and compatibility.
> •Configuration options and startup scripts should accept and correctly
> process IPv6 IP addresses wherever a server name or host is expected.
> •The cluster should properly recognize, route, and validate IPv6 addresses
> during discovery, registration, health checks, and client data operations.
>
> *Impact:*
> Supporting HBase startup and communication using IPv6 IP addresses improves
> compatibility with modern network infrastructures, facilitates deployment in
> cloud and enterprise environments mandating IPv6, and resolves scenarios
> where hostnames are not available or not preferred.
> Resolution:
> •Update server identification, registration, and communication logic to
> accept, encode/decode, and validate IPv6 IP addresses using Java’s standard
> networking API.
> •Ensure all paths, config entries, and network-dependent features are fully
> compatible and secure with raw IPv6 IP usage.
>
> This change is vital for long-term compatibility and seamless HBase operation
> in IPv6-based setups.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
