Re: Ignite in docker (Native Persistence)

[Nikolai Tikhonov]

Hello!

Yes, sure! I'll investigate this question and update our doc.

On Thu, Dec 7, 2017 at 9:57 AM, Denis Magda  wrote:

> Nick,
>
> As one of Ignite docker maintainers, could you please investigate one how
> to map Ignite persistence to docker volumes:
> https://docs.docker.com/engine/admin/volumes/volumes/#
> use-a-read-only-volume
>
> and update the docker documentation:
> https://apacheignite.readme.io/docs/docker-deployment
>
> —
> Denis
>
> On Dec 1, 2017, at 8:40 AM, afedotov  wrote:
>
> Hi,
>
> You need to create volumes and map them to the ${IGNITE_HOME}/work/db or
> any
> other path that
> you might have specified via setPersistentStorePath. These volumes should
> outlive the Ignite containers
> and thus it will be possible to reuse them on restart.
>
> It's worth trying docker-compose, docker-swarm or kubernetes, depending on
> your needs.
> For example, Kubernetes provides a wide variety of volume options
> https://kubernetes.io/docs/concepts/storage/volumes/
>
>
> Has anyone use Ignite Native Persistence with Docker?
> Is there a solution on how to map the Volume dynamically? And how about
> when
> you restart the whole cluster, how does it maps all volumes?
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
>

Re: Ignite Logger & logging file config output

[Nikolai Tikhonov]

Alexey,

Looks cool and helpful! I understand correctly that improvement is
implemented for all type of loggers which Ignite supports?

On Fri, Dec 1, 2017 at 5:18 PM, Alexey Popov  wrote:

> Hi Denis,
>
> https://issues.apache.org/jira/browse/IGNITE-6971
>
> Sample quite=true output:
>
> [17:16:41]__  
> [17:16:41]   /  _/ ___/ |/ /  _/_  __/ __/
> [17:16:41]  _/ // (7 7// /  / / / _/
> [17:16:41] /___/\___/_/|_/___/ /_/ /___/
> [17:16:41]
> [17:16:41] ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
> [17:16:41] 2017 Copyright(C) Apache Software Foundation
> [17:16:41]
> [17:16:41] Ignite documentation: http://ignite.apache.org
> [17:16:41]
> [17:16:41] Quiet mode.
> [17:16:41]   ^-- Logging to file 'C:\incubator-ignite\work\log\
> ignite-7317b109.log'
> [17:16:41]   ^-- Logging by 'Log4JLogger [quiet=true,
> config=/C:/incubator-ignite/config/ignite-log4j.xml]'
> [17:16:41]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-v" to ignite.{sh|bat}
> [17:16:41]
> [17:16:41] OS: Windows 10 10.0 amd64
> [17:16:41] VM information: Java(TM) SE Runtime Environment 1.8.0_141-b15
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
> [17:16:41] Initial heap size is 254MB (should be no less than 512MB, use
> -Xms512m -Xmx512m).
> [17:16:41] Configured plugins:
> [17:16:41]   ^-- None
> [17:16:41]
>
> Sample verbose output:
>
> >>>__  
> >>>   /  _/ ___/ |/ /  _/_  __/ __/
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/
> >>>
> >>> ver. 2.4.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2017 Copyright(C) Apache Software Foundation
> >>>
> >>> Ignite documentation: http://ignite.apache.org
>
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Config
> URL: n/a
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] Daemon
> mode: off
> 2017-12-01T17:06:49,403][INFO ][main][IgniteKernal%verboseLogGrid] OS:
> Windows 10 10.0 amd64
> 2017-12-01T17:06:49,404][INFO ][main][IgniteKernal%verboseLogGrid] OS
> user: gridgain
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] PID:
> 5984
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid]
> Language runtime: Java Platform API Specification ver. 1.8
> 2017-12-01T17:06:49,408][INFO ][main][IgniteKernal%verboseLogGrid] VM
> information: Java(TM) SE Runtime Environment 1.8.0_141-b15 Oracle
> Corporation Java HotSpot(TM) 64-Bit Server VM 25.141-b15
> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] VM
> total memory: 3.5GB
> 2017-12-01T17:06:49,409][INFO ][main][IgniteKernal%verboseLogGrid] Remote
> Management [restart: off, REST: off, JMX (remote: off)]
> 2017-12-01T17:06:49,416][INFO ][main][IgniteKernal%verboseLogGrid]
> Logger: Log4J2Logger [quiet=false, config=C:\incubator-ignite\
> modules\core\src\test\config\log4j2-verbose-test.xml]
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid]
> IGNITE_HOME=C:\incubator-ignite
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] VM
> arguments: [-ea, -Didea.test.cyclic.buffer.size=1048576,
> -javaagent:C:\Program Files\JetBrains\IntelliJ IDEA Community Edition
> 2017.2.5\lib\idea_rt.jar=64660:C:\Program Files\JetBrains\IntelliJ IDEA
> Community Edition 2017.2.5\bin, -Dfile.encoding=UTF-8]
> 2017-12-01T17:06:49,417][INFO ][main][IgniteKernal%verboseLogGrid] System
> cache's DataRegion size is configured to 40 MB. Use
> DataStorageConfiguration.systemCacheMemorySize property to change the
> setting.
> 2017-12-01T17:06:49,427][INFO ][main][IgniteKernal%verboseLogGrid]
> Configured caches [in 'sysMemPlc' dataRegion: ['ignite-sys-cache']]
> 2017-12-01T17:06:49,430][WARN ][pub-#19%verboseLogGrid%][GridDiagnostic]
> This operating system has been tested less rigorously: Windows 10 10.0
> amd64. Our team will appreciate the feedback if you experience any problems
> running ignite in this environment.
> 2017-12-01T17:06:49,436][INFO ][main][IgniteKernal%verboseLogGrid] 3-rd
> party licenses can be found at: C:\incubator-ignite\libs\licenses
>
> Thank you,
> Alexey
>
> From: Denis Magda
> Sent: Tuesday, November 21, 2017 2:01 AM
> To: dev@ignite.apache.org
> Subject: Re: Ignite Logger & logging file config output
>
> Good point. Could you create a ticket and probably contribute this
> improvement?
>
> —
> Denis
>
> > On Nov 20, 2017, at 3:12 AM, Alexey Popov  wrote:
> >
> > Hi Igniters,
> >
> > Could you please advise why Ignite does not indicate
> > 1) the logger type it uses
> > 2) the logger configuration file (name) it applies
> > during startup?
> >
> > Can we add such output to IgniteLogger implementations?
> >
> > Thanks,
> > Alexey
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
>
>

Re: Confusing slf4j error messages

[Nikolai Tikhonov]

Hello Alexey!

If we exclude this dependency, which logger will be used by spring
framework?

On Thu, Nov 16, 2017 at 2:35 PM, Alexey Popov  wrote:

> Hi Igniters,
>
> Ignite examples and Ignite itself with some configurations prints out
> annoying messages related to slf4j:
>
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
>
> The reason for these messages is inside
> org.springframework.data:spring-data-commons. It adds a dependency to
> jcl-over-slf4j that "activates" slf4j. slf4j then tries to find
> slf4j-TO-SOMELOGGER to forward all messages to SOMELOGGER. Actually, it
> does
> not result in any issues with Ignite logging itself, it just confusing
> Ignite users.
>
> So, there are two options here to avoid these annoying messages:
> 1. exclude jcl-over-slf4j dependency from spring-data-commons in Ignite
> .pom
> files
> 2. add slf4j-TO-SOMELOGGER (for instance, slf4j-log4j12 for log4j, or
> slf4j-simple) dependency
>
> Please advice on a better solution here.
>
> Thank you,
> Alexey
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: ignite 2.3.0 docker image contains 2.2.0 files.

[Nikolai Tikhonov]

Good catch, thank you!

The latest image contains 2.3.0 (docker pull apacheignite/ignite) but image
with 2.3.0 tag contains binary files for 2.2.0 version. I've fixed it.

On Fri, Nov 3, 2017 at 8:13 AM, Denis Magda  wrote:

