Hi,
I am not using Ignite services to load the cache. Not sure what you mean by
sending ignite cache instance to executor. Is it not possible to load the
cache from cassandra backup from ignite client without deploying services?
Regards
Rohan
--
View this message in context:
http://apache-ign
Hi Igniters,
I have started learning and implementing ignite data grid. One of the basic
requirements I have is not to loose data stored in the cache, so if the data
evicts because of the size of the data going beyond the cache, I want this
data to be persisted in a file on a disk and still be ret
Hi Userx,
You might need to implement your own code to back Ignite by disk, but here
are examples, discussions and documentation around that topic that you can
review:
https://github.com/apache/ignite/tree/master/examples/src/main/java-lgpl/org/apache/ignite/examples/datagrid/store/hibernate
htt
hi,
when adding a new node to a cluster, the new node will demand some
partitions from other nodes.
if a write request comes when rebalancing, how does it send to the new node
according to old affinity?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/how-does-wri
yes of course, I've done ssh access in my cluster.
I rerun my tests and found that error disappeared.
thanks anyway
发件人: Andrey Gura
发送时间: 2017年7月7日 21:31:17
收件人: user@ignite.apache.org
主题: Re: yardstick-ignite:ERROR: Driver process has not started on dserver1
hello guys,
I checked all my configs in my "yardstick-ignite/config" path to look up
a parameter of the interval time between tests, however no matches can be found.
here is my log of my test, the 6 mins interval between tests is really too long.
[root@dserver1 yardstick-ignite]# tail -
is there a way to decrease the test interval time?
发件人: 罗 辉
发送时间: 2017年7月10日 10:53:04
收件人: user@ignite.apache.org
主题: how to set the interval time between tests while running yardstick-ignite
hello guys,
I checked all my configs in my "yardstick-ignite/con
Hi Limabean
Thanks for the the pointers, I went through them but it looks like that
these pointers actually talk about eternal persistent storage, which means
that the whole data is put in the underlying storage(say a database), so
whenever there is an update to the existing entry, it will surely