pod should not exit if DB is unavailable #oom


Jim Hahn
 

During one of the TSC meetings, it was said that pods should:
  • exit with non-zero for permanent errors (e.g., configuration issues)
  • retry without exiting for temporary errors (e.g., cannot connect to the DB because the DB pod has not yet initialized)
I assume that's still a goal.

My question is: if JPA is used, how can a java app determine that a connectivity issue is due to the fact that the DB is not yet online vs the configuration has an incorrect URL for the DB?  Furthermore, this must be determined in an extensible and/or generic way so that it will work regardless of what DBMS an organization chooses to use in their implementation.

Join onap-discuss@lists.onap.org to automatically receive all group messages.