Versions Compared

Old Version 16

changes.mady.by.user Alberto Bustamante Reyes

Saved on

compared with

New Version 17

changes.mady.by.user Alberto Bustamante Reyes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

After checking with the dev mailing list, we received the suggestion to configure serverAffinity in Kubernetes to solve the issue with the pings, but that option broke the failover of gw senders when a gw receiver is down.

FAQ

TBD

Errata

N/A

Annex: testExecuteOp failing

After our changes we have been stuck trying to solve testExecuteOp from ConnectionPoolImplJUnitTest. The test hangs when executing an operation that has been implemented to throw an exception. Instead of trying to execute the operation on both servers, we have seen it tries continuously to execute it on the same server.

The problem is in handshakeWithServer function at ClientSideHandshakeImpl class. We have seen that after the operation fails on the first server, and it is going to be executed on the second server,  at this line:

...

The variable contains the member id of the second server, but readServerMember return the id of the first server, so finally the operations is executed on that server again.