Documentation

influx replication create

Replication remotes and replication streams can only be configured for InfluxDB OSS.

The influx replication create command creates a new InfluxDB replication stream.

Usage

influx replication create [command options] [arguments...]

Flags

Flag Description Input type Maps to ?
-n --name Replication stream name string
-d --description Replication stream description string
--org-id Local organization ID string INFLUX_ORG_ID
-o --org Local organization name string INFLUX_ORG
--remote-id Remote connection ID to replicate data to string
--local-bucket-id Local bucket ID to replicate data from string
--remote-bucket Remote bucket name to replicate data to (mutually exclusive with --remote-bucket-id) string
--remote-bucket-id Remote bucket ID to replicate data to (mutually exclusive with --remote-bucket-name) string
--max-queue-bytes Max queue size in bytes (default: 67108860) integer
--drop-non-retryable-data Drop data when a non-retryable error is encountered
--no-drop-non-retryable-data Do not drop data when a non-retryable error is encountered
--max-age Specify a maximum age (in seconds) for data before it is dropped integer
--host InfluxDB HTTP address (default http://localhost:8086) string INFLUX_HOST
--skip-verify Skip TLS certificate verification INFLUX_SKIP_VERIFY
--configs-path Path to influx CLI configurations (default ~/.influxdbv2/configs) string INFLUX_CONFIGS_PATH
-c --active-config CLI configuration to use for command string
--http-debug Inspect communication with InfluxDB servers string
--json Output data as JSON (default false) INFLUX_OUTPUT_JSON
--hide-headers Hide table headers (default false) INFLUX_HIDE_HEADERS
-t --token InfluxDB API token string INFLUX_TOKEN

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token

Create a replication stream

  1. Create a remote connection, if you haven’t already.
  2. Use influx remote list to get the ID for the remote you want to replicate data to.
    $ influx remote list
    ID			        Name		Org ID
    0ooxX0xxXo0x 	    myremote    [...]
    
  3. Create the replication:
    influx replication create \
      --name myreplication
      --local-bucket example-local-bucket
      --remote-bucket example-remote-bucket
      --remote-id 0ooxX0xxXo0x
    

Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud Serverless