date:20160811

Re: Fail to join topology and repeat join process

2016-08-11 Thread Jason

The attached is the config file.

For server node, one node one machine. For the client node, one machine may
have few ones.

Just do a rough check, the error logs in all the server nodes are almost the
same.

default-config.xml
  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Fail-to-join-topology-and-repeat-join-process-tp6987p7002.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Fail to join topology and repeat join process

2016-08-11 Thread vkulichenko

Hi Jason,

Please attach your current configuration and logs from all nodes. Do you
have nodes running on the same physical box?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Fail-to-join-topology-and-repeat-join-process-tp6987p6997.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: LOOK THORUGH THIS ERROR

2016-08-11 Thread vkulichenko

Ravi,

You have to use the same version of ignite-hibernate as the ignite-core (the
latest is 1.7). The ignite-hibernate module is not deployed to Maven central
anymore due to licensing restrictions, but you can use the repo provided by
GridGain [1]. Another option is to build this module from sources by
yourself.

[1] www.gridgainsystems.com/nexus/content/repositories/external

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/LOOK-THORUGH-THIS-ERROR-tp6977p6995.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Problem with installing ODBC Driver

2016-08-11 Thread vkulichenko

Hi Austin,

You're using deprecated CacheTypeMetadata which probably causing problems.
Looks like the schema is create, but when you insert the data, Ignite does
not associate your objects with this schema. Please try configuring SQL
fields using annotations or QueryEntity [1]. I would recommend the former as
it's much easier.

[1] https://apacheignite.readme.io/docs/sql-queries

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Problem-with-installing-ODBC-Driver-tp5914p6994.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite 1.7 doesn't play along with ignite-spatial 1.2-incubating

2016-08-11 Thread vkulichenko

Hi,

You should use version 1.7 for all artifacts. ignite-spatial is not deployed
to Maven central due to licensing restrictions, but GridGain provides the
repo [1] that has it (as well as other LGPL dependencies). If you don't want
to use a third-party repo, you can build the module from sources by
yourself.

[1] http://www.gridgainsystems.com/nexus/content/repositories/external

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-7-doesn-t-play-along-with-ignite-spatial-1-2-incubating-tp6950p6993.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Clear the cached data?

2016-08-11 Thread Ravi kumar Puri

I will use clear or destroy method.. but in order to invoke that methods i
need ignite object from the server or client loaded classes as i have to
implement that in other class... In order to use in another i need to
create a new instance for ignite and intialise it null. That means i didnt
get any reference from server or clientloaded classes ignite object.
Undeestand?

Suppose

Class A()
Ignite ignite=Ignition.start("ignite-cfg.xml");
Then i create a cache name with this ignite object.

Class B()
In this class i want to use above class ignite object in order to clear the
cache.

So how to use it in class B() so that watever nodes loaded and data cached
in classA() cna be cleared from the scratch??

Understood??
On 11-Aug-2016 15:38, "Alisher Alimov"  wrote:

> All 2 methods clear cache entries, but also IgniteCache#destroy delete
> cache meta info from all nodes and theoretically IgniteCache#clear will be
> faster to clean cache
>
> With best regards
> Alisher Alimov
> alimovalis...@gmail.com
>
>
>
>
> On 11 авг. 2016 г., at 12:53, Alexey Kuznetsov 
> wrote:
>
> Alisher, Ravi.
>
> cache.clear() could take a lot of time in case of large grid / many
> entries.
>
> Will cache.destroy() + ignite.getOrCreateCache(ccfg) - faster?
>
> On Thu, Aug 11, 2016 at 4:39 PM, Alisher Alimov 
> wrote:
>
>> Hi!
>>
>> IgniteCache#close doesn’t clear data by contract for non local caches
>>
>> /**
>>  * Closes this cache instance.
>>  * 
>>  * For local cache equivalent to {@link #destroy()}.
>>  * For distributed caches, if called on clients, stops client cache, if 
>> called on a server node,
>>  * just closes this cache instance and does not destroy cache data.
>>  * 
>>  * After cache instance is closed another {@link IgniteCache} instance for 
>> the same
>>  * cache can be created using {@link Ignite#cache(String)} method.
>>  */
>>
>> To clear cache data you must invoke IgniteCache#clear() it’s will clear
>> cache contents
>>
>> Ignite doesn’t have method to clean data in all cache, but you can use
>>
>> Ignite#cacheNames(cacheName -> Ignite#cache(cacheName).clear())
>>
>> With best regards
>> Alisher Alimov
>> alimovalis...@gmail.com
>>
>>
>>
>>
>> On 11 авг. 2016 г., at 10:14, Alexey Kuznetsov 
>> wrote:
>>
>> Hi, Ravi.
>>
>> You may close all caches and recreate them (from code).
>> Will this work in your case?
>>
>> On Thu, Aug 11, 2016 at 2:04 PM, Ravi Puri 
>> wrote:
>>
>>> I want to clear all the data cached in server and client nodes. So how
>>> to do
>>> it as i have to do it another class.
>>>
>>>
>>>
>>> --
>>> View this message in context: http://apache-ignite-users.705
>>> 18.x6.nabble.com/Clear-the-cached-data-tp6946.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com
>>> .
>>>
>>
>>
>>
>> --
>> Alexey Kuznetsov
>> GridGain Systems
>> www.gridgain.com
>>
>>
>>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
>
>

Re: LOOK THORUGH THIS ERROR

2016-08-11 Thread Ravi kumar Puri

Ignite-hibernate 1.2 incubating jar.. is this what u meant?
On 11-Aug-2016 18:40, "Alisher Alimov"  wrote:

> Hi!
>
> Can you specify hibernate version that you use?
>
> With best regards
> Alisher Alimov
> alimovalis...@gmail.com
>
>
>
>
> On 11 авг. 2016 г., at 16:01, Ravi Puri  wrote:
>
> java.lang.NoSuchMethodError:
> org.hibernate.SessionFactory.openSession()Lorg/hibernate/Session;
> at
> org.apache.ignite.cache.store.hibernate.CacheHibernateStoreSessionList
> ener.onSessionStart(CacheHibernateStoreSessionListener.java:178)
> at
> org.apache.ignite.internal.processors.cache.store.
> GridCacheStoreManagerAdapter.sessionInit0(GridCacheStoreManagerAdapter.
> java:818)
> at
> org.apache.ignite.internal.processors.cache.store.
> GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.
> java:479)
> at
> org.apache.ignite.internal.processors.cache.distributed.
> dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:515)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.
> localLoadCache(IgniteCacheProxy.java:387)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$
> LoadCacheClosure.call(GridCacheAdapter.java:5716)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$
> LoadCacheClosure.call(GridCacheAdapter.java:5663)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.
> execute(GridClosureProcessor.java:1789)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$
> 2.call(GridJobWorker.java:509)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.
> java:6397)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.
> execute0(GridJobWorker.java:503)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.
> body(GridJobWorker.java:456)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/LOOK-THORUGH-THIS-ERROR-tp6977.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com
> .
>
>
>

Fail to join topology and repeat join process

2016-08-11 Thread Jason

hi Ignite team,

In a cluster with 20 server nodes, I manually restarted a server node to
test its partition re-balance and reliability, then the restarted node
couldn't join the topology with the below error. And this process lasted for
few hours, but still couldn't move forward.

The attached is the log in the other remote server nodes.

FYI, we've a big cache with 20G off_heap memory per node.

Would you like to take a look and give us some suggestion on how to tune
this? 

Any suggestion or advice will be appreciated.

Thanks,
-Jason

[TcpDiscoverySpi] Node has not been connected to topology and will repeat
join process. Check remote nodes logs for possible error messages. Note that
large topology may require significant time to start. Increase
'TcpDiscoverySpi.networkTimeout' configuration property if getting this
message on the starting nodes [networkTimeout=3]

error_log.txt
  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Fail-to-join-topology-and-repeat-join-process-tp6987.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread percent620

Hello, Nikolai,

I'm a new ignite, can you please provide more detail steps for this? thanks
again!!!



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-Spark-on-YARN-Deployment-tp6910p6986.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

2016-08-11 Thread Vladislav Pyatkov

Please, attach all logs as files.
In additional, can you provide system statistics (using dstat -t --top-mem
-m -s -g -d --fs --top-io-adv)?

All logs must be collected at the moment of  topology segmentation, hence
dstat must  works parallel with the application.

The actions will help us discover system state when grid is segmented.

On Thu, Aug 11, 2016 at 4:37 PM, yucigou  wrote:

> Another question is: What is the reason that Ignite shall stop the node in
> the case of big GC pause or temporary network issue? (By the way, I'm not
> saying big GC pause or temporary network issue is the case for this topic
> though.)
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Local-node-seems-to-be-disconnected-
> from-topology-failure-detection-timeout-is-reached-tp6797p6983.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Vladislav Pyatkov

Re: Node authentication using security credentials

2016-08-11 Thread Vladislav Pyatkov

Hi,

Authentication process protects access to grid in first, but authorization
allow to determine list of authorized permissions.
In other word you can have some clients with difference rights. Any user
can have or have not permission to grid functionality. Description of the
permission you can see in the enum
org.apache.ignite.plugin.security.SecurityPermission.

On Thu, Aug 11, 2016 at 3:52 PM, pragmaticbigdata 
wrote:

> When you mention "Ignite has all the hooks in the code" I think you are
> referring the the plugin support that ignite provides and the classes under
> the package "org.apache.ignite.plugin.security".
>
> What could be the reasons of having a security layer given that ignite
> would
> be deployed on a private aws network (VPC)? I do not foresee a need of
> having client authentication but just wanted to know your thoughts.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Node-authentication-using-security-
> credentials-tp6853p6976.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

-- 
Vladislav Pyatkov

Re: Local node seems to be disconnected from topology (failure detection timeout is reached)

2016-08-11 Thread yucigou

Another question is: What is the reason that Ignite shall stop the node in
the case of big GC pause or temporary network issue? (By the way, I'm not
saying big GC pause or temporary network issue is the case for this topic
though.)



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Local-node-seems-to-be-disconnected-from-topology-failure-detection-timeout-is-reached-tp6797p6983.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread Nikolai Tikhonov

