Skip to content

Documentation: Update the MySQL Hive Metastore configuration docs#1514

Merged
openshift-merge-robot merged 1 commit intokube-reporting:masterfrom
timflannagan:update-mysql-metastore-documentation
Feb 22, 2021
Merged

Documentation: Update the MySQL Hive Metastore configuration docs#1514
openshift-merge-robot merged 1 commit intokube-reporting:masterfrom
timflannagan:update-mysql-metastore-documentation

Conversation

@timflannagan
Copy link
Copy Markdown
Contributor

After updating the MySQL connector/J JDBC driver version in the Hive
image, we're now seeing problems with running newer versions of Metering
with older MySQL server versions (e.g. 5.6, 5.7). When diving into the
MySQL Pod logs, we may see the "[NOTE] Bad handshake" message logged,
which may indicate we're attempting to authenticate from the client
using TLS 1.2 or TLS 1.3 during the handshake. This is likely because
earlier MySQL server versions only support TLS 1.1 versions and earlier,
so we need to explicitly document this behavior.

@openshift-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: timflannagan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 18, 2021
@timflannagan timflannagan force-pushed the update-mysql-metastore-documentation branch from f24b8f6 to 95f5145 Compare February 18, 2021 19:25
After updating the MySQL connector/J JDBC driver version in the Hive
image, we're now seeing problems with running newer versions of Metering
with older MySQL server versions (e.g. 5.6, 5.7). When diving into the
MySQL Pod logs, we may see the `"[NOTE] Bad handshake"` message logged,
which may indicate we're attempting to authenticate from the client
using TLS 1.2 or TLS 1.3 during the handshake. This is likely because
earlier MySQL server versions only support TLS 1.1 versions and earlier,
so we need to explicitly document this behavior.
@timflannagan timflannagan force-pushed the update-mysql-metastore-documentation branch from 95f5145 to f78e874 Compare February 18, 2021 19:26
@timflannagan
Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.7

@openshift-cherrypick-robot
Copy link
Copy Markdown

@timflannagan: once the present PR merges, I will cherry-pick it on top of release-4.7 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@timflannagan timflannagan added the lgtm Indicates that a PR is ready to be merged. label Feb 22, 2021
@openshift-merge-robot openshift-merge-robot merged commit 753c5e8 into kube-reporting:master Feb 22, 2021
@openshift-cherrypick-robot
Copy link
Copy Markdown

@timflannagan: new pull request created: #1516

Details

In response to this:

/cherry-pick release-4.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants