Executor options

Executor options for the dsbulk command

cassandra.yaml

The location of the cassandra.yaml file depends on the type of installation:
Package installations /etc/dse/cassandra/cassandra.yaml
Tarball installations installation_location/resources/cassandra/conf/cassandra.yaml

Specify executor options for the dsbulk command.

The options can be used in short form (-k keyspace_name) or long form (--schema.keyspace keyspace_name).

--executor.maxPerSecond, --dsbulk.executor.maxPerSecond number

The maximum number of concurrent operations per second. This acts as a safeguard to prevent more requests than the cluster can handle. Batch statements are counted by the number of statements included. Reduce this setting when the latencies get too high and a remote cluster cannot keep up with throughput, as dsbulk requests will eventually time out. Extend the functionality to loading by making it take into account the number of received rows, not the number of requests sent, and applies to rate limiting for both loading and unloading. Setting this option to any negative value will disable it.

Default: -1

--executor.continuousPaging.enabled, --dsbulk.executor.continuousPaging.enabled {true | false}

Enable or disable continuous paging. If the target cluster does not support continuous paging, or if driver.query.consistency is not ONE or LOCAL_ONE, traditional paging is used regardless of this setting. Used for unloading only.

Default: true

--executor.continuousPaging.maxConcurrentQueries, --dsbulk.executor.continuousPaging.maxConcurrentQueries number
The maximum number of concurrent continuous paging queries that should be carried in parallel. Set this number to a value equal to, or lesser than, the value configured server-side for continuous_paging.max_concurrent_sessions in the cassandra.yaml configuration file. If not set as noted above, some requests may be rejected. Setting this option to any negative value or zero will disable it.

Default: 60

--executor.continuousPaging.maxPages, --dsbulk.executor.continuousPaging.maxPages number

Deprecated. Instead use --datastax-java-driver.advanced.continuous-paging.max-pages.

--executor.continuousPaging.maxPagesPerSecond, --dsbulk.executor.continuousPaging.maxPagesPerSecond number

Deprecated. Instead use --datastax-java-driver.advanced.continuous-paging.max-pages-per-second.

--executor.continuousPaging.pageSize, --dsbulk.executor.continuousPaging.pageSize number

Deprecated. Instead use --datastax-java-driver.advanced.continuous-paging.page-size.

--executor.continuousPaging.pageUnit, --dsbulk.executor.continuousPaging.pageUnit {ROWS | BYTES}

Deprecated. Instead use --datastax-java-driver.advanced.continuous-paging.page-size-in-bytes.

--executor.maxInFlight, --dsbulk.executor.maxInFlight number

The maximum number of "in-flight" requests, or maximum number of concurrent requests waiting for a response from the server. This acts as a safeguard to prevent more requests than the cluster can handle. Batch statements count as one request. Reduce this value when the throughput for reads and writes cannot match the throughput of mappers; this is usually a sign that the workflow engine is not well calibrated and will eventually run out of memory. Setting this option to any negative value will disable it.

Default: 1024