Skip to content
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

too many tgs_req from jdbc (for kerberos) #414

Open
lurnagao-dahua opened this issue Dec 17, 2022 · 0 comments
Open

too many tgs_req from jdbc (for kerberos) #414

lurnagao-dahua opened this issue Dec 17, 2022 · 0 comments

Comments

@lurnagao-dahua
Copy link

lurnagao-dahua commented Dec 17, 2022

Hi !
I have a question in trino/prestodb, so i was wondering if openlookeng has this problem?

In function StatementClientV1#advance, each call to the JsonResponse.execute(QUERY_RESULTS_CODEC, httpClient, request) will sends a tgs_req to kdc :

while (true) {
    if (isClientAborted()) {
        return false;
    }
    ...
    JsonResponse<QueryResults> response;
    try {
        response = JsonResponse.execute(QUERY_RESULTS_CODEC, httpClient, request);
    }
    catch (RuntimeException e) {
        cause = e;
        continue;
    }
    ...
}

The function statementClientV1#advance is getting results from coordinator.

Sounds like there is no service ticket cache so the client does the auth everytime.

Thank you very much for the answer!

@lurnagao-dahua lurnagao-dahua changed the title will jdbc cache kerberos service ticket to reduce kdc pressure? too many tgs_req from jdbc in trino/prestodb Dec 21, 2022
@lurnagao-dahua lurnagao-dahua changed the title too many tgs_req from jdbc in trino/prestodb too many tgs_req from jdbc (for kerberos) Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant