Thanks for the confirmation Stanislav. Is this compatibility kept between
minors as a commitment from the team or is it just specific to the versions
I mentioned?
If this is a backward compatibility feature that you have intentions to
maintain, I think it's worth mentioning that in the
Hi Dimitry and community,
Is this still true? My intention is to do it between versions 2.7.6 and
2.8.1/2.9. Basically, I want to only update the docker image keeping the
volumes so that I can recover the persisted data. I couldn't find
documentation regarding this topic.
On the other hand,
Hi,
Thanks for the recommendations.
in this case, both server and client didn't show memory issues (heap and
available memory in the container). The GC pauses were very short too.
The configured timeouts are default:
clientFailureDetectionTimeout = 3
failureDetectionTimeout = 1
The
Hello,
we recently had a production incident in which our application got stuck
connecting to the cluster. The *IgnitionEx start0* method was blocked for
more than 24 hours waiting for that latch to be notified, but that never
happened. Finally, the container was restarted in order to recover the
Hi,
I tried your suggestion of using a NodeFilter but, is not solving this
issue. Using a NodeFilter by consistent-id in order to create the cache in
only one node is creating persistence information in every node:
In the node for which the filter is true (directory size 75MB):
Hi, thanks for the prompt response
We can have several of these caches, one for each query (is an exceptional
case but, with load, there can be several simultaneously) that is being
executed so we would like to preserve the persistence to take advantage of
the swapping in case the amount of memory
Hi Ignite team, We have a use case where a small portion of the dataset must
answer successive queries that could be relatively expensive. For this, we
create a temporary cache with that small subset of the dataset and operate
on that new cache. At the end of the process, that cache is destroyed.
Hi Andrei, thanks for taking the time to answer my question. I will consider
your suggestion if we decide to switch to a multiple tables approach that
will require those JOIN considerations. But, in this case we have only 1
cache and the operation that we are executing is an update. We tried using
Hi,
We are experiencing slow updates to a cache with multiple indexed fields
(around 25 indexes during testing but we expect to have many more) for
updates that are only changing one field. Basically, we have a
customer*->belongsto->*segment relationship and we have one column per
segment. Only
Hi,
We are experiencing slow updates to a cache with multiple indexed fields
(around 25 indexes during testing but we expect to have many more) for
updates that are only changing one field. Basically, we have a
customer*->belongsto->*segment relationship and we have one column per
segment. Only
Hi,
Is it possible to configure a custom IndexingSpi per cache? I'd like to have
a custom indexing mechanism to improve the full text capabilities but I
would like to enable only in some caches. is that possible? Is it possible
to configure multiple indexingSpi?
Adding a custom indexingspi to
Hi,
We are also facing this issue while trying to retrieve domain objects inside
a compute task.
Do you have plans to add this feature in the near future? maybe 2.7 release?
regards
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Does anyone have information about this?
Thanks.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello,
I have a question about p2p class loading.
My topology is 1 dedicated server, 1 client.
I have deployed a Service in the ignite client node (selecting clusterGroup
forClients) from which I'm trying to execute a compute() to the server node.
The IgniteCallable that I'm sending to call() is
Hello Igniters,
We noticed that IgniteUtils class has a static initialization block (line
796 in version 2.6) in which System properties are being changed. In
particular, the property "http.strictPostRedirect" is set to "true".
This could change how an application behaves when referencing any
Hi,
It is not mandatory to provide a filter.
For example, this will get all the events from "myCache"
ContinuousQuery qry = new ContinuousQuery<>();
qry.setLocalListener(new MyEventListener());
myCache.withKeepBinary().query(qry);
@IgniteAsyncCallback
private class MyEventListener implements
Thanks for replying PRasad,
I understand your approach but, I still don't get /when/ I should group all
events for the same transaction. In my tests I get onSessionStart and
onSessionEnd for each cache (both sharing the same cix). I would love to
have a post commit hook because at that point I'm
Hi,
Do you know if there is mechanism to subscribe for to transaction events
(pre or post commit)?
My scenario is the following:
I have 2 caches (A and B) that are modified in the same transaction. On the
other hand, I have a third C cache whose entries are calculated based on A
and B values.
I
18 matches
Mail list logo