Okay - figured it out...
Had to prefix the 'PUBLIC' schema to the table name during the CREATE TABLE
query:
CREATE TABLE PUBLIC.City(...
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
hi Denis, Thanks for the reply. I would like to ask is it possible to
monitor the off-heap memory? or check its size easily?
2018-03-05 14:52 GMT+08:00 Denis Mekhanikov :
> Hi!
>
> Ignite 2.0 and newer uses off-heap memory. VisualVM shows only consumed
> Java heap, but main part of memory consump
Hi Denis,
I inserted a cache definition in the config of all the nodes, as
recommended. Then activated the cluster and connected using the client JDBC
driver, specifying the cache name in the connection string... it connected
successfully.
But when I submit a CREATE TABLE query, I receive the err
Hi!
Ignite 2.0 and newer uses off-heap memory. VisualVM shows only consumed
Java heap, but main part of memory consumption lays outside of it.
You can approximate consumed off-heap memory by using
*DataRegionMetrics#getPhysicalMemoryPages()
*and multiplying it by page size (4KB by default since Ig
Hi,
Currently, Ignite doesn't support auto-generate functionality. You are able
to generate IDs manually using distributed atomic sequence provided by
IgniteCacheAtomicSequence [1].
[1] https://apacheignite.readme.io/docs/id-generator
Best Regards,
Roman
--
Sent from: http://apache-ignite-use
I have an Ignite Server with below config:
JAVA_OPTS="-server -Xms1024m -Xmx4096m -XX:NewSize=64m
-XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=1024m -XX:+UseParNewGC
-XX:+UseConcMarkSweepGC"
everyday when I check it using VisualVM, it is healthy, total RAM usage is
below 4G, 2G Heap, 1G Metaspace