>
> 3) I'm running spark-shell on driver machine NOT yarn cluster?
>

ignite-spark starts Ignite client node which should have direct access to
YARN ignite cluster (have network access, open ports and etc).

Re: LOOK THORUGH THIS ERROR

2016-08-11 Thread Alisher Alimov

Hi!

Can you specify hibernate version that you use?

With best regards
Alisher Alimov
alimovalis...@gmail.com




> On 11 авг. 2016 г., at 16:01, Ravi Puri  wrote:
> 
> java.lang.NoSuchMethodError:
> org.hibernate.SessionFactory.openSession()Lorg/hibernate/Session;
>   at
> org.apache.ignite.cache.store.hibernate.CacheHibernateStoreSessionListener.onSessionStart(CacheHibernateStoreSessionListener.java:178)
>   at
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.sessionInit0(GridCacheStoreManagerAdapter.java:818)
>   at
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:479)
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:515)
>   at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localLoadCache(IgniteCacheProxy.java:387)
>   at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5716)
>   at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5663)
>   at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1789)
>   at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
>   at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
>   at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
>   at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
>   at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>   at java.lang.Thread.run(Unknown Source)
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/LOOK-THORUGH-THIS-ERROR-tp6977.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Embedded mode ignite on spark

2016-08-11 Thread Alisher Alimov

Hi!

I want to notice that totalCounter var is not passed to job by reference, that 
why you retrieves the different values on computation, and it is not a good 
idea to change the var outside fun context

If you wan’t to calculate totalCount use map that reduce result

With best regards
Alisher Alimov
alimovalis...@gmail.com




> On 11 авг. 2016 г., at 8:09, percent620  wrote:
> 
> Hello, I want to integrate ignite with spark on Embedded mode , and here is
> my detailed steps for this.
> 
> 1、added maven dependencies for pom.xml
> 
>
>org.apache.ignite
>ignite-core
>1.6.0
>
>
>org.apache.ignite
>ignite-indexing
>1.6.0
>
>
>org.apache.ignite
>ignite-visor-console
>1.6.0
>
>
>org.apache.ignite
>ignite-spring
>1.6.0
>
>
>org.apache.ignite
>ignite-spark
>1.6.0
>
>
>org.apache.ignite
>ignite-yarn
>1.6.0
>
> 
> 2、Write spark code and submit these code to yarn application, and the code
> is
> val igniteContext = new IgniteContext[String, BaseLine](sc,() => new
> IgniteConfiguration(),false)
> 
> false: is embedded mode for ignite, right?
> tempDStream.foreachRDD(rdd =>{
>  val rddCounter = rdd.count().toInt
> totallyCounter += rddCounter
> println(DateUtil.getNowDate() + " invoked! count=" + rddCounter +
> ";totallyCounter= => " + totallyCounter)
> if(!rdd.isEmpty()) {
>//==start==
>val cacheRdd = igniteContext.fromCache("partitioned")
> 
>   //fianlLatestBaselineRDD: total rdd that need to cache on ignite
>   cacheRdd.savePairs(fianlLatestBaselineRDD)
> 
> println("xx=> " + xxx() +"\t " +
>  " xxx => " + xxx() + "\t " +
>  " cacheRdd.counter=> " + cacheRdd.count())
> }
> 
> 
> 
> }
> 3、the code is running on yarn successfully and I found that the ignite can't
> cache all the datas,and it discard some datas, such as
> 2016-08-11 11:28:00:es write invoked! count=10;totally totallyCounter= => 10
> cacheRdd.start.counter=> 0
> 2、cacheRdd.start.fianlLatestBaselineRDD.counter=> 10
> xxx.count=> 140   yyy.count => 10   cacheRdd.counter=> 5(need to be 10)
> ===
> 2016-08-11 11:28:48:write invoked! count= 9;totallyCounter= => 19
> cacheRdd.start.counter=> 5
> .count=> 126   yyy.count => 9   cacheRdd.counter=> 9(need to be 19)
> =
> 
> 
> Can anyone help me on this issues? thanks again
> 
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Embedded-mode-ignite-on-spark-tp6942.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread percent620

1) containers logs as below
 
1、[20:07:14] Ignite node started OK (id=a3a87e37)
[20:07:14] Topology snapshot [ver=1, servers=1, clients=0, CPUs=24,
heap=2.0GB]
[20:07:14] Topology snapshot [ver=2, servers=2, clients=0, CPUs=48,
heap=4.0GB]
[20:07:15] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
heap=6.0GB]
[20:07:16] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]

2、[20:07:13] Security status [authentication=off, tls/ssl=off]
[20:07:16] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]
[20:07:17] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[20:07:17] 
[20:07:17] Ignite node started OK (id=6c5ee58d)
[20:07:17] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]

3、[20:07:13] Security status [authentication=off, tls/ssl=off]
[20:07:15] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
heap=6.0GB]
[20:07:16] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]
[20:07:17] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[20:07:17] 
[20:07:17] Ignite node started OK (id=d5a9f244)
[20:07:17] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]

4、[20:07:15] Security status [authentication=off, tls/ssl=off]
[20:07:17] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[20:07:17] 
[20:07:17] Ignite node started OK (id=9c74f586)
[20:07:17] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]



2)spark-shell hangs there

3) I'm running spark-shell on driver machine NOT yarn cluster?

Thanks!!!




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-Spark-on-YARN-Deployment-tp6910p6979.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster node stopped

2016-08-11 Thread Vladislav Pyatkov

Hello,

1) It is my mistake. I mean what a log level set as DEBUG for the package
org.apache.ignite.spi.discovery.

2) It the cluster group (172.21.0.181 and 172.21.0.183) was segmented again
at the time?
I think problem of network will do not stable.

3) Unfortunately, in my opinion, this problem bounds with system settings,
but do not with Ignite version.
However upgrade version will be good idea.

*About segmentation:*

*1. Log file from each nodes (including GC log)*

*2. System monitoring from each nodes and during all time (using dstat -t
--top-mem -m -s -g -d --fs --top-io-adv). We are need make sure, which we
have not delay by reason of memory swapping or IO activity.*

*3. Network monitoring for all time . You can to do it through ping, as you
do it before.*

Please, attach all the logs as soon the issue is repeated.

On Thu, Aug 11, 2016 at 1:58 PM, suhuadong  wrote:

> hi,
> 1:How to add additional logger to the Discovery classes:
> org.apache.ignite.spi.discovery?
>
> 2:
>  NetWork is ok.
>  Before all server nodes stoped,I deploy shell script that  ping
> 172.21.0.181 from 172.21.0.183 and 172.21.0.183.
> log:
> 64 bytes from 172.21.0.181: icmp_seq=51251 ttl=64 time=0.141 ms 14:14:15
> 64 bytes from 172.21.0.181: icmp_seq=51296 ttl=64 time=0.196 ms 14:15:00
> 64 bytes from 172.21.0.181: icmp_seq=51297 ttl=64 time=0.160 ms 14:15:01
> 64 bytes from 172.21.0.181: icmp_seq=51298 ttl=64 time=0.199 ms 14:15:02
> 64 bytes from 172.21.0.181: icmp_seq=51299 ttl=64 time=0.205 ms 14:15:03
> 64 bytes from 172.21.0.181: icmp_seq=51300 ttl=64 time=0.191 ms 14:15:04
> 64 bytes from 172.21.0.181: icmp_seq=51301 ttl=64 time=0.200 ms 14:15:05
> 64 bytes from 172.21.0.181: icmp_seq=51302 ttl=64 time=0.190 ms 14:15:06
> 64 bytes from 172.21.0.181: icmp_seq=51303 ttl=64 time=0.195 ms 14:15:07
> 64 bytes from 172.21.0.181: icmp_seq=51304 ttl=64 time=0.209 ms 14:15:08
> 64 bytes from 172.21.0.181: icmp_seq=51305 ttl=64 time=0.204 ms 14:15:09
> 64 bytes from 172.21.0.181: icmp_seq=51306 ttl=64 time=0.208 ms 14:15:10
> 64 bytes from 172.21.0.181: icmp_seq=51307 ttl=64 time=0.206 ms 14:15:11
> 64 bytes from 172.21.0.181: icmp_seq=51308 ttl=64 time=0.231 ms 14:15:12
> 64 bytes from 172.21.0.181: icmp_seq=51309 ttl=64 time=0.251 ms 14:15:13
> 64 bytes from 172.21.0.181: icmp_seq=51310 ttl=64 time=0.213 ms 14:15:14
> 64 bytes from 172.21.0.181: icmp_seq=51311 ttl=64 time=0.240 ms 14:15:15
> 64 bytes from 172.21.0.181: icmp_seq=51312 ttl=64 time=0.250 ms 14:15:16
> 64 bytes from 172.21.0.181: icmp_seq=51313 ttl=64 time=0.227 ms 14:15:17
> 64 bytes from 172.21.0.181: icmp_seq=51314 ttl=64 time=0.236 ms 14:15:18
> 64 bytes from 172.21.0.181: icmp_seq=51315 ttl=64 time=0.253 ms 14:15:19
> 64 bytes from 172.21.0.181: icmp_seq=51316 ttl=64 time=0.138 ms 14:15:20
> 64 bytes from 172.21.0.181: icmp_seq=51317 ttl=64 time=0.139 ms 14:15:21
> 64 bytes from 172.21.0.181: icmp_seq=51318 ttl=64 time=0.180 ms 14:15:22
> 64 bytes from 172.21.0.181: icmp_seq=51319 ttl=64 time=0.131 ms 14:15:23
> 64 bytes from 172.21.0.181: icmp_seq=51320 ttl=64 time=0.187 ms 14:15:24
> 64 bytes from 172.21.0.181: icmp_seq=51321 ttl=64 time=0.134 ms 14:15:25
> 64 bytes from 172.21.0.181: icmp_seq=51322 ttl=64 time=0.132 ms 14:15:26
> 64 bytes from 172.21.0.181: icmp_seq=51323 ttl=64 time=0.133 ms 14:15:27
> 64 bytes from 172.21.0.181: icmp_seq=51324 ttl=64 time=0.153 ms 14:15:28
> 64 bytes from 172.21.0.181: icmp_seq=51325 ttl=64 time=0.172 ms 14:15:29
> 64 bytes from 172.21.0.181: icmp_seq=51326 ttl=64 time=0.170 ms 14:15:30
> 64 bytes from 172.21.0.181: icmp_seq=51327 ttl=64 time=0.172 ms 14:15:31
> 64 bytes from 172.21.0.181: icmp_seq=51328 ttl=64 time=0.170 ms 14:15:32
> 64 bytes from 172.21.0.181: icmp_seq=51329 ttl=64 time=0.175 ms 14:15:33
> 64 bytes from 172.21.0.181: icmp_seq=51330 ttl=64 time=0.169 ms 14:15:34
> 64 bytes from 172.21.0.181: icmp_seq=51331 ttl=64 time=0.191 ms 14:15:35
> 64 bytes from 172.21.0.181: icmp_seq=51332 ttl=64 time=0.171 ms 14:15:36
> 64 bytes from 172.21.0.181: icmp_seq=51333 ttl=64 time=0.192 ms 14:15:37
> 64 bytes from 172.21.0.181: icmp_seq=51334 ttl=64 time=0.190 ms 14:15:38
> 64 bytes from 172.21.0.181: icmp_seq=51335 ttl=64 time=0.188 ms 14:15:39
> 64 bytes from 172.21.0.181: icmp_seq=51336 ttl=64 time=0.189 ms 14:15:40
> 64 bytes from 172.21.0.181: icmp_seq=51337 ttl=64 time=0.179 ms 14:15:41
> 64 bytes from 172.21.0.181: icmp_seq=51338 ttl=64 time=0.175 ms 14:15:42
> 64 bytes from 172.21.0.181: icmp_seq=51339 ttl=64 time=0.171 ms 14:15:43
> 64 bytes from 172.21.0.181: icmp_seq=51340 ttl=64 time=0.146 ms 14:15:44
> 64 bytes from 172.21.0.181: icmp_seq=51341 ttl=64 time=0.136 ms 14:15:45
> 64 bytes from 172.21.0.181: icmp_seq=51342 ttl=64 time=0.124 ms 14:15:46
> 64 bytes from 172.21.0.181: icmp_seq=51343 ttl=64 time=0.130 ms 14:15:47
> 64 bytes from 172.21.0.181: icmp_seq=51344 ttl=64 time=0.136 ms 14:15:48
> 64 bytes from 172.21.0.181: icmp_seq=51345 ttl=64 time=0.129 ms 14:15:49
> 64 bytes

