Skip to content

adding startupTimeout#13

Open
Amalraj-Joseph-IBM wants to merge 2 commits intomainfrom
adding-startupTimeout
Open

adding startupTimeout#13
Amalraj-Joseph-IBM wants to merge 2 commits intomainfrom
adding-startupTimeout

Conversation

@Amalraj-Joseph-IBM
Copy link

@Amalraj-Joseph-IBM Amalraj-Joseph-IBM commented Jan 9, 2026

Adding MP Health startupTimeout parameter to reduce intermittent application startup failures

#12

@paulben
Copy link

paulben commented Jan 14, 2026

@Amalraj-Joseph-IBM the doc says the default is 500 seconds, and 30 is the minimum allowed. Do we really want the minimum here?

@Amalraj-Joseph-IBM
Copy link
Author

@paulben @jgawor @reshmismenon @thasnim-fluxone

Sorry, I am missing something here. I thought the default value was something lower. If the default is 500, how would the app startup time out? Does the sample app take more than 8 minutes to start up? When running it locally, I felt like it started within a few seconds, so I thought 30 seconds would be reasonable.

So, if the mpHealth feature defaults the startup timeout to 500 seconds, it means the app is failing to start even after 8 minutes.
I think we need to find out why that is happening, if that is the case.
Increasing the timeout further could help us reduce the occurrence of this failure, but I think it would be like covering up a performance issue (which could not be caused by mpHealth, as we have been seeing this for a long time) by increasing the wait time—because most of the time, the app doesn’t take that long.

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

Successfully merging this pull request may close these issues.

2 participants