You can use APIs only on one of them, or create a cluster of two server nodes, embed a client in the application and use APIs there. In any case, I don't see why you need custom affinity function or even backup filter.
And your understanding of backup filter is not correct. Primary node for a partition is assigned first and backup filter does not control it in any way. The filter is then invoked when backups are assigned, providing corresponding primary that is already chosen. You can tell whether you want to use a node as a backup for that primary or not. This is usually used to make sure primary and backup are in different server racks, for example. It's not really applicable to your case. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-do-I-provide-AffinityFunction-BackupFilter-when-mainly-using-C-bindings-tp11930p12023.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
