---
** [tickets:#2559] imm: change log level to warning on ERR_TRY_AGAIN in PBE**
**Status:** accepted
**Milestone:** 5.17.10
**Created:** Thu Aug 17, 2017 12:45 PM UTC by Zoran Milinkovic
**Last Updated:** Thu Aug 17, 2017 12:45 PM UTC
**Owner:** Zoran Milinkovic
In ticket #2491, the added block
~~~
> + if (errorCode != SA_AIS_ERR_NOT_EXIST
> + && errorCode != SA_AIS_ERR_INVALID_PARAM) {
> + LOG_ER("Failed to get class description for class '%s' from imm "
> + "with error=%d, exiting",
> + classNameString.c_str(), errorCode);
> + exit(1);
> + }
~~~
is too strict and log error messages even for ERR_TRY_AGAIN.
ERR_TRY_AGAIN is very common to get if the cluster goes headless. Then if the
switchover is very quick and is done before IMMD goes down, PBE can start
regenerating the database on the new elected IMM coordinator node, and receive
ERR_TRY_AGAIN.
For ERR_TRY_AGAIN in this case, the log level should be reduced from error to
warning level.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
