Hi ,
There is a vulnerability reported in the usage of HTTP/2 protocol. so we
would like to know if Ignite uses this protocol. Details of the
vulnerability is in the below link.
https://www.kb.cert.org/vuls/id/605641/
Regards
Hi ,
We have received the below vulnerability for the mongodb version - 3.4.4.
VAMS :MongoDB Server 3.4.x < 3.4.22, 3.6.x < 3.6.13, 4.0.x < 4.0.9,
4.1.x < 4.1.9 - Improper Authorisation Vulnerability -
SERVER-38984(CVE-2019-2386): SVM-49539
After user deletion in MongoDB Server the improper inval
Hi ,
We are working on ignite on Kubernetes environment and using
Ignite-web-console for querying. When we ran security scan on Ignite web
console there are some security issues reported by the scans. Below are the
issues. All the below issue are reported as HIGH severity.
Could you please let me
Hi ,
how can we auto scale ignite pods based on the load. ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
We are testing and also the production data would be so much.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
We are testing and also the production data would be so much.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Team,
We are installing ignite on kubernetes environment with native persistence
enabled. When we try to create around 400 tables using the sqlline end point
, the pods are restarting after creating 200 tables with jvm heap error so
we have increased the java heap size from 1GB to 2GB and this
Hi Team,
We are installing ignite on kubernetes environment with native persistence
enabled. When we try to create around 400 tables using the sqlline end point
, the pods are restarting after creating 200 tables with jvm heap error so
we have increased the java heap size from 1GB to 2GB and this
Hi ,
We are using ignite in our architecture in kubernetes environment. In our
current development phase I am working on scale out and scale in of ignite
nodes automatically when the event is triggered.
Could you please give me the steps for scale out and scale in with out any
data loss. Also the