Kong Cluster Initial Core Migration to Cassandra cluster

[Nareen M]

Hi, 

I am trying to set up 3-Kong and 3-Cassandra cluster. I've learnt that core migrations should not run concurrently on Kong servers. Do all three Kong nodes need to migrate their core? OR only one node is enough, so other two nodes see existing core data from 1st node and skip migration?  I am trying to set up like this:

1. Install & start Cassandra cluster

2. Install & start Kong service on 1st Kong node.

3. Install & start Kong service concurrently on remaining 2 nodes.

Please let me know if the above set-up is feasible or not.

Thanks,

Nareen.

[Thibault Charbonnier]

Hi,

On 8/10/17 1:38 PM, Nareen M wrote:
>
> Hi,
>
> I am trying to set up 3-Kong and 3-Cassandra cluster. I've learnt that
> core migrations should not run concurrently on Kong servers. Do all
> three Kong nodes need to migrate their core? OR only one node is enough,
> so other two nodes see existing core data from 1st node and skip
> migration?

Cassandra is a distributed database, meaning that your 3 nodes should be
clustered together. Now, migrations should indeed be running from a
single node only via the CLI ('kong migrations up'), meaning that this
node will run DDL queries (CREATE TABLE, CREATE INDEX, etc...) in one of
your Cassandra nodes, and - hopefully - successfully exit. Once that
node has migrated successfully, the database schema should be propagated
to all of your 3 Cassandra nodes (Kong's migrations wait until all of
your Cassandra peers schemas are up-to-date).

You are then clear to start all of your 3 Kong nodes via 'kong start'.

-- Thibault