Re: Replace Cron4J with Quartz for ignite-schedule module.

[Alexey Kuznetsov]

Val and Michael ,

Very good point!

Any idea how it could be implemented?

Actually I need distributed scheduling.


On Thu, Jun 22, 2017 at 5:37 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> I think Michael brought up a very good point. Current ignite-scheduler
> module schedules jobs only locally which is not very useful in distributed
> system. I don't think I've ever seen it used and I don't think it makes
> sense to spend time on it if we just replace one dependency with another.
> However, if we switch to Quartz in order to enhance functionality and
> introduce distributed scheduling - that can add value.
>
> -Val
>
> On Wed, Jun 21, 2017 at 3:21 PM, Michael André Pearce <
> michael.andre.pea...@me.com> wrote:
>
> > If taking the quartz route, it be great if ignite could expose a
> > distributed ignite job store, so you could setup and use quartz in a
> > distributed way, in a similar way to terracotta or hazelcasts quartz
> > jobstores.
> >
> >
> > Sent from my iPhone
> >
> > > On 21 Jun 2017, at 15:43, Alexey Kuznetsov 
> > wrote:
> > >
> > > Hi!
> > >
> > > Good point, I will take a look.
> > >
> > >> On Wed, Jun 21, 2017 at 5:42 PM, 李玉珏  wrote:
> > >>
> > >> Hi，
> > >>
> > >>
> > >> There is also an alternative that the community can consider using the
> > >> scheduling functionality in the spring-context module, for the
> following
> > >> reasons:
> > >> 1.quartz is a very heavy framework, and most functions we don't need;
> > >> 2., we already have spring dependencies in our project without
> > introducing
> > >> new dependencies;
> > >> 3.spring is also Apache 2.0 license;
> > >> 4.spring's scheduler supports standard CRON, and cron4j does not
> support
> > >> standard CRON;
> > >> 5.spring's code quality is very good, maintainability is good, and the
> > >> quality of quartz code is not very good.
> > >> On 06/21/2017 13:26，Alexey Kuznetsov wrote：
> > >> Hi!
> > >>
> > >> 1) Cron4J is very old:
> > >>  Latest Cron4j 2.2.5 released: *28-Dec-2011 *
> > >>  Latest Quarz 2.3.0 released: *20-Apr-2017*
> > >>
> > >> 2) Not very friendly license:
> > >>  CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
> > >>  Quartz is freely usable, licensed under the *Apache 2.0* license.
> > >>
> > >> So, if we replace Cron4J  with Quartz we can move *ignite-schedule*
> > module
> > >> from lgpl profile to main distribution.
> > >>
> > >> Any objections?
> > >>
> > >> If no, I will create JIRA issue and implement this change.
> > >>
> > >> --
> > >> Alexey Kuznetsov
> > >>
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> >
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: Zookeeper Discovery SPI & external IP address in AWS

[Valentin Kulichenko]

Anton, Nikolay,

Looks like you participated in the fix. Can you please check?

-Val

On Wed, Jun 21, 2017 at 7:01 PM Igor Rudyak  wrote:

> Thanks Val,
>
> It looks like there is still this problem in version 2.0.0
>
> Igor
>
> On Wed, Jun 21, 2017 at 3:20 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Igor,
> >
> > Here is the ticket I'm talking about:
> > https://issues.apache.org/jira/browse/IGNITE-3230
> >
> > -Val
> >
> > On Wed, Jun 21, 2017 at 8:57 AM, Igor Rudyak  wrote:
> >
> > > Val,
> > >
> > > Are there any ticket for this in Jira?
> > >
> > > Igor
> > >
> > > On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > > > Igor,
> > > >
> > > > What version are you going on? I believe we already fixed this in the
> > > past.
> > > >
> > > > -Val
> > > >
> > > > On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak 
> wrote:
> > > >
> > > > > Hi guys,
> > > > >
> > > > > How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP
> > > > address
> > > > > (in addition to private IP) of Ignite node when it's deployed in
> > > Amazon?
> > > > >
> > > > > By default it just publishing private IP addresses of nodes which
> > makes
> > > > it
> > > > > impossible to connect to cluster from outside using *Zookeeper
> > > Discovery
> > > > > SPI*.
> > > > >
> > > > > I tried to use something like this (see below) for *discoverySPI*:
> > > > >
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >  > > > >
> > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.
> > > > TcpDiscoveryZookeeperIpFinder">
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > > > But such way it only publish public IPs to Zookeeper.
> > > > >
> > > > > Actually I am looking for something like *advertised.host.name
> > > > > * analog in Kafka. Which allows to
> > > publish
> > > > > private and public IP addresses for a node to Zookeeper.
> > > > >
> > > > > Such way all internal services communicates through private IPs,
> but
> > > > > external services communicates using public IPs.
> > > > >
> > > > > Igor
> > > > >
> > > >
> > >
> >
>

Re: Zookeeper Discovery SPI & external IP address in AWS

[Igor Rudyak]

Thanks Val,

It looks like there is still this problem in version 2.0.0

Igor

On Wed, Jun 21, 2017 at 3:20 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Igor,
>
> Here is the ticket I'm talking about:
> https://issues.apache.org/jira/browse/IGNITE-3230
>
> -Val
>
> On Wed, Jun 21, 2017 at 8:57 AM, Igor Rudyak  wrote:
>
> > Val,
> >
> > Are there any ticket for this in Jira?
> >
> > Igor
> >
> > On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Igor,
> > >
> > > What version are you going on? I believe we already fixed this in the
> > past.
> > >
> > > -Val
> > >
> > > On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak  wrote:
> > >
> > > > Hi guys,
> > > >
> > > > How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP
> > > address
> > > > (in addition to private IP) of Ignite node when it's deployed in
> > Amazon?
> > > >
> > > > By default it just publishing private IP addresses of nodes which
> makes
> > > it
> > > > impossible to connect to cluster from outside using *Zookeeper
> > Discovery
> > > > SPI*.
> > > >
> > > > I tried to use something like this (see below) for *discoverySPI*:
> > > >
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  > > >
> > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.
> > > TcpDiscoveryZookeeperIpFinder">
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > > > But such way it only publish public IPs to Zookeeper.
> > > >
> > > > Actually I am looking for something like *advertised.host.name
> > > > * analog in Kafka. Which allows to
> > publish
> > > > private and public IP addresses for a node to Zookeeper.
> > > >
> > > > Such way all internal services communicates through private IPs, but
> > > > external services communicates using public IPs.
> > > >
> > > > Igor
> > > >
> > >
> >
>

Re: Replace Cron4J with Quartz for ignite-schedule module.

[Valentin Kulichenko]

I think Michael brought up a very good point. Current ignite-scheduler
module schedules jobs only locally which is not very useful in distributed
system. I don't think I've ever seen it used and I don't think it makes
sense to spend time on it if we just replace one dependency with another.
However, if we switch to Quartz in order to enhance functionality and
introduce distributed scheduling - that can add value.

-Val

On Wed, Jun 21, 2017 at 3:21 PM, Michael André Pearce <
michael.andre.pea...@me.com> wrote:

> If taking the quartz route, it be great if ignite could expose a
> distributed ignite job store, so you could setup and use quartz in a
> distributed way, in a similar way to terracotta or hazelcasts quartz
> jobstores.
>
>
> Sent from my iPhone
>
> > On 21 Jun 2017, at 15:43, Alexey Kuznetsov 
> wrote:
> >
> > Hi!
> >
> > Good point, I will take a look.
> >
> >> On Wed, Jun 21, 2017 at 5:42 PM, 李玉珏  wrote:
> >>
> >> Hi，
> >>
> >>
> >> There is also an alternative that the community can consider using the
> >> scheduling functionality in the spring-context module, for the following
> >> reasons:
> >> 1.quartz is a very heavy framework, and most functions we don't need;
> >> 2., we already have spring dependencies in our project without
> introducing
> >> new dependencies;
> >> 3.spring is also Apache 2.0 license;
> >> 4.spring's scheduler supports standard CRON, and cron4j does not support
> >> standard CRON;
> >> 5.spring's code quality is very good, maintainability is good, and the
> >> quality of quartz code is not very good.
> >> On 06/21/2017 13:26，Alexey Kuznetsov wrote：
> >> Hi!
> >>
> >> 1) Cron4J is very old:
> >>  Latest Cron4j 2.2.5 released: *28-Dec-2011 *
> >>  Latest Quarz 2.3.0 released: *20-Apr-2017*
> >>
> >> 2) Not very friendly license:
> >>  CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
> >>  Quartz is freely usable, licensed under the *Apache 2.0* license.
> >>
> >> So, if we replace Cron4J  with Quartz we can move *ignite-schedule*
> module
> >> from lgpl profile to main distribution.
> >>
> >> Any objections?
> >>
> >> If no, I will create JIRA issue and implement this change.
> >>
> >> --
> >> Alexey Kuznetsov
> >>
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
>

Re: IGNITE-2894 - Binary object inside of Externalizable still serialized with OptimizedMarshaller

[Valentin Kulichenko]

Hi Nikita,

1. Makes sense to me.

2. Externalizable object should not be written as binary with flag 103, it
should be written in the same way it's written now. I don't see any reason
to change the protocol. Purpose of this task it to move the logic to binary
marshaller instead of depending on optimized marshaller, and also fully
support handles for these objects and objects included in them. Currently
binary marshaller and optimized marshaller use different set of handles -
this is the main downside of current implementation.

3. I think this order is correct, but does it even make sense to implement
both Binarylizable and Externalizable?

-Val

On Mon, Jun 19, 2017 at 8:58 AM, Nikita Amelchev 
wrote:

