Hi,
I have a below query to run using joins
SELECT income_summarytest.workclass, income_summarytest.education,
income_summarytest.marital_status, income_summarytest.occupation,
income_summarytest.race, income_summarytest.gender,
income_summarytest.capital_gain, income_summarytest.capital_loss,
Thanks Ilya, it works and resolve my issue to an extent, but need to restart
all the nodes to get this change reflected.
But my question is, there is only Ignite instance running on this VM and the
exporter process is running, no other JVM running on the VM.
what else could be the reason why it
Hello!
I don't think it is possible since the H2 engine does not provide options
to limit CPU and heap AFAIK. Ignite community have decided to not rely on
forked H2 engine as e.g. recent GridGain does.
Maybe this will change when Calcite is introduced, and limiting will be
possible.
You can
Hello!
I don't understand your question. A collocated queue is located on a single
node, but you still need a method to run code on that specific node, don't
you?
The benefit is presumably shorter round-trip times.
Regards,
--
Ilya Kasnacheev
вт, 4 мая 2021 г. в 18:50, ps594 :
> I am trying
Hello!
This is in case you are running more than one node per VM.
You can disable addition of this number by setting
IGNITE_MBEAN_APPEND_CLASS_LOADER_ID system property or environment variable
to false prior to starting the VM, such as by adding the following JVM arg:
Hi Ilya,
I was wondering if it was a case of Node1 trying to connect to the old node
id of Node2 , but the Node2 has got a new node id since it was last
connected. ( That is the issue we faced in that link shared ) .
Maybe that is not what is happening here.
Please ignore if so,
regards,
Hello ALl
We are using Ignite 2.8.1 and have JMX exporters running on each node and
everything seems to be working fine.
Earlier it used to generate the metrics with the below 3d4eac69, all the 5
nodes used to generate the same
org_apache_*3d4eac69*_HeapMemoryUsed
Recently, we had to restart 2
