Hello. I'm not using config file I'm using java code to configure :
@Produces
@ApplicationScoped
public Ignite produceInstance() {
LOG.info("** Prepare Ignite ");
IgniteConfiguration config = new IgniteConfiguration();
config.setClientMode(false);
Gotcha
This is this part :
TcpDiscoverySpi discoverySpi=new TcpDiscoverySpi();
TcpDiscoveryJdbcIpFinder ipFinder=new TcpDiscoveryJdbcIpFinder();
ipFinder.setDataSource(dataSource);
discoverySpi.setIpFinder(ipFinder);
Hello,
In hazelcast we can persist Queues in Database, this help me for example when
consumer are down to no have OOM exception.
But I don't see this possibility in Ignite docs ?
This message and any attachments (the "message") is
intended solely for the intended addressees and is
Hy Yann,
My guess it is that TcpDiscoveryJdbcIpFinder hangs on an attempt to
connect to the data source provided in its configuration. Probably your
DB is not reachable from the Ignite node or it generates an error that
is not forwarded to Ignite.
In any case a threads dump knows the answer
Hi there,
I have an application where I need to share some data between all nodes, so
we created a cluster with REPLICATED caches, so far so good.
There are other pieces of data that we need to use that we don't need/want
to keep local, so we are trying to setup a different cluster and let the
Hello, me ; again...
I continue to replace Hazelcast by ignite in my code.
I have to use Queues, and sometime, tere some things I don't understand in the
Ignite code.
Well, In my case, I have multiple objects to push in Queues.
Each of its have its own Queues.But this object are "primary keys"
Hi Daniel,
It's easy to support your use case if to configure multicast [1] or
static IP finders in a particular way.
Please refer to these discussions happened earlier:
http://apache-ignite-users.70518.x6.nabble.com/How-keep-separate-different-grid-instances-on-the-same-network-td1609.html
Hi,
This seems to be an interesting functionality. As I understand you're
referring to [1].
Personally I think that it makes sense to support the same in Ignite.
However I would just extend CollectionConfiguration adding ability to
set an eviction policy and enable swap on demand. When
I was loading data from AWS Redshift into Ignite through the loadcache API.
cache.loadCache(null, "java.lang.Integer", "select * from lineorder where
lo_orderdate > 19970101");
I ran this from a single client. The query basically ran on all the nodes.
I had 1 client and 2 servers and the same
Hi Murthy,
Swap space allows to write evicted data to disc to avoid out of memory.
This is not persistence, because this data will be lost if the node leaves
topology. For caches persistence can be implemented with the help of
CacheStore interface [1]. For queues and sets it's not possible now, I
Paulo,
The issue has been fixed and the fix was merged to master. You should be
able to cherry-pick the commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 and
build Ignite from sources with this fix.
11 matches
Mail list logo