> Hello everebody.
>
> I would like to clarify about some moments in marshaller about custom
> serialization.
>
> 1. I suggest to divide the issue into two tasks: support the Externalizable
> and support the Serializable. The second task is to do as a separate issue.
>
> 2. In case the Optimized marshaller when object is the Extenalizable
> BinaryUtils.unmarshal() return deserialize value. But if we will not use
> Optimized marshaller and write the Extenalizable as the Object(103) it
> return the BinaryObjectExImpl. It break testBuilderExternalizable. (If we
> replace Externalizable to Binarilylizable it also dont work). Fix - check
> that object is the Extenalizable and deserialize
> manual(BinaryUtils.java:1833 in PR). We will use this fix or return
> BinaryObjectExImpl?
>
> 3. What are priority if was implemented several interfaces: Binarylizable
> -> Externalizable -> Serializable ?
>
> Also can you pre review this issue?
> PR: https://github.com/apache/ignite/pull/2160
>
> 2017-04-18 17:41 GMT+03:00 Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > Nikita,
> >
> > For Externalizable option 1 is the correct one. Externalizable objects
> > should not be treated as binary objects.
> >
> > For read/writeObject, you indeed have to extend ObjectOutputStream.
> > writeObject() is final because you should extend writeObjectOverride()
> > instead. Take a look at ObjectOutputStream's JavaDoc and on how this is
> > done in OptimizedObjectOutputStream. Note that ideally we need to
> implement
> > everything that is included in Java serialization spec, including some
> > non-trivial stuff like PutField. I would check if it's possible to
> somehow
> > reuse the code that already exists in optimized marshaller as much as
> > possible.
> >
> > -Val
> >
> > On Tue, Apr 18, 2017 at 1:36 PM, Nikita Amelchev 
> > wrote:
> >
> > > I see two ways to support the Externalizable in the BM:
> > > 1. Add a new type constant to the GridBinaryMarshaller class etc and
> > > read/writeExternal in the BinaryClassDescriptor.
> > > 2. Make read/writeExternal through the BINARY type without updating
> > > metadata.
> > > I don't know how to make a support read/writeObject of the Serializable
> > > without delegating to the OM. Because read/writeObject methods need the
> > > Objectoutputstream class argument. One way is to delegate it to the
> > > OptimizedObjectOutputStream. Second way is to extend the
> > Objectoutputstream
> > > in the BinaryWriterExImpl. But it is wrong way because the writeObject
> is
> > > final.
> > >
> > > 2017-01-19 20:46 GMT+03:00 Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com>:
> > >
> > > > Nikita,
> > > >
> > > > In my view we just need to support Externalizable and
> > > > writeObject/readObject in BinaryMarshaller and get rid of delegation
> to
> > > > optimized marshaller. Once such classes also go through
> > BinaryMarshaller
> > > > streams, they will be aware of binary configuration and will share
> the
> > > same
> > > > set of handles as well. This should take care of all the issues we
> have
> > > > here.
> > > >
> > > > -Val
> > > >
> > > > On Thu, Jan 19, 2017 at 7:26 AM, Nikita Amelchev <
> nsamelc...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > I have some questions about single Marshaller.
> > > > > It seems not easy to merge OptimizedMarshaller with
> BinaryMarshaller
> > > and
> > > > is
> > > > > there any sense in it?
> > > > > When Binary object inside Externalizable serialized with optimized
> it
> > > > > losing all benefits.
> > > > > Will OptimizedMarshaller be supported at 2.0 version? Or to merge
> > they
> > > is
> > > > > better?
> > > > > What do you think about it?
> > > > >
> > > > > In addition, Vladimir Ozerov, I would like to hear your opinion.
> > > > >
> > > > > 2017-01-17 23:32 GMT+03:00 Denis Magda :
> > > > >
> > > > > > Someone else added you to the contributors list in JIRA. This is
> > why
> > > I
> > > > > > couldn’t add you for the second time. Ignite committers, please
> > reply
> > > > on
> > > > > > the dev list if you add someone to the list.
> > > > > >
> > > > > > Nikita, yes, this ticket is still relevant. Go ahead and assign
> it
> > on
> > > > > > yourself.
> > > > > 

Re: IgniteCache#localEvict method

[Valentin Kulichenko]

I agree. Ivan, do you have objections?

-Val

On Mon, Jun 19, 2017 at 3:55 PM, Dmitriy Setrakyan 
wrote:

> Ivan,
>
> The semantic now is very confusing, because localEvict does not evict to
> off-heap, it just removes it from on-heap. The off-heap cache always has
> the entry anyway.
>
> My vote would be to remove this method as I don't see anyone every needing
> it. Perhaps a more useful method would be to flush the whole on-heap cache
> altogether.
>
> D.
>
> On Mon, Jun 19, 2017 at 4:16 PM, Ivan Rakov  wrote:
>
> > Semantics in 2.0: if onheap cache enabled, method evicts entry from it.
> If
> > onheap cache is disabled (default case), implementation is no-op.
> > Probably we should keep the method and add some note in javadoc.
> >
> > Best Regards,
> > Ivan Rakov
> >
> > On 19.06.2017 17:01, Igor Sapego wrote:
> >
> >> What if user enables on-heap cache?
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Mon, Jun 19, 2017 at 3:34 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> >> >
> >> wrote:
> >>
> >> Doesn't look useful to me.
> >>>
> >>> On Mon, Jun 19, 2017 at 1:03 AM, Valentin Kulichenko <
> >>> valentin.kuliche...@gmail.com> wrote:
> >>>
> >>> Folks,
> 
>  Does the subj make sense in 2.0? Before this method could be used to
> 
> >>> evict
> >>>
>  from on-heap memory to off-heap or swap. What are the semantics now?
> 
>  -Val
> 
> 
> >
>

Re: Replace Cron4J with Quartz for ignite-schedule module.

[Michael André Pearce]

If taking the quartz route, it be great if ignite could expose a distributed 
ignite job store, so you could setup and use quartz in a distributed way, in a 
similar way to terracotta or hazelcasts quartz jobstores.


Sent from my iPhone

> On 21 Jun 2017, at 15:43, Alexey Kuznetsov  wrote:
> 
> Hi!
> 
> Good point, I will take a look.
> 
>> On Wed, Jun 21, 2017 at 5:42 PM, 李玉珏  wrote:
>> 
>> Hi，
>> 
>> 
>> There is also an alternative that the community can consider using the
>> scheduling functionality in the spring-context module, for the following
>> reasons:
>> 1.quartz is a very heavy framework, and most functions we don't need;
>> 2., we already have spring dependencies in our project without introducing
>> new dependencies;
>> 3.spring is also Apache 2.0 license;
>> 4.spring's scheduler supports standard CRON, and cron4j does not support
>> standard CRON;
>> 5.spring's code quality is very good, maintainability is good, and the
>> quality of quartz code is not very good.
>> On 06/21/2017 13:26，Alexey Kuznetsov wrote：
>> Hi!
>> 
>> 1) Cron4J is very old:
>>  Latest Cron4j 2.2.5 released: *28-Dec-2011 *
>>  Latest Quarz 2.3.0 released: *20-Apr-2017*
>> 
>> 2) Not very friendly license:
>>  CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
>>  Quartz is freely usable, licensed under the *Apache 2.0* license.
>> 
>> So, if we replace Cron4J  with Quartz we can move *ignite-schedule* module
>> from lgpl profile to main distribution.
>> 
>> Any objections?
>> 
>> If no, I will create JIRA issue and implement this change.
>> 
>> --
>> Alexey Kuznetsov
>> 
> 
> 
> 
> -- 
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com

Re: Zookeeper Discovery SPI & external IP address in AWS

[Valentin Kulichenko]

Igor,

Here is the ticket I'm talking about:
https://issues.apache.org/jira/browse/IGNITE-3230

-Val

On Wed, Jun 21, 2017 at 8:57 AM, Igor Rudyak  wrote:

> Val,
>
> Are there any ticket for this in Jira?
>
> Igor
>
> On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
> valentin.kuliche...@gmail.com> wrote:
>
> > Igor,
> >
> > What version are you going on? I believe we already fixed this in the
> past.
> >
> > -Val
> >
> > On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak  wrote:
> >
> > > Hi guys,
> > >
> > > How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP
> > address
> > > (in addition to private IP) of Ignite node when it's deployed in
> Amazon?
> > >
> > > By default it just publishing private IP addresses of nodes which makes
> > it
> > > impossible to connect to cluster from outside using *Zookeeper
> Discovery
> > > SPI*.
> > >
> > > I tried to use something like this (see below) for *discoverySPI*:
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > >  > >
> > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.
> > TcpDiscoveryZookeeperIpFinder">
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > > But such way it only publish public IPs to Zookeeper.
> > >
> > > Actually I am looking for something like *advertised.host.name
> > > * analog in Kafka. Which allows to
> publish
> > > private and public IP addresses for a node to Zookeeper.
> > >
> > > Such way all internal services communicates through private IPs, but
> > > external services communicates using public IPs.
> > >
> > > Igor
> > >
> >
>

[GitHub] ignite pull request #1949: Ignite 1.8.7.b1

[AMashenkov]

Github user AMashenkov closed the pull request at:

https://github.com/apache/ignite/pull/1949


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2178: Ignite-1.7.6-p2

[AMashenkov]

GitHub user AMashenkov opened a pull request:

https://github.com/apache/ignite/pull/2178

Ignite-1.7.6-p2

for test purposes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-1.7.6-p2-fixed

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2178.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2178


commit d45383b69cc68c0ec967ebd673b197e437720214
Author: Pavel Tupitsyn 
Date:   2016-10-04T15:48:25Z

.NET: Fix code analysis warnings

commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1
Author: vozerov-gridgain 
Date:   2016-10-06T07:14:59Z

IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130.

commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497
Author: tledkov-gridgain 
Date:   2016-10-06T07:22:50Z

IGNITE-3163 IGFS: Added working directory support to 
IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This 
closes #1132.

commit e6317e01fa8a0de03e15dcdd84a575c6b06ce701
Author: vozerov-gridgain 
Date:   2016-10-06T09:03:48Z

IGNITE-3593 .NET: IgniteConfiguration.WorkDirectory has no effect. This 
closes #903. This closes #1145.

commit 952be8b995050b34379006dd6e739da3fe3b49e3
Author: Dmitriy Govorukhin 
Date:   2016-10-07T12:00:09Z

Squashed commit of the following:

commit 566881b695b8bc00e618fe9a9b4c86a8fd563cc1
Author: sboikov 
Date:   Fri Oct 7 13:08:38 2016 +0300

minor

commit 7fe88a1cb21f794ee55a176ab36d895cbf916528
Author: Dmitriy Govorukhin 
Date:   Thu Oct 6 11:11:24 2016 +0300

