What kind of OOM you've faced? Lack of free memory in data region or in
Java Heap?
Consider to share some logs.
On 12.07.2023 18:19, Arunima Barik wrote:
I have enabled Page eviction to Random-2-LRU for default region
Still whenever I write a big Spark DataFrame to Ignite
Like
As a workaroud you can try to add *-v* option to ignite.sh, this should
enable verbose logging (e.g. non quiet logging)
01.02.2023 17:38, Jeremy McMillan пишет:
This seems to be at the level of a high quality bug report, and has
enough detail that a fix could probably be implemented and
));
but getting SQLException.
Basically I want to configure the index in my Ignite XML Configuration.
referenceId
customerId
In above in have define one index and now need to create one more
index on name field which should be case-insensitive
On Thu, Jan 12, 2023 at 9:46 PM Ilya Korol
Hi, usually this can be achieved by using lower() function in index
definition. I guess it should be something like:
CREATE INDEX title_idx ON books (lower(title));
I'm not sure whether Ignite supports such feature, but you can give it a
try.
Btw, to exploit this index you also would have to
also it is confirmed . Problem with the two cache
approach you suggested is , it requires 2 GET requests , if avg GET
latency is 10 ms , for 2 cache gets doubled to 20 ms . either we will
require some sort of server side function or mapping like
On Tue, 18 Oct 2022 at 21:49, Ilya Korol wrote
Hi, do you use multinode cluster? What do you mean by 'beans', is it
simple POJO or Spring bean?
I don't think that this is a good idea to store Spring beans in ignite
cache, because all data that goes to cache would be transformed to so
called BinaryObjects (However you can give it a try
Hi,
According to logs you have the following:
[17:02:04,774][INFO][grid-nio-worker-tcp-comm-0-#40%MATCHERWORKER%][TcpCommunicationSpi]
Accepted incoming communication connection
[locAddr=/xx.xx.xxx.IP2:47100, rmtAddr=/xx.xx.xxx.IP1:52166]
Hi,
Please take look to
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/client/ClientAddressFinder.html,
according to this ThinClientKubernetesAddressFinder should refresh
address list on client connection failure, or you can try to set
*paritionAwareness = true* in
Hi,
Asterisk (*) in cache name is just a flag for Ignite to not initiate
this cache but instead register it as a template, that for example can
be used further for SQL table creations:
CREATE TABLE IF NOT EXISTS Person (
id int,
city_id int,
name varchar,
age int,
company varchar,
Hi, try to set java property IGNITE_NO_SHUTDOWN_HOOK=true.
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteSystemProperties.html#IGNITE_NO_SHUTDOWN_HOOK
21.06.2022 17:27, Yuriy Ivkin пишет:
Greetings!
I am using embedded Apache Ignite in my project and syncronyze
Hi, are you able to run simple DML query like: SELECT * FROM
PRODUCT_TABLE; ?
02.06.2022 00:13, Sachin janani пишет:
Hi,
I am trying to run Analyze table command from sqlline to collect the
statistics of a table but its failing with parsing error. Following is
the error that i am getting.
lication writes inversely. Currently
checkpointing
> frequency and threads are default
>
>
> On Sun, Apr 17, 2022 at 6:33 AM Ilya Korol wrote:
>
> > Hi, From my perspective this looks like your physical storage is not
> > fast enough to handle incoming writes. ma
Hi, From my perspective this looks like your physical storage is not
fast enough to handle incoming writes. markDirty speed is 2x times
faster that checkpointWrite even in the presence of throttling. You've
mentioned that ignite work folder stored on SSD, but what about PDS
folder
Hi,
There is some issue related to B+tree corruption that would be included
in next release 2.13: https://issues.apache.org/jira/browse/IGNITE-15990
Does this scenario looks similar to your case?
If you have a working reproducer feel free to submit a new Jira ticket.
15.04.2022 22:04,
Hi Lokesh,
Updates for running Ignite over Java 17 is already in master. Please
take a look:
https://github.com/apache/ignite/blob/master/bin/include/jvmdefaults.sh
On 2022/04/12 10:11:57 Lokesh Bandaru wrote:
> You are fast. :) Was just typing a reply on top of the last one and yours
> is
Hi Surinder,
I guess that there was Integer overflow in expression #{2 * 1024 * 1024
* 1024} so it was evaluated as -2147483648. Try to add 'L' to one of
multipliers like:
#{2 * 1024 * 1024 * 1024L}
22.03.2022 23:14, Surinder Mehra пишет:
Hi,
We noticed that WalArchive size is going beyond
Hi. What about sqlline that is available out of the box? Is it not
enough for you?
18.01.2022 17:57, Adriel Peng пишет:
Hi
Can Ignite have an interactive shell (like pyspark) for SQL similar
operations in the future version?
Thanks
I've checked latest master and didn't find any mentions of HASH_JOIN_IDX
in it (except documentation sources). Meanwhile in gridgain community
repository you can find HashJoinIndex class
PeerDeploymentClassLoading should help to work around this issue,
shouldn't it?
10.12.2021 20:56, Pavel Tupitsyn пишет:
Yes, the problem is that the predicate class "ThinClient$1" is not
deployed on the server.
On Fri, Dec 10, 2021 at 1:24 PM 18624049226 <18624049...@163.com
I guess so. If vulnerability present in particular JAR by excluding this
JAR from classpath, CVE should not affect you environment.
On 2021/10/27 12:58:12 Dana Milan wrote:
> Hi,
> .
> Can anyone provide a clarification of how jetty is being used by Ignite
> 2.8.1 and whether there is another
Hi MJ.
This is a bug, i've created a jira for it:
https://issues.apache.org/jira/browse/IGNITE-15867
However this should not affect ignite workflow, since it just produces
excessive stack traces and nothing more.
On 2021/11/03 03:27:42 "MJ" wrote:
> Hi,
>
>
>
>
>
>
> I experienced
Hi Bharath.
I've checked the sources and looks like method
CollectionConfiguration.getOffHeapMaxMemory() is never called, so the
only way to restrict queue capacity is to use capacity parameter of
ignite.queue().
One can argue about it, but this looks quite natural to restrict queue
by
Hi Sumit,
What is Ignite version that you use?
AFAIK partition map exchange is a king of "stop the world" actiity for
the cluster, so any other actions with cluster (like cache creation)
would be suspended until PME end.
If all of your clients concurrently try to create same cache it's OK
Actually Query interface doesn't define close() method, but QueryCursor
does.
In your snippets you're using try-with-resource construction for SELECT
queries which is good, but when you run MERGE INTO query you would also
get an QueryCursor as a result of
igniteCacheService.getCache(ID,
Hi,
It looks like baseline topology auto-adjustment is in process. Did you
checked cluster state later?
Also to track auto-adjustment events please check your logs for messages
like:
Baseline auto-adjust will be executed right now ...
Baseline auto-adjust will be executed in ...
Baseline
AFAIK there were not any significant changes related to this feature.
Also note that but default there is no restriction for size of on-heap
memory that would be used for sql caching, so try to add some tunings
like increasing heap memory or specifying number of cached rows via
Hi,
Are you running ignite every of nodes on dedicated machines? When you
restart ignite node do you also restart whole machine? Is there any kind
of DHCP? Could you also share more logs from 11th node and from other
server node.
On 2021/08/12 05:57:31, BEELA GAYATRI wrote:
> Dear Team,>
>
I guess that you have an option to move whole PDS (if you enable it) via
SSH from one cluster to another, but this approach could be tricky
because caches partitions distribution may not be the same on different
clusters.
On 2021/07/29 16:55:28, wrote:
> Hello,>
>
> What's the best way to
Hi,
Apache moved Ignite's repositories here:
https://apache.jfrog.io/artifactory/ignite-deb/
https://apache.jfrog.io/artifactory/ignite-rpm/
https://stackoverflow.com/questions/68493785/ignite-deb-package-mirrors
On 2021/07/22 20:53:55, Mustafa Sunka wrote:
> looking more into this, it
Hi,
Looks like following lines of error stack trace says that the issue
really may be related to class loader:
Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to deploy
class for local deployment
Hi,
Which Ignite version do you use? Have you enabled any optional ignite libs? Am
I right that you're trying to call Ignite REST API? Do you know call to which
endpoint produces described error? Which client do you use for calling this
endpoint? Can you repeat this call via other tools like
Hi,
Which Ignite version do you use? Have you enabled any optional ignite libs? Am
I right that you're trying to call Ignite REST API? Do you know call to which
endpoint produces described error? Which client do you use for calling this
endpoint? Can you repeat this call via other tools like
Hi Shubham Shirur,
Afaik kafka module was moved to separate repo
https://github.com/apache/ignite-extensions, and now it released
independently.
Concerning missing kafka optional module in ignite distribution:
Looks like existing docs is a bit outdated and should be fixed. Because
neither
Hi, Vladislav.
Did you also deployed appropriate cache configuration along with ignite
server? See examples in ignite docs or ignite repo about how to
define/configure caches.
17.06.2021 02:21, Vladislav Shipugin пишет:
I started the ignite-server in Kubernetes and am trying to connect the
Is there any logs on server side when you face this issue?
16.06.2021 11:19, Moshe Rosten пишет:
Greetings,
I'm attempting to retrieve a list of values from this query line:
List>res =conn.sqlQuery("select * from TWSources");
It works sometimes perfectly fine, and at other times it gives me
I've created a Jira for this issue
https://issues.apache.org/jira/browse/IGNITE-14898
10.06.2021 18:56, Ilya Kasnacheev пишет:
Hello!
I guess so. I think you should file a ticket against Ignite JIRA.
Regards,
--
Ilya Kasnacheev
ср, 9 июн. 2021 г. в 20:26, gigabot
Yes, you're right. There is no remote listeners. I mean do you use only
local listener or also configured remote filters? (Excuse me for being
not clear enough).
Did you configure backups for cache partitions? If so at which node you
are listening for event (primary or backup)?
Try to
What kind of listener you used? Could you share your configuration or
link to a reproducer?
I've checked write behind feature with mysql instance and don't find any
performance loss (i receive cache put events instantly via registered
listener but they appear in DB with configured time
Hi, afaik unfortunately there is no opportunity to implement custom
ExpiryPolicy that will rely on cache entry value field for expiry
calculation because there is no any hook for intercepting value during
expiry policy creation or calls.
But you can use a little hacky trick with cache proxy
39 matches
Mail list logo
