答复: 答复: problems in test ignite PersistentStore

2017-08-21 Thread
got it ,thank you Val, I got to have another try.


发件人: vkulichenko 
发送时间: 2017年8月19日 1:54:11
收件人: user@ignite.apache.org
主题: Re: 答复: problems in test ignite PersistentStore

You don't see anything in /ssd folder, because you provided it in
PersistenceStoreConfiguration object which is not even set anywhere. This
code has no effect:

val psc = new PersistentStoreConfiguration
psc.setPersistentStorePath("/ssd")

Actually, Ignite configuration can't be changed in runtime anyway, so it
should be done in XML as part of PersistentStoreConfiguration bean:






-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/problems-in-test-ignite-PersistentStore-tp16244p16297.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


problems in running Ignite examples in cluster.

2017-08-18 Thread
hello there

 I got classpath problems to run the examples in my cluster.

 I'm trying to run 
examples.(https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/persistentstore/PersistentStoreExampleNodeStartup.java)
 in my cluster with following command:


"bin/ignite.shexamples/config/persistentstore/example-persistent-store.xml"

,then I got this exception:

[root@dserver1ignite]# bin/ignite.sh 
examples/config/persistentstore/example-persistent-store.xml
class org.apache.ignite.IgniteException: Failed to instantiate Spring XML 
application context (make sure all classes used in Spring configuration are 
present at CLASSPATH) 
[springUrl=file:/data/disk01/huzongxing/ignite/examples/config/persistentstore/example-persistent-store.xml]
at 
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
at org.apache.ignite.Ignition.start(Ignition.java:350)
at 
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302)

Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.model.Organization
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)
at 
org.springframework.util.ClassUtils.resolveClassName(ClassUtils.java:284)
... 40 more
Failed to start grid: Failed to instantiate Spring XML application context 
(make sure all classes used in Spring configuration are present at CLASSPATH) 
[springUrl=file:/data/disk01/huzongxing/ignite/examples/config/persistentstore/example-persistent-store.xml]
Note! You may use 'USER_LIBS' environment variable to specify your classpath.

I tried to set various  'USER_LIBS' settings ,however none of them worked. Is 
there a guide to to start my ignite node with this class correctly? Should I 
compile Ignite via maven so that the dependencies included in the jar?

Any ideas are welcome~!



答复: problems in test ignite PersistentStore

2017-08-17 Thread
thank you dkarachentsev, i realized the type undefined mistake


 I correct my codes like below :

object SingleNodePersist {
  def main(args: Array[String]) {
Ignition.setClientMode(true)
val config = "/data/disk01/huzongxing/ignite/config/test.xml"
val ig = Ignition.start(config)
ig.active(true)
val cache = ig.getOrCreateCache[Long, Int]("organization")
val psc = new PersistentStoreConfiguration
psc.setPersistentStorePath("/ssd")

val streamer = ig.dataStreamer[Long, Int]("organization")
streamer.allowOverwrite(true)
for (i <- 1 to 1) {
  streamer.addData(i, i)
  if (i > 0 && i % 1 == 0)
println("Done: " + i)
}

cache.close()
  }
}


and my test.xml as well:

http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>
































127.0.0.1:47500..47502









after I changed my code and xml file,the test program can run normally.
I am expecting something to be written into /ssd directory , however I found 
nothing.
It seems the cache default behaviour is to store the cache data into memory 
only , not memory and disk simultaneously.
I will continue to look up the docs which you mentioned .

thanks again.



发件人: dkarachentsev 
发送时间: 2017年8月18日 0:08:17
收件人: user@ignite.apache.org
主题: Re: problems in test ignite PersistentStore

Hi,

1. You need to set types for datastreamer just like for cache you did:
var streamer = ig.dataStreamer[Int, String]("organization")

2. Check that classes from ignite/examples are in classpath. It's a maven
module which has scala examples that you may play with.

3. [1, 2, 3]

[1]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/PersistentStoreConfiguration.html#setPersistentStorePath(java.lang.String)
[2]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/PersistentStoreConfiguration.html#setWalStorePath(java.lang.String)
[3]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/PersistentStoreConfiguration.html#setWalArchivePath(java.lang.String)

Thanks!
-Dmitry.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/problems-in-test-ignite-PersistentStore-tp16244p16256.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


problems in test ignite PersistentStore

2017-08-16 Thread
hello guys:

  I'm trying to test the new feature PersistentStore, and got below 
questions:


  1.  streamer.addData() only support Nothing type input, how to make it 
support Int,String and others? here is my code:

import java.util.List;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.IgniteDataStreamer;
import org.apache.ignite.Ignition;
import org.apache.ignite.cache.query.QueryCursor;
import org.apache.ignite.cache.query.SqlFieldsQuery;
object singlenodepersist {
  def main(args:Array[String]){
Ignition.setClientMode(true)
val config = "config/test.xml"
val ig = Ignition.start(config)
ig.active(true)
val cache = createCache$[Int, String]("organization")

val streamer = ig.dataStreamer("organization")
streamer.allowOverwrite(true)
for(i<- 1 to 1){
  streamer.addData(1, "1")//I got problem in this line :typemismatch;  
found   : Int(1)  required: Nothing
}
  }
}
I am using scala 2.10.6

2. In the path of  IGNITE_HOME, I did no changes and tried to run
bin/ignite.shexamples/config/persistentstore/example-persistent-store.xml,
I got below exception:
classorg.apache.ignite.IgniteException: Failed to instantiate Spring XML 
application context (make sure all classes used in Spring configuration are 
present at CLASSPATH)
Caused by: java.lang.ClassNotFoundException: 
org.apache.ignite.examples.model.Organization
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.springframework.util.ClassUtils.forName(ClassUtils.java:250)
at 
org.springframework.util.ClassUtils.resolveClassName(ClassUtils.java:284)
... 40 more
..
Failed to start grid: Failed to instantiate Spring XML application context 
(make sure all classes used in Spring configuration are present at CLASSPATH) 
[springUrl=file:/data/disk01/huzongxing/ignite/examples/config/persistentstore/example-persistent-store.xml]
Note! You may use 'USER_LIBS' environment variable to specify your classpath.
It seems that I need to include the class 
org.apache.ignite.examples.model.Organization into my classpath, in which 
library it locates?

3.I want to set the persistentstore path to my SSD mount point, which 
configuration I can apply?

Any ideas are appreciated!

San.Luo


答复: Is it possible to make use of SSD in a Ignite cluster?

2017-07-27 Thread
Thank you ,I got it.


发件人: Michael Cherkasov 
发送时间: 2017年7月27日 16:54:52
收件人: user@ignite.apache.org
主题: Re: Is it possible to make use of SSD in a Ignite cluster?

Hi San Luo.

>1.Is there a way to use SSD when my cluster memory is running out to cache the 
>data?
Ignite 2.1 can do this for you:
https://apacheignite.readme.io/v2.1/docs/distributed-persistent-store
it will be release this week.
>2.Is there a parameter that control intermediate result storage directory, 
>like the one "spark.local.dir" in apache spark?
Check PersistentStoreConfiguration there's a parameter for this where you can 
define dir to store data.
>3.Is there a parameter or a policy that Ignite can evict some data from memory 
>to SSD based on LRU when the memory is running out?
https://apacheignite.readme.io/v2.1/docs/evictions

Thanks,
Mikhail.

2017-07-27 11:12 GMT+03:00 罗 辉 mailto:luo...@zetyun.com>>:

Hello guys:

   My cluster has some SSDs, and I want to make use of them in my Ignite 
applications.

1.Is there a way to use SSD when my cluster memory is running out to cache the 
data?

2.Is there a parameter that control intermediate result storage directory, like 
the one "spark.local.dir" in apache spark?

3.Is there a parameter or a policy that Ignite can evict some data from memory 
to SSD based on LRU when the memory is running out?


Any relative ideas is appreciated.

thanks
San.Luo




Is it possible to make use of SSD in a Ignite cluster?

2017-07-27 Thread
Hello guys:

   My cluster has some SSDs, and I want to make use of them in my Ignite 
applications.

1.Is there a way to use SSD when my cluster memory is running out to cache the 
data?

2.Is there a parameter that control intermediate result storage directory, like 
the one "spark.local.dir" in apache spark?

3.Is there a parameter or a policy that Ignite can evict some data from memory 
to SSD based on LRU when the memory is running out?


Any relative ideas is appreciated.

thanks
San.Luo



ignite can not find other ignite clients with attched config xml

2017-07-10 Thread
hi guys

 I used attached file to run a distributed ignite cluster. This xml file 
had been copied to the same path to 192.168.1.83~85.

I tried 
org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder

and org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder, 
neither of them work.

for IPaddress, I tried

192.168.1.83:47500..47505
192.168.1.84:47500..47505
 192.168.1.85:47500..47505
and
192.168.1.83
192.168.1.84
192.168.1.85
as well.

Is there any other config that I ignored? How to fix this? Any idea is 
welcome.thanks.









http://www.springframework.org/schema/beans";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>























192.168.1.83:47500..47505
192.168.1.84:47500..47505
192.168.1.85:47500..47505











答复: how to set the interval time between tests while running yardstick-ignite

2017-07-09 Thread
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

2017-07-09 Thread
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.

2017-07-09 Thread
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.
>


yardstick-ignite:ERROR: Driver process has not started on dserver1 during 10.0 seconds.

2017-07-07 Thread
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.



test.properties
Description: test.properties