ignite-update-notifier fix after review

(cherry picked from commit a10d2ff)

commit f2de749f958a3b18dc479f8a5517d7bf9362b933
Author: Dmitriy Govorukhin 
Date:   Tue Oct 4 12:12:08 2016 +0300

ignite-2079-2 optimize import and change url path

(cherry picked from commit 830a3cf)

commit 0d1be85ad55b0aa91224690d6c112ae92e8bc0a9
Author: Dmitriy Govorukhin 
Date:   Thu Sep 29 19:54:54 2016 +0300

update-notifier remove parse xml, now parse like properties

(cherry picked from commit 9ecaa29)

commit e43bca6fb4528a7fc0dcb804a74fca1c59d7468b
Author: Dmitriy Govorukhin 
Date:   Tue Sep 27 17:07:21 2016 +0300

remove dom parser

(cherry picked from commit d1653b2)

commit b9c776a8423471706ecb1dc6176b38f23e799077
Author: Anton Vinogradov 
Date:   2016-10-10T08:52:57Z

IGNITE-3235 Failed to initialize primitive boolean cache property of 
superclass

commit f9a0676fad7fd6c23e3c91c10d7e0412ccb27c06
Author: vozerov-gridgain 
Date:   2016-10-11T07:23:01Z

IGNITE-4041: Created separate processor for thread pools and refactored IO 
manager. This closes #1150.

commit 9a6cfce659df40b0a4624f19fd91c217b74bafea
Author: nikolay_tikhonov 
Date:   2016-10-11T10:59:57Z

IGNITE-4014 Fixed "Transaction hangs if entry processor failed during 
serialization". This closes #1148.

commit 1938a17b01fac1e08c30011180bbcc3ed7374d83
Author: Andrey V. Mashenkov 
Date:   2016-10-11T11:50:18Z

IGNITE-3948: Fixed a bug causing TTL manager to continue tracking of 
evicted entries. This closes #1101.

commit 60d27547dfc6bd27c6d39cbcc523d0d1e872a821
Author: vozerov-gridgain 
Date:   2016-10-11T11:51:00Z

Merge remote-tracking branch 'upstream/ignite-1.6.10' into ignite-1.6.10

commit 359a392f1c53217c691c4c40762c51fd330666e2
Author: Valentin Kulichenko 
Date:   2016-01-15T06:58:41Z

Update notifier fixes

(cherry picked from commit a5c85ca)

commit 01ca6db70933fb7f50f161a80cde9647e68a3710
Author: dkarachentsev 
Date:   2016-10-11T13:18:40Z

Merge remote-tracking branch 'origin/ignite-1.6.10' into ignite-1.6.10

commit 0659bebe04dc9c0b0a163bc95061519c553e678c
Author: Andrey V. Mashenkov 
Date:   2016-10-12T11:49:36Z

IGNITE-3972: Fixed a bug causing continuous queries to be lost for ATOMIC 
cache when key's primary node leaves topology. This closes #1133.

commit f597aff1bdf65d3d430cf85c9932391a72c2d7dc
Author: Andrey V. Mashenkov 
Date:   2016-10-12T12:44:08Z

IGNITE-3875: Added separate thread pool for data streamer. This closes 
#1067.

commit 2ab094e08373dc6667af44d48a38b4f044953a79
Author: tledkov-gridgain 
Date:   

[GitHub] ignite pull request #2177: Ignite-1.8.8.b1

[AMashenkov]

GitHub user AMashenkov opened a pull request:

https://github.com/apache/ignite/pull/2177

Ignite-1.8.8.b1

for test purposes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-1.8.8.b1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2177.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2177


commit ac92bdb44ed0fb02893c1e7e9df4443a0a26d331
Author: Ivan Veselovskiy 
Date:   2016-12-19T08:57:00Z

IGNITE-3966: Hadoop: add Hadoop native library to Java arguments 
automatically. This closes #1320.

commit 1776e9eb04895bbb870f7c6aa89ca96db2af31b7
Author: tledkov-gridgain 
Date:   2016-12-29T08:14:10Z

IGNITE-4458: Hadoop: "striped" shuffle mode is default from now on. This 
closes #1390.

commit e7d781ee3221107d9a819dd70cb5776558a59e2a
Author: devozerov 
Date:   2017-01-05T08:30:42Z

IGNITE-4516: Hadoop: implemented optional compression for remote shuffle 
output. This closes #1399.

commit b6005b07b3e28907c8ff5cb6ebcce25bdb23bb48
Author: devozerov 
Date:   2017-01-05T11:48:06Z

IGNITE-4461: Hadoop: added automatic resolution of "raw" comparator for 
Text class.

commit 626f1d5614930bca0ab744a6049e5f83f321d46a
Author: Andrey V. Mashenkov 
Date:   2016-12-23T09:18:07Z

IGNITE-4142: Fixed assertion while update metrics. This closes #1372.

commit 852f03829c997883376245e3515e47822e9012eb
Author: Andrey Novikov 
Date:   2017-01-11T09:34:23Z

Merge branches 'ignite-1.7.5' and 'web-console-production' of 
https://github.com/gridgain/apache-ignite into web-console-production

commit 07752ec85dc3bf18297b728f9a31185d44ad3687
Author: sboikov 
Date:   2017-01-11T10:51:23Z

Improved cache.get benchmarks.

commit 660cd1e072496c323f5bdfc797f2a7cb7d74480d
Author: sboikov 
Date:   2017-01-11T14:34:46Z

Added cache.getAll benchmarks for offheap cache.

commit 074a4a08012822f3404807015bc63052c20e7439
Author: sboikov 
Date:   2017-01-11T14:54:55Z

Added cache.getAll benchmarks for offheap cache.

commit 1820eb3135c44d6768d53b95d69c2a93c7759b6f
Author: sboikov 
Date:   2017-01-11T15:09:42Z

Added cache.putAll benchmarks for offheap cache.

commit e04d83c4911bbd3e18f03ee1e80a99cd49fae87f
Author: sboikov 
Date:   2017-01-11T15:15:53Z

Added cache.putAll benchmarks for offheap cache.

commit fe424591161595de1151a29cf1cdeb50456c3e39
Author: Andrey V. Mashenkov 
Date:   2017-01-12T14:43:21Z

Minors

commit cf9f0a79da7540dc40c3ac860a94158e87e2d7ec
Author: Andrey V. Mashenkov 
Date:   2017-01-12T14:50:02Z

Minors

commit 55f7594fd0595a4269c3972446ba4ebe30c12442
Author: Alexandr Kuramshin 
Date:   2017-01-13T09:26:39Z

ignite-4293 Do not need store deserialized value for BinaryMarshaller

(cherry picked from commit d10946b)

commit 1665a615030201a7c9a51fd479868c3533b103b5
Author: Anton Vinogradov 
Date:   2016-12-30T10:41:34Z

IGNITE-4424 REPLICATED cache isn't synced across nodes

commit 80f7325211f6adb8a9f3cc0bd1192ded28aeff77
Author: Anton Vinogradov 
Date:   2017-01-16T09:15:17Z

Merge branch 'ignite-1.7.5-p1' into ignite-1.7.6

commit 496fb173d55a8ea0702fcb70a4e807f61d8fc53e
Author: nikolay_tikhonov 
Date:   2017-01-16T10:19:51Z

IGNITE-4513 Improve debug logging.

commit c3eae9fecff5ad01390170c034dca39c216a097c
Author: Andrey Novikov 
Date:   2017-01-16T03:33:16Z

IGNITE-4518 Fixed parallel load of cache. - Fixes #1426.

Signed-off-by: Andrey Novikov 

(cherry picked from commit 79401b2)

commit 71176473f9fd0aa2088ba4e611ba4b7fc45e76b8
Author: Andrey Novikov 
Date:   2017-01-16T04:22:34Z

IGNITE-4545 Added cache for router hostnames. - Fixes #1428.

Signed-off-by: Andrey Novikov 

(cherry picked from commit 27ba69b)

commit 22b7e76c00a77a06388bcef869f29d1a572a306a
Author: sboikov 
Date:   2017-01-17T09:33:32Z

ignite-4465 Prevent cache entry eviction while it is loaded from store 
(otherwise loaded value can be not stored in cache).

commit 67225b24dbc77ed70f5aa6bac6d750623c67045d
Author: sboikov 
Date:   2017-01-17T09:46:28Z

Merge remote-tracking branch 'remotes/community/ignite-1.7.5-p1' into 
ignite-1.7.6

commit 74d0dcc6c56118f9e4fdaa4aa70d25d1abe7b80e
Author: Andrey V. Mashenkov 
Date:   

[GitHub] ignite pull request #2176: ignite-5574 For offheap_tiered cache first try re...

[agura]

GitHub user agura opened a pull request:

https://github.com/apache/ignite/pull/2176

ignite-5574 For offheap_tiered cache first try read value from offheap in 
order to avoid redundant synchronization on entry



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/agura/incubator-ignite ignite-5574

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2176.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2176


commit 8c56e4516e55c7ed9c14779f0e77e00f055d9a81
Author: vozerov-gridgain 
Date:   2016-09-02T15:05:16Z

IGNITE-3827: Removed double marshalling of keys in 
DataStreamerImpl.addData(Map) method.

commit 4dc624fc9a8852f77f1fe7db4dc06a474b34c2eb
Author: vozerov-gridgain 
Date:   2016-09-02T15:23:09Z

IGNITE-3829: Optimized affinity key field name handling.

commit 7b0d2326ccc62afd5d162b056398f96d8d7c9100
Author: vozerov-gridgain 
Date:   2016-09-05T07:19:48Z

IGNITE-3829: Additional fix.

commit b8cb82de65a529040ea18b0dc03fa7109c69bb4a
Author: Vasiliy Sisko 
Date:   2016-12-29T07:48:45Z

IGNITE-4442 Implemented cache affinity configuration.

(cherry picked from commit f4a1e6c)

commit 71412cecd861119965a873520da96078f99c94e2
Author: Anton Vinogradov 
Date:   2016-12-30T10:41:34Z

IGNITE-4424 REPLICATED cache isn't synced across nodes

