Menu
On Mac, I pulled latest docker images. As I run stack, everything seems to be okay but "Connect" crashed with Exit 137.
When I looked at the command center, cluster health seems to be fine. What is the impact of this? How to correct the problem ?
Appreciate any help.
Thanks !
545
Exit code 137 means a container or pod is trying to use more memory than it's allowed. The process gets terminated to prevent memory usage ballooning indefinitely, which could cause your host system to become unstable.
Connect Kafka Connect to Confluent Cloud. Create the Topics in Cloud Cluster. Set up a local Connect Worker with Confluent Platform install. Standalone Cluster.
Confluent Schema RegistryAlthough Schema Registry is not a required service for Kafka Connect, it enables you to easily use Avro, Protobuf, and JSON Schema as common data formats for the Kafka records that connectors read from and write to.
After you have Confluent Platform and Kafka Connect and your connectors running, you can check the log levels and change log levels using Connect API endpoints. Changes made through the API are not permanent. That is, any changes made using the API do not change properties in the connect-log4j. properties file.
Error 137 is indicative of out-of-memory.
To run Confluent Platform you must allocate a minimum of 8 GB of Docker memory resource.
E.g. the default memory allocation on Docker Desktop for Mac is 2 GB and must be changed.
108
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