LOOK THORUGH THIS ERROR

2016-08-11 Thread Ravi Puri

java.lang.NoSuchMethodError:
org.hibernate.SessionFactory.openSession()Lorg/hibernate/Session;
at
org.apache.ignite.cache.store.hibernate.CacheHibernateStoreSessionListener.onSessionStart(CacheHibernateStoreSessionListener.java:178)
at
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.sessionInit0(GridCacheStoreManagerAdapter.java:818)
at
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:479)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:515)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.localLoadCache(IgniteCacheProxy.java:387)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5716)
at
org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheClosure.call(GridCacheAdapter.java:5663)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1789)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/LOOK-THORUGH-THIS-ERROR-tp6977.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Node authentication using security credentials

2016-08-11 Thread pragmaticbigdata

When you mention "Ignite has all the hooks in the code" I think you are
referring the the plugin support that ignite provides and the classes under
the package "org.apache.ignite.plugin.security".

What could be the reasons of having a security layer given that ignite would
be deployed on a private aws network (VPC)? I do not foresee a need of
having client authentication but just wanted to know your thoughts.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Node-authentication-using-security-credentials-tp6853p6976.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread Nikolai Tikhonov

Could you show logs from containers? spark-shell just hangs or print some
logs? Also are you sure that you have direct access to machine on which
running yarn cluster?

On Thu, Aug 11, 2016 at 3:43 PM, percent620  wrote:

> Hello, Nikolai,
> 1、
> Just updated configuration default-config.xm on
> /u01/XXX/apache-ignite-fabric-1.6.0-bin/config/default-config.xm
>
> 2）./hdfs dfs -put
> /u01/XXX/apache-ignite-fabric-1.6.0-bin/config/default-config.xm
> /ignite/release16/apache-ignite-fabric-1.6.0-bin/config/
>
>
>
> 3)
> scala> import org.apache.ignite.spark._
> import org.apache.ignite.spark._
>
> scala> import org.apache.ignite.configuration._
> import org.apache.ignite.configuration._
>
> scala> val ic = new IgniteContext[Integer, Integer](sc,
> "/u01/XXX/apache-ignite-fabric-1.6.0-bin/config/default-config.xml")
>
>
> it also hanging, 
>
> Can I miss some files to be changed? thanks!!!
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-for-Spark-on-YARN-Deployment-tp6910p6974.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread percent620

Hello, Nikolai,
1、
Just updated configuration default-config.xm on
/u01/XXX/apache-ignite-fabric-1.6.0-bin/config/default-config.xm

2）./hdfs dfs -put
/u01/XXX/apache-ignite-fabric-1.6.0-bin/config/default-config.xm
/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/



3)
scala> import org.apache.ignite.spark._
import org.apache.ignite.spark._

scala> import org.apache.ignite.configuration._
import org.apache.ignite.configuration._

scala> val ic = new IgniteContext[Integer, Integer](sc,
"/u01/XXX/apache-ignite-fabric-1.6.0-bin/config/default-config.xml")


it also hanging, 

Can I miss some files to be changed? thanks!!!




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-Spark-on-YARN-Deployment-tp6910p6974.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Cannot get cache through the REST API

2016-08-11 Thread Alexey Kuznetsov

Hi Yuci!

Could you please give more info about "Web Console monitoring
places too much overhead to the application, the CPU and memory wise
according to JVisualVM statistics" ?

Also, about "Wonder if there is any available tool like this?"

GridGain provide "In-Memory Computing Platform Built on Apache Ignite" and
it has Visor GUI - a monitoring tool.
See:
  http://www.gridgain.com/resources/download (30 days trial is available)
  and https://gridgain.readme.io/docs/visor-gui for more info about Visor
GUI.

Hope this help.

On Thu, Aug 11, 2016 at 6:15 PM, yucigou  wrote:

> Hi Val,
>
> As for the REST API, I don't have a particular favouritism towards it. I
> started to look at it because the Ignite Web Console agent uses it to
> collect statistics. It looks to me that the Ignite Web Console monitoring
> places too much overhead to the application, the CPU and memory wise
> according to JVisualVM statistics.
>
> Thanks for the suggestion. Yes, it is a good idea to create a client node
> for the management. Wonder if there is any available tool like this? I
> think
> this is a common use case, similar to what the Ignite Web Console
> monitoring
> does over the REST API.
>
> Thanks,
> Yuci
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Cannot-get-cache-through-the-REST-API-tp6806p6965.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread Nikolai Tikhonov

Hi,

You can use hdfs path as
hdfs://your_host:9000/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml.
Or you can just copy this config file on local disk. ;) You should use the
same configuration, but it can be different files with the same content.

On Thu, Aug 11, 2016 at 3:14 PM, percent620  wrote:

> Thanks Nikolai very much.
>
> As your request, and changed configuration
> /ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml
>
> but this file is hfs file
>
> 1)
> $./hdfs dfs -text
> /ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/u01/hadoop-2.6.0-cdh5.5.0/share/hadoop/common/
> lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/u01/hadoop-2.6.0-cdh5.5.0/share/hadoop/common/
> lib/tachyon-client-0.9.0-SNAPSHOT-jar-with-dependencies.jar!/org/slf4j/
> impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> 
>
>
>
> 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;>
>
>
>
>   
>   
>class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>   
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.
> TcpDiscoveryMulticastIpFinder"/>
>
> 
>
> 
>
> 
>
> 
> 
>
>
> 2) get the following error message as below
>
> scala> val ic = new IgniteContext[Integer, Integer](sc,
> "/ignite/release16/apache-ignite-fabric-1.6.0-bin/
> config/default-config.xml")
> class org.apache.ignite.IgniteCheckedException: Spring XML configuration
> path is invalid:
> /ignite/release16/apache-ignite-fabric-1.6.0-bin/
> config/default-config.xml.
> Note that this path should be either absolute or a relative local file
> system path, relative to META-INF in classpath or valid URL to IGNITE_HOME.
> at
> org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.
> java:3580)
> at
> org.apache.ignite.internal.IgnitionEx.loadConfigurations(
> IgnitionEx.java:678)
> at
> org.apache.ignite.internal.IgnitionEx.loadConfiguration(
> IgnitionEx.java:717)
> at
> org.apache.ignite.spark.IgniteContext$$anonfun$$lessinit$greater$2.apply(
> IgniteContext.scala:85)
> at
> org.apache.ignite.spark.IgniteContext$$anonfun$$lessinit$greater$2.apply(
> IgniteContext.scala:85)
> at org.apache.ignite.spark.Once.apply(IgniteContext.scala:198)
> at org.apache.ignite.spark.IgniteContext.ignite(
> IgniteContext.scala:138)
> at org.apache.ignite.spark.IgniteContext.(
> IgniteContext.scala:59)
> at org.apache.ignite.spark.IgniteContext.(
> IgniteContext.scala:85)
> at
> $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.
> (:33)
> at
> $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<
> init>(:38)
> at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(<
> console>:40)
> at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(<
> console>:42)
> at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:44)
> at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:46)
> at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:48)
> at $iwC$$iwC$$iwC$$iwC$$iwC.(:50)
> at $iwC$$iwC$$iwC$$iwC.(:52)
> at $iwC$$iwC$$iwC.(:54)
> at $iwC$$iwC.(:56)
> at $iwC.(:58)
> at (:60)
> at .(:64)
> at .()
> at .(:7)
> at .()
> at $print()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
> at
> org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
> at org.apache.spark.repl.SparkIMain.loadAndRunReq$1(
> SparkIMain.scala:840)
> at org.apache.spark.repl.SparkIMain.interpret(
> SparkIMain.scala:871)
> at org.apache.spark.repl.SparkIMain.interpret(
> SparkIMain.scala:819)
> at org.apache.spark.repl.SparkILoop.reallyInterpret$1(
> SparkILoop.scala:857)
> at
> org.apache.spark.repl.SparkILoop.interpretStartingWith(
> SparkILoop.scala:902)
> at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
> at

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread percent620