commit 852f03829c997883376245e3515e47822e9012eb
Author: Andrey Novikov 
Date:   2017-01-11T09:34:23Z

Merge branches 'ignite-1.7.5' and 'web-console-production' of 
https://github.com/gridgain/apache-ignite into web-console-production

commit fe424591161595de1151a29cf1cdeb50456c3e39
Author: Andrey V. Mashenkov 
Date:   2017-01-12T14:43:21Z

Minors

commit cf9f0a79da7540dc40c3ac860a94158e87e2d7ec
Author: Andrey V. Mashenkov 
Date:   2017-01-12T14:50:02Z

Minors

commit d3e2e0c5574f7677645e73e1fbafaee3563895f1
Author: Andrey Novikov 
Date:   2017-01-25T07:27:01Z

Merge branches 'ignite-1.7.6' and 'web-console-production' of 
https://github.com/gridgain/apache-ignite into web-console-production

commit 295f80d10da02692540435d46961a9c3cca99b3c
Author: Andrey Novikov 
Date:   2017-01-25T06:58:57Z

IGNITE-4520 Added credential request for authentication on proxy.

(cherry picked from commit ef04f35)

commit faa20530a707014ac34477cba8adaaa4b67de1bb
Author: Andrey Novikov 
Date:   2017-01-25T09:48:05Z

IGNITE-1596 Fixed version sort.

(cherry picked from commit 128ba07)

commit 1b3bbdb1758eb19c755dabcb5fe329529fa0f378
Author: Andrey Novikov 
Date:   2017-01-27T04:30:49Z

IGNITE-4622 Fixed generation in domain model for cache store.

(cherry picked from commit 43007d5)

commit a8355feef630a5c8c4edbe02224c8325dd5952d3
Author: Andrey Novikov 
Date:   2017-02-03T04:58:43Z

IGNITE-4610 Added more informative message.

(cherry picked from commit 9ff2a8f)

commit 94d8a6fc0a61bb3046e2ebd8b3cbffb8917c2b6a
Author: Andrey Novikov 
Date:   2017-02-08T04:43:22Z

IGNITE-4472 Added user activities in Web Console.

(cherry picked from commit 26ee9c2)

commit b571fd40f009709718bce0c969d47b62be06b8f6
Author: Andrey Novikov 
Date:   2017-02-08T10:05:08Z

IGNITE-4472 Added user activities in Web Console.

(cherry picked from commit 26ee9c2)

commit db48f545a83bb72cded77d8269fe4f8820e8380f
Author: Andrey Novikov 
Date:   2017-02-10T08:55:05Z

IGNITE-4678 Web Console: Implemented demo load as service.

(cherry picked from commit a600caf)

commit e4b54c985f256478ae2cae23b423d9b8e0842df8
Author: Andrey Novikov 
Date:   2017-02-13T02:48:50Z

Merge branch 'ignite-1.8.3' of https://github.com/gridgain/apache-ignite 
into web-console-production

commit 2d6735a20ac8009d1ac3f003da4fcd319271bd71
Author: Alexey Kuznetsov 
Date:   2017-02-09T09:44:41Z

IGNITE-4676 Fixed hang if closure executed nested internal task with 
continuation. Added test.

(cherry picked from commit e7a5307)

commit d307e2eced1fd10b007ee08c3dd113e7bb4f22ba
Author: Andrey Novikov 
Date:   2017-02-13T10:35:29Z

IGNITE-4687 Added pool to process REST request in Web Agent.

(cherry picked from commit 262a341)

commit 8874f99f44dc2edf08a525619edb49d5db70b938
Author: dkarachentsev 
Date:   2017-02-14T15:44:57Z

IGNITE-4641 - Refresh client attributes during reconnect

commit 

Re: Zookeeper Discovery SPI & external IP address in AWS

[Igor Rudyak]

Val,

Are there any ticket for this in Jira?

Igor

On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
valentin.kuliche...@gmail.com> wrote:

> Igor,
>
> What version are you going on? I believe we already fixed this in the past.
>
> -Val
>
> On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak  wrote:
>
> > Hi guys,
> >
> > How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP
> address
> > (in addition to private IP) of Ignite node when it's deployed in Amazon?
> >
> > By default it just publishing private IP addresses of nodes which makes
> it
> > impossible to connect to cluster from outside using *Zookeeper Discovery
> > SPI*.
> >
> > I tried to use something like this (see below) for *discoverySPI*:
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  >
> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.
> TcpDiscoveryZookeeperIpFinder">
> > 
> > 
> > 
> > 
> > 
> >
> > But such way it only publish public IPs to Zookeeper.
> >
> > Actually I am looking for something like *advertised.host.name
> > * analog in Kafka. Which allows to publish
> > private and public IP addresses for a node to Zookeeper.
> >
> > Such way all internal services communicates through private IPs, but
> > external services communicates using public IPs.
> >
> > Igor
> >
>

Re: Zookeeper Discovery SPI & external IP address in AWS

[Igor Rudyak]

Hi Val,

I am using version 2.0.0.

Igor

On Jun 21, 2017 5:50 AM, "Valentin Kulichenko" <
valentin.kuliche...@gmail.com> wrote:

> Igor,
>
> What version are you going on? I believe we already fixed this in the past.
>
> -Val
>
> On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak  wrote:
>
> > Hi guys,
> >
> > How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP
> address
> > (in addition to private IP) of Ignite node when it's deployed in Amazon?
> >
> > By default it just publishing private IP addresses of nodes which makes
> it
> > impossible to connect to cluster from outside using *Zookeeper Discovery
> > SPI*.
> >
> > I tried to use something like this (see below) for *discoverySPI*:
> >
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  >
> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.
> TcpDiscoveryZookeeperIpFinder">
> > 
> > 
> > 
> > 
> > 
> >
> > But such way it only publish public IPs to Zookeeper.
> >
> > Actually I am looking for something like *advertised.host.name
> > * analog in Kafka. Which allows to publish
> > private and public IP addresses for a node to Zookeeper.
> >
> > Such way all internal services communicates through private IPs, but
> > external services communicates using public IPs.
> >
> > Igor
> >
>

[GitHub] ignite pull request #2175: IGNITE-5489

[ntikhonov]

GitHub user ntikhonov opened a pull request:

https://github.com/apache/ignite/pull/2175

IGNITE-5489

IGNITE-5489

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5489

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2175.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2175


commit a92f20b5cc75e6b80b2731da0192723526b0c1dc
Author: vozerov-gridgain 
Date:   2016-10-04T11:10:26Z

IGNITE-3597: Removed static work directory.

commit d45383b69cc68c0ec967ebd673b197e437720214
Author: Pavel Tupitsyn 
Date:   2016-10-04T15:48:25Z

.NET: Fix code analysis warnings

commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1
Author: vozerov-gridgain 
Date:   2016-10-06T07:14:59Z

IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130.

commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497
Author: tledkov-gridgain 
Date:   2016-10-06T07:22:50Z

IGNITE-3163 IGFS: Added working directory support to 
IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This 
closes #1132.

commit e6317e01fa8a0de03e15dcdd84a575c6b06ce701
Author: vozerov-gridgain 
Date:   2016-10-06T09:03:48Z

IGNITE-3593 .NET: IgniteConfiguration.WorkDirectory has no effect. This 
closes #903. This closes #1145.

commit 952be8b995050b34379006dd6e739da3fe3b49e3
Author: Dmitriy Govorukhin 
Date:   2016-10-07T12:00:09Z

Squashed commit of the following:

commit 566881b695b8bc00e618fe9a9b4c86a8fd563cc1
Author: sboikov 
Date:   Fri Oct 7 13:08:38 2016 +0300

minor

commit 7fe88a1cb21f794ee55a176ab36d895cbf916528
Author: Dmitriy Govorukhin 
Date:   Thu Oct 6 11:11:24 2016 +0300

ignite-update-notifier fix after review

(cherry picked from commit a10d2ff)

commit f2de749f958a3b18dc479f8a5517d7bf9362b933
Author: Dmitriy Govorukhin 
Date:   Tue Oct 4 12:12:08 2016 +0300

ignite-2079-2 optimize import and change url path

(cherry picked from commit 830a3cf)

commit 0d1be85ad55b0aa91224690d6c112ae92e8bc0a9
Author: Dmitriy Govorukhin 
Date:   Thu Sep 29 19:54:54 2016 +0300

update-notifier remove parse xml, now parse like properties

(cherry picked from commit 9ecaa29)

commit e43bca6fb4528a7fc0dcb804a74fca1c59d7468b
Author: Dmitriy Govorukhin 
Date:   Tue Sep 27 17:07:21 2016 +0300

remove dom parser

(cherry picked from commit d1653b2)

commit b9c776a8423471706ecb1dc6176b38f23e799077
Author: Anton Vinogradov 
Date:   2016-10-10T08:52:57Z

IGNITE-3235 Failed to initialize primitive boolean cache property of 
superclass

commit f9a0676fad7fd6c23e3c91c10d7e0412ccb27c06
Author: vozerov-gridgain 
Date:   2016-10-11T07:23:01Z

IGNITE-4041: Created separate processor for thread pools and refactored IO 
manager. This closes #1150.

commit 9a6cfce659df40b0a4624f19fd91c217b74bafea
Author: nikolay_tikhonov 
Date:   2016-10-11T10:59:57Z

IGNITE-4014 Fixed "Transaction hangs if entry processor failed during 
serialization". This closes #1148.

commit 1938a17b01fac1e08c30011180bbcc3ed7374d83
Author: Andrey V. Mashenkov 
Date:   2016-10-11T11:50:18Z

IGNITE-3948: Fixed a bug causing TTL manager to continue tracking of 
evicted entries. This closes #1101.

commit 60d27547dfc6bd27c6d39cbcc523d0d1e872a821
Author: vozerov-gridgain 
Date:   2016-10-11T11:51:00Z

Merge remote-tracking branch 'upstream/ignite-1.6.10' into ignite-1.6.10

commit 359a392f1c53217c691c4c40762c51fd330666e2
Author: Valentin Kulichenko 
Date:   2016-01-15T06:58:41Z

Update notifier fixes

(cherry picked from commit a5c85ca)

commit 01ca6db70933fb7f50f161a80cde9647e68a3710
Author: dkarachentsev 
Date:   2016-10-11T13:18:40Z

Merge remote-tracking branch 'origin/ignite-1.6.10' into ignite-1.6.10

commit 0659bebe04dc9c0b0a163bc95061519c553e678c
Author: Andrey V. Mashenkov 
Date:   2016-10-12T11:49:36Z

IGNITE-3972: Fixed a bug causing continuous queries to be lost for ATOMIC 
cache when key's primary node leaves topology. This closes #1133.

commit f597aff1bdf65d3d430cf85c9932391a72c2d7dc
Author: Andrey V. Mashenkov 
Date:   2016-10-12T12:44:08Z

IGNITE-3875: Added separate thread 

[jira] [Created] (IGNITE-5573) Yardstick: Incorrect actual warmup and duration when test with pds and many caches

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-5573:
---

 Summary: Yardstick: Incorrect actual warmup and duration when test 
with pds and many caches
 Key: IGNITE-5573
 URL: https://issues.apache.org/jira/browse/IGNITE-5573
 Project: Ignite
  Issue Type: Bug
  Components: yardstick
Affects Versions: 2.1
Reporter: Ksenia Rybakova


Load config:
- CacheRandomOperation benchmak
- 5 driver nodes
- 12 server nodes (1 per host)
- 14 phisical caches + 50 groups with 500 logical caches (10 per group)
- preloading amount 10K, key range 20K
- warmup time 300s
- duration 1800s

But according to driver logs actual warmup time and duration are incorrect (or 
it's just logging problem)
{noformat}
<16:15:35> Preload logger was started.
...
<16:27:19> Preload logger was stopped.
<16:27:19> Probe writer is not configured (using default CSV 
writer)
<16:27:19> ThroughputLatencyProbe is started.
<16:27:19> DStatProbe is started. Command: 'dstat -m --all 
--noheaders --noupdate 1'
<16:27:19> PercentileProbe is started.
<16:27:19> Starting warmup.
...
<17:02:09> Starting main test (warmup finished).
<17:02:09> Starting iteration: 18
<17:02:09> Starting iteration: 10
<17:02:09> Starting iteration: 9
<17:02:09> Starting iteration: 25
<17:02:09> Starting iteration: 27
<17:02:09> Starting iteration: 23
<17:02:09> Starting iteration: 34
<17:02:09> Starting iteration: 36
<17:02:09> Starting iteration: 41
<17:02:09> Starting iteration: 1
<17:02:09> Starting iteration: 44
<17:02:09> Starting iteration: 46
<17:02:09> Starting iteration: 47
<17:02:09> Starting iteration: 48
<17:02:09> Starting iteration: 39
<17:02:09> Starting iteration: 52
<17:02:09> Starting iteration: 54
<17:02:09> Starting iteration: 56
<17:02:09> Starting iteration: 57
<17:02:09> Starting iteration: 58
<17:02:09> Starting iteration: 20
<17:02:09> Starting iteration: 24
<17:02:09> Starting iteration: 59
<17:02:09> Starting iteration: 60
<17:02:09> Starting iteration: 61
<17:02:09> Starting iteration: 62
<17:02:09> Starting iteration: 63
<17:02:09> Starting iteration: 21
<17:02:09> Starting iteration: 22
<17:02:09> Starting iteration: 7
<17:02:09> Starting iteration: 8
<17:02:09> Starting iteration: 5
<17:02:09> Starting iteration: 3
<17:02:09> Starting iteration: 15
<17:02:09> Starting iteration: 2
<17:02:09> Starting iteration: 11
<17:02:09> Starting iteration: 12
<17:02:09> Starting iteration: 4
<17:02:09> Starting iteration: 16
<17:02:09> Starting iteration: 19
<17:02:09> Starting iteration: 6
<17:02:09> Starting iteration: 17
<17:02:09> Starting iteration: 13
<17:02:09> Starting iteration: 14
<17:02:09> Starting iteration: 64
<17:02:09> Starting iteration: 37
<17:02:09> Starting iteration: 55
<17:02:09> Starting iteration: 53
<17:02:09> Starting iteration: 51
<17:02:09> Starting iteration: 50
<17:02:09> Starting iteration: 49
<17:02:09> Starting iteration: 45
<17:02:09> Starting iteration: 38
<17:02:09> Starting iteration: 42
<17:02:09> Starting iteration: 43
<17:02:09> Starting iteration: 40
<17:02:09> Starting iteration: 35
<17:02:09> Starting iteration: 31
<17:02:09> Starting iteration: 32
<17:02:09> Starting iteration: 33
<17:02:09> Starting iteration: 29
<17:02:09> Starting iteration: 30
<17:02:09> Starting iteration: 28
<17:02:09> Starting iteration: 26
<17:02:10> ThroughputLatencyProbe results will be 
saved to: results-20170621-161454/0-172.25.1.31
<17:02:10> DStatProbe results will be saved to: 
results-20170621-161454/0-172.25.1.31
...
Finishing main test [ts=1498054591988, date=Wed Jun 21 17:16:31 MSK 2017]
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Replace Cron4J with Quartz for ignite-schedule module.

[Alexey Kuznetsov]

Hi!

Good point, I will take a look.

On Wed, Jun 21, 2017 at 5:42 PM, 李玉珏  wrote:

> Hi，
>
>
> There is also an alternative that the community can consider using the
> scheduling functionality in the spring-context module, for the following
> reasons:
> 1.quartz is a very heavy framework, and most functions we don't need;
> 2., we already have spring dependencies in our project without introducing
> new dependencies;
> 3.spring is also Apache 2.0 license;
> 4.spring's scheduler supports standard CRON, and cron4j does not support
> standard CRON;
> 5.spring's code quality is very good, maintainability is good, and the
> quality of quartz code is not very good.
> On 06/21/2017 13:26，Alexey Kuznetsov wrote：
> Hi!
>
> 1) Cron4J is very old:
>   Latest Cron4j 2.2.5 released: *28-Dec-2011 *
>   Latest Quarz 2.3.0 released: *20-Apr-2017*
>
> 2) Not very friendly license:
>   CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
>   Quartz is freely usable, licensed under the *Apache 2.0* license.
>
> So, if we replace Cron4J  with Quartz we can move *ignite-schedule* module
>  from lgpl profile to main distribution.
>
> Any objections?
>
> If no, I will create JIRA issue and implement this change.
>
> --
> Alexey Kuznetsov
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-5572) DDL: Support ALTER TABLE ADD COLUMN

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5572:
---

 Summary: DDL: Support ALTER TABLE ADD COLUMN
 Key: IGNITE-5572
 URL: https://issues.apache.org/jira/browse/IGNITE-5572
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
 Fix For: 2.2






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5571) Make sure that cache-less execution works as good as cache-based

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5571:
---

 Summary: Make sure that cache-less execution works as good as 
cache-based
 Key: IGNITE-5571
 URL: https://issues.apache.org/jira/browse/IGNITE-5571
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Alexander Paschenko
Priority: Critical
 Fix For: 2.1


Compare the following two methods:
1) {{GridQueryProcessor.querySqlFields}} - old good entry point for query 
execution;
2) {{GridQueryProcessor.querySqlFieldsNoCache}} - new method for "cache-less" 
execution.

Note how cache context is used in the first method:
1) First, it helps determine whether query can be converted to "local"
2) Second, it gets query parallelism of current cache, and if it differs from 
{{1}}, then it turns on {{distributedJoins}}.

Neither of this happens in the second implementation. Moreover, I had to throw 
an exception for local queries, as I didn't know how to handle them properly.

We need to investigate and fix these two deficiencies somehow. Probably some 
inputs from [~sergi.vladykin] would be required, to understand what is going on.

Our ultimate goal is to make "cache-less" execution as good as the old one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2174: Ignite 5558: mock-based standalone WAL records it...

[dspavlov]

GitHub user dspavlov opened a pull request:

https://github.com/apache/ignite/pull/2174

Ignite 5558: mock-based standalone WAL records iterator

Don't merge, this PR is for testing purposes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5558

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2174.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2174


commit bdbba0ee9a5437a3f66d05c8175bfcb2f309b3bd
Author: Dmitriy Govorukhin 
Date:   2017-06-11T18:53:56Z

IGNITE-5392 - Joining node must accept cluster active status

commit 6bf5ce46c1e6c4e3dcf042ac91a5b61a726c5821
Author: Alexey Goncharuk 
Date:   2017-06-11T20:02:44Z

IGNITE-5267 - Moved ignite-ps module to ignite-core

commit 4dc81ca86347107848328d1e2e206b796976fb23
Author: Alexey Goncharuk 
Date:   2017-06-12T05:22:49Z

IGNITE-5267 - Added missing class

commit 195147d573d7cb3fc637f74937ee561b03a3c574
Author: Dmitriy Govorukhin 
Date:   2017-06-13T05:23:38Z

IGNITE-5267 - Activate nodes after start

commit d38dfcd5c4a49b6ec4be1cfdb4f28f7d152cd14a
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:01:16Z

ignite-5267-merge remove pds dependency, restore data structures only in 
snapshot operation

commit cf886fd5816534b46a1247d3bdc41061087608e4
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:22:30Z

ignite-2.1.1 fix java doc

commit d2dcc1d032c7f9692ddfe50fa8a80e375e8d4c9b
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:45:11Z

ignite-2.1.1 fix import

commit b65ca6854828c0f2368edab202ba00f31365a3e3
Author: Ivan Rakov 
Date:   2017-06-13T10:50:31Z

ignite-2.1.1 fixing pds tests

commit 1181b478d7810d4485da43204c9f64757be6a8e4
Author: Ivan Rakov 
Date:   2017-06-13T11:51:25Z

ignite-2.1.1 fixing pds tests

commit 68739b7cffae5b4bb3714dfe12bcf93327f136b8
Author: Alexey Kuznetsov 
Date:   2017-06-13T12:27:32Z

IGNITE-5267 Snapshots support.

commit ec50e23591c4d2e2332b7a81b7218ee44f358afe
Author: Ilya Lantukh 
Date:   2017-06-13T12:34:02Z

Merge with ignite-5267-merge.

