Troubleshoot SmithDB

SmithDB is optional and available in beta. Use this page to gather troubleshooting context or safely disable and reset a SmithDB deployment. Keep ClickHouse configured and available throughout.

Use this page to gather troubleshooting context or safely disable and reset a SmithDB deployment.

Before making changes

Stop at the current installation or migration stage until the issue is understood.
Record the LangSmith and Helm chart versions and the most recent configuration change.
Preserve failed Jobs, TaskDB, and relevant logs before deleting or recreating resources.
Do not delete the SmithDB metastore or object-storage data while troubleshooting.

Support

If no documented issue matches, contact LangChain through the Support Portal.

Disable or reset SmithDB

Use this section to stop routing LangSmith traffic to SmithDB and disable SmithDB services in an existing self-hosted deployment. Keep ClickHouse configured and available throughout.

Return to Install LangSmith with SmithDB for the installation and cutover sequence.

If a historical migration is active or its progress must be preserved, stop before disabling SmithDB. Disabling migration removes chart-managed TaskDB resources and, by default, its PVC. Contact LangChain through the Support Portal if you need to preserve migration progress.

Before you begin

Expect re-enabling SmithDB ingestion later to require another migration to restore consistency with ClickHouse.

Step 1. Disable SmithDB LangSmith integration

Keep SmithDB services enabled, but disable query, ingestion, and migration:

smithdb:
  enabled: true
  langsmith:
    ingestion:
      enabled: false
    migration:
      enabled: false
    query:
      enabled: false

Apply the chart through your normal deployment workflow and wait for the rollout to complete. This sets LangSmith query and ingestion traffic to solely ClickHouse before any SmithDB workloads are removed.

Step 2. Disable SmithDB services

After the first Helm update completes, disable SmithDB services while leaving the integration flags off:

smithdb:
  enabled: false
  langsmith:
    ingestion:
      enabled: false
    migration:
      enabled: false
    query:
      enabled: false

Apply the chart again. Separating traffic cutover from workload removal avoids requests racing with SmithDB shutdown.

Step 3. Optional: remove SmithDB data

This cleanup is destructive. Continue only after SmithDB services are disabled and its data is no longer needed for re-enablement, diagnosis, or recovery.

Optionally remove the dedicated SmithDB object-storage data and PostgreSQL metastore. Re-enabling SmithDB after this cleanup requires recreating its supporting infrastructure and re-migrating data from ClickHouse.

Get started by cloud provider

Deploy with Terraform

Setup guides

Configuration

Connect external services

SmithDB (optional)

Platform auth & access control

Self-hosted observability

Hybrid

Scripts

Reference

Before making changes

Support

Disable or reset SmithDB

Before you begin

Step 1. Disable SmithDB LangSmith integration

Step 2. Disable SmithDB services

Step 3. Optional: remove SmithDB data

See also

​Before making changes

​Support

​Disable or reset SmithDB

​Before you begin

​Step 1. Disable SmithDB LangSmith integration

​Step 2. Disable SmithDB services

​Step 3. Optional: remove SmithDB data

​See also

Before making changes

Support

Disable or reset SmithDB

Before you begin

Step 1. Disable SmithDB LangSmith integration

Step 2. Disable SmithDB services

Step 3. Optional: remove SmithDB data

See also