RE: [External]Re: Segregating Ignite client discovery and heartbeat exchange on different networks

Thanks Alex. Actually, I don't want to start two different clusters on same machine, rather am looking to have a different networks for Ignite clients discovery and internal communication. Not sure whether we can achieve this using below. Thanks and Regards, Kamlesh Joshi -Original

Re: About Ignite Thin client performance

Hello. I saw the document in Wiki that logic has been improved. https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients#IEP23:BestEffortAffinityforthinclients-Tickets -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: About Ignite Thin client performance

Hello, I saw a document Wiki that logic has been improved. https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients#IEP23:BestEffortAffinityforthinclients-Tickets -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: ignite load Cache and cluster warm up

Hi, - loadCache has to be called only after cluster have reached a minimum amount of nodes (currently 3 nodes) You can use events to see when nodes join, or use the cluster api to see how many servers/clients are online, and then call loadCache() cluster api:

Re: Segregating Ignite client discovery and heartbeat exchange on different networks

Hi, An example of isolated cluster is provided here: https://apacheignite.readme.io/docs/tcpip-discovery#isolated-ignite-clusters-on-same-set-of-machines You can try binding specific IPs to a different networks use: CommunicationSpi:

Re: Zookeeper discovery in mix environments.

It is possible. All discovery communication is through ZooKeeper, but yes private docker IPs (172.. ) might be leaked over. Would need to see the full logs(Ignite and Zookeper) which contain the IPs of the node and the particular one used for a given communication. Try running docker w/--net=host

ignite load Cache and cluster warm up

Hi everyone, I'm developing an application with apache ignite and I'm looking for some help I have an ignite cluster deployment on k8s, currently 3 server nodes and 2 client nodes I'm using a custom implementation of Ignite CacheStore in order to have a database backup of cache data The only

Re: Zookeeper discovery in mix environments.

So, I'm guessing that the client node reports multiple I.Ps to the zookeeper so then when another node tries to connect to the client node to create the full mesh maybe it connecting to the wrong I.P? On Mon, 1 Jun 2020 at 11:26, akorensh wrote: > Hi, >ZookeperDiscoverySpi > < >

Re: Can Apache Superset connect with Apache Ignite ?

Hi, Superset uses SqlAlchemy supporting the JDBC driver, so technically it should be possible to connect to Ignite. Here is the information on jdbc driver: https://apacheignite-sql.readme.io/docs/jdbc-driver and on some tools: https://apacheignite-sql.readme.io/docs/sql-tooling Please let us

Re: Zookeeper discovery in mix environments.

Hi, ZookeperDiscoverySpi uses ZooKeeper to transmit discovery messages. You can specify a comma separated host:port pairs, each corresponding to a zooKeeper server here:

Segregating Ignite client discovery and heartbeat exchange on different networks

Hi Igniters, Is there any way, we can separate out Ignite client discovery and cluster internal communication (heart beat exchange and PME) on two different networks (may be by using 2 Ethernet cards) ? Currently, we are using TcpDiscoveryVmIpFinder. Thanks and Regards, Kamlesh Joshi

Re: Zookeeper discovery in mix environments.

Maybe you would ask the question on VM/container related mailing list? Regards On Mon, Jun 1, 2020 at 9:32 PM John Smith wrote: > Any news on this? Thanks > > > On Thu., May 28, 2020, 1:10 p.m. John Smith, > wrote: > >> Hi, I'm running an ignite cluster on VMs running on Openstack and using

Re: Zookeeper discovery in mix environments.

Any news on this? Thanks On Thu., May 28, 2020, 1:10 p.m. John Smith, wrote: > Hi, I'm running an ignite cluster on VMs running on Openstack and using > regular network stack nothing special here. > > My CLIENT (client=true) applications are running in DC/OS using docker > container in bridged

Can Apache Superset connect with Apache Ignite ?

as the topic ,apache superset can connect the database from ignite ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Building Ignite 2.8.1 using open jdk

Any compliant JDK should work. Lots of people use OpenJDK. > On 30 May 2020, at 10:02, Debdatta Bhattacharjee > wrote: > >  > Thanks a lot Stephan! Just to confirm when you say JDK, you mean OpenJDK as > well, right? I can build it on Oracle JDK 8, b it can run on Oracle JDK 11 or > Open