commit 4342f46ab4258f8219e45f4b69435f38b6d0f2b5
Author: Ilya Lantukh 
Date:   2017-06-13T12:37:34Z

ignite-5267 : Test for unique name per group.

commit 2b0741039e7cc6e36871b97bab53780edfc84648
Author: Ilya Lantukh 
Date:   2017-06-13T12:38:55Z

ignite-5267 : Removed redundant test.

commit 4a86cae203ed9aed953cd6093884cf8cab4531e3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T12:48:39Z

ignite-2.1.1 fix state processor, skip if daemon

commit 5c567aeb5458159bc41dbd251dfa8a65701f4861
Author: Ivan Rakov 
Date:   2017-06-13T13:06:42Z

ignite-2.1.1 moving pds tests that depend on indexing to separate suite

commit 5e9d9ebc1140f9647fc1b325ba81d0ad6c2c69f3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:20Z

ignite-2.1.1 Added description to MX bean

commit 2c2a9e652b13cf60b7e878a4e20f4ab4ae014e9c
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:39Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit 9141b3698d0ec98e512efbc78864cc06781fd8c7
Author: devozerov 
Date:   2017-06-13T13:32:28Z

IGNITE-5267: Fixed too early StoredCacheData initialization.

commit 0a00f03da78649320cb0bb3579f44d6fe037facc
Author: devozerov 
Date:   2017-06-13T13:32:58Z

Merge remote-tracking branch 'upstream/ignite-2.1.1' into ignite-2.1.1

commit 2d8c6519d36e2d7890a45b258d3b7439942dca66
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:13Z

ignite-2.1.1 Add joining node tests

commit c5cee32a510e5a3524ff88119acfd1963c74d8ad
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:30Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit d369dfc4973c179861d1d2ff37fbe8c6c0543d1a
Author: Ivan Rakov 
Date:   2017-06-13T13:47:22Z

ignite-2.1.1 IgniteSpringDataTestSuite - added vm ip finder

commit ab62ce847cb73854f31f1232144f487786a6a3d1
Author: Pavel Kovalenko 
Date:   2017-06-08T21:30:41Z

IGNITE-5267 Remove entry from on-heap locks map if it was removed from 
off-heap

commit 33a9cc4cf9b32d93e34c5855d52ce208a3fd8228
Author: Pavel Kovalenko 
Date:   2017-06-08T21:33:30Z

IGNITE-5267 

[jira] [Created] (IGNITE-5570) IgniteMessaging should have sendAsync() method

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-5570:
---

 Summary: IgniteMessaging should have sendAsync() method
 Key: IGNITE-5570
 URL: https://issues.apache.org/jira/browse/IGNITE-5570
 Project: Ignite
  Issue Type: Improvement
  Components: messaging
Affects Versions: 2.1
Reporter: Dmitry Karachentsev
 Fix For: 2.2


With old API IgniteMessaging.send() checks async mode, and if it's true, 
invokes local listener asynchronously in public pool. Support of async listener 
invocation should be added in IgniteMessaging, f.e.:

IgniteFuture sendAsync()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Zookeeper Discovery SPI & external IP address in AWS

[Valentin Kulichenko]

Igor,

What version are you going on? I believe we already fixed this in the past.

-Val

On Wed, Jun 21, 2017 at 2:30 AM Igor Rudyak  wrote:

> Hi guys,
>
> How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP address
> (in addition to private IP) of Ignite node when it's deployed in Amazon?
>
> By default it just publishing private IP addresses of nodes which makes it
> impossible to connect to cluster from outside using *Zookeeper Discovery
> SPI*.
>
> I tried to use something like this (see below) for *discoverySPI*:
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.TcpDiscoveryZookeeperIpFinder">
> 
> 
> 
> 
> 
>
> But such way it only publish public IPs to Zookeeper.
>
> Actually I am looking for something like *advertised.host.name
> * analog in Kafka. Which allows to publish
> private and public IP addresses for a node to Zookeeper.
>
> Such way all internal services communicates through private IPs, but
> external services communicates using public IPs.
>
> Igor
>

[GitHub] ignite pull request #2173: storing binary metadata on disk

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

https://github.com/apache/ignite/pull/2173

storing binary metadata on disk



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12347

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2173.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2173


commit 65d21ebd094c2d93fe18693f5f1ff9dfbb330053
Author: Ilya Lantukh 
Date:   2017-06-09T14:45:56Z

ignite-5324 : Volatile data structures.

commit f9ed6120baa6d0db826f1e58f4fd7b791711734a
Author: Alexey Goncharuk 
Date:   2017-06-09T15:15:28Z

IGNITE-5267 - Fixed NPE in checkpointer

commit bdbba0ee9a5437a3f66d05c8175bfcb2f309b3bd
Author: Dmitriy Govorukhin 
Date:   2017-06-11T18:53:56Z

IGNITE-5392 - Joining node must accept cluster active status

commit 6bf5ce46c1e6c4e3dcf042ac91a5b61a726c5821
Author: Alexey Goncharuk 
Date:   2017-06-11T20:02:44Z

IGNITE-5267 - Moved ignite-ps module to ignite-core

commit 4dc81ca86347107848328d1e2e206b796976fb23
Author: Alexey Goncharuk 
Date:   2017-06-12T05:22:49Z

IGNITE-5267 - Added missing class

commit 195147d573d7cb3fc637f74937ee561b03a3c574
Author: Dmitriy Govorukhin 
Date:   2017-06-13T05:23:38Z

IGNITE-5267 - Activate nodes after start

commit d38dfcd5c4a49b6ec4be1cfdb4f28f7d152cd14a
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:01:16Z

ignite-5267-merge remove pds dependency, restore data structures only in 
snapshot operation

commit cf886fd5816534b46a1247d3bdc41061087608e4
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:22:30Z

ignite-2.1.1 fix java doc

commit d2dcc1d032c7f9692ddfe50fa8a80e375e8d4c9b
Author: Dmitriy Govorukhin 
Date:   2017-06-13T10:45:11Z

ignite-2.1.1 fix import

commit b65ca6854828c0f2368edab202ba00f31365a3e3
Author: Ivan Rakov 
Date:   2017-06-13T10:50:31Z

ignite-2.1.1 fixing pds tests

commit 1181b478d7810d4485da43204c9f64757be6a8e4
Author: Ivan Rakov 
Date:   2017-06-13T11:51:25Z

ignite-2.1.1 fixing pds tests

commit 68739b7cffae5b4bb3714dfe12bcf93327f136b8
Author: Alexey Kuznetsov 
Date:   2017-06-13T12:27:32Z

IGNITE-5267 Snapshots support.

commit ec50e23591c4d2e2332b7a81b7218ee44f358afe
Author: Ilya Lantukh 
Date:   2017-06-13T12:34:02Z

Merge with ignite-5267-merge.

commit 4342f46ab4258f8219e45f4b69435f38b6d0f2b5
Author: Ilya Lantukh 
Date:   2017-06-13T12:37:34Z

ignite-5267 : Test for unique name per group.

commit 2b0741039e7cc6e36871b97bab53780edfc84648
Author: Ilya Lantukh 
Date:   2017-06-13T12:38:55Z

ignite-5267 : Removed redundant test.

commit 4a86cae203ed9aed953cd6093884cf8cab4531e3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T12:48:39Z

ignite-2.1.1 fix state processor, skip if daemon

commit 5c567aeb5458159bc41dbd251dfa8a65701f4861
Author: Ivan Rakov 
Date:   2017-06-13T13:06:42Z

ignite-2.1.1 moving pds tests that depend on indexing to separate suite

commit 5e9d9ebc1140f9647fc1b325ba81d0ad6c2c69f3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:20Z

ignite-2.1.1 Added description to MX bean

commit 2c2a9e652b13cf60b7e878a4e20f4ab4ae014e9c
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:39Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit 9141b3698d0ec98e512efbc78864cc06781fd8c7
Author: devozerov 
Date:   2017-06-13T13:32:28Z

IGNITE-5267: Fixed too early StoredCacheData initialization.

commit 0a00f03da78649320cb0bb3579f44d6fe037facc
Author: devozerov 
Date:   2017-06-13T13:32:58Z

Merge remote-tracking branch 'upstream/ignite-2.1.1' into ignite-2.1.1

commit 2d8c6519d36e2d7890a45b258d3b7439942dca66
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:13Z

ignite-2.1.1 Add joining node tests

commit c5cee32a510e5a3524ff88119acfd1963c74d8ad
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:30Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit d369dfc4973c179861d1d2ff37fbe8c6c0543d1a
Author: Ivan Rakov 
Date:   2017-06-13T13:47:22Z

ignite-2.1.1 IgniteSpringDataTestSuite - added vm ip finder

commit ab62ce847cb73854f31f1232144f487786a6a3d1

[jira] [Created] (IGNITE-5569) TCP Discovery SPI allows multiple NODE_JOINED / NODE_FAILED leading to a cluster DDoS

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5569:


 Summary: TCP Discovery SPI allows multiple NODE_JOINED / 
NODE_FAILED leading to a cluster DDoS
 Key: IGNITE-5569
 URL: https://issues.apache.org/jira/browse/IGNITE-5569
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.1


A firewall configuration issue may effectively lead to a cluster DDoS. The 
scheme is as follows:

1) A node G joins the cluster, and a firewall rule forbids incoming connection 
from cluster to this node
2) Cluster successfully processes NodeAddedMesage (not sure why) and sends 
NodeAddFinishedMessage
3) Each node receives NodeAddFinishedMessage and fires a discovery NODE_JOINED 
event
4) The last node in the ring fails to connect to the newly joined node and 
generates NODE_FAILED event
5) Coordinator drops the connection, joining node attempts to connect again

The issues I see here:
1) Neither coordinator nor joining node print out the reason why the joining 
node failed / did not join. A slight hint (failed to send message to the next 
node) is printed on the node with the largest order (the one that attempted to 
close the ring), but the root cause (connection refused) is also not printed
2) The joining node attempts to connect to the cluster with the same node ID. 
This violates an invariant we heavily rely on that once a node ID leaves a 
cluster, this ID never comes back again
3) Each discovery event leads to a partition exchange which blocks all cache 
operations for a time interval equal at least to the full ring latency time. If 
several nodes are started on a malicious host, this may lead to almost full 
cluster degradation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Replace Cron4J with Quartz for ignite-schedule module.