> Nick, Vovan,
>
> Have we really upgraded docker and the other images to 2.3?
>
> —
> Denis
>
> Begin forwarded message:
>
> *From: *bjason 
> *Subject: **ignite 2.3.0 docker image contains 2.2.0 files.*
> *Date: *November 2, 2017 at 3:37:34 PM PDT
> *To: *u...@ignite.apache.org
> *Reply-To: *u...@ignite.apache.org
>
>
>
> ignite 2.3.0 docker image contains 2.2.0 files. Please check.
>
> $ docker pull apacheignite/ignite:2.3.0
> 2.3.0: Pulling from apacheignite/ignite
> 3e17c6eae66c: Pull complete
> 74d44b20f851: Pull complete
> a156217f3fa4: Pull complete
> 4a1ed13b6faa: Pull complete
> 77980e5d0a6d: Pull complete
> 5458607a81d3: Pull complete
> e34cf8338f42: Pull complete
> 2f3d3da5c56e: Pull complete
> 2ade7a861e3f: Pull complete
> 686e6ce078d5: Pull complete
> f1d36075868f: Pull complete
> 2131367cd2fc: Pull complete
> 4c80ef6fe713: Pull complete
> ebe7c3987073: Pull complete
> Digest:
> sha256:78c6cca73d8a360d4705a8dbe722f386b90cdf6115a247c59753b796254a9116
> Status: Downloaded newer image for apacheignite/ignite:2.3.0
>
> $ sudo docker run -it --net=host -e
> "CONFIG_URI=https://raw.githubusercontent.com/apache/
> ignite/master/examples/config/example-cache.xml"
> apacheignite/ignite:2.3.0
> /opt/ignite/*apache-ignite-fabric-2.2.0-bin*/bin/ignite.sh, WARN: Failed
> to
> resolve JMX host (JMX will be disabled): moby
> [22:09:46]__  
> [22:09:46]   /  _/ ___/ |/ /  _/_  __/ __/
> [22:09:46]  _/ // (7 7// /  / / / _/
> [22:09:46] /___/\___/_/|_/___/ /_/ /___/
>
>
> $ docker ps
> CONTAINER IDIMAGE   COMMAND
> CREATED STATUS  PORTS   NAMES
> db37561bc87eapacheignite/ignite:2.3.0   "/bin/sh -c $IGNIT..."
>   22
> seconds ago  Up 20 seconds   sleepy_panini
>
> $ docker exec -it sudo docker run -it --net=host -e
> "CONFIG_URI=https://raw.githubusercontent.com/apache/
> ignite/master/examples/config/example-cache.xml"
> apacheignite/ignite
> $ docker exec -it db37561bc87e bash
>
> root@moby:/opt/ignite# ls -l
> total 4
> drwxr-xr-x 1 root root 4096 Nov  2 22:09 *apache-ignite-fabric-2.2.0-bin*
> root@moby:/opt/ignite#
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
>

Re: IGNITE-6252 patch

[Nikolai Tikhonov]

Hello,

Thank you for your contribution! I've reviewed your changes and left
comment to ticket. Could you look jira https://issues.apache.org/
jira/browse/IGNITE-6252?

On Mon, Oct 30, 2017 at 10:57 AM, Sunny Chan, CLSA 
wrote:

> Hello,
>
> During our testing we have found an issue and I have raised a JIRA ticket
> https://issues.apache.org/jira/browse/IGNITE-6252. I have also provided a
> patch that would fix the issue. Could someone take a look and see whether
> the patch is acceptable?
>
> Thanks.
> The content of this communication is intended for the recipient and is
> subject to CLSA Legal and Regulatory Notices.
> These can be viewed at https://www.clsa.com/disclaimer.html or sent to
> you upon request.
> CLSA is ISO14001 certified and committed to reducing environmental impact.
>

Re: [VOTE] Apache Ignite 2.3.0 RC2

[Nikolai Tikhonov]

+1 (binding)

I've verified result of automatic checker.

On Mon, Oct 30, 2017 at 7:40 PM, Vyacheslav Daradur 
wrote:

> Well, I can't provide stable reproducer, it seems like described issue
> relates to my system environment.
> I will try to investigate the issue in more detail and will file a
> ticket if it will be necessary.
>
> Anyway, the release is built success via Maven 3.3.9.
>
> I cancel my negative vote if it is possible according to ASF rules.
>
> On Mon, Oct 30, 2017 at 5:01 PM, Anton Vinogradov
>  wrote:
> > +1 (binding)
> >
> > I've checked release using automated checker
> > https://ci.ignite.apache.org/viewLog.html?buildId=919727=
> AssemblyAndRelease_PrepareVote4CheckRcLicensesChecksum=buildLog
> > Project should be visible for any PMC member.
> >
> > It checks:
> > - licenses
> > - pgp signatures
> > - md5 & sha512 hashes
> > - compilation from sources
> > - javadoc assembly
> > - hadoop & fabric editions assembly
> >
> > On Mon, Oct 30, 2017 at 3:00 PM, Pavel Tupitsyn 
> > wrote:
> >
> >> +1 (binding)
> >>
> >> Checked .NET:
> >> * Build from source
> >> * Build and run examples
> >> * Binary distribution
> >> * NuGet package
> >>
> >>
> >> Release notes for .NET are not correct: local collection joins were
> added
> >> in 2.1
> >> I would include the following tickets instead:
> >> https://issues.apache.org/jira/browse/IGNITE-5615
> >> https://issues.apache.org/jira/browse/IGNITE-6253
> >>
> >>
> >> Thanks,
> >> Pavel
> >>
> >> On Mon, Oct 30, 2017 at 2:52 PM, Vladimir Ozerov 
> >> wrote:
> >>
> >> > Hi Vyacheslav,
> >> >
> >> > I tried building Ignite on Maven 3.5.2 with clean local repository on
> >> Win10
> >> > and it worked fine. Looks like you have a kind of environmental issue.
> >> >
> >> > On Mon, Oct 30, 2017 at 12:57 PM, Vyacheslav Daradur <
> >> daradu...@gmail.com>
> >> > wrote:
> >> >
> >> > > -1
> >> > >
> >> > > The reason is the issues at building via Maven 3.5.0, see 3rd
> >> environment
> >> > > below.
> >> > >
> >> > > 1 Environment - Build success (clean repo). Started several
> examples.
> >> > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> >> > > 2015-11-10T19:41:47+03:00)
> >> > > Maven home: c:\apache-maven-3.3.9
> >> > > Java version: 1.8.0_144, vendor: Oracle Corporation
> >> > > Java home: C:\Program Files\Java\jdk1.8.0_144\jre
> >> > > Default locale: ru_RU, platform encoding: Cp1251
> >> > > OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> >> > >
> >> > > 2 Environment - Build success (clean repo). Started several
> examples.
> >> > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-
> >> > > 7+03:00)
> >> > > Maven home: C:\Users\SBT-Daradur-V\Programs\apache-maven-3.3.9
> >> > > Java version: 1.8.0_121, vendor: Oracle Corporation
> >> > > Java home: c:\Users\UserName\Programs\Java\jdk1.8.0_121_x64\jre
> >> > > Default locale: ru_RU, platform encoding: Cp1252
> >> > > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> >> > >
> >> > > 3 Environment - Build failed (clean repo).
> >> > > Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
> >> > > 2017-04-03T22:39:06+03:00)
> >> > > Maven home: c:\apache-maven-3.5.0
> >> > > Java version: 1.8.0_144, vendor: Oracle Corporation
> >> > > Java home: C:\Program Files\Java\jdk1.8.0_144\jre
> >> > > Default locale: ru_RU, platform encoding: Cp1251
> >> > > OS name: "windows 10", version: "10.0", arch: "amd64", family:
> >> "windows"
> >> > >
> >> > > Errors for all modules:
> >> > > [ERROR] Non-resolvable parent POM for
> >> > > org.apache.ignite:ignite-yardstick:2.3.0: Failure to find
> >> > > org.apache.ignite:ignite-parent:pom:1 in
> >> > > https://repo.maven.apache.org/maven2 was cached in the local
> >> > > repository, resolution will not be reattempted until the update
> >> > > interval of central has elapsed or updates are forced and
> >> > > 'parent.relativePath' points at wrong local POM @ line 26, column 13
> >> > > -> [Help 2]
> >> > > [ERROR]
> >> > >
> >> > > On Mon, Oct 30, 2017 at 12:12 PM, Igor Sapego 
> >> > wrote:
> >> > > > +1
> >> > > >
> >> > > > 1. Building C++ from binary release - OK.
> >> > > > 2. Building C++ examples - OK.
> >> > > > 3. Building ODBC from binary release - OK.
> >> > > > 4. ODBC installers - OK.
> >> > > > 5. Building C++ from source release - OK.
> >> > > > 6. Building ODBC from source release - OK.
> >> > > >
> >> > > > Best Regards,
> >> > > > Igor
> >> > > >
> >> > > > On Mon, Oct 30, 2017 at 6:58 AM, Alexey Kuznetsov <
> >> > akuznet...@apache.org
> >> > > >
> >> > > > wrote:
> >> > > >
> >> > > >> +1 (binding)
> >> > > >>
> >> > > >> 1. Download sources - OK
> >> > > >> 2. Build from sources - OK
> >> > > >> 3. Started ignite.bat  - OK
> >> > > >>
> >> > > >> On Sat, Oct 28, 2017 at 5:58 PM, Vladimir Ozerov <
> >> > voze...@gridgain.com>
> >> > > >> wrote:
> >> 

Re: IGNITE-2092: upgrade java

[Nikolai Tikhonov]

Hello,

It sounds common sense. Can you create pull request for this ticket?

On Thu, Sep 7, 2017 at 8:03 AM, Maxim Neverov  wrote:

> Hi Igniters!
>
> I've investigated  the ticket
>    and found out that
> it
> can be fixed by updating java from 8u111 to 8u141 (current). Moreover, the
> image that is used in Dockerfile (FROM java:8) is  deprecated
>    and has no recent java updates.
> As I understand there will be a release soon, so can the java image be
> updated to openjdk:8?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Re: Yardstick framework for Ignite 2.1

[Nikolai Tikhonov]

Anton,

In this case we'll break a links in blog posts. Let's to add note in
readme.md file (about that repository contains outdate benchmarks) and link
to a repo with actual version of benchmark.

On Mon, Sep 4, 2017 at 12:30 PM, Anton Vinogradov <a...@apache.org> wrote:

> Dmitriy,
>
> No,
> We should not keep obsolete repositories to provide urls to correct repo
> .
> We should remove this repo and create special Benchmarking page at site or
> readme.io.
>
> On Mon, Sep 4, 2017 at 8:03 AM, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
>
> > Igniters,
> >
> > Can we simply update this page with a link to the new repo hosting the
> > benchmarks?
> > https://github.com/apacheignite/yardstick-ignite/blob/master/README.md
> >
> > Once we update the page, we can remove the old benchmark code.
> >
> > D.
> >
> > On Thu, Aug 31, 2017 at 5:29 AM, Anton Vinogradov <a...@apache.org> wrote:
> >
> > > Nikolay,
> > >
> > > 1) It's impossible to use this repo to benchmark Ignite, it's content
> > > incompatible with latest versions.
> > > It's also a bad idea to copy current bench to this repo, you'll need to
> > > support it.
> > >
> > > 2) Google will reindex removal in 2 weeks and provide correct link to
> > > Yardstick.
> > > It's also a bad idea to keep outdated repo to provide correct links to
> > > current repo.
> > >
> > > 3) We should have Benchmarking page at ignite.apache.org
> > > instead of possible outdated
> > > https://cwiki.apache.org/confluence/display/IGNITE/
> > > Testing+and+benchmarking
> > > and it should explain how to benchmark Ignite in proper way.
> > >
> > > On Thu, Aug 31, 2017 at 3:16 PM, Nikolai Tikhonov <
> ntikho...@apache.org>
> > > wrote:
> > >
> > > > Guys,
> > > >
> > > > I think this repository useful if I want just run benchmark and play
> > with
> > > > them. Downloading binary distribution (or checkout whole Apache
> Ignite
> > > > source) for this goals doesn't look as clear and effective way (on my
> > > > view). Also github allows to transparently fork this project, change
> > > > something and share got result with world. As Dmitry noticed this
> repo
> > > has
> > > > links from google and it's cool and valuable, it means that users can
> > > easy
> > > > find our awesome product. Let's just update this repository, I don't
> > > think
> > > > that is so difficult (seems need just copy files from /benchmark
> > folder).
> > > >
> > > > Thoughts?
> > > >
> > > > On Thu, Aug 31, 2017 at 3:00 PM, Anton Vinogradov <a...@apache.org>
> > wrote:
> > > >
> > > > > Guys,
> > > > >
> > > > > Lets's just delete this repo.
> > > > >
> > > > > On Thu, Aug 31, 2017 at 10:18 AM, Aleksei Zaitsev <
> > > > ign...@alexzaitzev.pro>
> > > > > wrote:
> > > > >
> > > > > > Exactly, because that benchmarks works only with Ignite 1.9. So
> not
> > > to
> > > > > > maintain code in two places I deleted it in yardstick-ignite repo
> > and
> > > > > gave
> > > > > > a direct link to up-to-date version of Ignite with benchmarks
> > inside.
> > > > > >
> > > > > > 31.08.2017, 02:50, "Dmitriy Setrakyan" <dsetrak...@apache.org>:
> > > > > > > Alexey, I am seeing that some code was removed. Are we offering
> > to
> > > > > users
> > > > > > to
> > > > > > > try the benchmarks shipped with Ignite instead?
> > > > > > >
> > > > > > > On Wed, Aug 30, 2017 at 7:40 PM, Aleksei Zaitsev <
> > > > > ign...@alexzaitzev.pro
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > >>  Have done just like we discussed.
> > > > > > >>
> > > > > > >>  PR: https://github.com/apacheignite/yardstick-ignite/pull/6
> > > > > > >>
> > > > > > >>  24.08.2017, 02:02, "Dmitriy Setrakyan" <
> dsetrak...@apache.org
> > >:
> > > > > > >>  > I would delete all the code from the Yardstick repo to
> av

Re: How to configure ignite-jcl and Ignite-slf4j logger

[Nikolai Tikhonov]

Hello Prachi!

You need to set gridLogger property in IgniteConfiguration and remove
ignite-log4j dependency from POM file.

For example for Sl4j logger:

*igniteConfiguration.setGridLogger(new Slf4jLogger());*

and for Jc logger:

*igniteConfiguration.setGridLogger(new JclLogger());*

On Fri, Sep 1, 2017 at 2:44 AM, Prachi Garg  wrote:

> Engineers,
>
> In the attempt to document loggers supported by Ignite, I am having a hard
> time configuring ignite-jcl and ignite-slf4j (I could configure log4j and
> log4j2). I don't see the log message on my console when I use ignite-jcl or
> ignite-slf4j.
>
>  Below is the configuration and sample code I am using:
>
> *ignite-log4j.xml*
>
> 
>  xmlns:log4j='http://jakarta.apache.org/log4j/'>
>
> 
> 
> 
> 
> 
> 
>
> 
> 
> 
> 
>
> 
>
>
> *Maven dependency -*
>
> 
> org.apache.ignite
> ignite-log4j
> 2.1.0
> 
>
> 
> org.apache.ignite
> ignite-jcl
> 2.1.0
> 
>
>
> *Configuration for JCL ( as specified in javadoc)- *
>
> 
> 
> 
> 
>  value="/Users/prachig/myexamples/config/ignite-log4j.xml"/>
> 
> 
> 
> 
>
>
> *Sample code I am using- *
>
> public class LoggerExample {
> public static void main(String[] args) throws IgniteException {
> try (Ignite ignite =
> Ignition.start("/Users/prachig/myexamples/config/cluster-config.xml"))
> {
> ignite.log().info("Info Message 1 Logged !!!");
> ignite.log().info("Info Message 2 Logged !!!");
>
> System.out.println(ignite.log().getClass());
> }
> }
> }
>
> *Output*
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/bin/java
> -Didea.launcher.port=7535
> "-Didea.launcher.bin.path=/Applications/IntelliJ IDEA
> CE.app/Contents/bin" -Dfile.encoding=UTF-8 -classpath
> "/Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/lib/
> charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/jre/lib/deploy.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/lib/
> ext/cldrdata.jar:/Library/Java/JavaVirtualMachines/jdk1.
> 8.0_74.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/
> Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/
> lib/ext/jaccess.jar:/Library/Java/JavaVirtualMachines/jdk1.
> 8.0_74.jdk/Contents/Home/jre/lib/ext/jfxrt.jar:/Library/
> Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/
> lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/jre/lib/ext/nashorn.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/lib/
> ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/lib/
> ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.
> 8.0_74.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/Library/
> Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/
> lib/javaws.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/jre/lib/jce.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/lib/
> jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/jre/lib/jfxswt.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/lib/
> jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/jre/lib/management-agent.jar:/Library/
> Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/
> lib/plugin.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/jre/lib/resources.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/jre/lib/
> rt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/lib/ant-javafx.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/lib/dt.
> jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/lib/
> javafx-mx.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/lib/jconsole.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/lib/
> packager.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_
> 74.jdk/Contents/Home/lib/sa-jdi.jar:/Library/Java/
> JavaVirtualMachines/jdk1.8.0_74.jdk/Contents/Home/lib/
> tools.jar:/Users/prachig/myexamples/target/classes:/
> Users/prachig/.m2/repository/org/apache/ignite/ignite-core/
> 2.1.0/ignite-core-2.1.0.jar:/Users/prachig/.m2/repository/
> javax/cache/cache-api/1.0.0/cache-api-1.0.0.jar:/Users/
> prachig/.m2/repository/org/jetbrains/annotations/13.0/
> annotations-13.0.jar:/Users/prachig/.m2/repository/org/
> gridgain/ignite-shmem/1.0.0/ignite-shmem-1.0.0.jar:/Users/
> prachig/.m2/repository/org/apache/ignite/ignite-spring/2.
> 1.0/ignite-spring-2.1.0.jar:/Users/prachig/.m2/repository/
> org/apache/ignite/ignite-indexing/2.1.0/ignite-indexing-2.1.0.jar:/Users/

