We recently upgraded the PI AF to 2017 SP1.
Previously it was configured as a single member collective, post upgrade we are not able to do the same.
Any one has any pointers regarding the same?
I couldn't find anything in particular related to failures of collective when upgrading to AF 2017 SP1, so would it be possible to share with us more details on what errors you are facing?
The steps to upgrade a collective are as follows: PI AF collective upgrades As you only have one machine, you would only be following the steps to upgrade your primary.
Can I inquire as to why you are using such a set up in the first place? AF collectives have several drawbacks and we now longer recommend them as a high availability option. For details see this article.
There were no errors, it just became unresponsive with no progress for more than half an hour
Wouldn't a single member collective be the same as a stand-alone server?
What you say is correct, it will be same as a stand alone server, but before the upgrade it was a single collective.
Retrieving data ...