[李玉珏]

Hi，


There is also an alternative that the community can consider using the 
scheduling functionality in the spring-context module, for the following 
reasons:
1.quartz is a very heavy framework, and most functions we don't need;
2., we already have spring dependencies in our project without introducing new 
dependencies;
3.spring is also Apache 2.0 license;
4.spring's scheduler supports standard CRON, and cron4j does not support 
standard CRON;
5.spring's code quality is very good, maintainability is good, and the quality 
of quartz code is not very good.
On 06/21/2017 13:26，Alexey Kuznetsov wrote：
Hi!

1) Cron4J is very old:
  Latest Cron4j 2.2.5 released: *28-Dec-2011 *
  Latest Quarz 2.3.0 released: *20-Apr-2017*

2) Not very friendly license:
  CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
  Quartz is freely usable, licensed under the *Apache 2.0* license.

So, if we replace Cron4J  with Quartz we can move *ignite-schedule* module
 from lgpl profile to main distribution.

Any objections?

If no, I will create JIRA issue and implement this change.

-- 
Alexey Kuznetsov

[GitHub] ignite pull request #2172: IGNITE-5548

[gvvinblade]

GitHub user gvvinblade opened a pull request:

https://github.com/apache/ignite/pull/2172

IGNITE-5548



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5548

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2172.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2172


commit 8c9f1488131f77c6d2994dab033fb4aee5a524e7
Author: Igor Seliverstov 
Date:   2017-06-21T12:05:05Z

IGNITE-5548




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5568) setActiveOnStart have no effect on node startup

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-5568:
--

 Summary: setActiveOnStart have no effect on node startup
 Key: IGNITE-5568
 URL: https://issues.apache.org/jira/browse/IGNITE-5568
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Stanilovsky Evgeny
Assignee: Sergey Kozlov
 Fix For: 2.1


{code}
icfg.setActiveOnStart(true);
Ignite ignite = Ignition.start(icfg);
{code}
brings to:

Exception in thread "main" class org.apache.ignite.IgniteException: Can not 
perform the operation because the cluster is inactive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2170: H2Indexes are not deleted if key class implements...

[ezhuravl]

GitHub user ezhuravl opened a pull request:

https://github.com/apache/ignite/pull/2170

H2Indexes are not deleted if key class implements Externalizable



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12256

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2170.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2170


commit b252b441a9ada31c7200b385d75e0b3e7c0362dd
Author: Alexey Kuznetsov 
Date:   2016-12-23T11:20:44Z

Implemented Visor tasks for Services.

(cherry picked from commit fdf1f4b)

commit fb8191028eb19b0683b8239b7024f7fa6ccabd4e
Author: Alexey Kuznetsov 
Date:   2016-12-23T11:40:51Z

Updated classnames for ignite-1.7.5.

commit 2da2816fd74b17590f45781268337da5205c44fa
Author: Vasiliy Sisko 
Date:   2016-12-23T11:58:47Z

Fixed broken links.

(cherry picked from commit 6ca8670)

commit 2ccae40e2a21398d15c3762b72575216c56a7fb0
Author: dkarachentsev 
Date:   2016-12-23T14:51:49Z

IGNITE-4109 - BinaryType.isEnum() throws an exception if typeId==0

commit 9273e51cd039049a4aae73f9dcafc02915bc6153
Author: Alexandr Kuramshin 
Date:   2016-12-26T10:23:28Z

ignite-4167 Do not log cache key/values

commit 5769f44367cae5908cd291f226e9fccd68fe1c39
Author: Alexey Kuznetsov 
Date:   2016-12-27T08:14:13Z

Fixed Visor queries for BinaryObjects.

commit 5494dfb8dd222bf7aee8214b6bb201d3ae8a1ec5
Author: Ignite Teamcity 
Date:   2016-12-27T11:50:58Z

1.8.0-SNAPSHOT

commit b8cb82de65a529040ea18b0dc03fa7109c69bb4a
Author: Vasiliy Sisko 
Date:   2016-12-29T07:48:45Z

IGNITE-4442 Implemented cache affinity configuration.

(cherry picked from commit f4a1e6c)

commit 6c38eb28623271a3604ee8d966deb88677a3adb1
Author: devozerov 
Date:   2016-12-29T09:20:20Z

IGNITE-4167: Changed IGNITE_TO_STRING_INCLUDE_SENSITIVE default value to 
"true".

commit 864a95e13f1262f14351df0883d0a1abd1bf70c7
Author: sboikov 
Date:   2016-12-29T11:45:08Z

Removed duplicated benchmark.

commit da5b68cc89ba6eeff25beb66e3a4d8c2b9871ab3
Author: sboikov 
Date:   2016-12-29T12:46:59Z

For communication spi disabled pairedConnections by default, implemented 
NIO sessions balancing for this mode.

commit 71412cecd861119965a873520da96078f99c94e2
Author: Anton Vinogradov 
Date:   2016-12-30T10:41:34Z

IGNITE-4424 REPLICATED cache isn't synced across nodes

commit 121f034e5739dcc7dd9c9577c9a437acaf710a19
Author: devozerov 
Date:   2017-01-05T09:00:49Z

Merge branch 'ignite-1.8.2' into ignite-1.8.3

commit 494cf88209b196f2677e26f468aab1f98d791217
Author: devozerov 
Date:   2017-01-05T09:05:04Z

Merge branch 'ignite-1.7.5' into ignite-1.8.3

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryObjectExImpl.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/query/GridQueryProcessor.java
#   
modules/platforms/dotnet/Apache.Ignite.Benchmarks/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests.NuGet/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Cache/Query/CacheQueriesCodeConfigurationTest.cs
#   
modules/platforms/dotnet/Apache.Ignite.Core.Tests/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/Apache.Ignite.NLog/Properties/AssemblyInfo.cs
#   modules/platforms/dotnet/Apache.Ignite/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/examples/Apache.Ignite.Examples/Properties/AssemblyInfo.cs
#   
modules/platforms/dotnet/examples/Apache.Ignite.ExamplesDll/Properties/AssemblyInfo.cs

commit ac92bdb44ed0fb02893c1e7e9df4443a0a26d331
Author: Ivan Veselovskiy 
Date:   2016-12-19T08:57:00Z

IGNITE-3966: Hadoop: add Hadoop native library to Java arguments 
automatically. This closes #1320.

commit 1776e9eb04895bbb870f7c6aa89ca96db2af31b7
Author: tledkov-gridgain 
Date:   2016-12-29T08:14:10Z

IGNITE-4458: Hadoop: "striped" shuffle mode is default from now on. This 
closes #1390.

commit e7d781ee3221107d9a819dd70cb5776558a59e2a
Author: devozerov 
Date:   2017-01-05T08:30:42Z

IGNITE-4516: Hadoop: implemented optional compression for remote shuffle 
output. This closes #1399.

commit b6005b07b3e28907c8ff5cb6ebcce25bdb23bb48
Author: devozerov 
Date:   2017-01-05T11:48:06Z

IGNITE-4461: Hadoop: added automatic resolution of "raw" 

Ready for review - IGNITE-2313 (fail atomic operations within a transaction)

[Дмитрий Рябов]

Hello, please review.

PR: https://github.com/apache/ignite/pull/1709/files
JIRA: https://issues.apache.org/jira/browse/IGNITE-2313
CI:
http://ci.ignite.apache.org/viewLog.html?buildId=675135=buildResultsDiv=Ignite20Tests_RunAll

Re: More JIRA rights

[Jokser]

Thank you very much!



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/More-JIRA-rights-tp19006p19008.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: More JIRA rights

[Semyon Boikov]

Done.

On Wed, Jun 21, 2017 at 11:44 AM, Jokser  wrote:

> Hi guys,
>
> Could you please give me JIRA task workflow rights (assign, change status),
> edit descriptions and so on?
> My JIRA account is Jokser.
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/More-JIRA-rights-tp19006.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

More JIRA rights

[Jokser]

Hi guys,

Could you please give me JIRA task workflow rights (assign, change status),
edit descriptions and so on?
My JIRA account is Jokser.



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/More-JIRA-rights-tp19006.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Facing problem in examples.

[Igor Sapego]

Denis, great idea!

Best Regards,
Igor

On Wed, Jun 21, 2017 at 6:43 AM, Denis Magda  wrote:

> Thanks for confirming that the issue has been solved.
>
> I’ve added a special documentation section [1] to avoid issues like that
> in the future and placed "Platforms Interoperability Getting Started”
> callout block to C++ Getting Started Guide [2] to draw attention to these
> extra settings.
>
> [1] https://apacheignite-cpp.readme.io/docs/cross-platform-
> interoperability#binary-marshaller-configuration <
> https://apacheignite-cpp.readme.io/docs/cross-platform-
> interoperability#binary-marshaller-configuration>
> [2] https://apacheignite-cpp.readme.io/v2.0/docs/getting-
> started-1#section-start-from-command-line  readme.io/v2.0/docs/getting-started-1#section-start-from-command-line>
>
> —
> Denis
>
> > On Jun 20, 2017, at 8:05 AM, Rahul.S  wrote:
> >
> > BINGO!
> > that helped alot, it is working now thank you very much people for such a
> > positive and good support...
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Facing-problem-in-examples-tp13894p13981.html
> > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>

[jira] [Created] (IGNITE-5566) Improve TcpCommunicationSpi protocol for node stopping

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-5566:


 Summary: Improve TcpCommunicationSpi protocol for node stopping
 Key: IGNITE-5566
 URL: https://issues.apache.org/jira/browse/IGNITE-5566
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Semen Boikov
Assignee: Semen Boikov
 Fix For: 2.1


Currently if node starts stopping then TcpCommunicationSpi starts to close all 
incoming connections. In some benchmarks with large nodes number I observe that 
when client starts to stop it receives 1000s incoming connections from servers 
trying to connect to it. Need improve communication protocol and if node 
started to stop it should either immediately close NioServer or send some reply 
to connecting node so that it should stop connection attempts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2168: IGNITE-5424 Fix GridServiceProxy does not unwraps...

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

