Hi,
I see that you use both ipv4 and ipv6 stacks, I think it can somehow affect
this behavior, so, I would recommend enabling -Djava.net.preferIPv4Stack=true
for all nodes in the cluster(including clients). Also, why do you decided
to set such parameters to the communicationSPI:
Hi,Evgenii
Thank you for your such quick reply. When met the error we added the parameters
to the communicationSPI and changed the values several times, but did not take
effect, and we forgot deleting them.
Now we start to enabling the IPv4Stack on all nodes as your recommendation, but
i
Hi,
NTILE function currently is not supported, but I'm sure that you can share
the query you want to run on Ignite and Community will help you to rewrite
it for Ignite.
Evgenii
2018-01-23 9:48 GMT+03:00 sindhu somisetty <
sindhu.somase...@aline-consulting.com>:
> IS NTILE function is possible
Hello Wolfram,
After some reflection, it doesn't clear to me that this behavior is a bug.
SQL engine always works with binary objects. When some operation (insert,
update etc) is executed via SQL api, you can think about it as using
something like the following: cache.withKeepBinary().query(...)
I
Hi Evgenii,
Now that error gone , but another exception thrown:
[ERROR] 2018-01-23 04:11:58.849 [srvc-deploy-#146] [ig] GridServiceProcessor -
Error when executing service: null
java.lang.IllegalStateException: Getting affinity for topology version earlier
than affinity is calculated [locNod
Hi Aaron,
Most probably this issue won't be fixed in 2.4, since it's not in progress
yet.
As a workaround, setting -DIGNITE_EXCHANGE_COMPATIBILITY_VER_1=true JVM
argument seems to fix this problem.
Evgenii
2018-01-23 14:47 GMT+03:00 aa...@tophold.com :
> Hi Evgenii,
>
>
> Now that error gone ,
Hi,
Ignite uses JCache’s ExpiryPolicy, and that API only provides a way to specify
three kinds of TTL – for creation, modification and access.
AFAIU you’d like to tune TTL on a finer level, having different values per
different operations. If so, you can’t do that just with ExpiryPolicy.
But you
Hi,
At first, you may take a look at Ignite 2.0 migration guide:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
Also, the main difference in configuration between these versions is related
to the memory configuration, so take a look at this section from
docum
Hello!
So you are suggesting to store types of keys and values which are supposed
to be stored in cache?
I think it is already present, as cacheConfiguration.queryEntities[].keyType
and cacheConfiguration.queryEntities[].valType.
They're not always present, but they often are. They're somewhat t
Hi ,
I have a 40 node cluster. We are using on heap caching. I want to figure
out how much memory each cache node is consuming. I was looking at the
metrics where heap and non heap usage is printed. Is the metics gives me
the correct info ? Or are there different api’s in ignite to print it ?
Th
Hi Svonn,
I'm not sure that I properly understand your issue. Could you please provide
a problematic code snipped?
> is the policy also deleting the Map
Yes, if it was stored as a value.
Thanks!
-Dmitry
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> This keeps the performance stable, but I'm not sure how to persist the
> expired data properly
Perhaps you could listen to the EXPIRED events of the cache that stores the
data you want to persist,
create an additional cache with persistence enabled and put all your expired
data there.
Thus you
Hi,
It's less about a specific code snipped, more about a conceptual question:
How to keep a time window of 5 minutes in Offheap/Inmemory while storing
anything older on the harddrive.
@Stan:
That sounds like possible solution! I'll just have to figure out how to
catch, process and delete those p
I believe that’s correct, although listening for
javax.cache.event.EventType.EXPIRED in ContinuousQuery
may be more straightforward.
Also, I don’t think you need to disable eager TTL for that.
Eager TTL is about when to pay for deletion of the old data – other words, if
you specify a TTL
with a
Ranjit,
Then it sounds like you're recreating embedded mode on your own :) In this
case deprecation will not affect you of course, but this still a NOT
recommended way to use Ignite with Spark.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I’d like to carry this conversation further, cross-posting to dev list:
I now have possible production use cases for accessing cache key
[metadata].
As an example, suppose I want to scan all keys from a cache that may
contain large amounts of data and perform some operation on a few of them,
Looks like this is fixed in 2.4 😊
-Original Message-
From: Alexey Popov [mailto:tank2.a...@gmail.com]
Sent: Tuesday, November 14, 2017 5:09 AM
To: user@ignite.apache.org
Subject: Re: Error serialising arrays using Ignite 2.2 C# client
Hi Raymond,
You are right. True multidimensional arra
Bump.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi ,
We are using ignite JDBC thin driver to store 1 million records in a table
on ignite cache. To insert 1 Million records on single node it take 60 sec,
whereas on cluster of 2 nodes it takes 5 min and time grows exponentially
as number of nodes are increased.
attached ignite log file where ti
What is the Java source code? Most of the people have difficulties to write
proper Java JDBC code for bulk inserts (even for normal databases). It requires
some thinking on threading, buffers and of course selecting the right
methodology to insert etc
> On 24. Jan 2018, at 08:20, Ganesh Sarde
20 matches
Mail list logo
