| Active |
|
Normal charm operations |
No actions required |
| Active |
manual partition reassignment may be needed to utilize new storage volumes |
Existing data is not automatically rebalanced when new storage is attached. New storage will be used for newly created topics and/or partitions |
Inspect the storage utilization and based on the need, use the bash utility script /snap/charmed-kafka/current/opt/kafka/bin/kafka-reassign-partitions.sh for manual data rebalancing. |
| Active |
potential data loss due to storage removal without replication |
Some partition/topics are not replicated on multiple storages, therefore potentially leading to data loss |
Add new storage, increase replication of topics/partitions and/or rebalance data across multiple storages/brokers |
| Active |
machine system settings are not optimal - see logs for info |
The broker is running on a machine that has sub-optimal OS settings. Although this may not preclude Apache Kafka to work, it may result in sub-optimal performances |
Check the juju debug-log for insights on which settings are sub-optimal and may be changed |
| Active |
sysctl params cannot be set. Is the machine running on a container? |
Some of the sysctl settings required by Apache Kafka could not be set, therefore affecting Apache Kafka performance and correct settings. This can also be due to the charm being deployed on the wrong substrate |
Remove the deployment and make sure that the selected charm is correct given the Juju cloud substrate |
| Blocked |
unable to install charmed-kafka snap |
There are issues with the network connection and/or the Snap Store |
Check your internet connection and https://status.snapcraft.io/. Remove the application and when everything is ok, deploy the charm again |
| Blocked |
snap service not running |
The charm failed to start the snap daemon processes |
Check the Apache Kafka logs for insights on the issue |
| Blocked |
missing required zookeeper relation |
Apache Kafka charm has not been connected to any ZooKeeper cluster |
Relate to an Apache ZooKeeper charm |
| Blocked |
unit not connected to zookeeper |
Although the relation is present, the unit has failed to connect to Apache ZooKeeper |
Make sure that Apache Kafka and Apache ZooKeeper can connect and exchange data. When using encryption, make sure that certificates/ca are correctly setup. |
| Blocked |
tls must be enabled on both kafka and zookeeper |
Encryption (and relation with TLS-certificates operators) must be either enabled or disabled on both Charmed Apache Kafka and Charmed Apache ZooKeeper |
Make sure that both Charmed Apache Kafka and Charmed Apache ZooKeeper either both use or neither of them use encryption. |
| Waiting |
zookeeper credentials not created yet |
Credentials are being created on Charmed Apache ZooKeeper, and Charmed Apache Kafka is waiting to receive them to connect to Apache ZooKeeper |
|
| Waiting |
internal broker credentials not yet added |
Intra-broker credentials being created to enable communication and syncing among brokers belonging to the Apache Kafka clusters. |
|
| Waiting |
unit waiting for signed certificates |
Unit has requested a CSR request via the certificates relation and it is waiting to receive the signed certificate |
|
| Maintenance |
|
Charm is performing the internal maintenance (e.g. cluster re-configuration, upgrade, …) |
No actions required |
| Error |
any |
An unhanded internal error happened |
Read the message hint. Execute juju resolve <error_unit/0> after addressing the root of the error state |
| Terminated |
any |
The unit is gone and will be cleaned by Juju soon |
No actions possible |
| Unknown |
any |
Juju doesn’t know the charm app/unit status. Possible reason: K8s charm termination in progress. |
Manual investigation required if status is permanent |
