Hi Team,
We are using sql queries and sql feature of C++ for our existing cache data
on our application.
The code runs perfectly fine on AMD linux version but on ARM machine, it
abruptly stops the application , after few entries in the DB.
If we try to again start the application, it again stops i
Hi Igniters,
Does Ignite support reading the encrypted password from Ignite config file
because keeping a clear text password in ignite config file is not a good
practice?
If yes how to use it? If it does not support by default is it possible to
implement it using any plugins?
Any kind of help is g
Hello Maxim, Could you please share the current state of this issue? Have you managed to resolve it or it still exists? What is your pods configuration in terms of resource usage? From: Maxim VolkomorovSent: Thursday, March 11, 2021 11:44 PMTo: user@ignite.apache.orgSubject: slow node discovering o
Hi,
Which version of ignite you are using ?
Even we had hit the same WAL issue with 2.9.0 release during our POC on K8s
test cluster.
Similar issue was reported at
https://issues.apache.org/jira/browse/IGNITE-13912
Not sure what is trigger for this issue and how it can be avoided.
Regards,
Vis
Hello!
Are there hs_err_pid*.log files around after the abrupt stopping? If there
are, please share the latest one.
Regards,
--
Ilya Kasnacheev
чт, 8 апр. 2021 г. в 15:06, rakshita04 :
> Hi Team,
>
> We are using sql queries and sql feature of C++ for our existing cache data
> on our applicat
Hi Ilya,
No hs_err logs are being generated.
No information on terminal as well, its just a stop of application.
Regards,
Rakshita chaudhary
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
will take a look at that.
I'm using version 2.10
Another interesting point is that even though I have disabled WAL Archive,
there are segments created and reported via
io_datastorage_WalArchiveSegments metric.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi experts,
I have a question regarding setting system view JMX exporter via
configuration.
When I was using ignite 2.8.0 I had problem using prometheus jmx exporter to
export metrics, with same issue described here
https://issues.apache.org/jira/browse/IGNITE-13996 . And the workaround
provided
Hi,
I have a SQL performance issue. There are indexes on both fields that are
used in the ORDER BY clause and the WHERE clause.
The following statement takes about 133941 ms with several warnings from
IgniteH2Indexing:
SELECT JQ._KEY
FROM "JobQueue".JOBQUEUE AS JQ
INNER JOIN "Jobs".JOBS AS J ON