The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
How to configure the Aerospike Outbound Connector for Kafka to avoid /tmp
Context
The Aerospike Outbound Connector for Kafka allows Aerospike clusters to ship records to Kafka topics. By default, the Connector installs software in /tmp notably the netty client/server framework used by the Connector.
Some environments may mount /tmp with the noexec flag to prevent malicious exploits. How can the Connector be configured to avoid use of /tmp?
Method
To use an alternate directory the user should edit the /etc/systemd/system/aerospike-kafka-outbound.service file and add the following line:
Environment=AEROSPIKE_KAFKA_OUTBOUND_OPTS=-Dio.netty.native.workdir=<changeit>
[Service]
...
...
Environment=AEROSPIKE_KAFKA_OUTBOUND_OPTS=-Dio.netty.native.workdir=<changeit>
...
...
Then the Connector daemon should be reloaded and then restarted.
$sudo systemctl daemon-reload
$sudo systemctl start aerospike-kafka-outbound
Keywords
KAFKA OUTBOUND CONNECTOR TMP NOEXEC
Timestamp
June 2021