hazelcast / hazelcast/hazelcast-python-client

Feature Request: Ability to control request timeout > 120 seconds

Ouverte
#116 4 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Estimation: XL Priority: Low Source: Community Type: Enhancement
Langage dominant
Python
Étoiles
116
Forks
78
Merge moyen
10 j 22 h
PR mergées (30 j)
1

Description

Currently, if any request takes longer than 120 seconds, the following exception gets raised:
> TimeoutError: Request timed out after 120 seconds.

This appears to be controlled by the `invocation.INVOCATION_TIMEOUT` constant and does not appear tunable. I see that the constructor for `Invocation` takes in a `timeout` parameter that defaults to that constant value, but as far as I can tell there's no way to get a timeout actually passed-in to the `Invocation` object since that's all handled under-the-hood when the client is configured.

I would love it if I could control the timeout on a per-request basis.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start with the invocation.INVOCATION_TIMEOUT constant and the Invocation constructor's timeout parameter, then trace how client configuration creates Invocation objects. Identify the request entry point where a per-request timeout could be supplied. Done means callers can control the timeout for an individual request rather than being limited to 120 seconds.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python
Domaine
api
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.