KONG API INSTALLATION FAILURE DUE TO CASSANDRA CONFIG

We have Kong API running on Kubernetes. It uses Cassandra to store meta data. The setup used in production is clustered one but due to cost consideration we were asked to build a POC environment with single node. We were given two VMs – one to run Kubernetes control plane and other to run Cassandra and Kong worker nodes.

As you are aware there are 3 basic steps to install Kong API:
1) Create and run Cassandra pods.
2) Run Kong migrations to create Kong data schemas in Cassandra.
3) Create and run Kong pods.

We made necessary changes in values.yaml of helm charts of Cassandra and Kong to reflect new environment. When we ran Helm charts Cassandra DB and Kong migrations got created successfully but Kong pods were stuck in Init state. Kong pod had two containers: wait-for-db and Kong containers. wait-for-db container had been stuck so pod also stuck in Init state. We looked at this init container using following command:
kubectl logs <kong pod> -c wait-for-db

The error message we found in logs is:
{“log”:”Error: kong/cmd/utils/migrations.lua:25: New migrations available; run ‘kong migrations up’ to proceed\n”,”stream”:”stderr”,”time”:”2021-03-13T13:59:43.307717562Z”}

As error message had suggested to run “kong migrations up“, I have logged into init container shell and ran the command. It threw another error:

[kong@kong-pod /]$ kong migrations up
2021/03/12 14:52:13 [warn] RBAC authorization is enabled but Admin API calls will not be encrypted via SSL
Error: [Cassandra error] failed to insert cluster lock: [Unavailable exception] Cannot achieve consistency level QUORUM

Basically, the error is saying that Cassandra was not able to insert records due to insufficient quorum. Though we are using single node for Cassandra some how it was expecting a quorum. So, we revisited Kong configuration and found that Cassandra configuration was set to cluster. So we made following changes to values.yaml. Deleted Cassandra and Kong Helm deployments and re-executed Helm charts. Finally issue got fixed.

  • Changed replicatio starategy from NetworkTopologyStrategy to SimpleStrategy
  • Added: cassandra_repl_factor: 1

Side note, though migrations job failed to create Kong schemas it was marked as success. This prolonged our investigation.

Comments

Post a Comment

Popular posts from this blog

HOW WE REDUCED SOA OSB PROVISIONING FROM 4 DAYS TO 4 HOURS

 In our organization, we’ve undertaken the task of upgrading both SOA and OSB from version 12.2.1.3 to 12.2.1.4. This involves an out-of-place migration approach, wherein we create a new environment and switch traffic during the cutover. As you know, this process typically requires several days we opt for manual provisioing. A very significant amount of automation work was previously accomplished for 12.2.1.3 by our predecessors. Despite these efforts, the process still used to take lot of time due to following factors: Bugs in existing automation. For example, SOA composite deployments is not stable which warrants lot of manual work Import of 10s of TLS Certificates into KSS Manual retiring and shutting down of services Monitoring setup Miscellaneous: Increasing Log file count, enabling GC logging, changing heap parameters, bash profile changes While our current automation initiatives have yielded substantial savings, we aimed to capitalize on this upgrade activity to enable end-t...
Read more

NOT ABLE TO START RABBITMQ CLUSTER: CANNOT DECLARE A QUEUE ‘~S’ ON NODE ‘~S’: ~255P

We have 7 node rabbitmq cluster and we are using sharding queues. We have shutdown all non prod rabbitmq nodes as part of VM patching. As it was non prod, we thought of shutting down all together instead of rolling patching. We couldn’t start the any of the rabbitmq post patching. All of nodes were failing to start with the below error: 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> “Cannot declare a queue ‘~s’ on node ‘~s’: ~255p”, 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> [“queue ‘sharding: shard.my.queue – rabbit@rabbit1’ in vhost ‘my_vhost'” This is a known issue in some old versions of rabbitmq. rabbitmq node fails to come up with above error. Work around for this is to disable sharding policy for the problematic sharding queue. It can be done either from command line or from rabbitmq admin page. It requires to connect a running node. But as all the nodes were down, we could not disable sharding policy. Luckily, rabbitmq allows disabling sharding pulgi...
Read more

SOA SUITE 12.2.1.4 INSTALLATION: GOT EXCEPTION WHEN AUTO CONFIGURING THE SCHEMA COMPONENT(S) WITH DATA OBTAINED FROM SHADOW TABLE

  We planned to do out of place upgrade from soa suite 12.2.1.3 to 12.2.1.4. As part of this, we planned to automate end to end provisioning. While executing domain configuration using ansible and python scripts, we got following error in domain creation step. Got exception when auto configuring the schema component(s) with data obtained from shadow table. Failed to build JDBC Connection object: com.oracle.cie.domain.script.jython.CommandExceptionHandler. exception. Quick internet search gave few solutions like deleting domain-registry.xml file, verifying dehydration store password supplied to script etc. But none of them helped. After trying several options, I thought I might have done some stupid error prior to domain creation step. To track down the issue, though of checking what getDatabaseDefaults actually doing. I tried to grep for the getDatabaseDefaults function call inside oracle home. But couldn’t find the source code for the python function. As a final resort, thought of...
Read more