Jacana: Stream Solana events into ClickHouse

Understand the project

Practical overview

Use Jacana when you have a Solana Geyser environment and ClickHouse destination and need a real-time ingestion path between them.

Operators building a self-hosted Solana data index backed by ClickHouse.
Developers creating analytics pipelines that need Solana event data stored in ClickHouse.

Ingest Solana Geyser events into ClickHouse for downstream queries.
Batch and stream event data in a columnar format rather than using a row-oriented serialization path.
Configure worker pools, buffering and flush behavior for different event types.

Before you choose

The repository is public and identified as open source. The service is described as server-side, self-hosted infrastructure.

Requires a compiled plugin library and a Solana environment that can load a Geyser plugin.
Requires a reachable ClickHouse server and connection details, including database credentials.
The documented native protocol uses port 9000; this is distinct from ClickHouse's HTTP interface.
Worker counts, buffer limits and flush intervals affect throughput, latency and backpressure behavior.
The README describes drops logged when bounded channels are full, so channel and workload sizing matter.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Prepare Jacana’s configuration to connect to ClickHouse over its native protocol.

A compiled Jacana plugin library, whose path is supplied as libpath.
A ClickHouse server hostname or IP, database name, and ClickHouse credentials.
A ClickHouse server reachable through the native protocol; the documented default port is 9000.

Set libpath to the compiled plugin library’s path; the documentation recommends an absolute path for production.
Set host, database, username, and password for your ClickHouse server. Use port 9000 for the native protocol unless your setup requires another value.
Choose a supported compression value (none, lz4, or zstd); lz4 is the documented recommendation for throughput and CPU balance.
Keep validate_schemas enabled to check table schemas on startup, and set other documented options such as starting_slot, log_level, and runtime_threads as appropriate.

A Jacana configuration specifies the plugin library, ClickHouse connection details, and schema-validation and runtime options.

The documented configuration does not provide a complete configuration file or describe building the plugin library.
This guide covers configuration only; it does not document installing Jacana, configuring a Solana validator to load it, or verifying ingestion.
The documentation’s performance and latency figures are stated expectations, not guaranteed results.

Evidence and transparency

Source record details

Source availability: Active
Sources checked: 17 October 2026
Original website title: mip404/jacana · Official homepage title · retained in its source language