Igniters,My tutorial post about loading big tables into Apache Ignite has finally arrived [1]. Many thanks to @Denis Magda and @Ksenia Romanova for their valuable help.[1] https://www.gridgain.com/resources/blog/how-fast-load-large-datasets-apache-ignite-using-key-value-apiVladimir
Thank you for the information Ilya.
Regards,
Shravya Nethula,
BigData Developer,
[cid:9d5782fd-7700-4644-9354-38435191aa05]
Hyderabad.
From: Ilya Kasnacheev
Sent: Thursday, September 24, 2020 5:01 PM
To: user@ignite.apache.org
Subject: Re: Issue in Alter Ta
I tried doubling it from 200 MB to 400 MB. My initial test worked, but as I
increased the number of fields that I was writing per entry, the same issue
occurred again. So it seems to just increase the capacity of what can be
written, not actually prevent the exception from occurring. I guess my
Adam,
Like your way of thinking. It makes sense to me.
For me, a computing platform comprises two essential components - a storage
engine and compute APIs (not only compute grid, but also streaming, SQL,
etc.). Under this definition, Ignite fits the "compute platform" category
for sure, but the p
Hi,
Highly likely some of the nodes go offline and try to connect again.
Probably you had some network issues. I think I will see this and other
information in the logs. Can you provide them?
BR,
Andrei
9/24/2020 6:54 PM, Alan Ward пишет:
The only log I see is from one of the server nodes, w
The only log I see is from one of the server nodes, which is spewing at a
very high rate:
[grid-nio-worker-tcp-comm-...][TcpCommunicationSpi] Accepted incoming
communication connection [locAddr=/:47100, rmtAddr=:
Note that each time the log is printed, i see a different value for .
Also note th
Hi,
Did you try to increase the DataRegion size a little bit? It looks like
190 MB isn't enough for some internal structures that Ignite stores in
OFF-HEAP except the data.
I suggest you increase the data region size to for example 512 MB - 1024
MB and take a look at how it will work.
If y
Hi,
Can you please provide the full server logs?
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
[image: Selected post]
I'm running a 5 node Ignite cluster, version 2.8.1, with persistence
enabled
and a small number of partitioned caches, ranging between a few thousand
records to one cache with over 1 billion records. No SQL use.
When I run a Java client app and connect to the cluster (with c
Hello!
I think it will be in 2.10 or 2.9.1. Maybe early next year?
Regards,
--
Ilya Kasnacheev
чт, 24 сент. 2020 г. в 14:04, Shravya Nethula <
shravya.neth...@aline-consulting.com>:
> Hi Ilya,
>
> Thank you for the confirmation and the workaround is working as expected.
> Much appreciated.
>
Hi Ilya,
Thank you for the confirmation and the workaround is working as expected. Much
appreciated.
Is there any rough release date or release version for this issue?
Regards,
Shravya Nethula,
BigData Developer,
[cid:357d40f2-e612-4cef-b899-fb17a36896bb]
Hyderabad.
_
Hello!
Thank you for this report, now I can indeed confirm I can see the issue! I
have filed https://issues.apache.org/jira/browse/IGNITE-13482 on your
behalf.
As a workaround you can do SELECT * FROM tbl LIMIT 0; before issuing ALTER
TABLE on that node.
Regards,
--
Ilya Kasnacheev
чт, 24 сен
Hi Ilya,
Yes, the code that you sent is working fine.
But can you please try the below code, by executing CREATE TABLE and ALTER
TABLE in separate programs. In this scenario, its not working.
public class ClientNode {
public static void main(String[] args) {
IgniteConfiguration igni
13 matches
Mail list logo