public Integer getNumCacheNodes() {
        return this.numCacheNodes;
    }
<p>
The number of cache nodes that the cluster should have. If the value for <code>NumCacheNodes</code> is greater
than the sum of the number of current cache nodes and the number of cache nodes pending creation (which may be
zero), more nodes are added. If the value is less than the number of existing cache nodes, nodes are removed. If
the value is equal to the number of current cache nodes, any pending add or remove requests are canceled.
</p>
<p>
If you are removing cache nodes, you must use the <code>CacheNodeIdsToRemove</code> parameter to provide the IDs
of the specific cache nodes to remove.
</p>
<p>
For clusters running Redis OSS, this value must be 1. For clusters running Memcached, this value must be between
1 and 40.
</p>
<note>
<p>
Adding or removing Memcached cache nodes can be applied immediately or as a pending operation (see
<code>ApplyImmediately</code>).
</p>
<p>
A pending operation to modify the number of cache nodes in a cluster during its maintenance window, whether by
adding or removing nodes in accordance with the scale out architecture, is not queued. The customer's latest
request to add or remove nodes to the cluster overrides any previous pending operations to modify the number of
cache nodes in the cluster. For example, a request to remove 2 nodes would override a previous pending operation
to remove 3 nodes. Similarly, a request to add 2 nodes would override a previous pending operation to remove 3
nodes and vice versa. As Memcached cache nodes may now be provisioned in different Availability Zones with
flexible cache node placement, a request to add nodes does not automatically override a previous pending
operation to add nodes. The customer can modify the previous pending operation to add more nodes or explicitly
cancel the pending request and retry the new request. To cancel pending operations to modify the number of cache
nodes in a cluster, use the <code>ModifyCacheCluster</code> request and set <code>NumCacheNodes</code> equal to
the number of cache nodes currently in the cluster.
</p>
</note>

@return The number of cache nodes that the cluster should have. If the value for <code>NumCacheNodes</code> is
        greater than the sum of the number of current cache nodes and the number of cache nodes pending creation
        (which may be zero), more nodes are added. If the value is less than the number of existing cache nodes,
        nodes are removed. If the value is equal to the number of current cache nodes, any pending add or remove
        requests are canceled.</p>
        <p>
        If you are removing cache nodes, you must use the <code>CacheNodeIdsToRemove</code> parameter to provide
        the IDs of the specific cache nodes to remove.
        </p>
        <p>
        For clusters running Redis OSS, this value must be 1. For clusters running Memcached, this value must be
        between 1 and 40.
        </p>
        <note>
        <p>
        Adding or removing Memcached cache nodes can be applied immediately or as a pending operation (see
        <code>ApplyImmediately</code>).
        </p>
        <p>
        A pending operation to modify the number of cache nodes in a cluster during its maintenance window,
        whether by adding or removing nodes in accordance with the scale out architecture, is not queued. The
        customer's latest request to add or remove nodes to the cluster overrides any previous pending operations
        to modify the number of cache nodes in the cluster. For example, a request to remove 2 nodes would
        override a previous pending operation to remove 3 nodes. Similarly, a request to add 2 nodes would
        override a previous pending operation to remove 3 nodes and vice versa. As Memcached cache nodes may now
        be provisioned in different Availability Zones with flexible cache node placement, a request to add nodes
        does not automatically override a previous pending operation to add nodes. The customer can modify the
        previous pending operation to add more nodes or explicitly cancel the pending request and retry the new
        request. To cancel pending operations to modify the number of cache nodes in a cluster, use the
        <code>ModifyCacheCluster</code> request and set <code>NumCacheNodes</code> equal to the number of cache
        nodes currently in the cluster.
        </p>
aws-java-sdk-elasticache/src/main/java/com/amazonaws/services/elasticache/model/ModifyCacheClusterRequest.java