Re: Yardstick framework for Ignite 2.1

[Nikolai Tikhonov]

Guys,

I think this repository useful if I want just run benchmark and play with
them. Downloading binary distribution (or checkout whole Apache Ignite
source) for this goals doesn't look as clear and effective way (on my
view). Also github allows to transparently fork this project, change
something and share got result with world. As Dmitry noticed this repo has
links from google and it's cool and valuable, it means that users can easy
find our awesome product. Let's just update this repository, I don't think
that is so difficult (seems need just copy files from /benchmark folder).

Thoughts?

On Thu, Aug 31, 2017 at 3:00 PM, Anton Vinogradov <a...@apache.org> wrote:

> Guys,
>
> Lets's just delete this repo.
>
> On Thu, Aug 31, 2017 at 10:18 AM, Aleksei Zaitsev <ign...@alexzaitzev.pro>
> wrote:
>
> > Exactly, because that benchmarks works only with Ignite 1.9. So not to
> > maintain code in two places I deleted it in yardstick-ignite repo and
> gave
> > a direct link to up-to-date version of Ignite with benchmarks inside.
> >
> > 31.08.2017, 02:50, "Dmitriy Setrakyan" <dsetrak...@apache.org>:
> > > Alexey, I am seeing that some code was removed. Are we offering to
> users
> > to
> > > try the benchmarks shipped with Ignite instead?
> > >
> > > On Wed, Aug 30, 2017 at 7:40 PM, Aleksei Zaitsev <
> ign...@alexzaitzev.pro
> > >
> > > wrote:
> > >
> > >>  Have done just like we discussed.
> > >>
> > >>  PR: https://github.com/apacheignite/yardstick-ignite/pull/6
> > >>
> > >>  24.08.2017, 02:02, "Dmitriy Setrakyan" <dsetrak...@apache.org>:
> > >>  > I would delete all the code from the Yardstick repo to avoid
> > confusion
> > >>  and
> > >>  > in the description of the repo ask users to download Ignite
> directly.
> > >>  >
> > >>  > On Wed, Aug 23, 2017 at 7:40 AM, Aleksei Zaitsev <
> > ign...@alexzaitzev.pro
> > >>  >
> > >>  > wrote:
> > >>  >
> > >>  >> Yes, we can, but then we will have to do it after each release.
> > Maybe
> > >>  it's
> > >>  >> better to add information in yardstick repo README, that Apache
> > Ignite
> > >>  >> contains benchmarks since version 2.0?
> > >>  >>
> > >>  >> 22.08.2017, 16:55, "Dmitriy Setrakyan" <dsetrak...@apache.org>:
> > >>  >> > On Tue, Aug 22, 2017 at 7:19 AM, Aleksei Zaitsev <
> > >>  ign...@alexzaitzev.pro
> > >>  >> >
> > >>  >> > wrote:
> > >>  >> >
> > >>  >> >> If newer versions of Ignite delivers with benchmarks I think
> it's
> > >>  >> >> redundant to support one more project.
> > >>  >> >
> > >>  >> > Well, there are google links. Can we somehow copy the new
> > benchmarks
> > >>  into
> > >>  >> > the yardstick repo?
> > >>  >> >
> > >>  >> >> 21.08.2017, 16:17, "Dmitriy Setrakyan" <dsetrak...@apache.org
> >:
> > >>  >> >> > Igniters,
> > >>  >> >> >
> > >>  >> >> > We should either update this repository or delete it. Why
> have
> > a
> > >>  >> >> repository
> > >>  >> >> > with outdated benchmarks.
> > >>  >> >> >
> > >>  >> >> > Thoughts?
> > >>  >> >> >
> > >>  >> >> > D.
> > >>  >> >> >
> > >>  >> >> > On Mon, Aug 21, 2017 at 7:14 AM, Aleksei Zaitsev <
> > >>  >> ign...@alexzaitzev.pro
> > >>  >> >> >
> > >>  >> >> > wrote:
> > >>  >> >> >
> > >>  >> >> >> Thanks, looks like that's what I need.
> > >>  >> >> >>
> > >>  >> >> >> 21.08.2017, 12:17, "Nikolai Tikhonov" <ntikho...@apache.org
> >:
> > >>  >> >> >> > Hello,
> > >>  >> >> >> >
> > >>  >> >> >> > Yes, this repository contains benchmarks for old Apache
> > Ignite
> > >>  and
> > >>  >> >> >> > yardstick version. The last versions Apache Ignite
> > distributed
> > >>  >> with
> > >>  >> >> >> > benchmarks. You can download there
> > >>  >> >> >> > https://ignite.apache.org/download.cgi#binaries and found
> > them
> > >>  >> and
> > >>  >> >> >> > instruction in /benchmarks folder.
> > >>  >> >> >> >
> > >>  >> >> >> > On Mon, Aug 21, 2017 at 10:54 AM, <ign...@alexzaitzev.pro
> >
> > >>  wrote:
> > >>  >> >> >> >
> > >>  >> >> >> >> I am handling with yardstick benchmark framework for
> > >>  Ignite[1],
> > >>  >> but
> > >>  >> >> the
> > >>  >> >> >> >> latest version available for 1.9. In versions 2.0-2.1
> were
> > >>  made
> > >>  >> many
> > >>  >> >> >> back
> > >>  >> >> >> >> incompatible changes. Is there any newer version that is
> > >>  working
> > >>  >> >> with
> > >>  >> >> >> >> Ignite 2.1 not to do a double job?
> > >>  >> >> >> >>
> > >>  >> >> >> >> [1] https://github.com/apacheignite/yardstick-ignite/
> >
>

Re: Yardstick framework for Ignite 2.1

[Nikolai Tikhonov]

Hello,

Yes, this repository contains benchmarks for old Apache Ignite and
yardstick version. The last versions Apache Ignite distributed with
benchmarks. You can download there
https://ignite.apache.org/download.cgi#binaries and found them and
instruction in /benchmarks folder.

On Mon, Aug 21, 2017 at 10:54 AM,  wrote:

> I am handling with yardstick benchmark framework for Ignite[1], but the
> latest version available for 1.9. In versions 2.0-2.1 were made many back
> incompatible changes. Is there any newer version that is working with
> Ignite 2.1 not to do a double job?
>
> [1] https://github.com/apacheignite/yardstick-ignite/
>

Re: Thin client protocol message format

[Nikolai Tikhonov]

For supporting different cases, might be useful to add to handshake message
one byte for different flags. compression is a good example. Also it can be
some specific logic for different clients (C++, JS, Python), crypting and
etc.

On Tue, Aug 1, 2017 at 7:27 PM, Alexey Kuznetsov 
wrote:

> Pavel,
>
> How about data compression?
> May be it make sense to add a byte with compression algorithm?
> 0 - none
> 1 - ZIP
> 2 - 
> 
>
> On Tue, Aug 1, 2017 at 11:10 PM, Pavel Tupitsyn 
> wrote:
>
> > Igniters,
> >
> > Below is a proposed design for thin client protocol [1] [2] socket data
> > exchange format.
> >
> > * Values are little-endian
> > * Every request and response message starts with 4-byte length (including
> > handshake)
> > * Ignite binary format is used for value serialization (via
> > GridBinaryMarshaller/BinaryWriter/BinaryReader). Ignite binary protocol
> > has
> > to be implemented by clients anyway to work with cache values, so it
> makes
> > sense to use for all data exchange.
> >
> >
> > 1) Socket connection is established on a port according
> > to ConnectorConfiguration.port
> >
> > 2) Handshake is performed.
> >  Request:
> >int32 length = 8 // message length
> >byte opCode = 1   // handshake command
> >int16 verMajor
> >int16 verMinor
> >int16 verMaintenance
> >byte clientCode = 2// client type code (odbc, jdbc, platform)
> >
> >  Response:
> >uint32 length = 1
> >byte success
> >
> > 3) Execute command. Request starts with a command code, then goes
> > command-specific data.
> > For example, IgniteCache.put(1, "foo") will look like
> > this:
> >  Request:
> >int16 opCode// OP_CACHE_GET
> >int32 cacheId// GridCacheUtils.cacheId
> >byte flags  // skipStore, noRetry, etc
> >binobject key
> >
> >  Response:
> >byte success
> >binobject value
> >
> > Where binobject corresponds to Ignite BinaryMarshaller format, which is
> > produced by BinaryWriter.writeObject method. Integer will be represented
> as
> >   byte typeCode = 3  // GridBinaryMarshaller.INT
> >   int32 value = 1
> >
> > 4) Goto (3)
> >
> >
> > Comments are welcome.
> >
> > Pavel
> >
> > [1]
> > http://apache-ignite-developers.2346864.n4.nabble.
> com/Support-for-Ignite-
> > clients-in-any-language-thin-client-protocol-td20297.html
> > [2] https://issues.apache.org/jira/browse/IGNITE-5896
> >
>
>
>
> --
> Alexey Kuznetsov
>

Re: [VOTE] Apache Ignite 2.1.0 RC4

[Nikolai Tikhonov]

+1 (binding)

On Tue, Jul 25, 2017 at 10:56 AM, Kozlov Maxim  wrote:

> +1
> > 25 июля 2017 г., в 10:53, Николай Ижиков 
> написал(а):
> >
> > +1
> >
> > 2017-07-25 10:50 GMT+03:00 Vyacheslav Daradur :
> >
> >> +1
> >>
> >> 2017-07-25 2:02 GMT+03:00 Valentin Kulichenko <
> >> valentin.kuliche...@gmail.com
> >>> :
> >>
> >>> +1 (binding)
> >>>
> >>> On Mon, Jul 24, 2017 at 6:39 AM, Dmitriy Setrakyan <
> >> dsetrak...@apache.org>
> >>> wrote:
> >>>
>  Anton,
> 
>  You should treat this vote as a brand new vote. According to Apache
> >>> rules,
>  you need 3 +1 votes and it has to go for 72 hours.
> 
>  D.
> 
>  On Mon, Jul 24, 2017 at 8:32 AM, Anton Vinogradov 
> >> wrote:
> 
> > Igniters,
> >
> > This vote based on same files as RC3.
> > Only one change is that I signed zips with my signature.
> > KEYS files (https://dist.apache.org/repos/dist/release/ignite/KEYS)
> >>> was
> > updated as well.
> >
> > We already got 5 "+1" at RC3, so, is there any reason to wait 72
> >> hours?
> > This vote will go for 72 hours but may be closed earlier if
> >> Konstantin
> > Boudnik confirmed security issue solved.
> >
> > We have uploaded a 2.1.0 release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc4/
> >
> > Git tag name is
> > 2.1.0-rc4
> >
> > This release includes the following changes:
> >
> > Ignite:
> > * Persistent cache store
> > * Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync()
> >>> mehtods
> > * Deprecated IgniteConfiguration.marshaller
> > * Updated Lucene dependency to version 5.5.2
> > * Machine learning: implemented K-means clusterization algorithm
>  optimized
> > for distributed storages
> > * SQL: CREATE TABLE and DROP TABLE commands support
> > * SQL: New thin JDBC driver
> > * SQL: Improved performance of certain queries, when affinity node
> >> can
> >>> be
> > calculated in advance
> > * SQL: Fixed return type of AVG() function
> > * SQL: BLOB type support added to thick JDBC driver
> > * SQL: Improved LocalDate, LocalTime and LocalDateTime support for
> >>> Java 8
> > * SQL: Added FieldsQueryCursor interface to get fields metadata for
> > SqlFieldsQuery
> > * ODBC: Implemented DML statement batching
> > * Massive performance and stability improvements
> >
> > Ignite.NET:
> > * Automatic remote assembly loading
> > * NuGet-based standalone node deployment
> > * Added conditional data removeal via LINQ DeleteAll
> > * Added TimestampAttribute to control DateTime serialization mode
> > * Added local collections joins support to LINQ.
> >
> > Ignite CPP:
> > * Added Compute::Call and Compute::Broadcast methods
> >
> > Web Console:
> > * Implemented support for UNIQUE indexes for key fields on import
> >> model
> > from RDBMS
> > * Added option to show full stack trace on Queries screen
> > * Added PK alias generation on Models screen.
> >
> > Complete list of closed issues:
> > https://issues.apache.org/jira/issues/?jql=project%20%
> >>> 3D%20IGNITE%20AND%
> > 20fixVersion%20%3D%202.1%20AND%20(status%20%3D%
> > 20closed%20or%20status%20%3D%
> > 20resolved)
> >
> > DEVNOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=DEVNOTES.txt;hb=refs/tags/2.1.0-rc4
> >
> > RELEASE NOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.1.0-rc4
> >
> > Please start voting.
> >
> > +1 - to accept Apache Ignite 2.1.0-rc4
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 2.1.0-rc4 (explain why)
> >
> > This vote will go for 72 hours.
> >
> 
> >>>
> >>
> >>
> >>
> >> --
> >> Best Regards, Vyacheslav D.
> >>
> >
> >
> >
> > --
> > Nikolay Izhikov
> > nizhikov@gmail.com
>
> --
> Best Regards,
> Max K.
>
>
>
>
>

Re: [VOTE] Apache Ignite 2.0.0 RC2

[Nikolai Tikhonov]

+1 binding

On Tue, May 2, 2017 at 10:42 AM, Sergi Vladykin 
wrote:

> +1 binding
>
> Sergi
>
> 2017-05-02 10:31 GMT+03:00 Alexey Kuznetsov :
>
> > Download zip with sorces: OK
> > Build: mvn clean package -DskipTests -Dmaven.javadoc.skip=true: OK
> > Build Web console from sources: OK
> > Build Web agent  from sources: OK
> > Start node: OK
> > Start Web Console locally: OK
> > Start Web agent: OK
> > Web agent connected to node and shown in Web Console: OK
> >
> > +1 (binding)
> >
> > On Tue, May 2, 2017 at 2:31 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > +1
> > >
> > > On Mon, May 1, 2017 at 3:12 PM Vladimir Ozerov 
> > > wrote:
> > >
> > > > +1
> > > >
> > > > 30 апр. 2017 г. 17:46 пользователь "Denis Magda" 
> > > > написал:
> > > >
> > > > > Igniters!
> > > > >
> > > > > We have uploaded a 2.0.0 release candidate to
> > > > > https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/ <
> > > > > https://dist.apache.org/repos/dist/dev/ignite/2.0.0-rc2/>
> > > > >
> > > > > Git tag name is
> > > > > 2.0.0-rc2
> > > > >
> > > > > This release includes the following changes:
> > > > >
> > > > > Ignite:
> > > > > * Introduced new page memory architecture.
> > > > > * Machine Learning beta: distributed algebra support for dense and
> > > sparse
> > > > > data sets.
> > > > > * Reworked and simplified API for asynchronous operations.
> > > > > * Custom thread pool executors for compute tasks.
> > > > > * Removed CLOCK mode in ATOMIC cache.
> > > > > * Deprecated schema-import utility in favor of Web Console.
> > > > > * Integration with Spring Data.
> > > > > * Integration with Hibernate 5.
> > > > > * Integration with RocketMQ.
> > > > > * Integration with ZeroMQ.
> > > > > * SQL: CREATE INDEX and DROP INDEX commands.
> > > > > * SQL: Ability to execute queries over specific set of partitions.
> > > > > * SQL: Improved REPLICATED cache support.
> > > > > * SQL: Updated H2 version to 1.4.195.
> > > > > * SQL: Improved performance of MIN/MAX aggregate functions.
> > > > > * ODBC: Added Time data type support.
> > > > > * Massive performance improvements.
> > > > >
> > > > > Ignite.NET :
> > > > > * Custom plugin API.
> > > > > * Generic cache store.
> > > > > * Binary types now can be registered dynamically.
> > > > > * LINQ: join, "contains" and DateTime property support.
> > > > >
> > > > > Ignite CPP:
> > > > > * Implemented Cache::Invoke.
> > > > > * Added remote filters support to continuous queries.
> > > > >
> > > > > Ignite Web Console:
> > > > > * Multi-cluster support.
> > > > > * Possibility to configure Kubernetes IP finder.
> > > > > * EnforceJoinOrder option on Queries screen.
> > > > >
> > > > > Complete list of closed issues:
> > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > 3D%20IGNITE%20AND%
> > > > > 20fixVersion%20%3D%202.0%20AND%20(status%20%3D%
> > > > > 20closed%20or%20status%20%3D%20resolved) <
> https://issues.apache.org/
> > > > > jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > > 20fixVersion%20%3D%202.0%
> > > > > 20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)>
> > > > >
> > > > > DEVNOTES
> > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > > plain;f=DEVNOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > https://git-wip-us.apache
> > > .
> > > > > org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=
> > > > > refs/tags/2.0.0-rc1>
> > > > >
> > > > > RELEASENOTES
> > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=
> > > > > blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc1>
> > > > >
> > > > > Please start voting.
> > > > >
> > > > > +1 - to accept Apache Ignite 2.0.0-rc2
> > > > > 0 - don't care either way
> > > > > -1 - DO NOT accept Apache Ignite 2.0.0-rc2 (explain why)
> > > > >
> > > > > This vote will go for 72 hours.
> > > >
> > >
> > > --
> > > Alexey Kuznetsov
> > >
> > >
> >
>