Thanks Nikolai very much.

As your request, and changed configuration
/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml

but this file is hfs file

1)
$./hdfs dfs -text
/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/u01/hadoop-2.6.0-cdh5.5.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/u01/hadoop-2.6.0-cdh5.5.0/share/hadoop/common/lib/tachyon-client-0.9.0-SNAPSHOT-jar-with-dependencies.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]




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;>

   

  
  
  
  
  
 


 


 


 




2) get the following error message as below

scala> val ic = new IgniteContext[Integer, Integer](sc,
"/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml")
class org.apache.ignite.IgniteCheckedException: Spring XML configuration
path is invalid:
/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml.
Note that this path should be either absolute or a relative local file
system path, relative to META-INF in classpath or valid URL to IGNITE_HOME.
at
org.apache.ignite.internal.util.IgniteUtils.resolveSpringUrl(IgniteUtils.java:3580)
at
org.apache.ignite.internal.IgnitionEx.loadConfigurations(IgnitionEx.java:678)
at
org.apache.ignite.internal.IgnitionEx.loadConfiguration(IgnitionEx.java:717)
at
org.apache.ignite.spark.IgniteContext$$anonfun$$lessinit$greater$2.apply(IgniteContext.scala:85)
at
org.apache.ignite.spark.IgniteContext$$anonfun$$lessinit$greater$2.apply(IgniteContext.scala:85)
at org.apache.ignite.spark.Once.apply(IgniteContext.scala:198)
at org.apache.ignite.spark.IgniteContext.ignite(IgniteContext.scala:138)
at org.apache.ignite.spark.IgniteContext.(IgniteContext.scala:59)
at org.apache.ignite.spark.IgniteContext.(IgniteContext.scala:85)
at
$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:33)
at
$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:38)
at 
$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:40)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:42)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:44)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:46)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:48)
at $iwC$$iwC$$iwC$$iwC$$iwC.(:50)
at $iwC$$iwC$$iwC$$iwC.(:52)
at $iwC$$iwC$$iwC.(:54)
at $iwC$$iwC.(:56)
at $iwC.(:58)
at (:60)
at .(:64)
at .()
at .(:7)
at .()
at $print()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
at
org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
at 
org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
at 
org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:857)
at
org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:902)
at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:814)
at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:657)
at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:665)
at
org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:670)
at
org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:997)
at

Re: Problem with installing ODBC Driver

2016-08-11 Thread austin solomon

I  am using Apache ignite 1.7.0-SNAPSHOT version.

My ignite cluster is running in CentOS server and I'm trying to connect to
it through ODBC driver from Windows PC.

My confguration is like below:






























































My problem here is, I could not able to get the data present in cache that i
have created, In Tableau i can see only the columns.

When i checked the cache using ignitevisorcmd.sh i got the following output:
Time of the snapshot: 08/09/16, 16:52:46
+=+
|  Name(@)  |Mode | Nodes | Entries (Heap / Off heap) |  
Hits|  Misses   |   Reads   |  Writes   |
+=+
| Organization(@c0) | PARTITIONED | 1 | min: 2 (2 / 0)| min:
0| min: 0| min: 0| min: 0|
|   | |   | avg: 2.00 (2.00 / 0.00)   | avg:
0.00 | avg: 0.00 | avg: 0.00 | avg: 0.00 |
|   | |   | max: 2 (2 / 0)| max:
0| max: 0| max: 0| max: 0|
+---+-+---+---+---+---+---+---+
| Person(@c1)   | PARTITIONED | 1 | min: 5 (5 / 0)| min:
0| min: 0| min: 0| min: 0|
|   | |   | avg: 5.00 (5.00 / 0.00)   | avg:
0.00 | avg: 0.00 | avg: 0.00 | avg: 0.00 |
|   | |   | max: 5 (5 / 0)| max:
0| max: 0| max: 0| max: 0|
+-+


screen shot:

 
 

Can you please help me what I am missing here.

Thanks



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Problem-with-installing-ODBC-Driver-tp5914p6970.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Understanding Grid Gain Multi-tenancy

2016-08-11 Thread pragmaticbigdata

Going through the  gridgain docs
  , I am trying to understand
how does the multi-tenancy feature work. With this enterprise feature one
could specify permissions at the cache level. The feature guarantees that a
tenant will never be able to read/update data for other tenants. I didn't
completely follow how does it achieve this. 
1. How is a tenant defined in ignite? Is it based on the number of
credentials defined? One bean of SecurityCredentials would map to a single
tenant?
2. A cache created by an authenticated client is linked to its
client(tenant) and no other client (differentiated by the credentials) is
allowed to access caches defined by other clients. Is that how it works?
3. How do we specify cache access permissions for dynamically created
caches? From the  code

 
snippets[1] it looks like the cache permissions are passed as an constructor
argument to the AuthenticationAclBasicProvider bean. This would mean that
the cache names would have to determined at the compile time and not
runtime. Am I missing something?

Thanks.

[1] -
https://github.com/gridgain/gridgain-advanced-examples/blob/e5c862f5c55db9ec7b9164854039354cc68816fa/config/security/security-base.xml



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Understanding-Grid-Gain-Multi-tenancy-tp6968.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: 答复: 答复: ignite 1.7 cache load problem

2016-08-11 Thread Alexey Kuznetsov

Hi, Kevin!

Actually code generation is a part of open source Ignite Web Console.
You may start Ignite Web Console locally and generate code.
See :
https://github.com/gridgain/apache-ignite/blob/master/modules/web-console/DEVNOTES.txt

On Thu, Aug 11, 2016 at 6:27 PM, Zhengqingzheng 
wrote:

> Hi  Alexey,
>
> Thank you.  And by the way , I cannot use console.gridgain.com to
> generate the java code.
>
> Due to security policies, I cannot upload anything from intranet to
> internet.
>
>
>
> Cheers,
>
> Kevin
>

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Cannot get cache through the REST API

2016-08-11 Thread yucigou

Hi Val,

As for the REST API, I don't have a particular favouritism towards it. I
started to look at it because the Ignite Web Console agent uses it to
collect statistics. It looks to me that the Ignite Web Console monitoring
places too much overhead to the application, the CPU and memory wise
according to JVisualVM statistics.

Thanks for the suggestion. Yes, it is a good idea to create a client node
for the management. Wonder if there is any available tool like this? I think
this is a common use case, similar to what the Ignite Web Console monitoring
does over the REST API.

Thanks,
Yuci



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cannot-get-cache-through-the-REST-API-tp6806p6965.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread Nikolai Tikhonov

Great! Ignite YARN cluster successfully started, but ignite spark shell
doesn't see server nodes. You need to configure IP finder, by default YARN
cluster using VmIpFinder, but ignite-spark MulticastIpFinder. Could you
change configuration for YARN cluster (IGNITE_XML_CONFIG=/ignite/
release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml) to the
following?



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;>











and also start IgniteContext with the same configuration?

val ic = new IgniteContext[Integer, Integer](sc,"path to configuration file"
)


On Thu, Aug 11, 2016 at 1:54 PM, percent620  wrote:

> 1、Adjusted cluster.properites as below
> $cat cluster16.properties
> # The number of nodes in the cluster.
> IGNITE_NODE_COUNT=4
> # The number of CPU Cores for each Apache Ignite node.
> IGNITE_RUN_CPU_PER_NODE=1
> # The number of Megabytes of RAM for each Apache Ignite node.
> IGNITE_MEMORY_PER_NODE=2048
> # The version ignite which will be run on nodes.
> IGNITE_VERSION=1.6.0
> IGNITE_WORK_DIR=/u01/yueyi/apache-ignite-fabric-1.6.0-bin/
> IGNITE_XML_CONFIG=/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/
> default-config.xml
> IGNITE_RELEASES_DIR=/ignite/release16/
> #IGNITE_USERS_LIBS=/u01/yueyi/apache-ignite-fabric-1.6.0-bin/libs/
> #IGNITE_HOSTNAME_CONSTRAINT=vmsecdomain010194070026.cm10
> IGNITE_PATH=/ignite/release16/apache-ignite-fabric-1.6.0-bin.zip
>
> 2、hdfs directory
> $./hdfs dfs -ls /ignite/release16
> drwxr-xr-x   - hbase hbase  0 2016-08-11 12:44
> /ignite/release16/apache-ignite-fabric-1.6.0-bin
> -rw-r--r--   3 hbase hbase  175866626 2016-08-11 18:31
> /ignite/release16/apache-ignite-fabric-1.6.0-bin.zip
>
> 3、yarn console
> INFO: Application master registered.
> Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
> INFO: Making request. Memory: 2,432, cpu 1.
> Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
> INFO: Making request. Memory: 2,432, cpu 1.
> Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
> INFO: Making request. Memory: 2,432, cpu 1.
> Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
> INFO: Making request. Memory: 2,432, cpu 1.
> 16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
> xx1:29077
> 16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
> xxx2:57492
> 16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
> xxx3:59929
> 16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
> xx4:23159
>
> 5、contain logs as below
> 1)
> [18:33:13] Security status [authentication=off, tls/ssl=off]
> [18:33:18] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [18:33:18]
> [18:33:18] Ignite node started OK (id=a060a3ee)
> [18:33:18] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
> heap=6.0GB]
> [18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
> heap=8.0GB]
>
> 2)[18:33:13] Security status [authentication=off, tls/ssl=off]
> [18:33:19] To start Console Management & Monitoring run
> ignitevisorcmd.{sh|bat}
> [18:33:19]
> [18:33:19] Ignite node started OK (id=5c8dfd50)
> [18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
> heap=8.0GB]
>
> 3)[18:33:12] Ignite node started OK (id=4e75d238)
> [18:33:12] Topology snapshot [ver=1, servers=1, clients=0, CPUs=24,
> heap=2.0GB]
> [18:33:14] Topology snapshot [ver=2, servers=2, clients=0, CPUs=48,
> heap=4.0GB]
> [18:33:17] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
> heap=6.0GB]
> [18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
> heap=8.0GB]
>
> 4)[18:33:14] Ignite node started OK (id=250fcb93)
> [18:33:14] Topology snapshot [ver=2, servers=2, clients=0, CPUs=48,
> heap=4.0GB]
> [18:33:17] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
> heap=6.0GB]
> [18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
> heap=8.0GB]
>
> faced issues=
>
> 1、spark-shell test
> ./spark-shell --jars
> /u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/ignite-core-1.
> 6.0.jar,/u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/
> ignite-spark/ignite-spark-1.6.0.jar,/u01/xxx/apache-ignite-
> hadoop-1.6.0-bin/libs/cache-api-1.0.0.jar,/u01/xxx/apache-
> ignite-hadoop-1.6.0-bin/libs/ignite-log4j/ignite-log4j-1.6.
> 0.jar,/u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/ignite-
> log4j/log4j-1.2.17.jar
> --packages
> org.apache.ignite:ignite-spark:1.6.0,org.apache.ignite:ignite-spring:1.6.0
>
> 2、SQL context available as sqlContext.
>
> scala> import org.apache.ignite.spark._
> import org.apache.ignite.spark._
>
> scala> import org.apache.ignite.configuration._
> import

Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread percent620

