return jobProcess != null && jobProcess.getProcess().isAlive();
    }

    /**
     * Internal method to destroy a specific JobProcess.
     * Handles cleanup of streams, threads, and process termination.
     *
     * @param sessionId unique identifier for the process session
     * @param jobProcess the JobProcess to destroy

     * ScheduledExecutorService#scheduleWithFixedDelay} method.
     *
     * @param initialDelay the time to delay first execution
     * @param delay the delay between the termination of one execution and the commencement of the
     *     next
     * @since 33.4.0 (but since 28.0 in the JRE flavor)
     */
    @IgnoreJRERequirement // Users will use this only if they're already using Duration

  a user to request FallbackToLogsOnError, which will read from the container's
  logs to populate the termination message if the user does not write to the
  termination message log file. The termination message file is now properly
  readable for end users and has a maximum size (4k bytes) to prevent abuse.
  Each pod may have up to 12k bytes of termination messages before the contents
  of each will be truncated.

    protected long documentSize;

    /** Maximum number of indexer errors allowed */
    protected int maxIndexerErrorCount = 0;

    /** Maximum number of general errors allowed before termination */
    protected int maxErrorCount = 2;

    /** List of finished crawler session IDs for cleanup */
    protected List<String> finishedSessionIdList = new ArrayList<>();

* Fix race condition introduced by graceful termination which can lead to a deadlock in kube-proxy ([#72361](https://github.com/kubernetes/kubernetes/pull/72361), [@lbernail](https://github.com/lbernail))
* Support graceful termination with IPVS when deleting a service ([#71895](https://github.com/kubernetes/kubernetes/pull/71895), [@lbernail](https://github.com/lbernail))

  the iptables or ipvs mode of kube-proxy with `EndpointSlices` enabled. Specifically, if a
  connection for such a service arrives on a node when there are no "Ready" endpoints
  for the service, but there is at least one Terminating pod for that service on the node,
  then kube-proxy will send the traffic to the Terminating pod rather than dropping it. This

* Remove headers that are unnecessary for proxy target ([#34076](https://github.com/kubernetes/kubernetes/pull/34076), [@mbohlool](https://github.com/mbohlool))
* Support graceful termination in kube-dns ([#31894](https://github.com/kubernetes/kubernetes/pull/31894), [@MrHohn](https://github.com/MrHohn))

        int len = 0;
        while (src[srcIndex + len] != (byte) 0x00) {
            if (len++ > max) {
                throw new RuntimeCIFSException("zero termination not found: " + this);
            }
        }
        return len;
    }

    @Override
    public int encode(final byte[] dst, int dstIndex) {

* kube-proxy in IPVS mode will stop initiating connections to terminating pods for services with sessionAffinity set. ([#71834](https://github.com/kubernetes/kubernetes/pull/71834), [@lbernail](https://github.com/lbernail))
* kubeadm: improve hostport parsing error messages ([#71258](https://github.com/kubernetes/kubernetes/pull/71258), [@bart0sh](https://github.com/bart0sh))

- Fixed the preStop hook will block the pod termination grace period ([#115835](https://github.com/kubernetes/kubernetes/pull/115835), [@HirazawaUi](https://github.com/HirazawaUi)) [SIG Node and Testing]