solana-accountsdb-plugin-kafka 0.1.4+solana.1.11.3

Solana AccountsDb plugin for Kafka failed to build solana-accountsdb-plugin-kafka-0.1.4+solana.1.11.3
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure builds.
If you believe this is' fault, open an issue.

Solana AccountsDB Plugin for Kafka

Kafka publisher for use with Solana's plugin framework.


Binary releases

Find binary releases at:

Building from source

cargo build --release
  • Linux: ./target/release/
  • macOS: ./target/release/libsolana_accountsdb_plugin_kafka.dylib

Important: Solana's plugin interface requires the build environment of the Solana validator and this plugin to be identical.

This includes the Solana version and Rust compiler version. Loading a plugin targeting wrong versions will result in memory corruption and crashes.


Config is specified via the plugin's JSON config file.

Example Config

  "libpath": "/solana/target/release/",
  "kafka": {
    "bootstrap.servers": "localhost:9092",
    "request.required.acks": "1",
    "": "30000",
    "compression.type": "lz4",
    "partitioner": "murmur2_random"
  "shutdown_timeout_ms": 30000,
  "update_account_topic": "solana.testnet.account_updates",
  "slot_status_topic": "solana.testnet.slot_status",
  "publish_all_accounts": false,
  "program_ignores": [


  • libpath: Path to Kafka plugin
  • kafka: librdkafka config options. This plugin overrides the defaults as seen in the example config.
  • shutdown_timeout_ms: Time the plugin is given to flush out all messages to Kafka upon exit request.
  • update_account_topic: Topic name of account updates. Omit to disable.
  • slot_status_topic: Topic name of slot status update. Omit to disable.
  • publish_all_accounts: Publish all accounts on startup. Omit to disable.
  • program_ignores: Solana program IDs for which to ignore updates for owned accounts.


The Kafka producer acts strictly non-blocking to allow the Solana validator to sync without much induced lag. This means incoming events from the Solana validator will get buffered and published asynchronously.

When the publishing buffer is exhausted any additional events will get dropped. This can happen when Kafka brokers are too slow or the connection to Kafka fails. Therefor it is crucial to choose a sufficiently large buffer.

The buffer size can be controlled using librdkafka config options, including:

  • queue.buffering.max.messages: Maximum number of messages allowed on the producer queue.
  • queue.buffering.max.kbytes: Maximum total message size sum allowed on the producer queue.