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 reporting
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 canc
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 t
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
is
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 c
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/
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
exceptio
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
Externalizable
I have a client code that is trying to connect to the remote 3 node cluster.
The code is throwing the following exception:
SEVERE: Failed to reinitialize local partitions (preloading will be
stopped): GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion
[topVer=22, minorTopVer=0], discoEvt=D
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
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 w
"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 i
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/
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]
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&bui
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. I think this is more
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 no
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 callba
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 s
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) control.bat --activate =>
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
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: http://apache-ignite-users.70518.x
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" at
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: http://apac
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 ac
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 wa
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
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cluster/ClusterMetrics.html#getNonHeapMemoryCommi
26 matches
Mail list logo