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

SNOW-1632317: connector does not retry in certain cases where connector receives None response from the server #2030

Open
sfc-gh-aling opened this issue Aug 19, 2024 · 1 comment
Assignees
Labels
bug status-triage_done Initial triage done, will be further handled by the driver team

Comments

@sfc-gh-aling
Copy link
Collaborator

sfc-gh-aling commented Aug 19, 2024

Python version

any

Operating system and processor architecture

any

Installed packages

snowflake-connector-python

What did you do?

server sometimes send back http response with None, leading to the connector raises UnknownError, this could happen at any http requests

What did you expect to see?

retry upon None without any side effect

Can you set logging to DEBUG and collect the logs?

import logging
import os

for logger_name in ('snowflake.connector',):
    logger = logging.getLogger(logger_name)
    logger.setLevel(logging.DEBUG)
    ch = logging.StreamHandler()
    ch.setLevel(logging.DEBUG)
    ch.setFormatter(logging.Formatter('%(asctime)s - %(threadName)s %(filename)s:%(lineno)d - %(funcName)s() - %(levelname)s - %(message)s'))
    logger.addHandler(ch)

more context

in the PR SNOW-1562604: enhance error handling when polling query result by sfc-gh-aling · Pull Request #2027 · snowflakedb/snowflake-connector-python we enhanced retry on handling 499 error (client receiving None response) when polling long running query result.

there are more get/post requests in the connector which need similar enhancement, but they also need more tests.

@github-actions github-actions bot changed the title connector does not retry in certain cases where connector receives None response from the server SNOW-1632317: connector does not retry in certain cases where connector receives None response from the server Aug 19, 2024
@sfc-gh-dszmolka
Copy link
Contributor

sfc-gh-dszmolka commented Aug 26, 2024

(looks to be an internal tracking issue)

@sfc-gh-dszmolka sfc-gh-dszmolka added status-triage_done Initial triage done, will be further handled by the driver team and removed needs triage labels Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

2 participants