$cat default-config.xml




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;>





$cat example-default.xml





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








































127.0.0.1:47500..47509












--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-Spark-on-YARN-Deployment-tp6910p6963.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Cluster node stopped

2016-08-11 Thread suhuadong

hi,
1:How to add additional logger to the Discovery classes:
org.apache.ignite.spi.discovery?

2:
 NetWork is ok.
 Before all server nodes stoped,I deploy shell script that  ping
172.21.0.181 from 172.21.0.183 and 172.21.0.183.   
log:
64 bytes from 172.21.0.181: icmp_seq=51251 ttl=64 time=0.141 ms 14:14:15
64 bytes from 172.21.0.181: icmp_seq=51296 ttl=64 time=0.196 ms 14:15:00
64 bytes from 172.21.0.181: icmp_seq=51297 ttl=64 time=0.160 ms 14:15:01
64 bytes from 172.21.0.181: icmp_seq=51298 ttl=64 time=0.199 ms 14:15:02
64 bytes from 172.21.0.181: icmp_seq=51299 ttl=64 time=0.205 ms 14:15:03
64 bytes from 172.21.0.181: icmp_seq=51300 ttl=64 time=0.191 ms 14:15:04
64 bytes from 172.21.0.181: icmp_seq=51301 ttl=64 time=0.200 ms 14:15:05
64 bytes from 172.21.0.181: icmp_seq=51302 ttl=64 time=0.190 ms 14:15:06
64 bytes from 172.21.0.181: icmp_seq=51303 ttl=64 time=0.195 ms 14:15:07
64 bytes from 172.21.0.181: icmp_seq=51304 ttl=64 time=0.209 ms 14:15:08
64 bytes from 172.21.0.181: icmp_seq=51305 ttl=64 time=0.204 ms 14:15:09
64 bytes from 172.21.0.181: icmp_seq=51306 ttl=64 time=0.208 ms 14:15:10
64 bytes from 172.21.0.181: icmp_seq=51307 ttl=64 time=0.206 ms 14:15:11
64 bytes from 172.21.0.181: icmp_seq=51308 ttl=64 time=0.231 ms 14:15:12
64 bytes from 172.21.0.181: icmp_seq=51309 ttl=64 time=0.251 ms 14:15:13
64 bytes from 172.21.0.181: icmp_seq=51310 ttl=64 time=0.213 ms 14:15:14
64 bytes from 172.21.0.181: icmp_seq=51311 ttl=64 time=0.240 ms 14:15:15
64 bytes from 172.21.0.181: icmp_seq=51312 ttl=64 time=0.250 ms 14:15:16
64 bytes from 172.21.0.181: icmp_seq=51313 ttl=64 time=0.227 ms 14:15:17
64 bytes from 172.21.0.181: icmp_seq=51314 ttl=64 time=0.236 ms 14:15:18
64 bytes from 172.21.0.181: icmp_seq=51315 ttl=64 time=0.253 ms 14:15:19
64 bytes from 172.21.0.181: icmp_seq=51316 ttl=64 time=0.138 ms 14:15:20
64 bytes from 172.21.0.181: icmp_seq=51317 ttl=64 time=0.139 ms 14:15:21
64 bytes from 172.21.0.181: icmp_seq=51318 ttl=64 time=0.180 ms 14:15:22
64 bytes from 172.21.0.181: icmp_seq=51319 ttl=64 time=0.131 ms 14:15:23
64 bytes from 172.21.0.181: icmp_seq=51320 ttl=64 time=0.187 ms 14:15:24
64 bytes from 172.21.0.181: icmp_seq=51321 ttl=64 time=0.134 ms 14:15:25
64 bytes from 172.21.0.181: icmp_seq=51322 ttl=64 time=0.132 ms 14:15:26
64 bytes from 172.21.0.181: icmp_seq=51323 ttl=64 time=0.133 ms 14:15:27
64 bytes from 172.21.0.181: icmp_seq=51324 ttl=64 time=0.153 ms 14:15:28
64 bytes from 172.21.0.181: icmp_seq=51325 ttl=64 time=0.172 ms 14:15:29
64 bytes from 172.21.0.181: icmp_seq=51326 ttl=64 time=0.170 ms 14:15:30
64 bytes from 172.21.0.181: icmp_seq=51327 ttl=64 time=0.172 ms 14:15:31
64 bytes from 172.21.0.181: icmp_seq=51328 ttl=64 time=0.170 ms 14:15:32
64 bytes from 172.21.0.181: icmp_seq=51329 ttl=64 time=0.175 ms 14:15:33
64 bytes from 172.21.0.181: icmp_seq=51330 ttl=64 time=0.169 ms 14:15:34
64 bytes from 172.21.0.181: icmp_seq=51331 ttl=64 time=0.191 ms 14:15:35
64 bytes from 172.21.0.181: icmp_seq=51332 ttl=64 time=0.171 ms 14:15:36
64 bytes from 172.21.0.181: icmp_seq=51333 ttl=64 time=0.192 ms 14:15:37
64 bytes from 172.21.0.181: icmp_seq=51334 ttl=64 time=0.190 ms 14:15:38
64 bytes from 172.21.0.181: icmp_seq=51335 ttl=64 time=0.188 ms 14:15:39
64 bytes from 172.21.0.181: icmp_seq=51336 ttl=64 time=0.189 ms 14:15:40
64 bytes from 172.21.0.181: icmp_seq=51337 ttl=64 time=0.179 ms 14:15:41
64 bytes from 172.21.0.181: icmp_seq=51338 ttl=64 time=0.175 ms 14:15:42
64 bytes from 172.21.0.181: icmp_seq=51339 ttl=64 time=0.171 ms 14:15:43
64 bytes from 172.21.0.181: icmp_seq=51340 ttl=64 time=0.146 ms 14:15:44
64 bytes from 172.21.0.181: icmp_seq=51341 ttl=64 time=0.136 ms 14:15:45
64 bytes from 172.21.0.181: icmp_seq=51342 ttl=64 time=0.124 ms 14:15:46
64 bytes from 172.21.0.181: icmp_seq=51343 ttl=64 time=0.130 ms 14:15:47
64 bytes from 172.21.0.181: icmp_seq=51344 ttl=64 time=0.136 ms 14:15:48
64 bytes from 172.21.0.181: icmp_seq=51345 ttl=64 time=0.129 ms 14:15:49
64 bytes from 172.21.0.181: icmp_seq=51346 ttl=64 time=0.175 ms 14:15:50
64 bytes from 172.21.0.181: icmp_seq=51347 ttl=64 time=0.168 ms 14:15:51
64 bytes from 172.21.0.181: icmp_seq=51348 ttl=64 time=0.138 ms 14:15:52
64 bytes from 172.21.0.181: icmp_seq=51349 ttl=64 time=0.144 ms 14:15:53
64 bytes from 172.21.0.181: icmp_seq=51350 ttl=64 time=0.152 ms 14:15:54
64 bytes from 172.21.0.181: icmp_seq=51351 ttl=64 time=0.135 ms 14:15:55
64 bytes from 172.21.0.181: icmp_seq=51352 ttl=64 time=0.134 ms 14:15:56
64 bytes from 172.21.0.181: icmp_seq=51353 ttl=64 time=0.133 ms 14:15:57
64 bytes from 172.21.0.181: icmp_seq=51354 ttl=64 time=0.177 ms 14:15:58
64 bytes from 172.21.0.181: icmp_seq=51355 ttl=64 time=0.127 ms 14:15:59

3:Faced with the problem，I plan to upgrade ignite from 1.6 to 1.7。



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cluster-node-stopped-tp6608p6962.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread percent620

1、Adjusted cluster.properites as below
$cat cluster16.properties 
# The number of nodes in the cluster.
IGNITE_NODE_COUNT=4
# The number of CPU Cores for each Apache Ignite node.
IGNITE_RUN_CPU_PER_NODE=1
# The number of Megabytes of RAM for each Apache Ignite node.
IGNITE_MEMORY_PER_NODE=2048
# The version ignite which will be run on nodes.
IGNITE_VERSION=1.6.0
IGNITE_WORK_DIR=/u01/yueyi/apache-ignite-fabric-1.6.0-bin/
IGNITE_XML_CONFIG=/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml
IGNITE_RELEASES_DIR=/ignite/release16/
#IGNITE_USERS_LIBS=/u01/yueyi/apache-ignite-fabric-1.6.0-bin/libs/
#IGNITE_HOSTNAME_CONSTRAINT=vmsecdomain010194070026.cm10
IGNITE_PATH=/ignite/release16/apache-ignite-fabric-1.6.0-bin.zip

2、hdfs directory
$./hdfs dfs -ls /ignite/release16
drwxr-xr-x   - hbase hbase  0 2016-08-11 12:44
/ignite/release16/apache-ignite-fabric-1.6.0-bin
-rw-r--r--   3 hbase hbase  175866626 2016-08-11 18:31
/ignite/release16/apache-ignite-fabric-1.6.0-bin.zip

