cloud-bulldozer / cloud-bulldozer/perfscale-managed-services

Move all loops based on retries to time wait

Open
#122 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2
Forks
11
PR merge metrics
No merged PRs in 30d

Description

It is hard to calculate how many time we will wait for each loop when they are based on counting retries

Loops like:

```
for trying in range(1, 101):
[...]
logging.error("Failed to get namespace for %s on the %s cluster after 100 retries" % (cluster_name, type))
```

Can be moved to:

```
wait_time = 30 # (minutes)
starting_time = datetime.datetime.utcnow().timestamp()
while datetime.datetime.utcnow().timestamp() < starting_time + wait_time * 60:
[...]
logging.error("Waiting time expired. After %d minutes there are %d ready nodes (Expected: %d) on cluster %s" % (wait_time, ready_nodes, worker_nodes, cluster_name))
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Locate the Python loops that use retry counts, read their surrounding cluster-wait logic, and identify the intended timeout for each; done means those loops use elapsed waiting time and report the timeout and current state consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
infrastructure
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.