* This counter prevents an ABA issue where a thread may successfully schedule the worker, the
   * worker runs and exhausts the queue, another thread enqueues a task and fails to schedule the
   * worker, and then the first thread's call to delegate.execute() returns. Without this counter,
   * it would observe the QUEUING state and set it to QUEUED, and the worker would never be
   * scheduled again for future submissions.
   */
  @GuardedBy("queue")

   * addListener/SES.schedule. The later racy write in cancel() is not guaranteed to be observed,
   * however that is fine since the correctness is based on the atomic state in our base class. The
   * initial write to timer is never definitely visible to Fire.run since it is assigned after
   * SES.schedule is called. Therefore Fire.run has to check for null. However, it should be visible

labels.pagination_page_guide_msg={0}/{1} ({2} items)
labels.list_could_not_find_crud_table=Not registered.
labels.scheduledjob_configuration=Job Scheduler
labels.scheduledjob_title_details=Job
labels.scheduledjob_name=Name
labels.scheduledjob_target=Target
labels.scheduledjob_status=Status
labels.scheduledjob_cronExpression=Schedule
labels.scheduledjob_scriptType=Execution Method
labels.scheduledjob_scriptData=Script
labels.scheduledjob_jobLogging=Logging

### Go-Live

- [ ] Schedule maintenance window
- [ ] Final incremental data sync
- [ ] Switch DNS or endpoints to Fess
- [ ] Monitor logs for errors
- [ ] Monitor search performance metrics
- [ ] Have rollback plan ready

### Post-Migration

- [ ] Monitor search quality and relevance
- [ ] Tune ranking and boosting settings
- [ ] Set up regular crawl schedules
- [ ] Configure backup and disaster recovery

   * either it has exceeded the keep alive limit or the idle connections limit.
   *
   * Returns the duration in nanoseconds to sleep until the next scheduled call to this method.
   * Returns -1 if no further cleanups are required.
   */
  fun closeConnections(now: Long): Long {
    // Find the longest-idle connections in 2 categories:
    //

    @Resource
    protected FileConfigService fileConfigService;

    /** Helper for managing crawler processes */
    @Resource
    protected ProcessHelper processHelper;

    /** Service for managing scheduled jobs */
    @Resource
    protected ScheduledJobService scheduledJobService;

    // ===================================================================================

labels.pagination_page_guide_msg={0}/{1} ({2} items)
labels.list_could_not_find_crud_table=Not registered.
labels.scheduledjob_configuration=Job Scheduler
labels.scheduledjob_title_details=Job
labels.scheduledjob_name=Name
labels.scheduledjob_target=Target
labels.scheduledjob_status=Status
labels.scheduledjob_cronExpression=Schedule
labels.scheduledjob_scriptType=Execution Method
labels.scheduledjob_scriptData=Script
labels.scheduledjob_jobLogging=Logging

        // future `thread == currentThread()` calls from this thread don't incorrectly queue instead
        // of executing. Don't null out the latestTaskQueue field, because the work done here
        // may have scheduled more operations on another thread, and if those operations then
        // trigger reentrant calls that thread will have updated the latestTaskQueue field, and
        // we'd be interfering with their operation.

    * Specifically the new controller watches the API server for scheduled pods. It processes each pod and ensures that any volumes that implement the volume Attacher interface are attached to the node their pod is scheduled to.

#                                                  Scheduler
#                                                     ------

# Target name for the scheduler.
scheduler.target.name=
# Job class for the scheduler.
scheduler.job.class=org.codelibs.fess.app.job.ScriptExecutorJob
# Mode for concurrent execution in the scheduler.
scheduler.concurrent.exec.mode=QUIT
# Interval for scheduler monitoring.
scheduler.monitor.interval=30