Sie können in der Administrationsoberfläche (Web, Datei, Datenspeicher) Crawling-Ziele in den Crawler-Konfigurationsseiten registrieren und den Crawler manuell auf der [Scheduler-Seite](https://fess.codelibs.org/14.17/admin/scheduler-guide.html) starten.

## Migration von einem anderen Suchanbieter

Bitte lesen Sie [MIGRATION.md](MIGRATION.md).

## Datenspeicher

    private final AtomicInteger globalAttemptsInCurrentWindow = new AtomicInteger(0);
    private final AtomicLong currentWindowStart = new AtomicLong(System.currentTimeMillis());

    // Cleanup scheduler
    private final ScheduledExecutorService cleanupScheduler;
    private final AtomicBoolean closed = new AtomicBoolean(false);

    // Statistics
    private final AtomicLong totalAttemptsBlocked = new AtomicLong(0);

		<c:if test="${fe:permission('admin-scheduler')}">
			<li class="nav-item" data-toggle="tooltip" data-placement="left"
				title="<la:message key="labels.tooltip_run_crawler" />"><a class="nav-link"
									 href="${contextPath}/admin/scheduler/details/4/default_crawler"><em
					class="fa fa-play-circle"></a></li>
		</c:if>
		<c:if test="${not empty forumLink}">

            totalCalls.incrementAndGet();
            // Make sure that no other tasks are scheduled to run while this is running.
            assertFalse(fakePool.hasNext());
          }
        };

    assertFalse(fakePool.hasNext());
    e.execute(intCounter);
    // A task should have been scheduled
    assertTrue(fakePool.hasNext());
    e.execute(intCounter);
    // Our executor hasn't run any tasks yet.

# Background Tasks - `BackgroundTasks`

You can declare a parameter in a *path operation function* or dependency function with the type `BackgroundTasks`, and then you can use it to schedule the execution of background tasks after the response is sent.

You can import it directly from `fastapi`:

```python
from fastapi import BackgroundTasks
```

							<p><la:message key="labels.menu_crawl_config" /></p>
						</a>
					</li>
					</c:if>
					<c:if test="${fe:permission('admin-scheduler-view')}">
					<li class="nav-item">
						<a href="${fe:url('/admin/scheduler/')}" class="nav-link <c:if test="${param.menuType=='scheduler'}">active</c:if>">
							<em class='fa fa-genderless nav-icon'>
							<p><la:message key="labels.menu_scheduler_config" /></p>
						</a></li></c:if>

                                <c:if test="${fe:permission('admin-scheduler')}">
                                    <la:link styleClass="btn btn-success"
                                             href="/admin/scheduler/createnewjob/data_crawling/${f:u(id)}/${fe:base64(name)}">
                                        <em class="fa fa-plus-circle">

        .build();

    final long startNanos = System.nanoTime();
    final Call call = client.newCall(request);

    // Schedule a job to cancel the call in 1 second.
    executor.schedule(() -> {
      System.out.printf("%.2f Canceling call.%n", (System.nanoTime() - startNanos) / 1e9f);
      call.cancel();

* Fix a bug in scheduler happening after retrying unsuccessful bindings ([#37293](https://github.com/kubernetes/kubernetes/pull/37293), [@wojtek-t](https://github.com/wojtek-t))
* Try self-repair scheduler cache or panic ([#37379](https://github.com/kubernetes/kubernetes/pull/37379), [@wojtek-t](https://github.com/wojtek-t))

        new Runnable() {
          @Override
          public void run() {
            taskDone = true;
          }
        };
    ScheduledFuture<?> future =
        TestingExecutors.noOpScheduledExecutor().schedule(task, 10, MILLISECONDS);
    Thread.sleep(20);
    assertFalse(taskDone);
    assertFalse(future.isDone());
  }

  public void testNoOpScheduledExecutorShutdown() {