Change Details

This behaviour is seen in production. **Ticket Related to O 6 KR 1** We have 2 instances of ksqldb running but when a client connects, within a short period of time, all is connections are going to the same ksqldb instance. **How to replicate** * Scale ksqldb to 2 instances * connect to realtime API with multiple clients. **Acceptance Criteria** * Agree on solution. * Implement and test in DEV. **Developer Notes** * DNS resolution in same order due to quick dns lookups, skip the dns balancing. We should resolve the dns before connecting. The dial will use the sequencialDial to connect.

This behaviour is seen in production. **Ticket Related to O 6 KR 1** We have 2 instances of ksqldb running but when a client connects, within a short period of time, all is connections are going to the same ksqldb instance. **How to replicate** * Scale ksqldb to 2 instances * connect to realtime API with multiple clients. **Acceptance Criteria** * Agree on solution. * Implement and test in DEV. **Developer Notes** * DNS resolution in same order due to quick dns lookups, skip the dns balancing. We should resolve the dns before connecting. The dial will use the sequencialDial to connect. **RFC** Refer to `RfC-realtime-reconnection-delay`

This behaviour is seen in production. **Ticket Related to O 6 KR 1** We have 2 instances of ksqldb running but when a client connects, within a short period of time, all is connections are going to the same ksqldb instance. **How to replicate** * Scale ksqldb to 2 instances * connect to realtime API with multiple clients. **Acceptance Criteria** * Agree on solution. * Implement and test in DEV. **Developer Notes** * DNS resolution in same order due to quick dns lookups, skip the dns balancing. We should resolve the dns before connecting. The dial will use the sequencialDial to connect. **RFC** Refer to `RfC-realtime-reconnection-delay`