Hello,
We are facing a critical issue with Ignite 2.8.
We have two machines in same location running different ignite services.
M1
Ignite server (running on port 48500)
Ignite client-1 (running on port 48100)
M2
Ignite client-2 (running on port 14050)
Port opened between machines:
M2 to M1 -
Can someone provide inputs on this please?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello,
I was doing some performance profiling of my ignite.NET client under load
and found that it was taking enormous time while serializing an enum field.
I'm using IBinarizable approach for serialization and my writeBinary method
looks like this:
public void
Hello Ignite Experts,
We have recently upgraded from version 2.6 to 2.8.0 and have started to face
some weird behavior since then.
With the below configuration:
We are seeing the below log (with different thread names) multiple times
every second as soon as the ignite server is
Hi,
Can anyone provide an input on this please?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks akorensh,
As advised I'm trying to send a user-defined event from the receiving node
when it becomes ready to accept messages and listening to this event on the
sending node to wait until the receiver is ready.
However, the node that I'm trying to send a user-defined event from is a
.net
Thanks.
So I can think of two ways using which such a set could be maintained by the
remote node:
1. The remote node listens to a new topic through which the local node sends
it a message whenever the set changes.
2. Or, the local node puts the set values in a new table in the cache itself
and
Hi,
Sorry but I could not get it to work.
The standard way of defining a remote filter as shown in sample repo is
something like:
qry.setRemoteFilterFactory(new Factory>() {
@Override public CacheEntryEventFilter
create() {
return new
Hi Ignite experts,
I am facing an issue where some messages sent to a node are sometimes missed
when the node just joins the cluster.
On some debugging, I found that this is because as soon as the node joins
the cluster, the sender node receives a NODE_JOINED event for that receiver
node and it
Hi Ilya,
Thanks for your response.
I'm aware of remote filters but can these filters be modified once the query
is already attached?
Because if not, then this would not solve my use case as the filter would
always give me updates on a fixed subset of keys, however in my case this
subset is varying
Hi,
We have a table in ignite cache which would have say around 1Mn entries at
anytime. Now we wish to listen on updates on a subset of these keys (say
5-10 thousand keys) and this subset keeps on changing as the user
subscribes/unsubscribes to these keys.
The way it is currently working is one
*Topology*:
Server-1 --> Cache myCache, holds continuously updating data like market
data(prices, status, tradetime etc) for instruments. InstrumentId is the key
for this cache.
Server-1 running with following jvm params: -Xms1g,-Xmx6g
Client-1 --> Pushing continuous updates
*Topology*:
Server-1 --> Cache myCache, holds continuously updating data like market
data(prices, status, tradetime etc) for instruments. InstrumentId is the key
for this cache.
Server-1 running with following jvm params: -Xms1g,-Xmx6g
Client-1 --> Pushing continuous updates
13 matches
Mail list logo