3、yarn console
INFO: Application master registered.
Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
INFO: Making request. Memory: 2,432, cpu 1.
Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
INFO: Making request. Memory: 2,432, cpu 1.
Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
INFO: Making request. Memory: 2,432, cpu 1.
Aug 11, 2016 6:32:57 PM org.apache.ignite.yarn.ApplicationMaster run
INFO: Making request. Memory: 2,432, cpu 1.
16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
xx1:29077
16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
xxx2:57492
16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
xxx3:59929
16/08/11 18:32:57 INFO impl.AMRMClientImpl: Received new token for :
xx4:23159

5、contain logs as below
1)
[18:33:13] Security status [authentication=off, tls/ssl=off]
[18:33:18] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[18:33:18] 
[18:33:18] Ignite node started OK (id=a060a3ee)
[18:33:18] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
heap=6.0GB]
[18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]

2)[18:33:13] Security status [authentication=off, tls/ssl=off]
[18:33:19] To start Console Management & Monitoring run
ignitevisorcmd.{sh|bat}
[18:33:19] 
[18:33:19] Ignite node started OK (id=5c8dfd50)
[18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]

3)[18:33:12] Ignite node started OK (id=4e75d238)
[18:33:12] Topology snapshot [ver=1, servers=1, clients=0, CPUs=24,
heap=2.0GB]
[18:33:14] Topology snapshot [ver=2, servers=2, clients=0, CPUs=48,
heap=4.0GB]
[18:33:17] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
heap=6.0GB]
[18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]

4)[18:33:14] Ignite node started OK (id=250fcb93)
[18:33:14] Topology snapshot [ver=2, servers=2, clients=0, CPUs=48,
heap=4.0GB]
[18:33:17] Topology snapshot [ver=3, servers=3, clients=0, CPUs=72,
heap=6.0GB]
[18:33:19] Topology snapshot [ver=4, servers=4, clients=0, CPUs=96,
heap=8.0GB]

faced issues=

1、spark-shell test
./spark-shell --jars
/u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/ignite-core-1.6.0.jar,/u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/ignite-spark/ignite-spark-1.6.0.jar,/u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/cache-api-1.0.0.jar,/u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/ignite-log4j/ignite-log4j-1.6.0.jar,/u01/xxx/apache-ignite-hadoop-1.6.0-bin/libs/ignite-log4j/log4j-1.2.17.jar
--packages
org.apache.ignite:ignite-spark:1.6.0,org.apache.ignite:ignite-spring:1.6.0

2、SQL context available as sqlContext.

scala> import org.apache.ignite.spark._
import org.apache.ignite.spark._

scala> import org.apache.ignite.configuration._
import org.apache.ignite.configuration._

scala> val ic = new IgniteContext[Integer, Integer](sc, () => new
IgniteConfiguration())




the spark-shell hang here

Thanks again




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-Spark-on-YARN-Deployment-tp6910p6961.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Starting Datagrid servers as partitions on same machine

2016-08-11 Thread Pavel Tupitsyn

This discussion has continued in Gitter.
There was some misunderstanding on how the cache data is stored.

On Thu, Aug 11, 2016 at 12:12 PM, Vladislav Pyatkov 
wrote:

> Hello,
>
> The property (GridName) is a name of Ignite instance within one JVM.
> In your case (one instance Ignite in one JVM) the property can by not
> innitialized (by default is null).
>
> Node collect to cluster by TCPDiscovery configuration, in the process
> GridName does not participate.
>
> On Thu, Aug 11, 2016 at 8:54 AM, mrinalkamboj  > wrote:
>
>> I am using .Net configuration with v1.6 to start multiple data grid
>> servers
>> as partitions on same machine / hardware. Following are the important
>> details:
>>
>> Aim is to run the Cache like *OrderCache* as a partitioned across multiple
>> ignite grids and thus run the concurrency tests on a partitioned
>> configuration
>>
>> *Important configuration details*:
>>
>>  > xmlns=http://ignite.apache.org/schema/dotnet/IgniteCon
>> figurationSection
>> gridName=b>myGrid1*">
>> 
>>   
>> 
>>   127.0.0.1:47500
>> 
>>   
>> 
>>
>> 
>>   OrderCache*"
>> cacheMode="*Partitioned*" startSize="104857600">
>> 
>>   > valueType="OrderEntity,ApacheIgnite">
>>   
>> 
>>   
>> 
>>
>> Following is the C# code I am using from void Main () to start the server:
>>
>>  static void Main(string[] args)
>> {
>>
>> // Fetch existing Ignite object or start using the application
>> configuration
>> var ignite = Ignition.TryGetIgnite("myGrid1") ??
>> Ignition.StartFromApplicationConfiguration();
>>
>>   Console.WriteLine("Press Any Key :");
>>   Console.Read();
>> }
>>
>> Now using Visual studio as I go about starting the servers by using *Start
>> without debugging*, following are the results:
>>
>> - Above configuration where the gridName="*myGrid1*"
>> Starts four servers, with following details:
>>
>> 1st Data grid Server
>>
>> [10:52:00] Ignite node started OK (id=72a489ca, grid=myGrid1)
>> [10:52:00] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4,
>> heap=3.5GB]
>> [10:52:10] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4,
>> heap=7.1GB]
>> [10:52:20] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4,
>> heap=11.0GB]
>>
>> 2nd Data grid server
>>
>> [10:52:11] Ignite node started OK (id=47774f75, grid=myGrid1)
>> [10:52:11] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4,
>> heap=7.1GB]
>> [10:52:20] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4,
>> heap=11.0GB]
>>
>> 3rd Data grid server
>>
>> [10:52:21] Ignite node started OK (id=849382eb, grid=myGrid1)
>> [10:52:21] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4,
>> heap=11.0GB]
>>
>> In case before each server start I change the gridname *grid=myGrid1*,
>> results are same as above just that it shows the name as appropriate.
>>
>> Now I am not sure, which one is correct, in fact if I change the
>> cacheMode="*Replicated*" , still the result is same, please provide, which
>> one is the correct, as I am confused about the internal design
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Starting-Datagrid-servers-as-partitions-on-
>> same-machine-tp6945.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Vladislav Pyatkov
>

Re: ignite 1.7 cache load problem

2016-08-11 Thread Konstantinov Pavel

Hi, Kevin

I was able to repeat your test and successfully load test data from Oracle
to cache on Ignite version 1.7.0

