import org.opensearch.action.admin.cluster.node.hotthreads.NodesHotThreadsResponse;
import org.opensearch.common.unit.TimeValue;

/**
 * Monitor target for tracking hot threads in the OpenSearch cluster.
 * This class extends MonitorTarget to provide monitoring functionality for
 * hot threads, which helps identify performance bottlenecks and resource
 * usage issues in the search engine cluster.
 */

     * -2: use system default, -1: never expire, 0 or positive: expire after specified days.
     */
    protected int documentExpires = -2;

    /**
     * Hot thread monitoring interval in seconds.
     * -1: disabled, positive value: enable hot thread monitoring with specified interval.
     * Used for performance analysis and debugging of the crawler process.
     */
    protected int hotThreadInterval = -1;

    /**

        public String expires;

        /** Interval in milliseconds for hot thread monitoring and logging. */
        @Option(name = "-h", aliases = "--hotThread", metaVar = "hotThread", usage = "Interval for Hot Thread logging")
        public Integer hotThread;

        /**
         * Default constructor for Options.

crawler.system.monitor.interval=60
# Whether to ignore idle threads in hot thread monitoring.
crawler.hotthread.ignore_idle_threads=true
# Interval for hot thread monitoring (e.g., 500ms).
crawler.hotthread.interval=500ms
# Number of snapshots for hot thread monitoring.
crawler.hotthread.snapshots=10
# Number of threads for hot thread monitoring.
crawler.hotthread.threads=3
# Timeout for hot thread monitoring (e.g., 30s).
crawler.hotthread.timeout=30s

    /**
     * Get the value for the key 'lasta_di.smart.deploy.mode'. <br>
     * The value is, e.g. warm <br>
     * comment: The mode of Lasta Di's smart-deploy, should be cool in production (e.g. hot, cool, warm)
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getLastaDiSmartDeployMode();

    /**

            new ArrayBlockingQueue<Runnable>(1000));
    executorService.prestartAllCoreThreads();
    AtomicInteger integer = new AtomicInteger();
    // Execute a bunch of tasks to ensure that our threads are allocated and hot
    for (int i = 0; i < NUM_THREADS * 10; i++) {
      @SuppressWarnings("unused") // https://errorprone.info/bugpattern/FutureReturnValueIgnored
      Future<?> possiblyIgnoredError =
          executorService.submit(

        assertEquals("******@****.***", specialMailEnv.getMailReturnPath());
    }

    // Test deploy mode variations
    public void xtest_deployModeVariations() {
        String[] deployModes = { "hot", "cool", "warm" };

        for (String mode : deployModes) {
            FessEnv.SimpleImpl deployEnv = new FessEnv.SimpleImpl() {
                protected Properties prepareProperties() {

import org.lastaflute.di.core.exception.AutoBindingFailureException;
import org.lastaflute.di.core.exception.ComponentNotFoundException;
import org.lastaflute.di.core.factory.SingletonLaContainerFactory;
import org.lastaflute.di.core.smart.hot.HotdeployUtil;
import org.lastaflute.job.JobManager;
import org.lastaflute.web.servlet.request.RequestManager;
import org.lastaflute.web.servlet.request.ResponseManager;

/**

    }

    /*
     * These methods "should" call checkNotNull. However, I'm wary of accidentally introducing
     * anything that might slow down execution on such a hot path. Given that the methods are only
     * package-private, I feel OK with just not testing them for NPE.
     *
     * Note that testing casValue is particularly dangerous because it uses Unsafe under some

     * comment: Whether to ignore idle threads in hot thread monitoring.
     * @return The determination, true or false. (if not found, exception but basically no way)
     */
    boolean isCrawlerHotthreadIgnoreIdleThreads();

    /**
     * Get the value for the key 'crawler.hotthread.interval'. <br>
     * The value is, e.g. 500ms <br>
     * comment: Interval for hot thread monitoring (e.g., 500ms).