Tnx Ilya.
And what could be possible causes of long GC pauses?
Tnx
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I have a problem where my ignite node goes down often.
I attached the full log I have from last time my node crashed.
What I see from the log is problems with GC(possible long GC pause) and if I
understand correctly after that some locking happens and after some time
node simple crashed.
Could
Hi!
I get a bunch of "Failed to process selector key" errors. Can someone please
help what is the reason I could get those errors and any possible ways I
could fix this?
Below is the full error from my log.
Tnx.
[grid-nio-worker-client-listener-2-#31][ClientListenerProcessor] Failed to
I also have a problem with this so if someone can help..!
Tnx
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I have two node cluster: each on its own separate machine.
The replicated mode is turned on, as is native persistence.
While inserting data to a cluster, one of the nodes failed(still checking
why).
When I want to bring it back up(or start a new one with the same
configuration) it does not join
Yes of course.
All of my data is imported through sql. I have it in the warehouse, and then
just inserting them to ignite.
I was trying through SQL query get size in bytes for single row and then
based on that trying to predict resources needed. That's why I was confused
seeing so much more
Tnx ilya!
Never said it is significant. Not all of my caches will be so small in size.
This was only an example. I was just trying to predict (and understand) how
much resources will I need for all of my data I am planning to import.
Regards
--
Sent from:
created a table and inserted 9013 records in it.
The table has 17 columns and the total size of the data before import into
ignite is 282,625 bytes.
I have native persistence enabled and have 2 nodes in my cluster. Data is
replicated to both nodes.
I am using ignite 2.7.
After import into
I created a table and inserted 9013 records in it.
The table has 17 columns and the total size of the data before import into
ignite is 282,625 bytes.
I have native persistence enabled and have 2 nodes in my cluster. Data is
replicated to both nodes.
I am using ignite 2.7.
After import into
I wasn't able to configure it with those properties in xml config.
I was able to do it with following:
docker run -d --net=host -v
/walvolume/wal:/opt/ignite/apache-ignite/work/db/wal -v
/home/ec2-user/work:/opt/ignite/apache-ignite/work
Now, ignite writes to separate locations for wal and
Thanks for your reply but I don't quite understand.
How do you load this common spring file and how to you pass it to ignite on
docker run?
What is the example value for this:
#{systemEnvironment['IGNITE_PERSISTENT_STORE']}
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
By default, all ignite tables are added to PUBLIC schema.
Is it possible to create custom schema and create tables there?
With this, can I specify schemaName as a parameter when I query ignite over
rest api?
Thank you.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I have ignite deployed in docker.
I was studying Separate Disk Device for WAL part of docks:
https://apacheignite.readme.io/docs/durable-memory-tuning#native-persistence-related-tuning.
How can I configure this if I use docker? I have this deployed on ec2
machine where I have two separate
Tried it. Still not working. I also tried to setup S3 discovery.
My config is as follows:
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
http://www.springframework.org/schema/beans
Greetings all.
I have a few questions regarding memory.
1.) I am running ignite inside docker container. How can I increase heap
memory to ignite node when started?
I tried with passing -Xmx (I pass it to docker run command like this: -e
"JAVA_OPTS=-Xmx3g")
parameter but when node starts it
I have a 1 node cluster.
Ignite persistence turned on.
I create a bunch of tables with SQL.
At some point, I drop the table with SQL and try to create it again but it
says table already exists.
I try to execute Drop table once more, it says the table doesn't exist.
After I restart the cluster(I
Worked. Tnx :)
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Its a while from this thread but I am having the same issue.
I host configuration file on S3 bucket. First I added this bucket to be
publically accessible and everything works correctly. I simply pass
https://s3.amazonaws.com/... link to my docker run command when I start
ignite(I am using docker)
What if we have several people who would like to use the web console? The
idea is that each of them downloads web agent and run it locally each time
when he wants to use web console? Or is there a way to start the agent on
some server so it doesn't have to start each time locally?
Tnx
--
Sent
I am trying to setup ignite web console.
I pulled apache ignite web console standalone docker image and started it in
a docker container.
I still need to setup apache ignite web agent. When I download web agent and
start it on my local pc everything works perfectly. Web console connects to
my
Tnx for your help. Below is my config. Did you mean something like this?
http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
http://www.springframework.org/schema/beans
Greetings.
I am new to apache ignite and I would like to set up multiple ignite nodes
each running on separate ec2 instance inside docker container.
When I start the first ignite node, the cluster is created and now I have
one node in my cluster.
I create now new ec2 instance and start new
22 matches
Mail list logo