# SHOW CDC EXTRACTOR POOL

Displays information about the CDC-in pipelines.

This command returns the state of the CDC extractor pool, and enables the user to observe the pool state. Additionally, it provides information on when a pipeline will have access to data ingestion.

## Syntax

```sql
SHOW CDC EXTRACTOR POOL 
```

## Output

The following table lists the columns returned in the output of `SHOW CDC EXTRACTOR POOL` command and their descriptions:

| Column Name   | Description                                                                                                   |
| ------------- | ------------------------------------------------------------------------------------------------------------- |
| `ID`          | ID of the extractor in the pool in the`<database_name>.<pipeline_name>.<internal_instance_ID>`format.         |
| `AWAIT`       | The length of time (in seconds) a pipeline has been waiting in the queue to acquire the extractor subprocess. |
| `UPTIME`      | Uptime of the extractor subprocess, in seconds.                                                               |
| `DO_NOT_KILL` | Prevents yielding the pool slot to another pipeline.                                                          |
| `MEMORY`      | Memory used by the extractor subprocess, in MBs.                                                              |

## Remarks

* The extractors are shared by all the CDC pipelines.
* Each extractor is allocated at least `UPTIME` number of seconds for ingesting data and listening to CDC events.
* The `MEMORY` used by each extractor can be increased or decreased by updating the `pipelines_cdc_java_heap_size` engine variable, which specifies the JVM heap size limit.

## Example

The following is an example of the output returned by the `SHOW CDC EXTRACTOR POOL` command:

```sql
SHOW CDC EXTRACTOR POOL;

```

```output

+---------------------------------+-------+--------+-------------+--------+
| ID                              | AWAIT | UPTIME | DO_NOT_KILL | MEMORY |
+---------------------------------+-------+--------+-------------+--------+
| migr_db.migr_db.movie1.0fe5917f |       | 0.877  | NO          | 128    |
| migr_db.migr_db.movie2.4d24a1d1 | 9.984 |        |             |        |
| migr_db.migr_db.movie3.e2ffb071 |       | 13.821 | NO          | 245    |
| migr_db.migr_db.movie4.6fe0fb39 | 0.453 |        |             |        |
| migr_db.migr_db.movie5.43b17da1 | 0.559 |        |             |        |
| migr_db.migr_db.movie6.d7156804 |       | 0.551  | NO          | 128    |
| migr_db.migr_db.movie7.976164c7 |       | 0.633  | NO          | 128    |
| migr_db.migr_db.movie8.b6a7bd50 | 0.870 |        |             |        |
+---------------------------------+-------+--------+-------------+--------+
```

The output shows that the `migr_db.movie1`, `migr_db.movie3`, `migr_db.movie6`, and `migr_db.movie7` pipelines are currently ingesting data. While the `migr_db.movie2`, `migr_db.movie4`, `migr_db.movie5`, and `migr_db.movie8` pipelines are waiting.

In this example, the extractor IDs `migr_db.migr_db.movie<n>.<internal_ID>` indicate the following:

* `migr_db`: Database name.
* `migr_db.movie<n>`: Pipeline name in the `<database_name>.<table_name>` format, as created by the `CREATE {TABLE | TABLES} AS INFER PIPELINE` command.
* `internal_ID`: Internal extractor instance identifier.

***

Modified at: May 30, 2025

Source: [/cloud/reference/sql-reference/show-commands/show-cdc-extractor-pool/](https://docs.singlestore.com/cloud/reference/sql-reference/show-commands/show-cdc-extractor-pool/)

(An index of the documentation is available at /llms.txt)