Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Pavan PBPavan PBReporter
Amit KulkarniAmit KulkarniIs this a Regression?
UnknownTriage
TriagedStory Points
1Priority
MajorInstabug
Open Instabug
Details
Details
Assignee
Pavan PB
Pavan PBReporter
Amit Kulkarni
Amit KulkarniIs this a Regression?
Unknown
Triage
Triaged
Story Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created May 2, 2022 at 7:37 AM
Updated May 5, 2022 at 4:08 PM
Resolved May 3, 2022 at 2:47 PM
ALTER INDEX `travel-sample`.country_idx
WITH {"action": "replica_count", "num_replica": 2, "nodes": ["127.0.0.1:9001", "127.0.0.1:9002", "127.0.0.1:9003"]}
Will fail when encryption is enabled.
The issues was introduced where we started supporting the use of encrypted ports from the query. We were only using un encrypted port numbers always.
The design is to support
only un encrypted port numbers when encryption was disabled
both un-encrypted and encrypted port numbers when encryption was set to all
only encrypted port numbers when encryption was strict
But after the change only encrypted ports are working in encryption mode all which breaks backwards compatibility.