Re: [VOTE] Apache Ignite 1.7.0 RC1

+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. > > > >

Re: Ignite for Spark on YARN Deployment

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

Re: [VOTE] Use Upsource for Code Review

+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:

Re: [VOTE] Apche Ignite PMC Chair Election

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

Re: [VOTE] Apache Ignite 1.8.0 RC1

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

Re: Document issue

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

Re: IGNITE-4052 ready for review

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

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

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

Re: IGNITE-4052 ready for review

...@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>: > &

Re: IGNITE-4052 ready for review

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

Re: IGNITE-4052 ready for review

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

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

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

Re: [VOTE] Apache Ignite 2.1.0 RC4

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

Re: Thin client protocol message format

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

Re: [VOTE] Apache Ignite 2.0.0 RC2

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

Re: IGNITE-2092: upgrade java

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

Re: Yardstick framework for Ignite 2.1

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,

Re: Yardstick framework for Ignite 2.1

r 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 > > >> i

Re: Yardstick framework for Ignite 2.1

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+benchmark

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

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

Re: Confusing slf4j error messages

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:

Re: ignite 2.3.0 docker image contains 2.2.0 files.

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

Re: Ignite Logger & logging file config output

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

Re: Ignite in docker (Native Persistence)

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

Re: [VOTE] Apache Ignite 2.3.0 RC2

+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

Re: IGNITE-6252 patch

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