Re: Data eviction to disk
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 go to the underlying storage. My use case is around data eviction. I want to write to the persistent storage only when the cache falls short of memory(it has to evict some pages). Could you help me out with any pointers to the use case ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-eviction-to-disk-tp14535p14541.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
答复: how to set the interval time between tests while running yardstick-ignite
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/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 -f nohup.out <10:16:50> Driver is started on localhost with id=0 <10:22:53> Driver is stopped on localhost <10:22:54> Server is stopped on localhost <10:22:54> Server is stopped on localhost <10:22:54> Server is stopped on localhost <10:22:55> Starting server config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=0 <10:22:55> Starting server config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=1 <10:22:55> Starting server config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=2 <10:22:58> Starting driver config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=0 <10:22:58> Driver is started on localhost with id=0 <10:29:02> Driver is stopped on localhost <10:29:02> Server is stopped on localhost <10:29:02> Server is stopped on localhost <10:29:02> Server is stopped on localhost <10:29:03> Starting server config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=0 <10:29:03> Starting server config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=1 <10:29:03> Starting server config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=2 <10:29:06> Starting driver config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=0 <10:29:06> Driver is started on localhost with id=0 <10:35:10> Driver is stopped on localhost <10:35:10> Server is stopped on localhost <10:35:10> Server is stopped on localhost <10:35:10> Server is stopped on localhost <10:35:11> Starting server config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=0 <10:35:11> Starting server config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=1 <10:35:11> Starting server config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=2 <10:35:14> Starting driver config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=0 <10:35:15> Driver is started on localhost with id=0 <10:41:18> Driver is stopped on localhost
how to set the interval time between tests while running yardstick-ignite
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 -f nohup.out <10:16:50> Driver is started on localhost with id=0 <10:22:53> Driver is stopped on localhost <10:22:54> Server is stopped on localhost <10:22:54> Server is stopped on localhost <10:22:54> Server is stopped on localhost <10:22:55> Starting server config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=0 <10:22:55> Starting server config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=1 <10:22:55> Starting server config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=2 <10:22:58> Starting driver config '...-sn IgniteNode -ds ignite-1.9-atomic-put-get-bs-6-2-backup' on localhost with id=0 <10:22:58> Driver is started on localhost with id=0 <10:29:02> Driver is stopped on localhost <10:29:02> Server is stopped on localhost <10:29:02> Server is stopped on localhost <10:29:02> Server is stopped on localhost <10:29:03> Starting server config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=0 <10:29:03> Starting server config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=1 <10:29:03> Starting server config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=2 <10:29:06> Starting driver config '...k -sn IgniteNode -ds ignite-1.9-tx-optimistic-put-2-backup' on localhost with id=0 <10:29:06> Driver is started on localhost with id=0 <10:35:10> Driver is stopped on localhost <10:35:10> Server is stopped on localhost <10:35:10> Server is stopped on localhost <10:35:10> Server is stopped on localhost <10:35:11> Starting server config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=0 <10:35:11> Starting server config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=1 <10:35:11> Starting server config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=2 <10:35:14> Starting driver config '...gniteNode -ds ignite-1.9-tx-optim-repRead-put-get-2-backup' on localhost with id=0 <10:35:15> Driver is started on localhost with id=0 <10:41:18> Driver is stopped on localhost
答复: yardstick-ignite:ERROR: Driver process has not started on dserver1 during 10.0 seconds.
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 during 10.0 seconds. Hi, are there any errors in driver and server logs? Also please note, that you should have passwordless ssh access to localhost. On Fri, Jul 7, 2017 at 3:29 PM, 罗 辉 wrote: > Hello there > >I am new to Yarkstick, when I was running benckmark-run-all.sh with the > attached property file, I usually see below error: > > ERROR: Driver process has not started on dserver1 during 10.0 seconds. > Type "--help" for usage. > <20:26:05> Driver is started on dserver1 with id=0 > <20:26:05> Driver is stopped on dserver1 > <20:26:06> Server is stopped on dserver2 > <20:26:06> Server is stopped on dserver3 > <20:26:06> Server is stopped on dserver4 > <20:26:06> Server is stopped on dserver5 > > what is the reason this error takes place? > thanks for any idea. >
how does write request send to new node when rebalancing before affinity changed?
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-write-request-send-to-new-node-when-rebalancing-before-affinity-changed-tp14537.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Data eviction to disk
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 http://apache-ignite-users.70518.x6.nabble.com/How-to-do-write-behind-caching-td12138.html https://apacheignite.readme.io/v1.1/docs/persistent-store -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-eviction-to-disk-tp14535p14536.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Data eviction to disk
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 retrievable transparently to the client. How can I achieve this configuration ? I wasn't able to find the same in Ignite documentation. Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Data-eviction-to-disk-tp14535.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Ignite Load cache failing due to deserialization
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-ignite-users.70518.x6.nabble.com/Ignite-Load-cache-failing-due-to-deserialization-tp13207p14534.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
