Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Kong does not work with Azure Cosmos Db with Cassandra API #188
I'm trying to get Kong running with Cassandra database via Azure Cosmos Db with Cassandra API. This is using Cassandra drivers which are compatible with CQL v4.
However, while running the migrations it fails because "the host seems unhealthy" while it works fine in the Azure portal. Turning off SSL validation doesn't help as well.
I'm probably doing something wrong here, if not it would be great to have this support.
More information about Cosmos Db support for Cassandra:
⚡ tkerkhove@CLT-TKERKHOVE C:\Kong master ❯ docker run --rm -e "KONG_DATABASE=cassandra" -e "KONG_CASSANDRA_CONTACT_POINTS=kong-datastore.cassandra.cosmosdb.azure.com" -e "KONG_CASSANDRA_SSL=false" -e "KONG_CASSANDRA_KEYSPACE=kongdatastore" -e "KONG_CASSANDRA_USERNAME=kong-datastor e" -e "KONG_CASSANDRA_PASSWORD=<password>" -e "KONG_CASSANDRA_PORT=10350" kong:latest kong migrations up --v 2018/10/30 08:58:24 [verbose] Kong: 0.14.1 2018/10/30 08:58:24 [warn] You are using Cassandra but your 'db_update_propagation' setting is set to '0' (default). Due to the distributed nature of Cassandra, you should increase this value. Error: /usr/local/share/lua/5.1/kong/cmd/migrations.lua:33: [cassandra error] all hosts tried for query failed. kong-datastore.cassandra.cosmosdb.azure.com: host seems unhealthy, considering it down (timeout) stack traceback: [C]: in function 'assert' /usr/local/share/lua/5.1/kong/cmd/migrations.lua:33: in function 'cmd_exec' /usr/local/share/lua/5.1/kong/cmd/init.lua:87: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:87> [C]: in function 'xpcall' /usr/local/share/lua/5.1/kong/cmd/init.lua:87: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:44> /usr/local/bin/kong:7: in function 'file_gen' init_worker_by_lua:48: in function <init_worker_by_lua:46> [C]: in function 'xpcall' init_worker_by_lua:55: in function <init_worker_by_lua:53> 2018/10/30 08:58:24 [verbose] no config file found at /etc/kong/kong.conf 2018/10/30 08:58:24 [verbose] no config file found at /etc/kong.conf 2018/10/30 08:58:24 [verbose] no config file, skipping loading 2018/10/30 08:58:24 [verbose] prefix in use: /usr/local/kong
Thanks for your report. We recently did a quick test of Kong + Azure Cosmos DB, and came to the conclusion, after some discussion with Microsoft staff, that Kong does not currently support Cosmos DB, and that the work necessary to cause Kong to support Cosmos DB is more than minor.
In the long term, we do hope to support Cassandra "compatible" datastores like Cosmos DB, but I don't have any timeline to offer.
Just to clarify a point here: Kong is not compatible with CosmosDB because CosmosDB does not implement several (more than a couple) of the Cassandra features that Kong depends on.
Thanks for the update. What features are currently lacking that are required? Tom Kerkhove Azure Architect at Codit, Microsoft Azure MVP…
________________________________ From: Thibault Charbonnier <firstname.lastname@example.org> Sent: Tuesday, October 30, 2018 6:17:34 PM To: Kong/docker-kong Cc: Tom Kerkhove; Author Subject: Re: [Kong/docker-kong] Kong does not work with Azure Cosmos Db with Cassandra API (#188) Just to clarify a point here: Kong is not compatible with CosmosDB because CosmosDB does not implement several (more than a couple) of the Cassandra features that Kong depends on. There is no or very little amount of work to be done on Kong itself (in case someone stumbling upon this issue is wondering what a contribution would take), but work to be done by the CosmosDB team itself. Hope that clarifies the situation. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#188 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEJPP4uJRr304SV_YWIR0Ct9Yg49VsKZks5uqImugaJpZM4YBd0n>.
@tomkerkhove Hi there,
The specific features that Kong needs as of 1.0 are:
We are in touch with some folks on the CosmoDB team since last September. Given their current timeline, it'll be a few more months until CosmoDB implements the above feature, at which point, we'll give the Kong <-> CosmoDB test another go.