hsadia538 commented on issue #12154:
URL: https://github.com/apache/ignite/issues/12154#issuecomment-2999394370
Thank you so much.
Slightly unrelated to the parent question, but the main reason I was trying
replicas was that I am running Ignite and my applications locally for a POC
that deals with a lot of data.
I want to put the results entries in Ignite, where four C++ apps are writing
results to Ignite in batches of 1000. Each engine will write approximately
205,2000 records.
This is how my Ignite service looks in Docker Compose:
``` ignite:
<< : *ignite-def
container_name: ignite
command: --node-name ignite
deploy:
resources:
limits:
cpus: '5'
memory: 6g
environment:
- JAVA_OPTS=-Xms6g -Xmx6g
ports:
- 10300:10300
- 10800:10800
networks:
- mynet
```
After processing 30K records, Apache exits. I am assuming the engine gets
killed due to CPU constraints.
My question is, is there no way to write this many records to ignite
locally? And is there a way to determine ideal configurations for Apache to run
and process records like this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@ignite.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
