com.datastax.driver.core.exceptions.ProtocolError
Hi,
Greetings. Hope you are well! We have recently upgraded to Pega v8.8.2 and can see the below error in logs
|
|
An unexpected protocol error occurred on host / Proprietary information hidden:9042. This is a bug in this library, please report: Must not send frame with WARNING flag for native protocol version < 4 |
I was looking at the article https://support.pega.com/support-doc/intermittent-cassandra-40-protocol-error-sdr-321 and did add the DSS to use V4 but that is not working (may be this DSS is only for 8.4.4). I have looked at the apache-cassandra jar and it is using version 3.11.12. I have also looked at 8.8.4 and Pega Infinity '23 however these versions also do not have v4.0 of Cassandra as mentioned in the article. May i please know what might be the resolution? Regards, Bharat
Accepted Solution
Updated: 13 Nov 2023 14:15 EST
Pegasystems Inc.
GB
@KOMARINA It is unfortunate that the Resolved Issues does not clarify the fix, but according to the BUG-797626 Pega 8.8.3 with embedded Cassandra will make use of Cassandra 4.1 as the default embedded version.
Did you already try to simply upgrade Cassandra as per the article? That is what the Support Document suggests for Pega 8.8.2 users.....
External Cassandra in your deployment
You have correctly asked the question directly in the Support Document . The SME who provided details of the proposed 8.8.3 fix should answer you in that Support Document Intermittent Cassandra 4.0 protocol error [SDR-321].
Pegasystems Inc.
GB
@KOMARINA according to the Support Document you found you need to update to Pega 8.8.3 in order to run the correct version Cassandra 4.1 .
Default embedded Cassandra versions
Each Pega Platform version includes a default Cassandra version. A system update does not automatically apply the default Cassandra version to the DDS nodes; you manually update the DDS nodes to use the default Cassandra version.
Additionally, some earlier Pega Platform versions include Cassandra versions that contain a vulnerability. As a best practice, update your system to a later Pega Platform version that includes a secure Cassandra version as soon as possible.
As I was unable to find confirmation of the fix in the Resolved Issues which should have been documented under ISSUE-797626 I suggest you perform the following workaround:
1. Update to Pega 8.8.3
This is required as an update has been added which will allow for negotiating the protocol version in the Cassandra driver and override the required version.
@KOMARINA according to the Support Document you found you need to update to Pega 8.8.3 in order to run the correct version Cassandra 4.1 .
Default embedded Cassandra versions
Each Pega Platform version includes a default Cassandra version. A system update does not automatically apply the default Cassandra version to the DDS nodes; you manually update the DDS nodes to use the default Cassandra version.
Additionally, some earlier Pega Platform versions include Cassandra versions that contain a vulnerability. As a best practice, update your system to a later Pega Platform version that includes a secure Cassandra version as soon as possible.
As I was unable to find confirmation of the fix in the Resolved Issues which should have been documented under ISSUE-797626 I suggest you perform the following workaround:
1. Update to Pega 8.8.3
This is required as an update has been added which will allow for negotiating the protocol version in the Cassandra driver and override the required version.
2. Upgrade to Cassandra 4.1.1 .
Upgrade your Cassandra 4.0 version to Cassandra 4.1. Cassandra 4.1 contains a core driver that does not cause DDS operations to fail.
I will check internally if the Support Document needs to be amended to clarify the 8.8.3 Resolved Issues inclusion.
If you need further help I would suggest that you log a support incident via the MSP. Please let us know the INC ticket id so that we can help track it.
Are you using Externalized Cassandra service or Embedded Cassandra service ( in a container-based deployment in a Kubernetes environment.)?
Accenture
GB
@MarijeSchillern Thank you for this.We are using external cassandra, Cassandra version 4.0.9.
Regards,
Bharat
Accenture
GB
@MarijeSchillern Hi, Greetings. Can you please confirm if both upgrade to Pega 8.8.3 and Cassandra 4.1 should be performed? We just upgraded to 8.8.2 and is about to go-live, if we have to do another upgrade, it will be very risky from client perspective.
Regards,
Bharat
Accepted Solution
Updated: 13 Nov 2023 14:15 EST
Pegasystems Inc.
GB
@KOMARINA It is unfortunate that the Resolved Issues does not clarify the fix, but according to the BUG-797626 Pega 8.8.3 with embedded Cassandra will make use of Cassandra 4.1 as the default embedded version.
Did you already try to simply upgrade Cassandra as per the article? That is what the Support Document suggests for Pega 8.8.2 users.....
External Cassandra in your deployment
You have correctly asked the question directly in the Support Document . The SME who provided details of the proposed 8.8.3 fix should answer you in that Support Document Intermittent Cassandra 4.0 protocol error [SDR-321].
Accenture
GB
@MarijeSchillern Thank you.I have raised an incident (INC-A24139) and engineer confirmed either upgrade to Pega 8.8.3 or upgrade Cassandra to 4.1 if staying on 8.8.2. As we are about to go-live with 8.8.2 in a week, i think we will try to upgrade our Cassandra server to 4.1. I am happy for this question to be closed.
Regards,
Bharat