Package com.google.cloud.compute.v1

Class BackendServiceHAPolicy.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessage.Builder<BackendServiceHAPolicy.Builder>
com.google.cloud.compute.v1.BackendServiceHAPolicy.Builder
All Implemented Interfaces:
BackendServiceHAPolicyOrBuilder, com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable
Enclosing class:
BackendServiceHAPolicy
public static final class BackendServiceHAPolicy.Builder extends com.google.protobuf.GeneratedMessage.Builder<BackendServiceHAPolicy.Builder> implements BackendServiceHAPolicyOrBuilder
Protobuf type google.cloud.compute.v1.BackendServiceHAPolicy

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<BackendServiceHAPolicy.Builder>

    • clear

      public BackendServiceHAPolicy.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessage.Builder<BackendServiceHAPolicy.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<BackendServiceHAPolicy.Builder>

    • getDefaultInstanceForType

      public BackendServiceHAPolicy getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public BackendServiceHAPolicy build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public BackendServiceHAPolicy buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • mergeFrom

      public BackendServiceHAPolicy.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<BackendServiceHAPolicy.Builder>

    • mergeFrom

      public BackendServiceHAPolicy.Builder mergeFrom(BackendServiceHAPolicy other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessage.Builder<BackendServiceHAPolicy.Builder>

    • mergeFrom

      public BackendServiceHAPolicy.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<BackendServiceHAPolicy.Builder>
      Throws:
      IOException

    • hasFastIPMove

      public boolean hasFastIPMove()
       Specifies whether fast IP move is enabled, and if so, the mechanism to
 achieve it.

 Supported values are:

 - DISABLED: Fast IP Move is disabled. You can only use the
 haPolicy.leader API to update the leader.
 - >GARP_RA: Provides a method to very quickly define a new network
 endpoint as the leader. This method is faster than updating the leader
 using the haPolicy.leader API. Fast IP move works as follows: The VM
 hosting the network endpoint that should become the new leader sends
 either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router
 Advertisement(RA) packet (IPv6).  Google Cloud immediately but
 temporarily associates the forwarding rule IP address with that VM, and
 both new and in-flight packets are quickly delivered to that VM.



 Note the important properties of the Fast IP Move functionality:

 - The GARP/RA-initiated re-routing stays active for approximately 20
 minutes. After triggering fast failover, you must also
 appropriately set the haPolicy.leader.
 -  The new leader instance should continue to send GARP/RA packets
 periodically every 10 seconds until at least 10 minutes after updating
 the haPolicy.leader (but stop immediately if it is no longer the leader).
 - After triggering a fast failover, we recommend that you wait at least
 3 seconds before sending another GARP/RA packet from a different VM
 instance to avoid race conditions.
 - Don't send GARP/RA packets from different VM
 instances at the same time. If multiple instances continue to send
 GARP/RA packets, traffic might be routed to different destinations in an
 alternating order. This condition ceases when a single instance
 issues a GARP/RA packet.
 - The GARP/RA request always takes priority over the leader API.
 Using the haPolicy.leader API to change the leader to a different
 instance will have no effect until the GARP/RA request becomes
 inactive.
 - The GARP/RA packets should follow the GARP/RA
 Packet Specifications..
 -  When multiple forwarding rules refer to a regional backend service,
 you need only send a GARP or RA packet for a single forwarding rule
 virtual IP. The virtual IPs for all forwarding rules targeting the same
 backend service will also be moved to the sender of the GARP or RA
 packet.



 The following are the Fast IP Move limitations (that is, when fastIPMove
 is not DISABLED):

 - Multiple forwarding rules cannot use the same IP address if one of
 them refers to a regional backend service with fastIPMove.
 - The regional backend service must set the network field, and all
 NEGs must belong to that network. However, individual
 NEGs can belong to different subnetworks of that network.
 - The maximum number of network endpoints across all backends of a
 backend service with fastIPMove is 32.
 - The maximum number of backend services with fastIPMove that can have
 the same network endpoint attached to one of its backends is 64.
 - The maximum number of backend services with fastIPMove in a VPC in a
 region is 64.
 - The network endpoints that are attached to a backend of a backend
 service with fastIPMove cannot resolve to Gen3+ machines for IPv6.
 - Traffic directed to the leader by a static route next hop will not be
 redirected to a new leader by fast failover. Such traffic will only be
 redirected once an haPolicy.leader update has taken effect. Only traffic
 to the forwarding rule's virtual IP will be redirected to a new leader by
 fast failover.


 haPolicy.fastIPMove can be set only at backend service creation time.
 Once set, it cannot be updated.

 By default, fastIpMove is set to DISABLED.
 Check the FastIPMove enum for the list of possible values.
      optional string fast_i_p_move = 222633817;
      Specified by:
      hasFastIPMove in interface BackendServiceHAPolicyOrBuilder
      Returns:
      Whether the fastIPMove field is set.

    • getFastIPMove

      public String getFastIPMove()
       Specifies whether fast IP move is enabled, and if so, the mechanism to
 achieve it.

 Supported values are:

 - DISABLED: Fast IP Move is disabled. You can only use the
 haPolicy.leader API to update the leader.
 - >GARP_RA: Provides a method to very quickly define a new network
 endpoint as the leader. This method is faster than updating the leader
 using the haPolicy.leader API. Fast IP move works as follows: The VM
 hosting the network endpoint that should become the new leader sends
 either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router
 Advertisement(RA) packet (IPv6).  Google Cloud immediately but
 temporarily associates the forwarding rule IP address with that VM, and
 both new and in-flight packets are quickly delivered to that VM.



 Note the important properties of the Fast IP Move functionality:

 - The GARP/RA-initiated re-routing stays active for approximately 20
 minutes. After triggering fast failover, you must also
 appropriately set the haPolicy.leader.
 -  The new leader instance should continue to send GARP/RA packets
 periodically every 10 seconds until at least 10 minutes after updating
 the haPolicy.leader (but stop immediately if it is no longer the leader).
 - After triggering a fast failover, we recommend that you wait at least
 3 seconds before sending another GARP/RA packet from a different VM
 instance to avoid race conditions.
 - Don't send GARP/RA packets from different VM
 instances at the same time. If multiple instances continue to send
 GARP/RA packets, traffic might be routed to different destinations in an
 alternating order. This condition ceases when a single instance
 issues a GARP/RA packet.
 - The GARP/RA request always takes priority over the leader API.
 Using the haPolicy.leader API to change the leader to a different
 instance will have no effect until the GARP/RA request becomes
 inactive.
 - The GARP/RA packets should follow the GARP/RA
 Packet Specifications..
 -  When multiple forwarding rules refer to a regional backend service,
 you need only send a GARP or RA packet for a single forwarding rule
 virtual IP. The virtual IPs for all forwarding rules targeting the same
 backend service will also be moved to the sender of the GARP or RA
 packet.



 The following are the Fast IP Move limitations (that is, when fastIPMove
 is not DISABLED):

 - Multiple forwarding rules cannot use the same IP address if one of
 them refers to a regional backend service with fastIPMove.
 - The regional backend service must set the network field, and all
 NEGs must belong to that network. However, individual
 NEGs can belong to different subnetworks of that network.
 - The maximum number of network endpoints across all backends of a
 backend service with fastIPMove is 32.
 - The maximum number of backend services with fastIPMove that can have
 the same network endpoint attached to one of its backends is 64.
 - The maximum number of backend services with fastIPMove in a VPC in a
 region is 64.
 - The network endpoints that are attached to a backend of a backend
 service with fastIPMove cannot resolve to Gen3+ machines for IPv6.
 - Traffic directed to the leader by a static route next hop will not be
 redirected to a new leader by fast failover. Such traffic will only be
 redirected once an haPolicy.leader update has taken effect. Only traffic
 to the forwarding rule's virtual IP will be redirected to a new leader by
 fast failover.


 haPolicy.fastIPMove can be set only at backend service creation time.
 Once set, it cannot be updated.

 By default, fastIpMove is set to DISABLED.
 Check the FastIPMove enum for the list of possible values.
      optional string fast_i_p_move = 222633817;
      Specified by:
      getFastIPMove in interface BackendServiceHAPolicyOrBuilder
      Returns:
      The fastIPMove.

    • getFastIPMoveBytes

      public com.google.protobuf.ByteString getFastIPMoveBytes()
       Specifies whether fast IP move is enabled, and if so, the mechanism to
 achieve it.

 Supported values are:

 - DISABLED: Fast IP Move is disabled. You can only use the
 haPolicy.leader API to update the leader.
 - >GARP_RA: Provides a method to very quickly define a new network
 endpoint as the leader. This method is faster than updating the leader
 using the haPolicy.leader API. Fast IP move works as follows: The VM
 hosting the network endpoint that should become the new leader sends
 either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router
 Advertisement(RA) packet (IPv6).  Google Cloud immediately but
 temporarily associates the forwarding rule IP address with that VM, and
 both new and in-flight packets are quickly delivered to that VM.



 Note the important properties of the Fast IP Move functionality:

 - The GARP/RA-initiated re-routing stays active for approximately 20
 minutes. After triggering fast failover, you must also
 appropriately set the haPolicy.leader.
 -  The new leader instance should continue to send GARP/RA packets
 periodically every 10 seconds until at least 10 minutes after updating
 the haPolicy.leader (but stop immediately if it is no longer the leader).
 - After triggering a fast failover, we recommend that you wait at least
 3 seconds before sending another GARP/RA packet from a different VM
 instance to avoid race conditions.
 - Don't send GARP/RA packets from different VM
 instances at the same time. If multiple instances continue to send
 GARP/RA packets, traffic might be routed to different destinations in an
 alternating order. This condition ceases when a single instance
 issues a GARP/RA packet.
 - The GARP/RA request always takes priority over the leader API.
 Using the haPolicy.leader API to change the leader to a different
 instance will have no effect until the GARP/RA request becomes
 inactive.
 - The GARP/RA packets should follow the GARP/RA
 Packet Specifications..
 -  When multiple forwarding rules refer to a regional backend service,
 you need only send a GARP or RA packet for a single forwarding rule
 virtual IP. The virtual IPs for all forwarding rules targeting the same
 backend service will also be moved to the sender of the GARP or RA
 packet.



 The following are the Fast IP Move limitations (that is, when fastIPMove
 is not DISABLED):

 - Multiple forwarding rules cannot use the same IP address if one of
 them refers to a regional backend service with fastIPMove.
 - The regional backend service must set the network field, and all
 NEGs must belong to that network. However, individual
 NEGs can belong to different subnetworks of that network.
 - The maximum number of network endpoints across all backends of a
 backend service with fastIPMove is 32.
 - The maximum number of backend services with fastIPMove that can have
 the same network endpoint attached to one of its backends is 64.
 - The maximum number of backend services with fastIPMove in a VPC in a
 region is 64.
 - The network endpoints that are attached to a backend of a backend
 service with fastIPMove cannot resolve to Gen3+ machines for IPv6.
 - Traffic directed to the leader by a static route next hop will not be
 redirected to a new leader by fast failover. Such traffic will only be
 redirected once an haPolicy.leader update has taken effect. Only traffic
 to the forwarding rule's virtual IP will be redirected to a new leader by
 fast failover.


 haPolicy.fastIPMove can be set only at backend service creation time.
 Once set, it cannot be updated.

 By default, fastIpMove is set to DISABLED.
 Check the FastIPMove enum for the list of possible values.
      optional string fast_i_p_move = 222633817;
      Specified by:
      getFastIPMoveBytes in interface BackendServiceHAPolicyOrBuilder
      Returns:
      The bytes for fastIPMove.

    • setFastIPMove

      public BackendServiceHAPolicy.Builder setFastIPMove(String value)
       Specifies whether fast IP move is enabled, and if so, the mechanism to
 achieve it.

 Supported values are:

 - DISABLED: Fast IP Move is disabled. You can only use the
 haPolicy.leader API to update the leader.
 - >GARP_RA: Provides a method to very quickly define a new network
 endpoint as the leader. This method is faster than updating the leader
 using the haPolicy.leader API. Fast IP move works as follows: The VM
 hosting the network endpoint that should become the new leader sends
 either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router
 Advertisement(RA) packet (IPv6).  Google Cloud immediately but
 temporarily associates the forwarding rule IP address with that VM, and
 both new and in-flight packets are quickly delivered to that VM.



 Note the important properties of the Fast IP Move functionality:

 - The GARP/RA-initiated re-routing stays active for approximately 20
 minutes. After triggering fast failover, you must also
 appropriately set the haPolicy.leader.
 -  The new leader instance should continue to send GARP/RA packets
 periodically every 10 seconds until at least 10 minutes after updating
 the haPolicy.leader (but stop immediately if it is no longer the leader).
 - After triggering a fast failover, we recommend that you wait at least
 3 seconds before sending another GARP/RA packet from a different VM
 instance to avoid race conditions.
 - Don't send GARP/RA packets from different VM
 instances at the same time. If multiple instances continue to send
 GARP/RA packets, traffic might be routed to different destinations in an
 alternating order. This condition ceases when a single instance
 issues a GARP/RA packet.
 - The GARP/RA request always takes priority over the leader API.
 Using the haPolicy.leader API to change the leader to a different
 instance will have no effect until the GARP/RA request becomes
 inactive.
 - The GARP/RA packets should follow the GARP/RA
 Packet Specifications..
 -  When multiple forwarding rules refer to a regional backend service,
 you need only send a GARP or RA packet for a single forwarding rule
 virtual IP. The virtual IPs for all forwarding rules targeting the same
 backend service will also be moved to the sender of the GARP or RA
 packet.



 The following are the Fast IP Move limitations (that is, when fastIPMove
 is not DISABLED):

 - Multiple forwarding rules cannot use the same IP address if one of
 them refers to a regional backend service with fastIPMove.
 - The regional backend service must set the network field, and all
 NEGs must belong to that network. However, individual
 NEGs can belong to different subnetworks of that network.
 - The maximum number of network endpoints across all backends of a
 backend service with fastIPMove is 32.
 - The maximum number of backend services with fastIPMove that can have
 the same network endpoint attached to one of its backends is 64.
 - The maximum number of backend services with fastIPMove in a VPC in a
 region is 64.
 - The network endpoints that are attached to a backend of a backend
 service with fastIPMove cannot resolve to Gen3+ machines for IPv6.
 - Traffic directed to the leader by a static route next hop will not be
 redirected to a new leader by fast failover. Such traffic will only be
 redirected once an haPolicy.leader update has taken effect. Only traffic
 to the forwarding rule's virtual IP will be redirected to a new leader by
 fast failover.


 haPolicy.fastIPMove can be set only at backend service creation time.
 Once set, it cannot be updated.

 By default, fastIpMove is set to DISABLED.
 Check the FastIPMove enum for the list of possible values.
      optional string fast_i_p_move = 222633817;
      Parameters:
      value - The fastIPMove to set.
      Returns:
      This builder for chaining.

    • clearFastIPMove

      public BackendServiceHAPolicy.Builder clearFastIPMove()
       Specifies whether fast IP move is enabled, and if so, the mechanism to
 achieve it.

 Supported values are:

 - DISABLED: Fast IP Move is disabled. You can only use the
 haPolicy.leader API to update the leader.
 - >GARP_RA: Provides a method to very quickly define a new network
 endpoint as the leader. This method is faster than updating the leader
 using the haPolicy.leader API. Fast IP move works as follows: The VM
 hosting the network endpoint that should become the new leader sends
 either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router
 Advertisement(RA) packet (IPv6).  Google Cloud immediately but
 temporarily associates the forwarding rule IP address with that VM, and
 both new and in-flight packets are quickly delivered to that VM.



 Note the important properties of the Fast IP Move functionality:

 - The GARP/RA-initiated re-routing stays active for approximately 20
 minutes. After triggering fast failover, you must also
 appropriately set the haPolicy.leader.
 -  The new leader instance should continue to send GARP/RA packets
 periodically every 10 seconds until at least 10 minutes after updating
 the haPolicy.leader (but stop immediately if it is no longer the leader).
 - After triggering a fast failover, we recommend that you wait at least
 3 seconds before sending another GARP/RA packet from a different VM
 instance to avoid race conditions.
 - Don't send GARP/RA packets from different VM
 instances at the same time. If multiple instances continue to send
 GARP/RA packets, traffic might be routed to different destinations in an
 alternating order. This condition ceases when a single instance
 issues a GARP/RA packet.
 - The GARP/RA request always takes priority over the leader API.
 Using the haPolicy.leader API to change the leader to a different
 instance will have no effect until the GARP/RA request becomes
 inactive.
 - The GARP/RA packets should follow the GARP/RA
 Packet Specifications..
 -  When multiple forwarding rules refer to a regional backend service,
 you need only send a GARP or RA packet for a single forwarding rule
 virtual IP. The virtual IPs for all forwarding rules targeting the same
 backend service will also be moved to the sender of the GARP or RA
 packet.



 The following are the Fast IP Move limitations (that is, when fastIPMove
 is not DISABLED):

 - Multiple forwarding rules cannot use the same IP address if one of
 them refers to a regional backend service with fastIPMove.
 - The regional backend service must set the network field, and all
 NEGs must belong to that network. However, individual
 NEGs can belong to different subnetworks of that network.
 - The maximum number of network endpoints across all backends of a
 backend service with fastIPMove is 32.
 - The maximum number of backend services with fastIPMove that can have
 the same network endpoint attached to one of its backends is 64.
 - The maximum number of backend services with fastIPMove in a VPC in a
 region is 64.
 - The network endpoints that are attached to a backend of a backend
 service with fastIPMove cannot resolve to Gen3+ machines for IPv6.
 - Traffic directed to the leader by a static route next hop will not be
 redirected to a new leader by fast failover. Such traffic will only be
 redirected once an haPolicy.leader update has taken effect. Only traffic
 to the forwarding rule's virtual IP will be redirected to a new leader by
 fast failover.


 haPolicy.fastIPMove can be set only at backend service creation time.
 Once set, it cannot be updated.

 By default, fastIpMove is set to DISABLED.
 Check the FastIPMove enum for the list of possible values.
      optional string fast_i_p_move = 222633817;
      Returns:
      This builder for chaining.

    • setFastIPMoveBytes

      public BackendServiceHAPolicy.Builder setFastIPMoveBytes(com.google.protobuf.ByteString value)
       Specifies whether fast IP move is enabled, and if so, the mechanism to
 achieve it.

 Supported values are:

 - DISABLED: Fast IP Move is disabled. You can only use the
 haPolicy.leader API to update the leader.
 - >GARP_RA: Provides a method to very quickly define a new network
 endpoint as the leader. This method is faster than updating the leader
 using the haPolicy.leader API. Fast IP move works as follows: The VM
 hosting the network endpoint that should become the new leader sends
 either a Gratuitous ARP (GARP) packet (IPv4) or an ICMPv6 Router
 Advertisement(RA) packet (IPv6).  Google Cloud immediately but
 temporarily associates the forwarding rule IP address with that VM, and
 both new and in-flight packets are quickly delivered to that VM.



 Note the important properties of the Fast IP Move functionality:

 - The GARP/RA-initiated re-routing stays active for approximately 20
 minutes. After triggering fast failover, you must also
 appropriately set the haPolicy.leader.
 -  The new leader instance should continue to send GARP/RA packets
 periodically every 10 seconds until at least 10 minutes after updating
 the haPolicy.leader (but stop immediately if it is no longer the leader).
 - After triggering a fast failover, we recommend that you wait at least
 3 seconds before sending another GARP/RA packet from a different VM
 instance to avoid race conditions.
 - Don't send GARP/RA packets from different VM
 instances at the same time. If multiple instances continue to send
 GARP/RA packets, traffic might be routed to different destinations in an
 alternating order. This condition ceases when a single instance
 issues a GARP/RA packet.
 - The GARP/RA request always takes priority over the leader API.
 Using the haPolicy.leader API to change the leader to a different
 instance will have no effect until the GARP/RA request becomes
 inactive.
 - The GARP/RA packets should follow the GARP/RA
 Packet Specifications..
 -  When multiple forwarding rules refer to a regional backend service,
 you need only send a GARP or RA packet for a single forwarding rule
 virtual IP. The virtual IPs for all forwarding rules targeting the same
 backend service will also be moved to the sender of the GARP or RA
 packet.



 The following are the Fast IP Move limitations (that is, when fastIPMove
 is not DISABLED):

 - Multiple forwarding rules cannot use the same IP address if one of
 them refers to a regional backend service with fastIPMove.
 - The regional backend service must set the network field, and all
 NEGs must belong to that network. However, individual
 NEGs can belong to different subnetworks of that network.
 - The maximum number of network endpoints across all backends of a
 backend service with fastIPMove is 32.
 - The maximum number of backend services with fastIPMove that can have
 the same network endpoint attached to one of its backends is 64.
 - The maximum number of backend services with fastIPMove in a VPC in a
 region is 64.
 - The network endpoints that are attached to a backend of a backend
 service with fastIPMove cannot resolve to Gen3+ machines for IPv6.
 - Traffic directed to the leader by a static route next hop will not be
 redirected to a new leader by fast failover. Such traffic will only be
 redirected once an haPolicy.leader update has taken effect. Only traffic
 to the forwarding rule's virtual IP will be redirected to a new leader by
 fast failover.


 haPolicy.fastIPMove can be set only at backend service creation time.
 Once set, it cannot be updated.

 By default, fastIpMove is set to DISABLED.
 Check the FastIPMove enum for the list of possible values.
      optional string fast_i_p_move = 222633817;
      Parameters:
      value - The bytes for fastIPMove to set.
      Returns:
      This builder for chaining.

    • hasLeader

      public boolean hasLeader()
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;
      Specified by:
      hasLeader in interface BackendServiceHAPolicyOrBuilder
      Returns:
      Whether the leader field is set.

    • getLeader

      public BackendServiceHAPolicyLeader getLeader()
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;
      Specified by:
      getLeader in interface BackendServiceHAPolicyOrBuilder
      Returns:
      The leader.

    • setLeader

      public BackendServiceHAPolicy.Builder setLeader(BackendServiceHAPolicyLeader value)
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;

    • setLeader

      public BackendServiceHAPolicy.Builder setLeader(BackendServiceHAPolicyLeader.Builder builderForValue)
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;

    • mergeLeader

      public BackendServiceHAPolicy.Builder mergeLeader(BackendServiceHAPolicyLeader value)
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;

    • clearLeader

      public BackendServiceHAPolicy.Builder clearLeader()
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;

    • getLeaderBuilder

      public BackendServiceHAPolicyLeader.Builder getLeaderBuilder()
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;

    • getLeaderOrBuilder

      public BackendServiceHAPolicyLeaderOrBuilder getLeaderOrBuilder()
       Selects one of the network endpoints attached to the backend NEGs of
 this service as the active endpoint (the leader) that receives all
 traffic.

 When the leader changes, there is no connection draining to persist
 existing connections on the old leader.

 You are responsible for selecting a suitable endpoint as the
 leader. For example, preferring a healthy endpoint over unhealthy ones.
 Note that this service does not track backend endpoint health, and
 selects the configured leader unconditionally.
      optional .google.cloud.compute.v1.BackendServiceHAPolicyLeader leader = 503858441;
      Specified by:
      getLeaderOrBuilder in interface BackendServiceHAPolicyOrBuilder