* @param cmdList list of command and arguments to execute
     * @param pbCall callback to configure the ProcessBuilder
     * @param bufferSize size of the buffer for process output
     * @param outputCallback callback to handle process output lines
     * @return JobProcess representing the started process
     * @throws JobProcessingException if the process cannot be started
     */

import jakarta.annotation.PostConstruct;

/**
 * Response processor implementation for the Fess search engine.
 * This processor extends DefaultResponseProcessor to provide additional
 * processing capabilities through the ingest framework, allowing for
 * custom data transformation and enrichment during the crawling process.
 *
 * <p>It supports pluggable ingesters that can modify the result data

     * @param query the Lucene query to be processed
     * @param boost the boost factor to apply to the query
     * @return the processed OpenSearch QueryBuilder
     */
    public QueryBuilder execute(final QueryContext context, final Query query, final float boost) {
        return filterChain.execute(context, query, boost);
    }

    /**
     * Adds a query command to the processor.
     *

This is still true.

So, to be able to have **multiple processes** at the same time, there has to be a **single process listening on a port** that then transmits the communication to each worker process in some way.

### Memory per Process { #memory-per-process }

        }
    }

    /**
     * Processes and normalizes a document title.
     * Applies text normalization using configured space characters and returns
     * a clean title suitable for indexing.
     *
     * @param responseData the response data from crawling (not currently used)
     * @param title the raw title text to process
     * @param dataMap additional data map (not currently used)

A container is running as long as the **main process** (command or program) is running.

A container normally has a **single process**, but it's also possible to start subprocesses from the main process, and that way you will have **multiple processes** in the same container.

But it's not possible to have a running container without **at least one running process**. If the main process stops, the container stops.

```

</div>

////

The only new option here is `--workers` telling Uvicorn to start 4 worker processes.

You can also see that it shows the **PID** of each process, `27365` for the parent process (this is the **process manager**) and one for each worker process: `27368`, `27369`, `27370`, and `27367`.

## Deployment Concepts { #deployment-concepts }

errors.login.failure = Falha no login.
errors.app.illegal.transition = Transição ilegal. Por favor, tente novamente.
errors.app.db.already.deleted = Pode ter sido excluído por outro processo. Por favor, tente novamente.
errors.app.db.already.updated = Pode ter sido atualizado por outro processo. Por favor, tente novamente.
errors.app.db.already.exists = Os dados já existem. Por favor, tente novamente.

            flush();
        }
        return (long) ids.length;
    };

    /**
     * Processes the score boosting.
     * @return The number of processed documents.
     */
    public abstract long process();

    /**
     * Enables this score booster.
     */
    protected void enable() {

     * @param fessConfig the Fess configuration
     * @param entity the thumbnail queue entity to process
     */
    protected void process(final FessConfig fessConfig, final ThumbnailQueue entity) {
        final SystemHelper systemHelper = ComponentUtil.getSystemHelper();
        systemHelper.calibrateCpuLoad();

        if (logger.isDebugEnabled()) {
            logger.debug("Processing thumbnail: {}", entity);
        }