}

    private ChannelInfo selectWithAffinity(CommonServerMessageBlock message, Collection<ChannelInfo> channels) {
        // Use file handle or tree ID for affinity
        long affinityKey = 0;

        // Use tree ID for SMB2 requests for affinity
        if (message instanceof ServerMessageBlock2Request) {
            ServerMessageBlock2Request smb2Request = (ServerMessageBlock2Request) message;

     * Select the least busy channel based on pending operations
     */
    LEAST_LOADED,

    /**
     * Weighted random selection based on channel scores
     */
    WEIGHTED_RANDOM,

    /**
     * Affinity-based selection for related operations
     */
    AFFINITY_BASED,

    /**
     * Adaptive selection based on operation type and performance
     */
    ADAPTIVE

        loadBalancer.setStrategy(LoadBalancingStrategy.AFFINITY_BASED);

        Smb2ReadRequest readRequest = mock(Smb2ReadRequest.class);
        when(readRequest.getTreeId()).thenReturn(123); // Set consistent tree ID for affinity

        when(mockChannelManager.getHealthyChannels()).thenReturn(Arrays.asList(channel1, channel2));

        // Multiple calls with same file ID should return same channel

        }
        
        if (affinityKey != 0) {
            // Select channel based on affinity key
            List<ChannelInfo> list = new ArrayList<>(channels);
            int index = Math.abs((int)(affinityKey % list.size()));
            return list.get(index);
        }
        
        // No affinity, use weighted random
        return selectWeightedRandom(channels);
    }
    

- Changed the error message displayed when a pod is trying to attach a volume that does not match the label/selector from "x node(s) had volume node affinity conflict" to "x node(s) didn't match PersistentVolume's node affinity". ([#129887](https://github.com/kubernetes/kubernetes/pull/129887), [@rhrmo](https://github.com/rhrmo)) [SIG Scheduling and Storage]

- Made node affinity in Persistent Volume mutable. ([#134339](https://github.com/kubernetes/kubernetes/pull/134339), [@huww98](https://github.com/huww98)) [SIG API Machinery, Apps and Node]

- CRI: Added a field to support CPU affinity on Windows. ([#124285](https://github.com/kubernetes/kubernetes/pull/124285), [@kiashok](https://github.com/kiashok)) [SIG Node and Windows]

- The Kubernetes API server merged selectors built from `matchLabelKeys` into the `labelSelector` of `topologySpreadConstraints`, aligning Pod Topology Spread behavior with Inter-Pod Affinity. To prevent breaking existing Pods using `matchLabelKeys`, this scheduler behavior was preserved until v1.34. Upgrades from v1.32 to v1.34 should be done incrementally (v1.32 → v1.33 → v1.34), ensuring Pods created at v1.32 with `matchLabelKeys`...

    checkTryParse(Double.POSITIVE_INFINITY, "Infinity");
    checkTryParse(Double.POSITIVE_INFINITY, "+Infinity");
    checkTryParse(Double.NEGATIVE_INFINITY, "-Infinity");
  }

  private static final String[] BAD_TRY_PARSE_INPUTS = {
    "",
    "+-",
    "+-0",
    " 5",
    "32 ",
    " 55 ",
    "infinity",
    "POSITIVE_INFINITY",
    "0x9A",
    "0x9A.bE-5",
    ".",

  These hints allow the scheduler to retry scheduling a Pod
  that was previously rejected by the InterPodAffinity plugin if there are changes (create, delete, or update) to a related Pod or a node that matches the pod affinity criteria. ([#122471](https://github.com/kubernetes/kubernetes/pull/122471), [@nayihz](https://github.com/nayihz)) [SIG Scheduling and Testing]