I generated my test project using web console (https://console.gridgain.com)
instead schema-import.

Note: you have to manually set the Key Field in the 'Domain model for cache
store' section on Model screen of the web console. Also you need manually
put oracle jdbc driver into 'jdbc-drivers' folder in the generated project.

You may find my project in the attachment.
To run use src\main\java\startup\ServerNodeCodeStartup.java

Hope this helps.

test-cluster-project.zip

  



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-1-7-cache-load-problem-tp6912p6959.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Why there are no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub?

2016-08-11 Thread Nikolai Tikhonov

Hi,

I've updated apache ignite images on docker hub. Thank you for your
attention.

On Sun, Aug 7, 2016 at 12:18 AM, zshamrock 
wrote:

> Why there is no official 1.6.0 and 1.7.0 ignite docker images on Docker Hub
> https://hub.docker.com/r/apacheignite/ignite/tags/?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Why-there-are-no-official-1-6-0-and-1-7-
> 0-ignite-docker-images-on-Docker-Hub-tp6832.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Clear the cached data?

2016-08-11 Thread Alisher Alimov

All 2 methods clear cache entries, but also IgniteCache#destroy delete cache 
meta info from all nodes and theoretically IgniteCache#clear will be faster to 
clean cache

With best regards
Alisher Alimov
alimovalis...@gmail.com




> On 11 авг. 2016 г., at 12:53, Alexey Kuznetsov  
> wrote:
> 
> Alisher, Ravi.
> 
> cache.clear() could take a lot of time in case of large grid / many entries.
> 
> Will cache.destroy() + ignite.getOrCreateCache(ccfg) - faster?
> 
> On Thu, Aug 11, 2016 at 4:39 PM, Alisher Alimov  > wrote:
> Hi!
> 
> IgniteCache#close doesn’t clear data by contract for non local caches
> 
> /**
>  * Closes this cache instance.
>  * 
>  * For local cache equivalent to {@link #destroy()}.
>  * For distributed caches, if called on clients, stops client cache, if 
> called on a server node,
>  * just closes this cache instance and does not destroy cache data.
>  * 
>  * After cache instance is closed another {@link IgniteCache} instance for 
> the same
>  * cache can be created using {@link Ignite#cache(String)} method.
>  */
> To clear cache data you must invoke IgniteCache#clear() it’s will clear cache 
> contents
> 
> Ignite doesn’t have method to clean data in all cache, but you can use
> 
> Ignite#cacheNames(cacheName -> Ignite#cache(cacheName).clear())
> 
> With best regards
> Alisher Alimov
> alimovalis...@gmail.com 
> 
> 
> 
> 
>> On 11 авг. 2016 г., at 10:14, Alexey Kuznetsov > > wrote:
>> 
>> Hi, Ravi.
>> 
>> You may close all caches and recreate them (from code).
>> Will this work in your case?
>> 
>> On Thu, Aug 11, 2016 at 2:04 PM, Ravi Puri > > wrote:
>> I want to clear all the data cached in server and client nodes. So how to do
>> it as i have to do it another class.
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://apache-ignite-users.70518.x6.nabble.com/Clear-the-cached-data-tp6946.html
>>  
>> 
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com 
>> .
>> 
>> 
>> 
>> --
>> Alexey Kuznetsov
>> GridGain Systems
>> www.gridgain.com 
> 
> 
> 
> 
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re:Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread percent620



Thanks very much for your quick response.!!!
I will attache contain logs for this issues.

Can you please also help me on this issues as below?
http://apache-ignite-users.70518.x6.nabble.com/Embedded-mode-ignite-on-spark-tt6942.html

 


At 2016-08-11 17:43:40, "Nikolai Tikhonov-2 [via Apache Ignite Users]" 
 wrote:

Hi,


Could you please provide logs from containers? 
Also IGNITE_PATH property incorrect. The property should contains path to 
apache ignite zip archive. For example: 
/ignite/apache-ignite-fabric-1.7.0-bin.zip. Also IGNITE_USERS_LIBS not needed 
here. The property need to use when you want deploy to cluster your own libs.


On Thu, Aug 11, 2016 at 7:54 AM, percent620 <[hidden email]> wrote:
Thanks vkulichenko's quick response.

Here is my detailed steps about how to deploy and integration spark with
ignite as below.

1、Followed this guidelines about how to deploy ignite-yarn application.


it's successfully and the log is displayed ok
==
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/u01/hbase/hadoop-2.5.0-cdh5.3.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/u01/hbase/tmp/nm-local-dir/usercache/hbase/appcache/application_1455892346017_5077/filecache/10/ignite-yarn.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
16/08/10 22:54:57 INFO impl.ContainerManagementProtocolProxy:
yarn.client.max-cached-nodemanagers-proxies : 0
Aug 10, 2016 10:54:58 PM org.apache.ignite.yarn.ApplicationMaster run
INFO: Application master registered.
Aug 10, 2016 10:54:58 PM org.apache.ignite.yarn.ApplicationMaster run
INFO: Making request. Memory: 2,432, cpu 1.
Aug 10, 2016 10:54:58 PM org.apache.ignite.yarn.ApplicationMaster run
INFO: Making request. Memory: 2,432, cpu 1.
16/08/10 22:54:59 INFO impl.AMRMClientImpl: Received new token for :
vmsecdomain010194062066.cm10:61362
16/08/10 22:54:59 INFO impl.AMRMClientImpl: Received new token for :
vmsecdomain010194062042.cm10:42077
Aug 10, 2016 10:54:59 PM org.apache.ignite.yarn.ApplicationMaster
onContainersAllocated
INFO: Launching container: container_1455892346017_5077_02_02.
16/08/10 22:54:59 INFO impl.ContainerManagementProtocolProxy: Opening proxy
: vmsecdomain010194062066.cm10:61362
Aug 10, 2016 10:54:59 PM org.apache.ignite.yarn.ApplicationMaster
onContainersAllocated
INFO: Launching container: container_1455892346017_5077_02_03.
16/08/10 22:54:59 INFO impl.ContainerManagementProtocolProxy: Opening proxy
: vmsecdomain010194062042.cm10:42077
Aug 10, 2016 10:55:08 PM org.apache.ignite.yarn.ApplicationMaster
onContainersCompleted
INFO: Container completed. Container id:
container_1455892346017_5077_02_02. State: COMPLETE.
Aug 10, 2016 10:55:09 PM org.apache.ignite.yarn.ApplicationMaster
onContainersCompleted
INFO: Container completed. Container id:
container_1455892346017_5077_02_03. State: COMPLETE.


2、downloaded this apache-ignite-fabric-1.6.0-bin.zip and unzip this file to
the /u01/XXX/apache-ignite-fabric-1.6.0-bin directory.

3、cluster16.properis content is as below
$cat cluster16.properties
# The number of nodes in the cluster.
IGNITE_NODE_COUNT=2
# The number of CPU Cores for each Apache Ignite node.
IGNITE_RUN_CPU_PER_NODE=1
# The number of Megabytes of RAM for each Apache Ignite node.
IGNITE_MEMORY_PER_NODE=2048
# The version ignite which will be run on nodes.
IGNITE_VERSION=1.6.0
IGNITE_WORK_DIR=/u01/XXX/apache-ignite-fabric-1.6.0-bin/
IGNITE_XML_CONFIG=/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/default-config.xml
IGNITE_RELEASES_DIR=/ignite/release16/
IGNITE_USERS_LIBS=/u01/XXX/apache-ignite-fabric-1.6.0-bin/libs/
IGNITE_PATH=/ignite/release16/


hdfs directory is as below
===
./hdfs dfs -ls /ignite/
drwxr-xr-x   - hbase hbase  0 2016-08-10 17:07 /ignite/release16
drwxr-xr-x   - hbase hbase  0 2016-08-02 06:25 /ignite/releases
drwxr-xr-x   - hbase hbase  0 2016-08-10 17:24 /ignite/workdir
-rw-r--r--   3 hbase hbase   27710331 2016-08-10 17:04 /ignite/yarn
=
$./hdfs dfs -ls /ignite/release16
drwxr-xr-x   - hbase hbase  0 2016-08-11 12:44
/ignite/release16/apache-ignite-fabric-1.6.0-bin

=

4、Running spark code on yarn and the code is as below
val igniteContext = new IgniteContext[String, BaseLine](sc,() => new
IgniteConfiguration())


the code is hanging on this and i think that this client can't connect this
server

5、from yarn console and found the following error message
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in

Re: Clear the cached data?

2016-08-11 Thread Alexey Kuznetsov

Alisher, Ravi.

cache.clear() could take a lot of time in case of large grid / many entries.

Will cache.destroy() + ignite.getOrCreateCache(ccfg) - faster?

On Thu, Aug 11, 2016 at 4:39 PM, Alisher Alimov 
wrote:

> Hi!
>
> IgniteCache#close doesn’t clear data by contract for non local caches
>
> /**
>  * Closes this cache instance.
>  * 
>  * For local cache equivalent to {@link #destroy()}.
>  * For distributed caches, if called on clients, stops client cache, if 
> called on a server node,
>  * just closes this cache instance and does not destroy cache data.
>  * 
>  * After cache instance is closed another {@link IgniteCache} instance for 
> the same
>  * cache can be created using {@link Ignite#cache(String)} method.
>  */
>
> To clear cache data you must invoke IgniteCache#clear() it’s will clear
> cache contents
>
> Ignite doesn’t have method to clean data in all cache, but you can use
>
> Ignite#cacheNames(cacheName -> Ignite#cache(cacheName).clear())
>
> With best regards
> Alisher Alimov
> alimovalis...@gmail.com
>
>
>
>
> On 11 авг. 2016 г., at 10:14, Alexey Kuznetsov 
> wrote:
>
> Hi, Ravi.
>
> You may close all caches and recreate them (from code).
> Will this work in your case?
>
> On Thu, Aug 11, 2016 at 2:04 PM, Ravi Puri 
> wrote:
>
>> I want to clear all the data cached in server and client nodes. So how to
>> do
>> it as i have to do it another class.
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Clear-the-cached-data-tp6946.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com
>> .
>>
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
>
>


-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Ignite for Spark on YARN Deployment

2016-08-11 Thread Nikolai Tikhonov

Hi,

Could you please provide logs from containers?
Also IGNITE_PATH property incorrect. The property should contains path to
apache ignite zip archive. For example:
/ignite/apache-ignite-fabric-1.7.0-bin.zip.
Also IGNITE_USERS_LIBS not needed here. The property need to use when you
want deploy to cluster your own libs.

On Thu, Aug 11, 2016 at 7:54 AM, percent620  wrote:

> Thanks vkulichenko's quick response.
>
> Here is my detailed steps about how to deploy and integration spark with
> ignite as below.
>
> 1、Followed this guidelines about how to deploy ignite-yarn application.
>  >
>
> it's successfully and the log is displayed ok
> ==
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/u01/hbase/hadoop-2.5.0-cdh5.3.0/share/hadoop/
> common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/
> StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/u01/hbase/tmp/nm-local-dir/usercache/hbase/
> appcache/application_1455892346017_5077/filecache/
> 10/ignite-yarn.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> 16/08/10 22:54:57 INFO impl.ContainerManagementProtocolProxy:
> yarn.client.max-cached-nodemanagers-proxies : 0
> Aug 10, 2016 10:54:58 PM org.apache.ignite.yarn.ApplicationMaster run
> INFO: Application master registered.
> Aug 10, 2016 10:54:58 PM org.apache.ignite.yarn.ApplicationMaster run
> INFO: Making request. Memory: 2,432, cpu 1.
> Aug 10, 2016 10:54:58 PM org.apache.ignite.yarn.ApplicationMaster run
> INFO: Making request. Memory: 2,432, cpu 1.
> 16/08/10 22:54:59 INFO impl.AMRMClientImpl: Received new token for :
> vmsecdomain010194062066.cm10:61362
> 16/08/10 22:54:59 INFO impl.AMRMClientImpl: Received new token for :
> vmsecdomain010194062042.cm10:42077
> Aug 10, 2016 10:54:59 PM org.apache.ignite.yarn.ApplicationMaster
> onContainersAllocated
> INFO: Launching container: container_1455892346017_5077_02_02.
> 16/08/10 22:54:59 INFO impl.ContainerManagementProtocolProxy: Opening
> proxy
> : vmsecdomain010194062066.cm10:61362
> Aug 10, 2016 10:54:59 PM org.apache.ignite.yarn.ApplicationMaster
> onContainersAllocated
> INFO: Launching container: container_1455892346017_5077_02_03.
> 16/08/10 22:54:59 INFO impl.ContainerManagementProtocolProxy: Opening
> proxy
> : vmsecdomain010194062042.cm10:42077
> Aug 10, 2016 10:55:08 PM org.apache.ignite.yarn.ApplicationMaster
> onContainersCompleted
> INFO: Container completed. Container id:
> container_1455892346017_5077_02_02. State: COMPLETE.
> Aug 10, 2016 10:55:09 PM org.apache.ignite.yarn.ApplicationMaster
> onContainersCompleted
> INFO: Container completed. Container id:
> container_1455892346017_5077_02_03. State: COMPLETE.
>
>
> 2、downloaded this apache-ignite-fabric-1.6.0-bin.zip and unzip this file
> to
> the /u01/XXX/apache-ignite-fabric-1.6.0-bin directory.
>
> 3、cluster16.properis content is as below
> $cat cluster16.properties
> # The number of nodes in the cluster.
> IGNITE_NODE_COUNT=2
> # The number of CPU Cores for each Apache Ignite node.
> IGNITE_RUN_CPU_PER_NODE=1
> # The number of Megabytes of RAM for each Apache Ignite node.
> IGNITE_MEMORY_PER_NODE=2048
> # The version ignite which will be run on nodes.
> IGNITE_VERSION=1.6.0
> IGNITE_WORK_DIR=/u01/XXX/apache-ignite-fabric-1.6.0-bin/
> IGNITE_XML_CONFIG=/ignite/release16/apache-ignite-fabric-1.6.0-bin/config/
> default-config.xml
> IGNITE_RELEASES_DIR=/ignite/release16/
> IGNITE_USERS_LIBS=/u01/XXX/apache-ignite-fabric-1.6.0-bin/libs/
> IGNITE_PATH=/ignite/release16/
>
>
> hdfs directory is as below
> ===
> ./hdfs dfs -ls /ignite/
> drwxr-xr-x   - hbase hbase  0 2016-08-10 17:07 /ignite/release16
> drwxr-xr-x   - hbase hbase  0 2016-08-02 06:25 /ignite/releases
> drwxr-xr-x   - hbase hbase  0 2016-08-10 17:24 /ignite/workdir
> -rw-r--r--   3 hbase hbase   27710331 2016-08-10 17:04 /ignite/yarn
> =
> $./hdfs dfs -ls /ignite/release16
> drwxr-xr-x   - hbase hbase  0 2016-08-11 12:44
> /ignite/release16/apache-ignite-fabric-1.6.0-bin
>
> =
>
> 4、Running spark code on yarn and the code is as below
> val igniteContext = new IgniteContext[String, BaseLine](sc,() => new
> IgniteConfiguration())
>
>
> the code is hanging on this and i think that this client can't connect this
> server
>
> 5、from yarn console and found the following error message
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/u01/hbase/hadoop-2.5.0-cdh5.3.0/share/hadoop/
> common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/
> StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/u01/hbase/tmp/nm-local-dir/usercache/hbase/
>

Re: Clear the cached data?

2016-08-11 Thread Alisher Alimov

Hi!

IgniteCache#close doesn’t clear data by contract for non local caches

/**
 * Closes this cache instance.
 * 
 * For local cache equivalent to {@link #destroy()}.
 * For distributed caches, if called on clients, stops client cache, if called 
on a server node,
 * just closes this cache instance and does not destroy cache data.
 * 
 * After cache instance is closed another {@link IgniteCache} instance for the 
same
 * cache can be created using {@link Ignite#cache(String)} method.
 */
To clear cache data you must invoke IgniteCache#clear() it’s will clear cache 
contents

Ignite doesn’t have method to clean data in all cache, but you can use

Ignite#cacheNames(cacheName -> Ignite#cache(cacheName).clear())

With best regards
Alisher Alimov
alimovalis...@gmail.com

> On 11 авг. 2016 г., at 10:14, Alexey Kuznetsov  
> wrote:
> 
> Hi, Ravi.
> 
> You may close all caches and recreate them (from code).
> Will this work in your case?
> 
> On Thu, Aug 11, 2016 at 2:04 PM, Ravi Puri  > wrote:
> I want to clear all the data cached in server and client nodes. So how to do
> it as i have to do it another class.
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-users.70518.x6.nabble.com/Clear-the-cached-data-tp6946.html
>  
> 
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> 
> 
> 
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com 

signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Starting Datagrid servers as partitions on same machine

2016-08-11 Thread Vladislav Pyatkov

Hello,

The property (GridName) is a name of Ignite instance within one JVM.
In your case (one instance Ignite in one JVM) the property can by not
innitialized (by default is null).

Node collect to cluster by TCPDiscovery configuration, in the process
GridName does not participate.

On Thu, Aug 11, 2016 at 8:54 AM, mrinalkamboj 
wrote:

> I am using .Net configuration with v1.6 to start multiple data grid servers
> as partitions on same machine / hardware. Following are the important
> details:
>
> Aim is to run the Cache like *OrderCache* as a partitioned across multiple
> ignite grids and thus run the concurrency tests on a partitioned
> configuration
>
> *Important configuration details*:
>
>   xmlns=http://ignite.apache.org/schema/dotnet/
> IgniteConfigurationSection
> gridName=b>myGrid1*">
> 
>   
> 
>   127.0.0.1:47500
> 
>   
> 
>
> 
>   OrderCache*"
> cacheMode="*Partitioned*" startSize="104857600">
> 
>valueType="OrderEntity,ApacheIgnite">
>   
> 
>   
> 
>
> Following is the C# code I am using from void Main () to start the server:
>
>  static void Main(string[] args)
> {
>
> // Fetch existing Ignite object or start using the application
> configuration
> var ignite = Ignition.TryGetIgnite("myGrid1") ??
> Ignition.StartFromApplicationConfiguration();
>
>   Console.WriteLine("Press Any Key :");
>   Console.Read();
> }
>
> Now using Visual studio as I go about starting the servers by using *Start
> without debugging*, following are the results:
>
> - Above configuration where the gridName="*myGrid1*"
> Starts four servers, with following details:
>
> 1st Data grid Server
>
> [10:52:00] Ignite node started OK (id=72a489ca, grid=myGrid1)
> [10:52:00] Topology snapshot [ver=1, servers=1, clients=0, CPUs=4,
> heap=3.5GB]
> [10:52:10] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4,
> heap=7.1GB]
> [10:52:20] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4,
> heap=11.0GB]
>
> 2nd Data grid server
>
> [10:52:11] Ignite node started OK (id=47774f75, grid=myGrid1)
> [10:52:11] Topology snapshot [ver=2, servers=2, clients=0, CPUs=4,
> heap=7.1GB]
> [10:52:20] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4,
> heap=11.0GB]
>
> 3rd Data grid server
>
> [10:52:21] Ignite node started OK (id=849382eb, grid=myGrid1)
> [10:52:21] Topology snapshot [ver=3, servers=3, clients=0, CPUs=4,
> heap=11.0GB]
>
> In case before each server start I change the gridname *grid=myGrid1*,
> results are same as above just that it shows the name as appropriate.
>
> Now I am not sure, which one is correct, in fact if I change the
> cacheMode="*Replicated*" , still the result is same, please provide, which
> one is the correct, as I am confused about the internal design
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Starting-Datagrid-servers-as-
> partitions-on-same-machine-tp6945.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Vladislav Pyatkov