https://github.com/apache/ignite/pull/2168

IGNITE-5424 Fix GridServiceProxy does not unwraps exception message f…

…rom InvocationTargetException.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5424

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/2168.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2168


commit f169a9bfb2f074c02288dd287807ab4044282a3e
Author: dkarachentsev 
Date:   2017-06-21T07:46:33Z

IGNITE-5424 Fix GridServiceProxy does not unwraps exception message from 
InvocationTargetException.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Replace Cron4J with Quartz for ignite-schedule module.

[dsetrakyan]

Probably a good task for a newbie.

⁣D.​

On Jun 21, 2017, 9:41 AM, at 9:41 AM, Alexey Kuznetsov  
wrote:
>Done,
>
>https://issues.apache.org/jira/browse/IGNITE-5565
>
>I think it could take a couple of days in background mode.
>
>On Wed, Jun 21, 2017 at 1:40 PM, Dmitriy Setrakyan
>
>wrote:
>
>> Thanks! Please file a ticket. Do you have an idea on the amount of
>work
>> this would require?
>>
>> On Wed, Jun 21, 2017 at 8:39 AM, Alexey Kuznetsov
>
>> wrote:
>>
>> > Dima,
>> >
>> > IgniteScheduler provides functionality for scheduling jobs locally
>using
>> > UNIX cron-based syntax. Instance of GridScheduler is obtained from
>grid
>> as
>> > follows:
>> >IgniteScheduler s = Ignition.ignite().scheduler();
>> >
>> > Scheduler supports standard UNIX cron format with optional prefix
>of {n1,
>> > n2}, where n1 is delay of scheduling in seconds and n2 is the
>number of
>> > execution.
>> > Both parameters are optional. Here's an example of scheduling a
>closure
>> > that broadcasts a message to all nodes five times, once every
>minute,
>> with
>> > initial delay of two seconds:
>> >Ignition.ignite().scheduler().scheduleLocal(
>> >SchedulerFuture = Ignition.ignite().scheduler().
>> > scheduleLocal(new
>> > Callable() {
>> >@Override public Object call() throws
>IgniteCheckedException {
>> >..
>> >}
>> >}, "{2, 5} * * * * *" // 2 seconds delay with 5 executions
>only.
>> >);
>> >
>> > On Wed, Jun 21, 2017 at 1:31 PM, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>> > wrote:
>> >
>> > > Alexey,
>> > >
>> > > Can you remind what we use the schedule module in Ignite for?
>> > >
>> > > D.
>> > >
>> > > On Wed, Jun 21, 2017 at 7:26 AM, Alexey Kuznetsov <
>> akuznet...@apache.org
>> > >
>> > > wrote:
>> > >
>> > > > Hi!
>> > > >
>> > > > 1) Cron4J is very old:
>> > > >   Latest Cron4j 2.2.5 released: *28-Dec-2011 *
>> > > >   Latest Quarz 2.3.0 released: *20-Apr-2017*
>> > > >
>> > > > 2) Not very friendly license:
>> > > >   CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
>> > > >   Quartz is freely usable, licensed under the *Apache 2.0*
>license.
>> > > >
>> > > > So, if we replace Cron4J  with Quartz we can move
>*ignite-schedule*
>> > > module
>> > > >  from lgpl profile to main distribution.
>> > > >
>> > > > Any objections?
>> > > >
>> > > > If no, I will create JIRA issue and implement this change.
>> > > >
>> > > > --
>> > > > Alexey Kuznetsov
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>>
>
>
>
>--
>Alexey Kuznetsov

Re: Replace Cron4J with Quartz for ignite-schedule module.

[Alexey Kuznetsov]

Done,

https://issues.apache.org/jira/browse/IGNITE-5565

I think it could take a couple of days in background mode.

On Wed, Jun 21, 2017 at 1:40 PM, Dmitriy Setrakyan 
wrote:

> Thanks! Please file a ticket. Do you have an idea on the amount of work
> this would require?
>
> On Wed, Jun 21, 2017 at 8:39 AM, Alexey Kuznetsov 
> wrote:
>
> > Dima,
> >
> > IgniteScheduler provides functionality for scheduling jobs locally using
> > UNIX cron-based syntax. Instance of GridScheduler is obtained from grid
> as
> > follows:
> >IgniteScheduler s = Ignition.ignite().scheduler();
> >
> > Scheduler supports standard UNIX cron format with optional prefix of {n1,
> > n2}, where n1 is delay of scheduling in seconds and n2 is the number of
> > execution.
> > Both parameters are optional. Here's an example of scheduling a closure
> > that broadcasts a message to all nodes five times, once every minute,
> with
> > initial delay of two seconds:
> >Ignition.ignite().scheduler().scheduleLocal(
> >SchedulerFuture = Ignition.ignite().scheduler().
> > scheduleLocal(new
> > Callable() {
> >@Override public Object call() throws IgniteCheckedException {
> >..
> >}
> >}, "{2, 5} * * * * *" // 2 seconds delay with 5 executions only.
> >);
> >
> > On Wed, Jun 21, 2017 at 1:31 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > Alexey,
> > >
> > > Can you remind what we use the schedule module in Ignite for?
> > >
> > > D.
> > >
> > > On Wed, Jun 21, 2017 at 7:26 AM, Alexey Kuznetsov <
> akuznet...@apache.org
> > >
> > > wrote:
> > >
> > > > Hi!
> > > >
> > > > 1) Cron4J is very old:
> > > >   Latest Cron4j 2.2.5 released: *28-Dec-2011 *
> > > >   Latest Quarz 2.3.0 released: *20-Apr-2017*
> > > >
> > > > 2) Not very friendly license:
> > > >   CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
> > > >   Quartz is freely usable, licensed under the *Apache 2.0* license.
> > > >
> > > > So, if we replace Cron4J  with Quartz we can move *ignite-schedule*
> > > module
> > > >  from lgpl profile to main distribution.
> > > >
> > > > Any objections?
> > > >
> > > > If no, I will create JIRA issue and implement this change.
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> >
>



-- 
Alexey Kuznetsov

[jira] [Created] (IGNITE-5564) Race between read-through and topology version update

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5564:


 Summary: Race between read-through and topology version update
 Key: IGNITE-5564
 URL: https://issues.apache.org/jira/browse/IGNITE-5564
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.1


I occasionally observe the following assertions when working with ATOMIC cache 
with cache store on changing topology:
{code}
java.lang.AssertionError: Invalid version for inner update [isNew=false, 
entry=GridDhtAtomicCacheEntry [super=GridDhtCacheEntry [rdrs=[], 
locPart=GridDhtLocalPartition [id=157, 
map=org.apache.ignite.internal.processors.cache.GridCacheConcurrentMapImpl@7a99d0af,
 rmvQueue=GridCircularBuffer [sizeMask=31, idxGen=0], cntr=8, 
shouldBeRenting=false, state=OWNING, reservations=0, empty=false, 
createTime=06/21/2017 09:59:03], super=GridDistributedCacheEntry 
[super=GridCacheMapEntry [key=KeyCacheObjectImpl [val=1181, hasValBytes=true], 
val=CacheObjectImpl [val=1181, hasValBytes=true], startVer=1498028394357, 
ver=GridCacheVersion [topVer=109508344, time=1498028344708, 
order=1498028394358, nodeOrder=1], hash=1181, extras=GridCacheTtlEntryExtras 
[ttl=6, expireTime=1498028404707], flags=0, newVer=GridCacheVersion 
[topVer=109508343, time=1498028344709, order=1498028394369, nodeOrder=1]]
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2311)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2485)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1887)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1727)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.mapSingle(GridNearAtomicAbstractUpdateFuture.java:264)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:494)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:436)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:209)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1242)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:675)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2294)
at 
org.apache.ignite.internal.processors.cache.distributed.near.GridNearAtomicCache.put(GridNearAtomicCache.java:437)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2271)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.put(IgniteCacheProxy.java:1379)
{code}

The assertion happens because there is a race between these events:
1) An update is mapped on topology version N
2) Topology version changes and discovery updates the version to N+1, but the 
event is not yet processed by the exchange future
3) A read-through request comes in and performs the read. Inside 
{{versionedValue()}} call a new entry version is generated. Since the discovery 
version is already updated, the new entry version is based on topVer=N+1
4) Update request proceeds and read-locks the topology. Since the exchange 
future is not yet initialized, the request does not attempt to remap and 
proceeds with version N
5) The next entry version is generated using request topology version = N
6) Inside the entry update method, we assert that new version is greater than 
old version, but it's not the case in this scenario, and assertion fails

Attached is a test reproducing the issue (see testConcurrentReadThroughUpdate())



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Replace Cron4J with Quartz for ignite-schedule module.

[Dmitriy Setrakyan]

Alexey,

Can you remind what we use the schedule module in Ignite for?

D.

On Wed, Jun 21, 2017 at 7:26 AM, Alexey Kuznetsov 
wrote:

> Hi!
>
> 1) Cron4J is very old:
>   Latest Cron4j 2.2.5 released: *28-Dec-2011 *
>   Latest Quarz 2.3.0 released: *20-Apr-2017*
>
> 2) Not very friendly license:
>   CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
>   Quartz is freely usable, licensed under the *Apache 2.0* license.
>
> So, if we replace Cron4J  with Quartz we can move *ignite-schedule* module
>  from lgpl profile to main distribution.
>
> Any objections?
>
> If no, I will create JIRA issue and implement this change.
>
> --
> Alexey Kuznetsov
>

Zookeeper Discovery SPI & external IP address in AWS

[Igor Rudyak]

Hi guys,

How to force *TcpDiscoveryZookeeperIpFinder* to publish public IP address
(in addition to private IP) of Ignite node when it's deployed in Amazon?

By default it just publishing private IP addresses of nodes which makes it
impossible to connect to cluster from outside using *Zookeeper Discovery
SPI*.

I tried to use something like this (see below) for *discoverySPI*:




















But such way it only publish public IPs to Zookeeper.

Actually I am looking for something like *advertised.host.name
* analog in Kafka. Which allows to publish
private and public IP addresses for a node to Zookeeper.

Such way all internal services communicates through private IPs, but
external services communicates using public IPs.

Igor