[yugabyted] Issue with KONG gateway

[bugrakeskin]

Jira Link: DB-9393

Description

Hey guys,
i have an issue with kong & yugabytedb. I did the installation like below. Everything seems to work fine but i get errors in kong;

Here is the kong error:

> Error Logs:

2023/12/28 11:23:58 [error] 1278#0: *152 [lua] init.lua:253: invalidate(): [DB cache] failed to broadcast cached entity invalidation: could not insert invalidation row: ERROR: System column "ctid" is not supported yet, context: ngx.timer
2023/12/28 11:23:58 [error] 1278#0: *152 [lua] events.lua:54: failed broadcasting target create to cluster: could not insert invalidation row: ERROR: System column "ctid" is not supported yet, context: ngx.timer

> Warn logs:

2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'cluster_events' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer
2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'clustering_data_planes' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer
2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'acme_storage' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer
2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'keyauth_credentials' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer
2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'oauth2_authorization_codes' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer
2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'oauth2_tokens' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer
2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'ratelimiting_metrics' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer
2023/12/28 11:29:51 [warn] 1278#0: *160 [lua] connector.lua:364: unable to clean expired rows from table 'sessions' on PostgreSQL database (ERROR: System column "ctid" is not supported yet), context: ngx.timer

Here is my KONG installation:

first i run migration script

docker run --rm --network=kong-net \
  -e "KONG_PG_HOST=internal_ip_adress \
  -e "KONG_PG_PORT=5433" \
  -e "KONG_DATABASE=postgres"         \
  -e "KONG_PG_PASSWORD=password"      \
  -e "KONG_PASSWORD=password"         \
  -e "KONG_PG_USER=yugabyte"         \
 kong:latest kong migrations bootstrap

Docker compose kong with konga

version: '3'
services:

  kong:
    image: kong:latest
    container_name: kong
    environment:
        LC_CTYPE: en_US.UTF-8
        LC_ALL: en_US.UTF-8
        KONG_DATABASE: "${KONG_DATABASE}"
        KONG_PG_HOST:  "${KONG_PG_HOST}"
        KONG_PG_PORT: "${KONG_PG_PORT}"
        KONG_PG_USER: "${KONG_PG_USER}"
        KONG_PG_PASSWORD: "${KONG_PG_PASSWORD}"        
        KONG_CASSANDRA_CONTACT_POINTS: kong
        KONG_PROXY_ACCESS_LOG: /dev/stdout
        KONG_ADMIN_ACCESS_LOG: /dev/stdout
        KONG_PROXY_ERROR_LOG: /dev/stderr
        KONG_ADMIN_ERROR_LOG: /dev/stderr
        KONG_ADMIN_LISTEN: 0.0.0.0:8001, 0.0.0.0:8444 ssl
       
    restart: on-failure
    ports:
      - '80:8000'
      - '443:8443'
      - '8001:8001'
      - '8444:8444'

  konga:
    image: pantsel/konga
    ports:
      - '1337:1337'
    links:
      - 'kong:kong'
    container_name: konga
    environment:
      - NODE_ENV=production

networks:
  default:
    name: kong-net
    external: true

Yugabyte Installation 3 nodes

./yugabyte-2.19.3.0/bin/yugabyted start --advertise_address 172.20.60.101 --base_dir=$HOME/yugabyte/node1 
./yugabyte-2.19.3.0/bin/yugabyted start --advertise_address 172.20.60.102 --join 172.20.60.101 --base_dir=$HOME/yugabyte/node2
./yugabyte-2.19.3.0/bin/yugabyted start --advertise_address 172.20.60.103 --join 172.20.60.101 --base_dir=$HOME/yugabyte/node3

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.

[ddorian]

See answer https://stackoverflow.com/questions/74093448/ctid-is-not-supported-yet-in-yugabytedb.

ctid is a system column of the default PostgreSQL storage engine, and shouldn't be relied upon.

Can you open an issue on kong why they're using ctid?