Currently, only field names can be obtained, there is no information about
field data types in thin client protocol.
ср, 4 нояб. 2020 г. в 13:58, Shravya Nethula <
shravya.neth...@aline-consulting.com>:
> Ilya and Alex,
>
> Thank you for information.
> Can you please also suggest how to get the d
HI,
We are using Apache Ignite 2.7.0 binary and servers are using Linux OS &
app servers are using Windows OS.We are using Apache Ignite .Net APIs.
Recently we have noticed that our application (Client Node) is stopping
with OOM error. App server has 32 GB RAM & we are specifying JVM Heap = 8
GB.
Before adding ignite-rest-http to the application my thread count was around
65
ashish@LAPTOP-0CGC34A5:~$ top -H -p 1468
top - 20:41:37 up 19:10, 0 users, load average: 0.20, 0.16, 0.15
Threads: 64 total, 0 running, 64 sleeping, 0 stopped, 0 zombie
After adding ignite-rest-http to the
The above idea did not work. The ignite setup is as follows/
Ignite 2.8.1
Hikari 3.4.5
Java 1.8
Spring JdbcTemplate
Apache ignite is in Azure K8S cluster, and the service is being exposed as
a Azure internal load balancer.
The api works well for some time, (*till * *1 hour of restart*), after tha
Ilya and Alex,
Thank you for information.
Can you please also suggest how to get the datatypes of those columns obtained
from the query?
Regards,
Shravya Nethula,
BigData Developer,
[cid:134aaaea-babf-48d0-9084-0e30ff58e8b5]
Hyderabad.
From: Alex Plehanov
Dear Courtney Robinson,
please write if you have any cases to update helper cache with paritions to
better understand the situation.
How and when are you going to clear this helper caches if the alternative
version (as you suggested in the first email) of CacheBased Dataset will be
provided?
A
Hi community,
The operation steps are as follows:
1.use ignite.sh example-deploy.xml start a server node
2.Put the service jar package in the /home/test/deploy directory
3.Deploy services using DeployClient
4.If you use ThickClientTest and ThinClientTest to access the service
respectively,
Hi,
Below are the logs
BaselineTopology of joining node (e6d542e7-cd73-4e57-90c1-b28da508c2c6) is not
compatible with BaselineTopology in the cluster. Branching history of cluster
BlT ([1016056908]) doesn't contain branching point hash of joining node BlT
(510622971). Consider cleaning persiste
Hi,
I did not remove the code ignite.cluster().active(true) , however added
condition on one application to check if cluster is active or not and the other
application activates the cluster.
Regards,
Gurmehar Singh
From: Andrei Aleksandrov
Sent: 30 October 2020 20:01
To: user@ignite.apache.or