Qlik Community

Ask a Question

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
QlikWorld Online 2021, May 10-12: Our Free, Virtual, Global Event REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
aadil_madarveet
Partner
Partner

QlikSense Scheduler Master/Slave issue

Hi all,

Could someone please share some info on the below.

I have a cluster of servers with few servers configured as schedulers. The central node is set as MASTER and there are rim nodes which are configured as SLAVES.

For some reason, the failover candidate server is becoming MASTER every now and then and the central node becomes SLAVE.

The failover timeout is set at 10 mins.

Any idea when does the MASTER/SLAVE switch happen and what is the reason for this.

Thanks,
Aadil

 

4 Replies
Anonymous
Not applicable

The switch happens when the Main Central node is seen to be offline for 10 minutes. Then the failover node takes over as central node. 

If this is happening unexpectedly, you should consider opening a support ticket as something is wrong. 

 

EDL

aadil_madarveet
Partner
Partner
Author

Any Idea why this error message is appearing in the logs often.

44352 20190823T021016.726-0500 ERROR SERVERNAME System.Repository.Repository.Core.Status.HeartbeatManager 88 6d2ec2c4-e7dd-42a3-8b31-a5a517cfb07f SERVERNAME\adminuser Failed to update heartbeat for Repository service status on node SERVERNAME at Repository.Core.Repository.Common.AbstractModelRepository.CheckConflicts(IRepositoryObject persistedItem, DateTime itemModifiedDate)↵↓ at Repository.Core.Repository.Common.ModelRepository`1.UpdateMany(IEnumerable`1 items, Boolean appendPrivileges, Int64 privilegesFilter)↵↓ at Repository.Core.Repository.Common.ModelRepository`1.Update(T item, Boolean appendPrivileges, Int64 privilegesFilter)↵↓ at Repository.Core.Repository.Common.SecurityAwareRepository.RunWithElevatedOrNoSecurity[TResult](Func`1 func)↵↓ at Repository.Core.Status.HeartbeatManager.<UpdateHeartbeat>b__14_0(ISecurityAwareRepository repository) 6d2ec2c4-e7dd-42a3-8b31-a5a517cfb07f

aadil_madarveet
Partner
Partner
Author

Along with this error.

Database object has newer timestamp than object being modified; pim4: 63701831838726, itms: 63701831836996, ityp: Repository.Domain.Model.ServerNodeHeartbeat

Anonymous
Not applicable

That is this:  https://support.qlik.com/articles/000059605

Hard to say about the heartbeat item. 

 

EDL