Ignite 2.0 C++ Segfault

The following segfault happens in multi-threaded ignite c++ application: C [test+0xf8116a] std::less::operator()(int const&, int const&) const+0x14 C [test+0x1106305] std::_Rb_tree, std::_Select1st >, std::less, std::allocator >

Re: How do I provide AffinityFunction.BackupFilter when mainly using C++ bindings

It is not applicable because it will require too much effort to convert the rest of the system for ACTIVE/ACTIVE set-up. On Thu, Apr 13, 2017 at 5:10 PM vkulichenko wrote: > Why not create two equal C++ nodes and use both of them? You will give you > data

Re: How do I provide AffinityFunction.BackupFilter when mainly using C++ bindings

wrote: > Well, there is a way to get C++ nodes. You can use the following code for > this: > > IgniteCluster#forAttribute("org.apache.ignite.platform", "cpp"); > > That returns you a cluster group of C++ nodes if that's what you need. > > Best Regards,

Re: How do I provide AffinityFunction.BackupFilter when mainly using C++ bindings

I have managed to put a AffinityFunction implementation in ./libs and load/use it. But I still could not figure out how to detect my C++ node. I see C++ API allows you to name my node via *Ignition::Start(const IgniteConfiguration , const char *name)* but ClusterNode

Re: How do I provide AffinityFunction.BackupFilter when mainly using C++ bindings

I am trying to create an ACTIVE/PASSIVE redundant environment, passive node being the vanilla .sh node. I would like to have control on what node is appointed as primary. According to what you are saying, for a moment I have to have only one node (that being C++ node) online for it to be primary

How do I provide AffinityFunction.BackupFilter when mainly using C++ bindings

Hello, I am in a similar situation with the following unanswered SO question: http://stackoverflow.com/questions/43386765/how-do-i-provide-affinityfunction-backupfilter-when-mainly-using-c-bindings How can I achieve this? Quoting the question: I am using the C++ bindings to have redundancy in