abrarfahim
RRunPod
•Created by abrarfahim on 5/26/2024 in #⚡｜serverless
Is there any limit on how many environment variables can be added per container?
I solved it by some of the envs load as json from env.
11 replies
RRunPod
•Created by abrarfahim on 5/26/2024 in #⚡｜serverless
Is there any limit on how many environment variables can be added per container?
Any other approach to bypass it?
11 replies
RRunPod
•Created by abrarfahim on 5/26/2024 in #⚡｜serverless
Is there any limit on how many environment variables can be added per container?
i have 20 envs now
11 replies
RRunPod
•Created by abrarfahim on 5/26/2024 in #⚡｜serverless
Is there any limit on how many environment variables can be added per container?
11 replies
RRunPod
•Created by abrarfahim on 5/21/2024 in #⚡｜serverless
How do i retry worker task in runpod serverless?
Let them make their decisions and opinions. Thank u for your time.
8 replies
RRunPod
•Created by abrarfahim on 5/21/2024 in #⚡｜serverless
How do i retry worker task in runpod serverless?
What is the max retry count in that case? Any documentation regarding these informations?
8 replies
RRunPod
•Created by abrarfahim on 5/21/2024 in #⚡｜serverless
How do i retry worker task in runpod serverless?
Implementing a retry mechanism is crucial for handling failures when interacting with external systems. Directly coding retries can be complex and messy. Instead, a queue-based retry system offers a cleaner and more maintainable solution. Message bus systems like Kafka, RabbitMQ, and AWS SQS manage retries by re-queuing failed messages, allowing for efficient and modular handling of retries. This approach improves system reliability and scalability while keeping the core application code clean.
I think exposing an http endpoint for worker is that how created the ambiguity of not offering a retry mechanism.As a customer I would highly appreciate it.
8 replies