Re: yarn deployment

2016-08-11 Thread Nikolai Tikhonov

Val,

Yes, you are right. For example: /ignite/apache-ignite-fabric-1.7.0-bin.zip

On Thu, Aug 11, 2016 at 2:16 AM, vkulichenko 
wrote:

> To my knowledge you can upload the ZIP file and provide the path to it. No
> need to unzip it manually.
>
> Nikolai, can you please confirm?
>
> -Val
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/yarn-deployment-tp6843p6939.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Ignite 1.7 doesn't play along with ignite-spatial 1.2-incubating

2016-08-11 Thread WhiteAncient

Is it that I am using the wrong library somewhere?

I have looked around but can't find any newer that has anything to do with
this.

The interesting row is:
class org.apache.ignite.internal.processors.query.h2.opt.GridH2SpatialIndex
overrides final method close.


The full stacktrace is this: 

class org.apache.ignite.IgniteCheckedException: Failed to register query
type: TypeDescriptor [name=GridInstanceSpatialPoint, fields={mc=class
java.lang.Long, entity=class java.lang.Long, id=class java.util.UUID,
xyz=class com.vividsolutions.jts.geom.Point, inRelationTo=class
java.util.UUID, inRelationToType=class java.lang.Short,
referenceSystem=class java.util.UUID},
indexes={inRelationTo_idx=IndexDescriptor [type=SORTED],
entity_idx=IndexDescriptor [type=SORTED], id_idx=IndexDescriptor
[type=SORTED], mc_idx=IndexDescriptor [type=SORTED],
inRelationToType_idx=IndexDescriptor [type=SORTED],
referenceSystem_idx=IndexDescriptor [type=SORTED], xyz_idx=IndexDescriptor
[type=GEO_SPATIAL]}, fullTextIdx=null, keyCls=class java.util.UUID,
valCls=class java.lang.Object, valTextIdx=false, affKey=null,
registered=false]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1302)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:313)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:483)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1055)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStart(GridCacheProcessor.java:802)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:930)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1739)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1589)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:964)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:850)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:769)
at org.apache.ignite.Ignition.start(Ignition.java:372)
at com.xxx$.(xxx.scala) /* my classes */
at sun.reflect.GeneratedConstructorAccessor21.newInstance(Unknown 
Source)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.lang.Class.newInstance(Class.java:442)
at
org.eclipse.jetty.server.handler.ContextHandler$Context.createInstance(ContextHandler.java:2370)
at
org.eclipse.jetty.servlet.ServletContextHandler$Context.createServlet(ServletContextHandler.java:1166)
at
org.eclipse.jetty.servlet.ServletHolder.newInstance(ServletHolder.java:1195)
at
org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:584)
at
org.eclipse.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:468)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:778)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at
org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:224)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at
org.eclipse.jetty.server.handler.ContextHandler.__doHandle(ContextHandler.java:1125)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:497)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:313)
at

Re: 答复: ignite 1.7 cache load problem

2016-08-11 Thread Alexey Kuznetsov

Hi, Kevin!

We a looking into your example.

Meanwhile, could you please generate jdbc mapping NOT via the schema-import
util, BUT with Web Console: https://console.gridgain.com/ ?
Go to Web Console, register, create cluster, go to "Model" screen and
import data from your Oracle DB.
After that go to Summary page and download project that will contain
pom.xml, configs and java classes.
After that change version in pom.xml to 1.7.0 and open project in IDE or
build with Maven.

Web Console has more advanced generation capabilities that schema-import
util.

Thanks.

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Clear the cached data?

2016-08-11 Thread Alexey Kuznetsov

Hi, Ravi.

You may close all caches and recreate them (from code).
Will this work in your case?

On Thu, Aug 11, 2016 at 2:04 PM, Ravi Puri 
wrote:

> I want to clear all the data cached in server and client nodes. So how to
> do
> it as i have to do it another class.
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Clear-the-cached-data-tp6946.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Clear the cached data?

2016-08-11 Thread Ravi Puri

I want to clear all the data cached in server and client nodes. So how to do
it as i have to do it another class.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Clear-the-cached-data-tp6946.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

46 matches

Mail list logo