-
Notifications
You must be signed in to change notification settings - Fork 471
TLS change in 20.1 Go version can break clients #7258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Oops. Looks like our internal testing is all on jdk 8 (or insecure mode). And the java patch releases that fix the problem are only a couple of weeks old. So this is going to affect most java users. Suggested docs (java users may want to tweak the language around "java" vs "openjdk"): CockroachDB 20.1 is incompatible with some releases of Java, including OpenJDK 11 versions older than 11.0.7 and OpenJDK 13 versions older than 13.0.3. The recommended solution is to upgrade to the latest JDK release in a given branch. If that is not possible, two workarounds are available:
|
In cockroachdb/cockroach#48294 we are discussing making a change in the first 20.1 patch release that would remedy this incompatibility by disabling TLS 1.3 by default. |
We've decided to disable TLS 1.3 in 20.1.0 instead of waiting for the first patch release, so we don't need to document anything here. |
@bdarnell, does that mean we're releasing another rc? |
I'm not sure if we're doing to do another RC or if we're just slipping this change into the final release. CC @dt |
just slipping it into v20.1.0 -- email coming shortly once the build finishes. |
@timveil tried upgrading his CC cluster to 20.1, and his app (java + spring boot deployed in GKE) crashed with the following error:
@vladdy identified the likely cause as:
And suggested this might have something to do with TLS change in the Go version we're using: https://golang.org/doc/go1.13#tls_1_3
golang/go#35722
We need to document this a 20.1 backward-incompatible change. The workaround in the Go issue might be what we need.
The text was updated successfully, but these errors were encountered: