public java.util.List<String> getNewAvailabilityZones() {
        if (newAvailabilityZones == null) {
            newAvailabilityZones = new com.amazonaws.internal.SdkInternalList<String>();
        }
        return newAvailabilityZones;
    }
<note>
<p>
This option is only supported on Memcached clusters.
</p>
</note>
<p>
The list of Availability Zones where the new Memcached cache nodes are created.
</p>
<p>
This parameter is only valid when <code>NumCacheNodes</code> in the request is greater than the sum of the number
of active cache nodes and the number of cache nodes pending creation (which may be zero). The number of
Availability Zones supplied in this list must match the cache nodes being added in this request.
</p>
<p>
Scenarios:
</p>
<ul>
<li>
<p>
<b>Scenario 1:</b> You have 3 active nodes and wish to add 2 nodes. Specify <code>NumCacheNodes=5</code> (3 + 2)
and optionally specify two Availability Zones for the two new nodes.
</p>
</li>
<li>
<p>
<b>Scenario 2:</b> You have 3 active nodes and 2 nodes pending creation (from the scenario 1 call) and want to
add 1 more node. Specify <code>NumCacheNodes=6</code> ((3 + 2) + 1) and optionally specify an Availability Zone
for the new node.
</p>
</li>
<li>
<p>
<b>Scenario 3:</b> You want to cancel all pending operations. Specify <code>NumCacheNodes=3</code> to cancel all
pending operations.
</p>
</li>
</ul>
<p>
The Availability Zone placement of nodes pending creation cannot be modified. If you wish to cancel any nodes
pending creation, add 0 nodes by setting <code>NumCacheNodes</code> to the number of current nodes.
</p>
<p>
If <code>cross-az</code> is specified, existing Memcached nodes remain in their current Availability Zone. Only
newly created nodes can be located in different Availability Zones. For guidance on how to move existing
Memcached nodes to different Availability Zones, see the <b>Availability Zone Considerations</b> section of <a
href="https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/CacheNodes.SupportedTypes.html">Cache Node
Considerations for Memcached</a>.
</p>
<p>
<b>Impact of new add/remove requests upon pending requests</b>
</p>
<ul>
<li>
<p>
Scenario-1
</p>
<ul>
<li>
<p>
Pending Action: Delete
</p>
</li>
<li>
<p>
New Request: Delete
</p>
</li>
<li>
<p>
Result: The new delete, pending or immediate, replaces the pending delete.
</p>
</li>
</ul>
</li>
<li>
<p>
Scenario-2
</p>
<ul>
<li>
<p>
Pending Action: Delete
</p>
</li>
<li>
<p>
New Request: Create
</p>
</li>
<li>
<p>
Result: The new create, pending or immediate, replaces the pending delete.
</p>
</li>
</ul>
</li>
<li>
<p>
Scenario-3
</p>
<ul>
<li>
<p>
Pending Action: Create
</p>
</li>
<li>
<p>
New Request: Delete
</p>
</li>
<li>
<p>
Result: The new delete, pending or immediate, replaces the pending create.
</p>
</li>
</ul>
</li>
<li>
<p>
Scenario-4
</p>
<ul>
<li>
<p>
Pending Action: Create
</p>
</li>
<li>
<p>
New Request: Create
</p>
</li>
<li>
<p>
Result: The new create is added to the pending create.
</p>
<important>
<p>
<b>Important:</b> If the new create request is <b>Apply Immediately - Yes</b>, all creates are performed
immediately. If the new create request is <b>Apply Immediately - No</b>, all creates are pending.
</p>
</important></li>
</ul>
</li>
</ul>

@return <p>
        This option is only supported on Memcached clusters.
        </p>
        </note>
        <p>
        The list of Availability Zones where the new Memcached cache nodes are created.
        </p>
        <p>
        This parameter is only valid when <code>NumCacheNodes</code> in the request is greater than the sum of
        the number of active cache nodes and the number of cache nodes pending creation (which may be zero). The
        number of Availability Zones supplied in this list must match the cache nodes being added in this
        request.
        </p>
        <p>
        Scenarios:
        </p>
        <ul>
        <li>
        <p>
        <b>Scenario 1:</b> You have 3 active nodes and wish to add 2 nodes. Specify <code>NumCacheNodes=5</code>
        (3 + 2) and optionally specify two Availability Zones for the two new nodes.
        </p>
        </li>
        <li>
        <p>
        <b>Scenario 2:</b> You have 3 active nodes and 2 nodes pending creation (from the scenario 1 call) and
        want to add 1 more node. Specify <code>NumCacheNodes=6</code> ((3 + 2) + 1) and optionally specify an
        Availability Zone for the new node.
        </p>
        </li>
        <li>
        <p>
        <b>Scenario 3:</b> You want to cancel all pending operations. Specify <code>NumCacheNodes=3</code> to
        cancel all pending operations.
        </p>
        </li>
        </ul>
        <p>
        The Availability Zone placement of nodes pending creation cannot be modified. If you wish to cancel any
        nodes pending creation, add 0 nodes by setting <code>NumCacheNodes</code> to the number of current nodes.
        </p>
        <p>
        If <code>cross-az</code> is specified, existing Memcached nodes remain in their current Availability
        Zone. Only newly created nodes can be located in different Availability Zones. For guidance on how to
        move existing Memcached nodes to different Availability Zones, see the <b>Availability Zone
        Considerations</b> section of <a
        href="https://docs.aws.amazon.com/AmazonElastiCache/latest/mem-ug/CacheNodes.SupportedTypes.html">Cache
        Node Considerations for Memcached</a>.
        </p>
        <p>
        <b>Impact of new add/remove requests upon pending requests</b>
        </p>
        <ul>
        <li>
        <p>
        Scenario-1
        </p>
        <ul>
        <li>
        <p>
        Pending Action: Delete
        </p>
        </li>
        <li>
        <p>
        New Request: Delete
        </p>
        </li>
        <li>
        <p>
        Result: The new delete, pending or immediate, replaces the pending delete.
        </p>
        </li>
        </ul>
        </li>
        <li>
        <p>
        Scenario-2
        </p>
        <ul>
        <li>
        <p>
        Pending Action: Delete
        </p>
        </li>
        <li>
        <p>
        New Request: Create
        </p>
        </li>
        <li>
        <p>
        Result: The new create, pending or immediate, replaces the pending delete.
        </p>
        </li>
        </ul>
        </li>
        <li>
        <p>
        Scenario-3
        </p>
        <ul>
        <li>
        <p>
        Pending Action: Create
        </p>
        </li>
        <li>
        <p>
        New Request: Delete
        </p>
        </li>
        <li>
        <p>
        Result: The new delete, pending or immediate, replaces the pending create.
        </p>
        </li>
        </ul>
        </li>
        <li>
        <p>
        Scenario-4
        </p>
        <ul>
        <li>
        <p>
        Pending Action: Create
        </p>
        </li>
        <li>
        <p>
        New Request: Create
        </p>
        </li>
        <li>
        <p>
        Result: The new create is added to the pending create.
        </p>
        <important>
        <p>
        <b>Important:</b> If the new create request is <b>Apply Immediately - Yes</b>, all creates are performed
        immediately. If the new create request is <b>Apply Immediately - No</b>, all creates are pending.
        </p>
        </important></li>
        </ul>
        </li>
aws-java-sdk-elasticache/src/main/java/com/amazonaws/services/elasticache/model/ModifyCacheClusterRequest.java