Re: IGNITE-4052 ready for review

[Nikolai Tikhonov]

Vadim,

Thank you for your contribution. I'll look at changes. Can you please post
the list improvements to jira ticket?

On Mon, Apr 17, 2017 at 3:23 PM, Вадим Опольский 
wrote:

> Hi, Nikolay!
>
> I've made the following improvements ( https://github.com/apache/
> ignite/pull/1783 ):
>
> 1) Moved framework builder related code to separate method, so it make
> code cleaner and framework testable.
>
> 2) Call framework builder method from test to test role and user.
>
> 3) Added validating mesos role according with mesos role documentation
> http://mesos.apache.org/documentation/latest/roles/
>
> 4) Still using setEnv method because in IgniteFramework we cannot override
> static method and make mock static methods (except powermock, but it would
> require 3 extra dependencies in the module).
>
> P.S. setEnv method designed to worked both on Linux and Windows, and it
> does not left variable in system environment  after testing.
>
> Vadim Opolski
>
>
> 2017-04-14 12:07 GMT+03:00 Nikolay Tikhonov (JIRA) :
>
>>
>> [ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.
>> atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
>> l=15968814#comment-15968814 ]
>>
>> Nikolay Tikhonov commented on IGNITE-4052:
>> --
>>
>> [~javaller]
>> It meens that lets remove #setEnv mathod and will create mock in test
>> which will override {{getUser}} and {{getRole}} methods. Also how do you
>> think might be need to add validation for role? Which valid set of values
>> for this property?
>>
>> > Add ability to set up users for MESOS
>> > -
>> >
>> > Key: IGNITE-4052
>> > URL: https://issues.apache.org/jira/browse/IGNITE-4052
>> > Project: Ignite
>> >  Issue Type: Improvement
>> >  Components: general
>> >Affects Versions: 1.7
>> >Reporter: Nikolay Tikhonov
>> >Assignee: Vadim Opolski
>> >Priority: Trivial
>> >
>> > In current implementation Ignite Mesos Framework connects to MESOS
>> cluster via current user. Need to add ability to configure this parameters
>> via system env properties. Also need to add properties for mesos role.
>> > See org/apache/ignite/mesos/IgniteFramework.java:537
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.15#6346)
>>
>
>

Re: [jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS

[Nikolai Tikhonov]

Vadim,

I've left comment in the ticket.

On Wed, Apr 12, 2017 at 3:00 PM, Вадим Опольский 
wrote:

> Hello guys!
>
> Nikolay, I looked at cassandra mesos integration, but cant find how to
> test ability to configure mesos and user via system env properties. I will
> continue to search in another projects which use Mesos.
>
> Review please pull request - https://github.com/vadopolski/ignite/pull/2.
> It contains new test and method for setting system environments.
>
> Can you close issue https://issues.apache.org/jira/browse/IGNITE-4052 and
> open new, about testing Mesos Integration.
>
> Vadim Opolski
>
> 2017-04-03 12:13 GMT+03:00 Nikolay Tikhonov (JIRA) :
>
>>
>> [ https://issues.apache.org/jira/browse/IGNITE-4052?page=com.a
>> tlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&
>> focusedCommentId=15953167#comment-15953167 ]
>>
>> Nikolay Tikhonov commented on IGNITE-4052:
>> --
>>
>> [~javaller],
>> For example you can look at cassandra mesos integration
>> https://github.com/mesosphere/dcos-cassandra-service/blob/5d
>> 6d15e646f1df2fa10fa98d91993d3a6b4719c4/cassandra-commons/src
>> /main/java/com/mesosphere/dcos/cassandra/common/config/ServiceConfig.java.
>> List of application which use Mesos not secret and can be found on official
>> mesos site http://mesos.apache.org/documentation/latest/frameworks. ;)
>>
>> I'm really don't understand how the libs can help you. Could you clarify
>> it?
>>
>> > Add ability to set up users for MESOS
>> > -
>> >
>> > Key: IGNITE-4052
>> > URL: https://issues.apache.org/jira/browse/IGNITE-4052
>> > Project: Ignite
>> >  Issue Type: Improvement
>> >  Components: general
>> >Affects Versions: 1.7
>> >Reporter: Nikolay Tikhonov
>> >Assignee: Vadim Opolski
>> >Priority: Trivial
>> >
>> > In current implementation Ignite Mesos Framework connects to MESOS
>> cluster via current user. Need to add ability to configure this parameters
>> via system env properties. Also need to add properties for mesos role.
>> > See org/apache/ignite/mesos/IgniteFramework.java:537
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.15#6346)
>>
>
>

Re: IGNITE-4052 ready for review - what can I improve

[Nikolai Tikhonov]

Sure!

On Fri, Mar 31, 2017 at 8:13 PM, Denis Magda <dma...@apache.org> wrote:

> Nick, Vadim,
>
> Please don’t forget to update Mesos doc once this contribution gets merged:
> https://apacheignite.readme.io/docs/mesos-deployment
>
> —
> Denis
>
> On Mar 31, 2017, at 4:07 AM, Вадим Опольский <vaopols...@gmail.com> wrote:
>
> Hello community!
>
> I want to add ability to connect to MESOS cluster via user name and role
> from system env properties and to add JUnit test.
>
> Review please pull request, what can I improve ? How correctly to test
> methods work?
>
> https://github.com/apache/ignite/pull/1662
>
> Vadim Opolski
>
>
> 2017-03-30 16:32 GMT+03:00 Вадим Опольский <vaopols...@gmail.com>:
>
> Hello everyone!
>
> Nikolay, method Protos.FrameworkInfo.Builder#setRoleBytes and
> Protos.FrameworkInfo.Builder#setUserBytes were added into
> IgniteFrameworkInfoTest.
>
> Details please what do you want to me do with the methods. How
> correctly to test methods work?
>
> The code was changed with official "Coding Guidelines" and the lib was
> deleted.
>
> I didn't try to use new properties on real mesos cluster.
>
> https://github.com/apache/ignite/pull/1662
>
> Vadim Opolski
>
> *You used only Protos.FrameworkInfo.Builder#setRole method, but also
> exists Protos.FrameworkInfo.Builder#setRoleBytes. Please, pay attention on
> it. You did some code styles changes which conflict with official "Coding
> Guidelines" (see *
> *https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute*
> <https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute>*).
> Also you use lib for testing with licence different from Apache Licence
> 2.0. Are you sure that for this test you need additional libs? I think this
> can be implemented without them.*
>
> *Also did you try to use new properties on real mesos cluster? Did work
> properly?*
>
>
> 2017-03-24 15:54 GMT+03:00 Вадим Опольский <vaopols...@gmail.com>:
>
> Nikolay, I will add properties for mesos role and unit test next week.
>
> -- Forwarded message --
> From: Вадим Опольский <vaopols...@gmail.com>
> Date: 2017-03-22 15:53 GMT+03:00
> Subject: Re: IGNITE-4052 ready for review
> To: dev@ignite.apache.org
>
>
> Nikolay, just changed status to "path available".
>
> 2017-03-22 15:44 GMT+03:00 Nikolai Tikhonov <ntikho...@apache.org>:
>
> Hi Вадим!
>
> Thank you for your contribution!
> Please change status of the ticket to "path available". I'll review your
> changes.
>
> Thanks,
> Nikolay
>
> On Wed, Mar 22, 2017 at 3:36 PM, Вадим Опольский <vaopols...@gmail.com>
> wrote:
>
> Hello everybody!
>
> Nikolay,
> review please https://github.com/apache/ignite/pull/1662 .
>
> Added ability to configure current user parameters via system env
> properties - "MESOS_USER".
>
> Vadim Opolski
>
>
> -- Forwarded message --
> From: Вадим Опольский <vaopols...@gmail.com>
> Date: 2017-03-21 14:40 GMT+03:00
> Subject: Assignee IGNITE-4052
> To: dev@ignite.apache.org
>
>
> Dear sirs !
>
> I want to resolve issue IGNITE-4052.
>
> https://issues.apache.org/jira/browse/IGNITE-4052
>
> Is it actual ?
>
> Vadim Opolski
>
>
>
>
>
>
>
>
>

Re: IGNITE-4052 ready for review

[Nikolai Tikhonov]

Thank you for your contribution! Please, don't forget to move ticket in
"path available" state.

On Wed, Mar 29, 2017 at 10:46 AM, Вадим Опольский <vaopols...@gmail.com>
wrote:

> Hello everybody!
>
> Nikolay, the properties for mesos role and JUnit test were added.
>
> Review please the pull request - https://github.com/apache/igni
> te/pull/1662
>
> Vadim Opolski
>
> 2017-03-24 18:41 GMT+03:00 Nikolai Tikhonov <ntikho...@apache.org>:
>
>> Great! Looking forward to the contribution.
>>
>> On Fri, Mar 24, 2017 at 3:54 PM, Вадим Опольский <vaopols...@gmail.com>
>> wrote:
>>
>>> Nikolay, I will add properties for mesos role and unit test next week.
>>>
>>> -- Forwarded message --
>>> From: Вадим Опольский <vaopols...@gmail.com>
>>> Date: 2017-03-22 15:53 GMT+03:00
>>> Subject: Re: IGNITE-4052 ready for review
>>> To: dev@ignite.apache.org
>>>
>>>
>>> Nikolay, just changed status to "path available".
>>>
>>> 2017-03-22 15:44 GMT+03:00 Nikolai Tikhonov <ntikho...@apache.org>:
>>>
>>>> Hi Вадим!
>>>>
>>>> Thank you for your contribution!
>>>> Please change status of the ticket to "path available". I'll review your
>>>> changes.
>>>>
>>>> Thanks,
>>>> Nikolay
>>>>
>>>> On Wed, Mar 22, 2017 at 3:36 PM, Вадим Опольский <vaopols...@gmail.com>
>>>> wrote:
>>>>
>>>> > Hello everybody!
>>>> >
>>>> > Nikolay,
>>>> >  review please https://github.com/apache/ignite/pull/1662 .
>>>> >
>>>> > Added ability to configure current user parameters via system env
>>>> > properties - "MESOS_USER".
>>>> >
>>>> > Vadim Opolski
>>>> >
>>>> >
>>>> > -- Forwarded message --
>>>> > From: Вадим Опольский <vaopols...@gmail.com>
>>>> > Date: 2017-03-21 14:40 GMT+03:00
>>>> > Subject: Assignee IGNITE-4052
>>>> > To: dev@ignite.apache.org
>>>> >
>>>> >
>>>> > Dear sirs !
>>>> >
>>>> > I want to resolve issue IGNITE-4052.
>>>> >
>>>> > https://issues.apache.org/jira/browse/IGNITE-4052
>>>> >
>>>> > Is it actual ?
>>>> >
>>>> > Vadim Opolski
>>>> >
>>>> >
>>>>
>>>
>>>
>>>
>>
>

Re: IGNITE-4052 ready for review

[Nikolai Tikhonov]

Great! Looking forward to the contribution.

On Fri, Mar 24, 2017 at 3:54 PM, Вадим Опольский <vaopols...@gmail.com>
wrote:

> Nikolay, I will add properties for mesos role and unit test next week.
>
> -- Forwarded message --
> From: Вадим Опольский <vaopols...@gmail.com>
> Date: 2017-03-22 15:53 GMT+03:00
> Subject: Re: IGNITE-4052 ready for review
> To: dev@ignite.apache.org
>
>
> Nikolay, just changed status to "path available".
>
> 2017-03-22 15:44 GMT+03:00 Nikolai Tikhonov <ntikho...@apache.org>:
>
>> Hi Вадим!
>>
>> Thank you for your contribution!
>> Please change status of the ticket to "path available". I'll review your
>> changes.
>>
>> Thanks,
>> Nikolay
>>
>> On Wed, Mar 22, 2017 at 3:36 PM, Вадим Опольский <vaopols...@gmail.com>
>> wrote:
>>
>> > Hello everybody!
>> >
>> > Nikolay,
>> >  review please https://github.com/apache/ignite/pull/1662 .
>> >
>> > Added ability to configure current user parameters via system env
>> > properties - "MESOS_USER".
>> >
>> > Vadim Opolski
>> >
>> >
>> > -- Forwarded message --
>> > From: Вадим Опольский <vaopols...@gmail.com>
>> > Date: 2017-03-21 14:40 GMT+03:00
>> > Subject: Assignee IGNITE-4052
>> > To: dev@ignite.apache.org
>> >
>> >
>> > Dear sirs !
>> >
>> > I want to resolve issue IGNITE-4052.
>> >
>> > https://issues.apache.org/jira/browse/IGNITE-4052
>> >
>> > Is it actual ?
>> >
>> > Vadim Opolski
>> >
>> >
>>
>
>
>

Re: IGNITE-4052 ready for review

[Nikolai Tikhonov]

Hi Вадим!

Thank you for your contribution!
Please change status of the ticket to "path available". I'll review your
changes.

Thanks,
Nikolay

On Wed, Mar 22, 2017 at 3:36 PM, Вадим Опольский 
wrote:

> Hello everybody!
>
> Nikolay,
>  review please https://github.com/apache/ignite/pull/1662 .
>
> Added ability to configure current user parameters via system env
> properties - "MESOS_USER".
>
> Vadim Opolski
>
>
> -- Forwarded message --
> From: Вадим Опольский 
> Date: 2017-03-21 14:40 GMT+03:00
> Subject: Assignee IGNITE-4052
> To: dev@ignite.apache.org
>
>
> Dear sirs !
>
> I want to resolve issue IGNITE-4052.
>
> https://issues.apache.org/jira/browse/IGNITE-4052
>
> Is it actual ?
>
> Vadim Opolski
>
>

Re: Document issue

[Nikolai Tikhonov]

Denis,
Yes, you are right. The pages contains the latest information about cloud
images.

If you have problem with deployment, could you point on step which wrong?



On Thu, Dec 22, 2016 at 8:39 PM, Denis Magda  wrote:

> Hi,
>
> Do be honest I don’t see any issue there. Apache Ignite images for AWS and
> GCE run inside of a docker container. So the latest docker related commands
> look valid for me. Nick, please confirm.
>
> —
> Denis
>
> > On Dec 22, 2016, at 8:10 AM, 李玉珏@163 <18624049...@163.com> wrote:
> >
> > Hi，
> >
> > The following two pages of documents, more errors, I hope the community
> can be a comprehensive review, and then fix it.
> >
> > https://apacheignite.readme.io/docs/aws-deployment
> >
> > https://apacheignite.readme.io/docs/google-compute-deployment
> >
> >
> > For example, under the two page, are all about docker information.
> >
> >
>
>

Re: [VOTE] Apche Ignite PMC Chair Election

[Nikolai Tikhonov]

Denis Magda

On Mon, Dec 12, 2016 at 8:02 PM, Roman Shaposhnik  wrote:

> On Sat, Dec 10, 2016 at 12:24 PM, Dmitriy Setrakyan
>  wrote:
> > According to the discussion on the dev list [1], the following candidates
> > were proposed for the Apache Ignite PMC Chair position:
> >
> >  Vladimir Ozerov
> >  Konstantin Boudnik
> >  Valentin Kulichenko
> >  Denis Magda
> >  Branko Čibej
>
> Konstantin Boudnik
>
> Thanks,
> Roman.
>

Re: [VOTE] Apache Ignite 1.8.0 RC1

[Nikolai Tikhonov]

+1 (binding)

On Tue, Dec 6, 2016 at 11:37 AM, Pavel Tupitsyn 
wrote:

> +1 (non-binding)
>
> On Tue, Dec 6, 2016 at 11:34 AM, Vladisav Jelisavcic 
> wrote:
>
> > +1 (non-binding)
> >
> > On Tue, Dec 6, 2016 at 9:17 AM, Anton Vinogradov <
> avinogra...@gridgain.com
> > >
> > wrote:
> >
> > > +1 (binding)
> > >
> > > On Tue, Dec 6, 2016 at 3:43 AM, Roman Shtykh  >
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > -Roman
> > > >
> > > >
> > > >
> > > >
> > > > On Tuesday, December 6, 2016 8:14 AM, Denis Magda  >
> > > > wrote:
> > > > +1 (binding)
> > > >
> > > > —
> > > > Denis
> > > >
> > > >
> > > > > On Dec 5, 2016, at 7:22 AM, Vladimir Ozerov 
> > > > wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > We have uploaded the 1.8.0 release candidate to
> > > > > *https://dist.apache.org/repos/dist/dev/ignite/1.8.0-rc1/
> > > > > *
> > > > >
> > > > > Tag name is
> > > > > 1.8.0-rc1
> > > > >
> > > > > This release includes the following changes:
> > > > >
> > > > > Ignite:
> > > > > * SQL: Added DML operations support (INSERT, UPDATE, DELETE, MERGE)
> > > > > * SQL: Improved DISTINCT keyword handling in aggregates
> > > > > * Hadoop: Added MapR distribution support
> > > > > * Visor: Improved SQL statistics
> > > > > * Added Redis protocol support
> > > > > * Added transactions deadlock detection
> > > > > * Many stability and fault-tolerance fixes
> > > > >
> > > > > Ignite.NET:
> > > > > * ASP.NET session state store provider
> > > > > * Entity Framework second level cache
> > > > > * Custom loggers support: NLog, Apache log4Net
> > > > >
> > > > > ODBC driver:
> > > > > * Added DML operations support
> > > > > * Added distributed joins support
> > > > > * Added DSN support
> > > > > * Performance improvements
> > > > >
> > > > > Complete list of closed issues:
> > > > > https://issues.apache.org/jira/issues/?jql=
> > > > > *project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%201.8%
> > > > 20AND%20status%20in%20(resolved%2C%20closed)*
> > > > >
> > > > > DEVNOTES
> > > > > *https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=
> > > > blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.8.0-rc1
> > > > >  > > > blob_plain;f=DEVNOTES.txt;hb=refs/tags/1.8.0-rc1>*
> > > > >
> > > > > RELEASE NOTES
> > > > > *https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=
> > > > blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.8.0-rc1
> > > > >  > > > blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/1.8.0-rc1>*
> > > > >
> > > > > Please start voting.
> > > > >
> > > > > +1 - to accept Apache Ignite 1.8.0-rc1
> > > > > 0 - don't care either way
> > > > > -1 - DO NOT accept Apache Ignite 1.8.0-rc1 (explain why)
> > > > >
> > > > > This vote will go for 72 hours.
> > > > >
> > > > > Vladimir.
> > > >
> > >
> >
>

Re: [VOTE] Use Upsource for Code Review

[Nikolai Tikhonov]

+1

On Wed, Nov 16, 2016 at 8:50 PM, Vladisav Jelisavcic 
wrote:

> +1 (non-binding)
>
> On Wed, Nov 16, 2016 at 6:15 PM, Denis Magda  wrote:
>
> > +1
> >
> > —
> > Denis
> >
> > > On Nov 16, 2016, at 2:08 AM, Pavel Tupitsyn 
> > wrote:
> > >
> > > Following the discussion on Upsource [1],
> > > I would like to call a vote on accepting it as our official code review
> > > tool.
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > > This vote will go on for 5 days.
> > >
> > > [1] http://apache-ignite-developers.2346864.n4.nabble.
> > > com/Code-Review-Tool-Proposal-Upsource-td12195.html
> >
> >
>

Re: Ignite for Spark on YARN Deployment

[Nikolai Tikhonov]

Hi,


> 1) What ports should be opened on driver machine or yarn machine?(There
> issues were happned on our production env)


Ignite by default using the following ports:11211 -  REST,  47100..47200 -
TCP communication, 47500...47600 - Discovery,  49112 -  JMX. You can change
the values (see TcpCommunicationSpi#setLocalPort and
TcpDiscoverySpi#setLocalPort).

About other issue, could you clarify your test environment and which
configuration spark you using and which get correct/incorrect results?
Standalone or embedded? YARN ignite cluster or local cluster?

Re: [VOTE] Apache Ignite 1.7.0 RC1

[Nikolai Tikhonov]

+1 (binding)

On Wed, Aug 3, 2016 at 1:25 PM, Vladimir Ozerov 
wrote:

> +1 (binding)
>
> Looks good to me.
>
> On Wed, Aug 3, 2016 at 10:48 AM, Alexey Kuznetsov  >
> wrote:
>
> > I managed to check sha1 and md5 checksums under Windows.
> >
> > C:\Program Files\Git\usr\bin>sha1sum -c *.sha1
> > apache-ignite-1.7.0-src.zip: OK
> >
> > C:\Program Files\Git\usr\bin>md5sum -c *.md5
> > apache-ignite-1.7.0-src.zip: OK
> >
> >
> > On Wed, Aug 3, 2016 at 10:39 AM, Alexey Kuznetsov <
> akuznet...@gridgain.com
> > >
> > wrote:
> >
> > > +1
> > >
> > > Downloaded
> > >
> >
> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/apache-ignite-1.7.0-src.zip
> > > - OK
> > > mvn validate -DskipTests -Pcheck-licenses  - OK
> > > mvn clean package -DskipTests - OK
> > > Unpacked ..\src\target\bin\apache-ignite-fabric-1.7.0-bin.zip  - OK
> > > Started several niodes with ignite.bat - OK
> > > Started with ignite-schema-import.bat - OK
> > >
> > >
> > > On Tue, Aug 2, 2016 at 10:51 PM, Pavel Tupitsyn 
> > > wrote:
> > >
> > >> Hello,
> > >>
> > >> We have uploaded the 1.7.0 release candidate to
> > >> https://dist.apache.org/repos/dist/dev/ignite/1.7.0-rc1/
> > >>
> > >> Tag name is
> > >> 1.7.0-rc1
> > >>
> > >> This release includes the following changes:
> > >>
> > >> Ignite:
> > >> * Added distributed SQL JOIN.
> > >> * Node can be assigned as primary only after preloading is finished.
> > >> * Fixed CountDownLatch re-create issue.
> > >> * ODBC: Added decimal type support.
> > >> * Visor: Fixed data nodes calculation when node filter is set for
> cache.
> > >> * Many stability and fault-tolerance fixes.
> > >>
> > >> Ignite.NET:
> > >> * Added ASP.NET Output Cache provider.
> > >> * Added ability to use .NET configuration in Apache.Ignite.exe.
> > >> * Added ability to implement custom affinity functions.
> > >> * Fixed a bug in IBinaryObjectBuilder causing type name to be lost.
> > >>
> > >> Ignite CPP:
> > >> * Marshalling performance improvements.
> > >>
> > >>
> > >> Complete list of closed issues:
> > >>
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > >> 20fixVersion%20%3D%201.7%20AND%20status%20%3D%20closed
> > >>
> > >> DEVNOTES
> > >>
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/
> > >> 1.7.0-rc1
> > >>
> > >> RELEASENOTES
> > >>
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/
> > >> 1.7.0-rc1
> > >>
> > >> Please start voting.
> > >>
> > >> +1 - to accept Apache Ignite 1.7.0-rc1
> > >> 0 - don't care either way
> > >> -1 - DO NOT accept Apache Ignite 1.7.0-rc1 (explain why)
> > >>
> > >> This vote will go for 72 hours.
> > >>
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>