[general] pass4SymmKey = xxxxxxxxxx serverName = xxxxxxxxxx site = site4 [clustering] available_sites = site4,site2 mode = master multisite = true pass4SymmKey = xxxxxxxxxxxxxx site_replication_factor = origin:1,site2:2,site4:2,total:5 site_search_factor = origin:1,site2:2,site4:2,total:5 INDEXER [general] pass4SymmKey = xxxxxx serverName = xxxxxxx site = site4 [clustering] master_uri = xxxxxxxx mode = slave pass4SymmKey = xxxxxxx Search head [general] pass4SymmKey = xxxxxxxx serverName = xxxxxxxx site = site4 sessionTimeout = 8h [clustering] master_uri = xxxxxxx mode = searchhead multisite = true pass4SymmKey = xxxxx As you can see - nothing unusual ... View more

Wow - my mistake. I don't know how I can miss that. Sorry for bothering you ! ... View more

Hello due to same problem I don't want to create new topic. In log I found ERROR DistributedPeerManagerHeartbeat - A time skew of approximately 1396 seconds exists between this search head and peer1 ERROR DistributedPeerManagerHeartbeat - A time skew of approximately 1909 seconds exists between this search head and peer2 But. When I check date I found that date is correct. 00:25:07 CEST on peer and 00:25:08 CEST on cluster master I have All Data is Searchable Search Factor is Met Replication Factor is Not Met. Settings in server.conf are: site_replication_factor = origin:1,site2:2,site4:2,total:4 site_search_factor = origin:1,site2:1,site4:1,total:2 We have 4 peers (showing under Indexer Clustering: Master Node) and 2 search (3 if we counting CM) and as you can see above - search factory is met (after a while) but replication factor is not. I also don't know what can happened if we have replication factor not met? Ohh and one more importaint thing - this cause after we switch from single-site to multisite. Should I add in [clustering] replication_factor = 2 and search_factor = 1 to aviod replication factor not met ? Thanks for any advice 😉 ... View more