Re: Strange cluster activation behaviour in ignite 2.4.0

yes, everything is clear now thanks! On Thu, Apr 26, 2018 at 2:05 PM, slava.koptilin wrote: > Hi, > > 1) start 2 server nodes > ^ the cluster was started at the first time. There was no baseline > topology yet. > > 2) control.bat --state => Cluster is inactive > 3)

Re: Which ports does ignite cluster need to run normally?

Hi, The configuration is fine and it does eliminate ranges so that node always binds to 47500. The only drawback is that if 47500 is not available for whatever reason, node would not start. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteDataStreamer.flush() returns before all futures are completed

"Could you please refine what kind of flaw do you suspect? " I think the basic flaw is that it is unclear how to write a simple task to stream in some data, and then confirm that all of that data was successfully stored before taking an action to record that. This may be simply a documentation

RE: Using a cache as an affinity co-located processing buffer in Ignite.Net

Raymond, If you want to have a single continuous query on one of the server nodes, then I think singleton service is the best option to achieve that. It will not only guarantee that there is one query at a time, but will also make sure to redeploy it in case of failure. Also I would be accurate

Re: Using a cache as an affinity co-located processing buffer in Ignite.Net

Val, What I really want is a .Net implementation of the Ignite distributed queue, assuming co-located server processing can pull members off the queue that are co-located with that node (yeah, that's probably mangling queue semantics a bit, but not that badly :) ) I have previously made a POC

RE: Using a cache as an affinity co-located processing buffer in Ignite.Net

Val, Thanks for the feedback. Essentially what I really want in Ignite.Net version of the Ignite distributed Queue with local consumers on each server reading and processing just the elements that server is responsible for (which may be a slight mangling of queue semantics...) I have written a

Re: Apache Ignite nightly release builds

Hi, Igniters! Some more news about Apache Ignite Nightly build: - added docker image in form of compressed image tar.gz archive; - added DEB and RPM packages. All latest artifacts as always available here: [1] Enjoy! [1]

Re: IgniteDataStreamer.flush() returns before all futures are completed

David, I believe that flush() should throw an exception if any of the futures has been completed with error. You can also call fut.get() after assert isDone(); In this case get() should return immediately. --Yakov 2018-04-26 16:37 GMT+03:00 David Harvey : > Thanks Yakov.

Re: Which ports does ignite cluster need to run normally?

Thanks Val one more question on this if I want to minimize number of potentially-used ports (because of our security guys) is it ok to have configuration like below one? here we have 3 server nodes each running on separate server, they always use the same 47500 port - no ranges As I understood

Strange cluster activation behaviour in ignite 2.4.0

Hi Igniters, I observe strange cluster activation behaviour in ignite 2.4.0 1) start 2 server nodes 2) control.bat --state => Cluster is inactive 3) control.bat --activate => Cluster activated 4) stop both nodes 5) start them again 6) control.bat --state => Cluster is active Q: why my cluster

Re: Strange cluster activation behaviour in ignite 2.4.0

Hello Oleks, The cluster can be automatically activated once all the nodes of the baseline topology have joined after a cluster restart. This is expected behaviour. [1] https://apacheignite.readme.io/docs/cluster-activation#section-automatic-activation Thanks, Slava. -- Sent from:

Re: What does "Non heap" mean in the log?

Hi, It's non-heap memory that can be used for JVM memory management. You can read about this here: https://docs.oracle.com/javase/7/docs/api/java/lang/management/MemoryUsage.html

Re: Strange cluster activation behaviour in ignite 2.4.0

Silly question, do you have native persistence enabled ? Mikael Den 2018-04-26 kl. 11:14, skrev Olexandr K: Hi Igniters, I observe strange cluster activation behaviour in ignite 2.4.0 1) start 2 server nodes 2) control.bat --state => Cluster is inactive 3) control.bat --activate => Cluster

RE: Service isn't initialized on cluster re-activation

Hi, Regarding service redeployment on reactivation – that’s https://issues.apache.org/jira/browse/IGNITE-8205, already fixed in the master branch, will be in 2.6. Regarding executing cancel() in the exchange thread – agree, that doesn’t seem right. I guess currently we just run init() and

Ignite Node failure - Node out of topology (SEGMENTED)

Hi, We are running apache ignite (v2.3) in embedded mode in a java based application with 9 node cluster in our production environment in AWS cloud infrastructure. Most of the time, we don't see any issue with node communication failure, but occasionally we find one of the node failure

Re: Client node error: org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to initialize DB connection: jdbc:h2:mem...

I found what the problem was. I'm using Ignite v 2.3.0 which is compatible with H2 v 1.4.195. However, I had H2 v 1.4.197 dependency in my pom.xml. Strange that H2 is not backward compatible within the same main version. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Service isn't initialized on cluster re-activation

Hi, I was doing some testing where I had some services deployed, then deactivated the cluster, then re-activated the cluster. I was expecting that the services would have their init and execute methods called again, but this did not happen. If I proceed to shutdown a node then the cancel method

Node failure handling semantics

Hi, I was wondering if there is any additional documentation on how Ignite internally handles node failures? The section in the documentation kind of skims over this too quickly[1]. I specifically have the following inquiries: 1) Does each node in the ring send heartbeats to all other nodes in

Re: Strange cluster activation behaviour in ignite 2.4.0

but I didn't setup baseline topology doc says: "To form the baseline topology from a set of nodes, use the ./control.sh --baseline set command along with a list of the nodes' consist ent IDs:" is it auto-resolving after first cluster activation and we don't need to use "control.bat --baseline"

Re: Strange cluster activation behaviour in ignite 2.4.0

Hi, 1) start 2 server nodes ^ the cluster was started at the first time. There was no baseline topology yet. 2) control.bat --state => Cluster is inactive 3) control.bat --activate => Cluster activated ^ the first activation of the cluster, it forms baseline topology 4) stop both nodes

Re: Cache metrics

Hello Sam, Yes, you can clear local cache's metrics. For instance, it can be done via JMX Bean org.apache:clsLdr=,group=default,name="org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl", just call clear() method. Thanks! -- Sent from:

Re: cache keys comparision

Hello, If an object can be serialized into a binary form, then Ignite will calculate its hash code during serialization and write it to the resulting binary array. Also, Ignite provides a custom implementation of the equals method for the binary object's comparison needs. This means that you do

Re: IgniteDataStreamer.flush() returns before all futures are completed

Hi, David, As far as a can see from streamer implementation, flush() call 1. won't return until all futures returned by addData() are (successfully) finished 2. will throw an exception if at least one future has been failed. Could you please refine what kind of flaw do you suspect? As for

Re: IgniteDataStreamer.flush() returns before all futures are completed

Thanks Yakov. I think this is more subtle. Our loading via IgniteDatastreamer is idempotent, but this depends on being certain that a batch of work has successfully completed. It is *not* sufficient for us to listen to the futures returned by addData, then to call flush(), and then to record

Re: Effective Data through DataStream

When you set the stream receiver, an instance of its class is created and serialized, which will also include any class it is nested in. On each Data Streamer buffer, the serialized form of that class is sent. If the class containing the stream receiver has a pointer that is not

Re: IgniteDataStreamer.flush() returns before all futures are completed

Thanks, David. I've created a ticket [1] to update javadoc for flush(). Behavior you describe looks rather natural. flush() should not track all previously completed add operations. So, one of the possible ways to ensure all data were added is to check whether flush() finishes without an