Executor options

Specify executor options for the dsbulk command. These options define how DataStax Bulk Loader executes queries, and they allow users to control throughput, throttling, concurrency, and query method execution.

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

    The maximum number of concurrent operations per second. This setting 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. This setting applies to all operations: when writing to the database, it applies to the number of statements executed; when reading from the database, it applies to the number of rows retrieved. Starting in 1.6.0, disabled by default.

    For important related information, see --dsbulk.engine.maxConcurrentQueries.

    Default: -1

  • --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 if you are facing out-of-memory errors. Starting in 1.6.0, disabled by default.

    For important related information, see --dsbulk.engine.maxConcurrentQueries.

    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 --datastax-java-driver.basic.request.consistency is not ONE or LOCAL_ONE, traditional paging is used regardless of this setting. Can be used with unload and count operations. Not applicable for load.

    Default: true

  • --executor.continuousPaging.maxConcurrentQueries, --dsbulk.executor.continuousPaging.maxConcurrentQueries number

    Deprecated. The correct option to use is --engine.maxConcurrentQueries.

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

    Deprecated. The correct option to use is --datastax-java-driver.advanced.continuous-paging.max-pages.

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

    Deprecated. The correct option to use is --datastax-java-driver.advanced.continuous-paging.max-pages-per-second.

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

    Deprecated. The correct option to use is --datastax-java-driver.advanced.continuous-paging.page-size.

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

    Deprecated. The correct option to use is --datastax-java-driver.advanced.continuous-paging.page-size-in-bytes.