Which PIM Version are you working on?
We've had simular error-messages a few versions ago.
Think this is a known bug in some older versions with multiserver-architecture.
For getting more information about running jobs on the servers have you tried which entries are shown in the (clusterix) control center?
We are in version: 8.1.0.01.03.1.2.0.305.r58341.
We get this master initializer error often(once in two days). after the restart, system behaves "OK" for
couple of days.
Some exports stops, even some functions like 'serach and replace' stops with this error.
I have already checked the data grid port which is 1812, is open.
and after the restart, I have also verified the Hazzlecast members of multi server architecture.
any pointers please??
for proper analysis I recommend opening a support ticket. Chanes are that this has been fixed with 8.1.0.03 (HF3 of 8.1.0 , you are on HF1 of 8.1.0 still).
1 of 1 people found this helpful
Support case is running sice last week.
"Update on Case 02689196 Search and replace over 50 entities doesn't work. It results in error"
no solution yet. Our products are waiting in Queue without being able to be pushed to the online SHOP.
the issue happens because one server got HUNG so the timeout kicks him out of Hazelcast.
As the server is not really dead, he will return and now there are two server which like to be the "MasterJob" which is not working.
That results that nothing is working anymore.
The Cause can be any action which must be checked. As you can see in the SF case it looks like the DB connection ist lost because of any action.
Just a short note on workaround that we implemented:
Issue was between app server and DB for various reasons(indexing, fragmentation), owing to this there were loss of connections between DB and app server. Hazzlecast members looks good after restart, but in some days, the connection as mentioned is lost.
to avoid this, make the client set up inside the JOB server, run the exports that is to be run from client server. It should work.
Meanhwile, check the DB for real issues between client and DB server.