[jira] [Created] (IGNITE-8644) CacheMetrics.getCacheMisses() returns incorrect values

[Roman Guseinov (JIRA)]

Roman Guseinov created IGNITE-8644:
--

 Summary: CacheMetrics.getCacheMisses() returns incorrect values
 Key: IGNITE-8644
 URL: https://issues.apache.org/jira/browse/IGNITE-8644
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.4
Reporter: Roman Guseinov
 Attachments: CacheMissesMetricTest.java

It looks like the correct value of this metric can be achieved only on a 
cluster of one node.

`ignite.cache(CACHE_NAME).metrics().getCacheMisses()` returns different values 
depending on cache type, backups count, nodes count, node type.

The test is attached [^CacheMissesMetricTest.java].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

Instructions for RPM Package Installation (snippet with repository 
configuration) at ignite.apache.org are obsolete and should be replaced by 
apacheignite.readme.io snippet.



> On 30 May 2018, at 02:57, Prachi Garg  wrote:
> 
> Peter,
> 
> I updated the RPM and DEB description on the downloads page[1] (following the 
> instructions on the documentation [2]). Please check that the repositories 
> and installation instructions are up-to-date.
> 
> [1] https://ignite.apache.org/download.cgi#rpm-package 
> 
> [2] 
> https://apacheignite.readme.io/docs/getting-started#section-rpm-deb-packages-installation
>  
> 
> 
> On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan  > wrote:
> I just tried the Debian install. This is what I got after executing "sudo
> apt get" command:
> 
> 
> >
> > *E: The repository 'https://apache.org/dist/ignite/deb 
> > 
> > > 
> > apache-ignite Release' does not have a
> > Release file.N: Updating from such a repository can't be done securely, and
> > is therefore disabled by default.N: See apt-secure(8) manpage for
> > repository creation and user configuration details.*
> 
> 
> D.
> 
> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  > wrote:
> 
> > Andrey,
> >
> > Please help to generate 2.5 release HTML file and add it to Ignite website
> > SVN. Sergey K and Ilya S. should be able to assist with this.
> >
> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> > can't announce the release and close it without having the docs done.
> >
> > --
> > Denis
> >
> >
> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  > > wrote:
> >
> >> Folks,
> >>
> >> I have released 2.5 documentation on readme.io . Also, 
> >> the downloads page
> >> on
> >> the website is updated with 2.5 release. Mauricio will work on updating
> >> the
> >> latest doc reference.
> >>
> >>
> >> Andrey,
> >>
> >> The following still needs attention:
> >>
> >>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/ 
> >> 
> >>2. Zookeper documentation -
> >>https://issues.apache.org/jira/browse/IGNITE-7900 
> >> 
> >>3. Consistency check utilities docs -
> >>https://issues.apache.org/jira/browse/IGNITE-8524 
> >> 
> >>
> >>
> >> Thanks,
> >> -Prachi
> >>
> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  >> > wrote:
> >>
> >> > Pavel,
> >> >
> >> > Thanks a lot!
> >> >
> >> >
> >> >
> >> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn  >> > >:
> >> >
> >> > > NuGet (.NET) packages pushed:
> >> > > https://www.nuget.org/packages?q=Apache.Ignite 
> >> > > 
> >> > >
> >> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  >> > > >
> >> wrote:
> >> > >
> >> > >> Dmitry,
> >> > >>
> >> > >> First we should check docker images. Also we are waiting for
> >> > >> publishing of artifacts to Maven Central.
> >> > >>
> >> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> >> > >> mailto:dsetrak...@apache.org>> wrote:
> >> > >> >
> >> > >> >
> >> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  >> > >> > >
> >> > wrote:
> >> > >> >>
> >> > >> >> RPM and DEB packages are published to bintray [1] [2]
> >> > >> >>
> >> > >> >> [1] https://bintray.com/apache/ignite-rpm 
> >> > >> >> 
> >> > >> >> [2] https://bintray.com/apache/ignite-deb 
> >> > >> >> 
> >> > >> >
> >> > >> >
> >> > >> > Thanks, Andrey! Can we update the download page on the website?
> >> > >> >
> >> > >> > D.
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
> 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Petr Ivanov]

I’ve updated instructions correspondingly: it seems that redirect from https to 
https requires more complicated rules, which I will try to introduce in next 
release (2.6).
Currently we should use http, i. e. ignite.list should be look like this: deb 
http://apache.org/dist/ignite/deb/ apache-ignite main



> On 30 May 2018, at 02:47, Dmitriy Setrakyan  wrote:
> 
> I just tried the Debian install. This is what I got after executing "sudo
> apt get" command:
> 
> 
>> 
>> *E: The repository 'https://apache.org/dist/ignite/deb
>>  apache-ignite Release' does not have a
>> Release file.N: Updating from such a repository can't be done securely, and
>> is therefore disabled by default.N: See apt-secure(8) manpage for
>> repository creation and user configuration details.*
> 
> 
> D.
> 
> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  wrote:
> 
>> Andrey,
>> 
>> Please help to generate 2.5 release HTML file and add it to Ignite website
>> SVN. Sergey K and Ilya S. should be able to assist with this.
>> 
>> Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
>> can't announce the release and close it without having the docs done.
>> 
>> --
>> Denis
>> 
>> 
>> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:
>> 
>>> Folks,
>>> 
>>> I have released 2.5 documentation on readme.io. Also, the downloads page
>>> on
>>> the website is updated with 2.5 release. Mauricio will work on updating
>>> the
>>> latest doc reference.
>>> 
>>> 
>>> Andrey,
>>> 
>>> The following still needs attention:
>>> 
>>>   1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
>>>   2. Zookeper documentation -
>>>   https://issues.apache.org/jira/browse/IGNITE-7900
>>>   3. Consistency check utilities docs -
>>>   https://issues.apache.org/jira/browse/IGNITE-8524
>>> 
>>> 
>>> Thanks,
>>> -Prachi
>>> 
>>> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
>>> 
 Pavel,
 
 Thanks a lot!
 
 
 
 вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
 
> NuGet (.NET) packages pushed:
> https://www.nuget.org/packages?q=Apache.Ignite
> 
> On Tue, May 29, 2018 at 8:59 PM, Andrey Gura 
>>> wrote:
> 
>> Dmitry,
>> 
>> First we should check docker images. Also we are waiting for
>> publishing of artifacts to Maven Central.
>> 
>> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>>  wrote:
>>> 
>>> 
>>> On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
 wrote:
 
 RPM and DEB packages are published to bintray [1] [2]
 
 [1] https://bintray.com/apache/ignite-rpm
 [2] https://bintray.com/apache/ignite-deb
>>> 
>>> 
>>> Thanks, Andrey! Can we update the download page on the website?
>>> 
>>> D.
>>> 
>> 
> 
> 
 
>>> 
>> 
>> 

[jira] [Created] (IGNITE-8643) Web console: Invalid chart width

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-8643:
-

 Summary: Web console: Invalid chart width
 Key: IGNITE-8643
 URL: https://issues.apache.org/jira/browse/IGNITE-8643
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Vasiliy Sisko
Assignee: Alexey Kuznetsov
 Attachments: Selection_133.png

Result charts are to wide and cut from right.

To reproduce:
 # Run demo.
 # Open Demo query page.
 # Switch result of any query to chart presentation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Prachi Garg]

Peter,

I updated the RPM and DEB description on the downloads page[1] (following
the instructions on the documentation [2]). Please check that the
repositories and installation instructions are up-to-date.

[1] https://ignite.apache.org/download.cgi#rpm-package
[2] https://apacheignite.readme.io/docs/getting-started#
section-rpm-deb-packages-installation


On Tue, May 29, 2018 at 4:47 PM, Dmitriy Setrakyan 
wrote:

> I just tried the Debian install. This is what I got after executing "sudo
> apt get" command:
>
>
> >
> > *E: The repository 'https://apache.org/dist/ignite/deb
> >  apache-ignite Release' does not
> have a
> > Release file.N: Updating from such a repository can't be done securely,
> and
> > is therefore disabled by default.N: See apt-secure(8) manpage for
> > repository creation and user configuration details.*
>
>
> D.
>
> On Tue, May 29, 2018 at 4:42 PM, Denis Magda  wrote:
>
> > Andrey,
> >
> > Please help to generate 2.5 release HTML file and add it to Ignite
> website
> > SVN. Sergey K and Ilya S. should be able to assist with this.
> >
> > Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> > can't announce the release and close it without having the docs done.
> >
> > --
> > Denis
> >
> >
> > On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:
> >
> >> Folks,
> >>
> >> I have released 2.5 documentation on readme.io. Also, the downloads
> page
> >> on
> >> the website is updated with 2.5 release. Mauricio will work on updating
> >> the
> >> latest doc reference.
> >>
> >>
> >> Andrey,
> >>
> >> The following still needs attention:
> >>
> >>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
> >>2. Zookeper documentation -
> >>https://issues.apache.org/jira/browse/IGNITE-7900
> >>3. Consistency check utilities docs -
> >>https://issues.apache.org/jira/browse/IGNITE-8524
> >>
> >>
> >> Thanks,
> >> -Prachi
> >>
> >> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
> >>
> >> > Pavel,
> >> >
> >> > Thanks a lot!
> >> >
> >> >
> >> >
> >> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
> >> >
> >> > > NuGet (.NET) packages pushed:
> >> > > https://www.nuget.org/packages?q=Apache.Ignite
> >> > >
> >> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura 
> >> wrote:
> >> > >
> >> > >> Dmitry,
> >> > >>
> >> > >> First we should check docker images. Also we are waiting for
> >> > >> publishing of artifacts to Maven Central.
> >> > >>
> >> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> >> > >>  wrote:
> >> > >> >
> >> > >> >
> >> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
> >> > wrote:
> >> > >> >>
> >> > >> >> RPM and DEB packages are published to bintray [1] [2]
> >> > >> >>
> >> > >> >> [1] https://bintray.com/apache/ignite-rpm
> >> > >> >> [2] https://bintray.com/apache/ignite-deb
> >> > >> >
> >> > >> >
> >> > >> > Thanks, Andrey! Can we update the download page on the website?
> >> > >> >
> >> > >> > D.
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Dmitriy Setrakyan]

I just tried the Debian install. This is what I got after executing "sudo
apt get" command:


>
> *E: The repository 'https://apache.org/dist/ignite/deb
>  apache-ignite Release' does not have a
> Release file.N: Updating from such a repository can't be done securely, and
> is therefore disabled by default.N: See apt-secure(8) manpage for
> repository creation and user configuration details.*


D.

On Tue, May 29, 2018 at 4:42 PM, Denis Magda  wrote:

> Andrey,
>
> Please help to generate 2.5 release HTML file and add it to Ignite website
> SVN. Sergey K and Ilya S. should be able to assist with this.
>
> Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We
> can't announce the release and close it without having the docs done.
>
> --
> Denis
>
>
> On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:
>
>> Folks,
>>
>> I have released 2.5 documentation on readme.io. Also, the downloads page
>> on
>> the website is updated with 2.5 release. Mauricio will work on updating
>> the
>> latest doc reference.
>>
>>
>> Andrey,
>>
>> The following still needs attention:
>>
>>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
>>2. Zookeper documentation -
>>https://issues.apache.org/jira/browse/IGNITE-7900
>>3. Consistency check utilities docs -
>>https://issues.apache.org/jira/browse/IGNITE-8524
>>
>>
>> Thanks,
>> -Prachi
>>
>> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
>>
>> > Pavel,
>> >
>> > Thanks a lot!
>> >
>> >
>> >
>> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
>> >
>> > > NuGet (.NET) packages pushed:
>> > > https://www.nuget.org/packages?q=Apache.Ignite
>> > >
>> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura 
>> wrote:
>> > >
>> > >> Dmitry,
>> > >>
>> > >> First we should check docker images. Also we are waiting for
>> > >> publishing of artifacts to Maven Central.
>> > >>
>> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>> > >>  wrote:
>> > >> >
>> > >> >
>> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
>> > wrote:
>> > >> >>
>> > >> >> RPM and DEB packages are published to bintray [1] [2]
>> > >> >>
>> > >> >> [1] https://bintray.com/apache/ignite-rpm
>> > >> >> [2] https://bintray.com/apache/ignite-deb
>> > >> >
>> > >> >
>> > >> > Thanks, Andrey! Can we update the download page on the website?
>> > >> >
>> > >> > D.
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Denis Magda]

Andrey,

Please help to generate 2.5 release HTML file and add it to Ignite website
SVN. Sergey K and Ilya S. should be able to assist with this.

Sergey Chugunov and Ivan R., finalize the docs as soon as you can. We can't
announce the release and close it without having the docs done.

--
Denis


On Tue, May 29, 2018 at 4:20 PM, Prachi Garg  wrote:

> Folks,
>
> I have released 2.5 documentation on readme.io. Also, the downloads page
> on
> the website is updated with 2.5 release. Mauricio will work on updating the
> latest doc reference.
>
>
> Andrey,
>
> The following still needs attention:
>
>1. Release notes for 2.5 on ignite.apache.org/releases/2.5.0/
>2. Zookeper documentation -
>https://issues.apache.org/jira/browse/IGNITE-7900
>3. Consistency check utilities docs -
>https://issues.apache.org/jira/browse/IGNITE-8524
>
>
> Thanks,
> -Prachi
>
> On Tue, May 29, 2018 at 2:08 PM, Andrey Gura  wrote:
>
> > Pavel,
> >
> > Thanks a lot!
> >
> >
> >
> > вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :
> >
> > > NuGet (.NET) packages pushed:
> > > https://www.nuget.org/packages?q=Apache.Ignite
> > >
> > > On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  wrote:
> > >
> > >> Dmitry,
> > >>
> > >> First we should check docker images. Also we are waiting for
> > >> publishing of artifacts to Maven Central.
> > >>
> > >> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
> > >>  wrote:
> > >> >
> > >> >
> > >> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura 
> > wrote:
> > >> >>
> > >> >> RPM and DEB packages are published to bintray [1] [2]
> > >> >>
> > >> >> [1] https://bintray.com/apache/ignite-rpm
> > >> >> [2] https://bintray.com/apache/ignite-deb
> > >> >
> > >> >
> > >> > Thanks, Andrey! Can we update the download page on the website?
> > >> >
> > >> > D.
> > >> >
> > >>
> > >
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Andrey Gura]

Pavel,

Thanks a lot!



вт, 29 мая 2018 г., 22:14 Pavel Tupitsyn :

> NuGet (.NET) packages pushed:
> https://www.nuget.org/packages?q=Apache.Ignite
>
> On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  wrote:
>
>> Dmitry,
>>
>> First we should check docker images. Also we are waiting for
>> publishing of artifacts to Maven Central.
>>
>> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>>  wrote:
>> >
>> >
>> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  wrote:
>> >>
>> >> RPM and DEB packages are published to bintray [1] [2]
>> >>
>> >> [1] https://bintray.com/apache/ignite-rpm
>> >> [2] https://bintray.com/apache/ignite-deb
>> >
>> >
>> > Thanks, Andrey! Can we update the download page on the website?
>> >
>> > D.
>> >
>>
>
>

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpitimeouts

[Valentin Kulichenko]

Stan,

OK, I got confused a little :)

I do agree that TcpDiscoverySpi.networkTimeout should inherit from
IgniteConfiguration.networkTImeout if not set explicitly. Do we have the
same setting for TcpCommunicationSpi, BTW? If yes, behavior should be
consistent.

As for TcpCommunicationSpi.socketWriteTimeout, I'm not sure why you want to
change its behavior. Can we just deprecate it and eventually remove, just
as we plan to do for all timeouts from #2?

-Val

On Tue, May 29, 2018 at 3:50 AM, Stanislav Lukyanov 
wrote:

> Val,
>
> Which timeouts do you mean?
>
> In #2 I don’t propose to change behavior.
>
> I propose to change behavior for a couple of settings in #3 though.
> I believe the correct approach here would be to target the behavior change
> for 2.6,
> but keep in mind that we’ll need to carefully analyze the impact before
> actually making the changes.
>
> Thanks,
> Stan
>
> From: Valentin Kulichenko
> Sent: 29 мая 2018 г. 0:57
> To: dev@ignite.apache.org
> Subject: Re: IgniteConfiguration, TcpDiscoverySpi,
> TcpCommunicationSpitimeouts
>
> Hi Stan,
>
> I'm 100% for this activity, however I don't think we should change the
> behavior of timeouts you listed in #2 - this can lead to unexpected
> behavior for users who already use them. I would just deprecate them and
> eventually remove.
>
> -Val
>
> On Mon, May 28, 2018 at 1:29 PM, Stanislav Lukyanov <
> stanlukya...@gmail.com>
> wrote:
>
> > Hi folks,
> >
> > It looks like we stopped half-way with this activity. I’d like to pick it
> > up.
> >
> > All seem to agree that we should simplify the timeout settings.
> > Here are the specific actions I’d like to propose:
> >
> > 1. Promote the use of global timeouts as the best practice
> > *What*: update the docs to encourage users to rely on the following
> > timeouts for their “network stability” settings
> > IgniteConfiguration.failureDetectionTimeout
> > IgniteConfiguration.clientFailureDetectionTimeout
> > IgniteConfiguration.networkTimeout
> > *When*: update readme.io docs for 2.5 and Javadoc for 2.6
> >
> > 2. Discourage the use of finer timeouts
> > *What*:
> > - update the docs to discourage users to use the following timeouts and
> > announce their upcoming deprecation and removal
> > TcpDiscoverySpi.socketTimeout
> > TcpDiscoverySpi.ackTimeout
> > TcpDiscoverySpi.maxAckTimeout
> > TcpDiscoverySpi.reconnectCount
> > TcpCommunicationSpi.connectTimeout
> > TcpCommunicationSpi.maxConnectTimeout
> > TcpCommunicationSpi.reconnectCount
> > - deprecate the properties in code
> > - remove the properties in code
> > *When*:
> > - readme.io update with deprecation announcement for 2.5
> > - @Deprecated in code + Javadoc update + respective readme.io rewording
> > for 2.6
> > - properties removal in 3.0
> >
> > 3. Make “orphan” timeouts rely on global timeouts, then deprecate and
> > remove
> > *What*:
> > Two settings currently don’t default to the global equivalents, although
> > they should:
> > - TcpCommunicationSpi.socketWriteTimeout should default to
> > failureDetectionTimeout
> > - TcpDiscoverySpi.networkTimeout should default to IgniteConfiguration.
> > networkTImeout
> > So the course of action would be:
> > - update the docs to explain that these timeouts have to be used for now,
> > but announce their upcoming deprecation and removal
> > - change the properties to default to their global counterparts and
> > deprecate them in code
> > - remove the properties in code
> > *When*:
> > - readme.io update with deprecation announcement for 2.5
> > - changing defaults + @Deprecated in code + Javadoc update + respective
> > readme.io rewording for 2.6
> > - properties removal in 3.0
> >
> > 4. Don’t touch other timeouts
> > Other timeouts, like TcpDiscoverySpi.joinTimeout or TcpCommunicationSpi.
> idleConnectionTimeout,
> > are orthogonal to the whole
> > “network stability” theme discussed above, and don’t have to be changed.
> >
> > Finally, I’ve prepared a draft of the docs page that may be used as a
> base
> > for the readme.io update.
> > This email is pretty long already, so please find the draft attached to
> > the JIRA issue
> > https://issues.apache.org/jira/browse/IGNITE-7704.
> >
> > Please share your thoughts.
> >
> > Thanks,
> > Stan
> >
> > From: Alexey Popov
> > Sent: 1 марта 2018 г. 17:01
> > To: dev@ignite.apache.org
> > Subject: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi
> timeouts
> >
> > Hi Igniters,
> >
> > We often see similar questions from users and customers related to
> > IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and
> > their
> > relations. And we see several side-effects after incorrect timeout
> > configuration.
> >
> > I tried to briefly describe these timeout settings (please see below) and
> > found out that the most of them do not have sense in terms of cluster
> > functions/operations and could not be explained to the users.
> >
> > I propose to deprecate most of them and leave only the timeouts we can
> > explain in common 

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Pavel Tupitsyn]

NuGet (.NET) packages pushed:
https://www.nuget.org/packages?q=Apache.Ignite

On Tue, May 29, 2018 at 8:59 PM, Andrey Gura  wrote:

> Dmitry,
>
> First we should check docker images. Also we are waiting for
> publishing of artifacts to Maven Central.
>
> On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
>  wrote:
> >
> >
> > On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  wrote:
> >>
> >> RPM and DEB packages are published to bintray [1] [2]
> >>
> >> [1] https://bintray.com/apache/ignite-rpm
> >> [2] https://bintray.com/apache/ignite-deb
> >
> >
> > Thanks, Andrey! Can we update the download page on the website?
> >
> > D.
> >
>

[GitHub] ignite pull request #4091: IGNITE-8642: Added thread dumping to FailureProce...

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-8642: Added thread dumping to FailureProcessor.



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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-8642

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

https://github.com/apache/ignite/pull/4091.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 #4091


commit 75353527233477582856b6889b6ea6f36f13984c
Author: Andrey Kuznetsov 
Date:   2018-05-29T18:59:15Z

IGNITE-8642: Added thread dumping to FailureProcessor.




---

List of Companies who use Internet of things

[Karen Stewart]

Hello there,



I would like to know if you are interested in acquiring Internet of things 
(IoT) Users List.



Information fields: Names, Title, Email, Phone, Company Name, Company URL, 
Company physical address, SIC Code, Industry, Company Size (Revenue and 
Employee).



If interested, let me know your targeted titles & targeted geography, so that 
we can get back to you with the counts and more information.


Regards,
Karen

Marketing Executive



If you are not interested in receiving further emails, please answer back with 
"overlook" in the title.

[jira] [Created] (IGNITE-8642) Failure processor should dump state of all threads

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-8642:
---

 Summary: Failure processor should dump state of all threads
 Key: IGNITE-8642
 URL: https://issues.apache.org/jira/browse/IGNITE-8642
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Gura
 Fix For: 2.6


Failure processor should dump state of all threads before failure processor 
will be invoked.

Use {{org.apache.ignite.internal.util.IgniteUtils#dumpThreads}} method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8641) SpringDataExample should use example-ignite.xml config

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-8641:
---

 Summary: SpringDataExample should use example-ignite.xml config
 Key: IGNITE-8641
 URL: https://issues.apache.org/jira/browse/IGNITE-8641
 Project: Ignite
  Issue Type: Bug
Reporter: Andrey Gura
 Fix For: 2.6


{{SpringDataExample}} uses 
{{org.apache.ignite.examples.springdata.SpringAppCfg}} as Spring configuration 
while all other example uses {{example-ignite.xml}} configuration file.

It leads to inconsistent examples behaviour.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Platform .NET add to RunAll Basic suite

[Pavel Tupitsyn]

Sorry for the late notice, but there are no tests in that PR, so the
regression is possible again.
Let's not rely on .NET tests for this.

On Tue, May 29, 2018 at 5:14 PM, Dmitry Pavlov 
wrote:

> Hi Igniters, Pavel, Ilya,
>
> Ilya's fix is merged to master. Ilya, thank you for contribution.
>
> Tests seems to be passing now. The only one left
> is DataRegionMetricsTest.TestMemoryMetrics, probably failed by
> IGNITE-8583.
>
> And I've also added dependency from Run All Basic to Platform .NET, so
> these tests will be executed on per-commit basis.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 29 мая 2018 г. в 10:49, Pavel Tupitsyn :
>
> > Dmitry, the fix looks good to me, I would appreciate if you merge it.
> >
> > Thanks,
> > Pavel
> >
> > On Tue, May 29, 2018 at 12:02 AM, Dmitry Pavlov 
> > wrote:
> >
> > > Hi Pavel,
> > >
> > > Thank you for pointing to this. We've noticed that, and Ilya K. has
> > already
> > > prepared the fix,
> > > https://issues.apache.org/jira/browse/IGNITE-8604
> > > https://github.com/apache/ignite/pull/4072
> > >
> > > If you have some time you can apply the PR, or I will merge it later.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пн, 28 мая 2018 г. в 23:45, Pavel Tupitsyn :
> > >
> > > > Hi Dmirty,
> > > >
> > > > IGNITE-5789 merge [1] introduces this bug:
> > > >
> > > > Additional cache is being started from a template (cache name ends
> with
> > > *).
> > > > Normally template caches are only started when a cache with matching
> > name
> > > > has been requested.
> > > >
> > > > Pavel
> > > >
> > > > [1]
> > > >
> > > > https://github.com/apache/ignite/commit/
> d821d0999749a1be318a2106d73654
> > > 2272a42ab0
> > > >
> > > > On Fri, May 25, 2018 at 8:23 PM, Dmitriy Setrakyan 
> > > wrote:
> > > >
> > > > > Hi Pavel, can you please respond here?
> > > > >
> > > > > -- Forwarded message --
> > > > > From: Dmitry Pavlov 
> > > > > Date: Fri, May 25, 2018 at 5:08 AM
> > > > > Subject: Platform .NET add to RunAll Basic suite
> > > > > To: dev 
> > > > >
> > > > >
> > > > > Hi Igniters,
> > > > >
> > > > > recently we've got 60-70 new test failures in .NET
> > > > >
> > > > > For me it is not simple to say which commit has failed build, so I
> > > > suggest
> > > > > the following:
> > > > >
> > > > > 1. Add Platform .NET tests to run-all basic, it will be started by
> > > > > per-VCS-commit basis. Per commit run will indicate change which
> > failed
> > > > the
> > > > > build.
> > > > >
> > > > > 2. Find out and mute flaky tests with tickets (if any).
> > > > >
> > > > > WDYT?
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Andrey Gura]

Dmitry,

First we should check docker images. Also we are waiting for
publishing of artifacts to Maven Central.

On Tue, May 29, 2018 at 8:24 PM, Dmitriy Setrakyan
 wrote:
>
>
> On Tue, May 29, 2018 at 9:08 AM, Andrey Gura  wrote:
>>
>> RPM and DEB packages are published to bintray [1] [2]
>>
>> [1] https://bintray.com/apache/ignite-rpm
>> [2] https://bintray.com/apache/ignite-deb
>
>
> Thanks, Andrey! Can we update the download page on the website?
>
> D.
>

Re: MTCGA & 6th mass run-all

[Dmitry Pavlov]

Hi Igniters,

New results (433 - tests, 22-suites). We can mention there is regression
since last mass run (3 weeks ago it was (361, 12)).

We can notice
 1) a lot of new timeouts ocurred
 2) ~72 tests came from bug indicated by .NET tests (bug was discussed in
separate thread and already fixed by Ilya K.).

But there we still can suspect that other regressions exists
- because 10 new suites falled to timeouts,
- simple calcs: 433-72 give us 361, - just like failed test number is
freezed. Several tests were defenetely fixed recently, so same count means
that fixed count=broken count.

I've attached full report to wiki (
https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=73631266
).
Please go through the results for your component and check which tests
require fixing as a priority.

Sincerely,
Dmitriy Pavlov


чт, 24 мая 2018 г. в 20:37, Denis Magda :

> Great outcomes! Can't wait seeing how many tests were fixed since the
> previous mass run.
>
> --
> Denis
>
> On Thu, May 24, 2018 at 7:06 AM, Dmitry Pavlov 
> wrote:
>
> > Hi,
> >
> > A lot of Igniters made their contributions to Make TC Green during 6 last
> > weeks. It is Aleksey Plekhanov, Maxim Muzafarov, Alexey Goncharuk, Ilya
> > Lantukh, Ivan Rakov, Alexey Kuznetsov, Taras Ledkov, Andrey Kuznetsov,
> > Alexei Scherbakov, Ivan Fedotov, Alexander Menshikov, Andrew Medvedev,
> > Andrew Mashenkov, Nikolay Izhikov, Stanilovsky Evgeny, Vyacheslav
> Daradur,
> > Alexey Kuznetsov, Pavel Kovalenko, Vitaliy Biryukov, Alexey Kukushkin,
> > Pavel Pereslegin, Amelchev Nikita.
> >
> > Folks, let me say thank you for your contributions. This effort will
> > definitely move us towards day with 0 fails.
> >
> > It’s time to check progress, so I’m going to schedule mass run-all's
> during
> > weekend. I plan to trigger these builds Fri May 25 at 15:00 GMT, 18:00
> MSK.
> > Please reply if you have objections or need TC at this time. Feel free to
> > move builds to top if you have needed fixes.
> >
> > Any finished patch review process for MTCGA PA issues is also
> appreciated.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>

Re: Ability to check and completely fill transactions on creation

[Dmitriy Setrakyan]

Anton,

We cannot have TransactionStartedEvent without having events for all other
transaction states, like TransactionPreparedEvent,
TransactionCommittedEvent, etc. Considering this, I sill do not like the
design, as we would have to create many extra event classes.

Instead, I would suggest that you create TransactionStateChangeEvent, which
would have previous and new transaction state and would cover all state
changes, not just the start of the transaction. This will make the design
consistent and thorough.

D.

On Tue, May 29, 2018 at 5:39 AM, Anton Vinogradov  wrote:

> Dmitriy,
> I fixed design according to your and Yakov's comments, thanks again for
> clear explanation.
>
> >> 1. You use internal API in public event, i.e. you cannot have user
> >> accessing to IgniteInternalTx instance through TxEvent.
>
> Event definition changed to
> public class TransactionStartedEvent extends EventAdapter {
> private IgniteTransactions tx;
> ...
> }
>
> Not it's 100% public.
>
> >> 2. Throwing runtime errors from listener is not documented and I doubt
> if
> >> it can be fully supported in the pattern you use in TxLabelTest. After
> >> looking at the mentioned test user may think that throwing runtime error
> >> when notified on new node join may prohibit new node joining which is
> not
> >> true. Do you have any example in Ignite when throwing exception from
> >> listener is valid and documented.
>
> Test's logic changed to
> ...
> // Label
> IgniteTransactions tx = evt.tx();
>
> if (tx.label() == null)
> tx.tx().rollback();
> ...
> and
> ...
> // Timeout
> Transaction tx = evt.tx().tx();
>
> if (tx.timeout() < 200)
> tx.rollback();
> ...
>
> So, tx will be rollbacked on creation and any commit attempt will cause
> TransactionRollbackException
>
> Full code listing available at
> https://github.com/apache/ignite/pull/4036/files
>
> Dmitriy, Yakov,
> Could you please check and confirm changes?
>
> чт, 24 мая 2018 г. в 16:32, Dmitriy Setrakyan :
>
> > Anton, why do you need to *alter* event sub-system to introduce a new
> > event? Yakov's issue was that you propagated private interface to public
> > API, which is bad of course. Come up with a clean design and it will be
> > accepted.
> >
> > My problem with TransactionValidator is that it only solves a small
> problem
> > for transactions. If we do that, then we will have to add cache
> validators,
> > compute validators, etc, etc, etc. That is why we either should use the
> > existing event subsystem or come up with a holistic design that will work
> > across the whole project.
> >
> > D.
> >
> > On Thu, May 24, 2018 at 1:38 AM, Anton Vinogradov  wrote:
> >
> > > Dmitriy,
> > >
> > > Yakov is against the solution based on event sub-system
> > > >> I think that we should think about some other solution instead of
> > > altering
> > > >> event sub-system.
> > >
> > > Also, I checked is there any chances to fix all the issues found by
> Yakov
> > > and see that solution becomes overcomplicated in that case.
> > > That's why I'm proposing this lightweight solution.
> > >
> > > As for me it's a good idea to have such validator since that's a common
> > > problem at huge deployments when more than one team have access to
> Ignite
> > > cluster and there is no other way to setup tx cretion rules.
> > >
> > > Yakov,
> > >
> > > Could you please share your thoughts on that?
> > >
> > >
> > > чт, 24 мая 2018 г. в 8:58, Dmitriy Setrakyan :
> > >
> > > > On Wed, May 23, 2018 at 4:08 AM, Anton Vinogradov 
> > wrote:
> > > >
> > > > > Dmitriy, Yakov
> > > > >
> > > > > Are there any objections to updated design taking into account the
> > > > comments
> > > > > I provided?
> > > > >
> > > >
> > > > Anton, I do not like an additional validator. I think you can
> > accomplish
> > > > the same with a transaction event. You just need to design it more
> > > cleanly,
> > > > incorporating the feedback from Yakov.
> > > >
> > >
> >
>

Re: I am sorry for causing confusion. IGNITE-6531

[Denis Magda]

Hello,

Thanks for outlining your problem and sending a patch for it. In general,
if such minor improvements help to solve business cases, then I would add
them to the project.

Guess, we might need to rename the interface method. Dmitriy P., as one of
the reviewers, could you please chime in and share your vision?

--
Denis

On Mon, May 28, 2018 at 6:57 AM, Ilya Lantukh  wrote:

> Welcome to Apache Ignite community!
>
> The problem with your ticket is that it's not clear what value it adds to
> the project and how it will improve user experience in general. The problem
> you described is rather narrow and I am sure it's possible to find a
> workaround without modifying Ignite code.
> If you think that such option can be helpful in more general cases, please
> explain why and how.
>
> Thanks!
>
> On Mon, May 28, 2018 at 4:27 PM, JD Nam  wrote:
>
> > Hello Igniter!
> >
> > First of all, I'm sorry. I was not aware of the ignite community process
> > well, so I did not follow the guideline and caused the confusion to the
> > community.
> > My name is joungdal.nam and I made the issue as following link.
> > https://issues.apache.org/jira/browse/IGNITE-6531
> >
> > Pleases allow me to introduce myself.
> > I am a java developer working in e-Commerce in a small country in Asia.
> > Currently, I am developing a Spring based framework (for our company
> domain
> > only).
> >
> > We had a little problems in developing our program, especially Batch.
> > Most java developers in the company for which I work are domain experts,
> > they are not getting away from jar-hell
> > There are a lot of problems associated with CPU and memory, etc., because
> > many java batches that are starting and shutdown by the scheduler work
> like
> > many beans of spring.
> > It is not possible to separate a module (lib) because it takes too much
> > time and resources.
> >
> > When I saw ignite I shouted Eureka.
> > By applying Spring-boot & Ignite's ComputeTask, I thought I'd have to a
> > Distribute Batch Platform with Daemon.
> > The main concept of this platform is to assign a job to a node with the
> > lowest load through the matrix information of the ignite cluster.
> > Since all CRUD work is handled by Oracle, ignite's distributed computing
> > seemed to be of great help (source can not be hdfs.)
> > I do not want to shutdown manually, so, the client node is managed by
> > initiating shutdown if the count of running nodes reaches the threshold
> > value by using userAttribute. The version is named to jar file name and
> > build time as postfix.
> >
> > Sorry. I'll get to the point. The reason why I created IGNITE-6531 is
> that
> > the batch of my company has too many beans.
> > Unfortunately, I am not able to tell which lib contains a particular
> bean.
> > Moreover, I am not able to remove the lib even if I find the lib (the
> > product may not be delivered to the customer)
> > Certain beans only work in stg, prod in dev, qa, stg, prod (external
> > communication issue or firewall problem)
> > Due to the nature of our Traditional Business, instances of beans are
> > created only under certain circumstances and cannot be injected in other
> > environments.
> >
> > After all, the best way to do this is to treat it the same as the method
> of
> > the spring framework.
> > When injecting another spring bean in ComputeTask,  we could write it
> just
> > like @AutoWired (required = false).
> > I did not want to see the non-operation of the daemon because of a
> runtime
> > exception due to a firewall problem.
> > So, I thought “required = false” is required @SpringResource.
> > Hope to hear your opinion on this.
> > Once, again, I would like to apologize that I did not aware of the ignite
> > process.
> >
> >
> >
> > I also have another question. I heard that there is an issue with
> > configuration on the mailing list.
> > How deploy node with different env, do you use it as below?
> >
> > In the java code,
> > try (Ignite ignite = Ignition.start("/config/ignite.xml")) { // deault
> > zone
> > try (Ignite ignite = Ignition.start("/config/ignite-dev.xml")) { // dev?
> > try (Ignite ignite = Ignition.start("/config/ignite-qa.xml")) { // qa?
> > try (Ignite ignite = Ignition.start("/config/ignite-stg.xml")) { //
> stg??
> >
> > It will be a more user friendly settling by using yaml. Our project has
> > over 300 properties
> > If yaml is supported by ignite, it would be much more convenience. (If
> you
> > do not have a plan to support spring-boot)
> > I used ignite-default.yml, ignite-dev.yml, etc in my project. By
> > distinguishing java -D options, codes are not revised and I only read
> > configuration.
> >
> >
> >
> > I think there's a mistype in the document of the link below.
> > It is the example of SqlFieldsQuery.
> > https://apacheignite-sql.readme.io/docs/java-sql-api
> > try (QueryCursor > cursor = cache.query (sql) {
> >
> > I think there should be one more ')' as below.
> > = cache.query (sql))  {
> >
> > I'll try to read 

Re: IGNITE-8238 - Operation can fails with unexpected RuntimeException when node is stopping

[Dmitriy Setrakyan]

As suggested before, please do not put blank ticket numbers into subjects
because no one understands ticket numbers. Please add titles or some other
context to the subject. This will improve the level of engagement from the
community.

I have changed the subject of this thread, let's continue the discussion
here.

D.

On Tue, May 29, 2018 at 9:10 AM, Александр Меньшиков 
wrote:

> Hi, Andrew.
>
> You suggested continuing the discussion on dev-list about IGNITE-8238 [1]
> I have reworked my PR [2]. Have I moved in the right direction?
>
> I see 57 usages of `checkpointReadLock` in the core module (without tests).
> And it still unclear for me should I catch all exceptions from
> `checkpointReadLock` or not?
> Some places look okay like usage inside overrides of `GridWorker#body`.
> But for example `GridCacheAdapter#getAllAsync0` makes me worry.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8238
> [2] https://github.com/apache/ignite/pull/3993/files
>

Re: NodeJS thin client: full API

[Denis Magda]

Hi Pavel,

Thanks for prompt improvements. I'll check them this week.

--
Denis

On Sun, May 27, 2018 at 5:04 PM, Pavel Petroshenko 
wrote:

> Hi Denis,
>
> Thanks for your feedback on the documentation! I addressed all your
> comments from https://issues.apache.org/jira/browse/IGNITE-8589.
>
> Please let me know if you have any questions.
>
> Thanks,
> p.
>
>
> On Thu, May 24, 2018 at 12:42 PM, Pavel Petroshenko  >
> wrote:
>
> > Hi Denis,
> >
> > That's a good point, thanks. This should be a part of the "Usage"
> section.
> > I'll follow up in JIRA.
> >
> > p.
> >
> > On Thu, May 24, 2018 at 10:49 AM, Denis Magda  wrote:
> >
> >> Pavel,
> >>
> >> Recalled that we've not described how to authenticate and set up SSL
> from
> >> the client side. Please consider this for the doc. Left some notes in
> the
> >> JIRA.
> >>
> >> --
> >> Denis
> >>
> >> On Wed, May 23, 2018 at 12:25 PM, Denis Magda 
> wrote:
> >>
> >> > Alexey, Pavel,
> >> >
> >> > I've done a preliminary review of the doc and moved it to the
> readme.io
> >> > page:
> >> > https://apacheignite.readme.io/v2.4/docs/nodejs-thin-client
> >> >
> >> > The page is hidden. I'll grant you access to readme so that you can
> >> update
> >> > the doc taking my suggestions into account:
> >> > https://issues.apache.org/jira/browse/IGNITE-8589
> >> >
> >> > --
> >> > Denis
> >> >
> >> >
> >> > On Mon, May 21, 2018 at 6:39 PM, Alexey Kuznetsov <
> >> akuznet...@apache.org>
> >> > wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> FYI, HZ also has NodeJs client: https://github.com/
> >> >> hazelcast/hazelcast-nodejs-client
> >> >> May be it is worth to take a look?
> >> >>
> >> >> --
> >> >> Alexey Kuznetsov
> >> >>
> >> >
> >> >
> >>
> >
> >
>

[GitHub] ignite pull request #4090: IGNITE-8610 Checkpoint history search fix + refac...

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-8610 Checkpoint history search fix + refactoring



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

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

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

https://github.com/apache/ignite/pull/4090.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 #4090


commit df3fb2a24d4d43771094e56fea6680f23e3790e6
Author: Pavel Kovalenko 
Date:   2018-05-18T09:37:13Z

IGNITE-8459 WIP

commit 54e88d22bfd4c0b61593b4a8f0d5c319288593b7
Author: Pavel Kovalenko 
Date:   2018-05-18T16:22:01Z

IGNITE-8459 WIP

commit e8aeeea9d6c30df2ee03bfada3a8a399cfef7b6b
Author: Pavel Kovalenko 
Date:   2018-05-21T12:42:33Z

IGNITE-8459 WIP

commit 7d58eb9e3c3fa2358c7937ce3f73715d850a33f1
Author: Pavel Kovalenko 
Date:   2018-05-24T19:46:24Z

IGNITE-8459 Rework.

commit bd8ef85034bbf7c03d6c8b40b36fa4398a3b23ca
Author: Pavel Kovalenko 
Date:   2018-05-24T19:50:11Z

IGNITE-8459 Remove trash.

commit b5addf2b44f8ebebc59823397e134d6796a7e3b6
Author: Pavel Kovalenko 
Date:   2018-05-25T01:18:45Z

IGNITE-8459 Fixed tests.

commit fe4d681ae4341accf047b8408a97a22d34f5520f
Author: Pavel Kovalenko 
Date:   2018-05-28T12:09:21Z

IGNITE-8459 Tests refactoring.

commit 702b88c7466555091c95890a4aa024d869c399f3
Author: Pavel Kovalenko 
Date:   2018-05-28T12:14:14Z

IGNITE-8459 Increase test running time.

commit 5b2ccaacafb2ef3c3e02730958c7708768b7c265
Author: Pavel Kovalenko 
Date:   2018-05-28T13:22:54Z

Merge branch 'master' into ignite-8459

# Conflicts:
#   
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/persistence/IgnitePdsCacheRebalancingAbstractTest.java

commit cc2fda56ecc48ae878baffe5079d25c917a1280c
Author: Pavel Kovalenko 
Date:   2018-05-28T14:25:30Z

IGNITE-8482 Tests improvements.

commit edd27a9ba264581e1d0541c2aafc30451dc469b3
Author: Pavel Kovalenko 
Date:   2018-05-28T14:28:18Z

IGNITE-8482 Remove unused import.

commit e4e1cb92e016230dc8c8b270c2f8dfe72cc3d098
Author: Pavel Kovalenko 
Date:   2018-05-29T14:36:01Z

IGNITE-8610 WIP

commit bae83681794bd02e708647494eba094a4213a9f9
Author: Pavel Kovalenko 
Date:   2018-05-29T16:55:22Z

IGNITE-8610 WIP




---

[GitHub] ignite pull request #4089: Ignite 6587 true

[andrey-kuznetsov]

GitHub user andrey-kuznetsov opened a pull request:

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

Ignite 6587 true

For TC tests now

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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6587-true

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

https://github.com/apache/ignite/pull/4089.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 #4089


commit 3b25cb934838feb3300c7088db4b3840ec7f9ab5
Author: Andrey Kuznetsov 
Date:   2018-05-07T12:43:26Z

IGNITE-6587: Refactored ServerImpl.TcpServer to use GridWorker.

commit 665ba863ceb95b643a805d6920f3f384275dae20
Author: Andrey Kuznetsov 
Date:   2018-05-07T13:06:22Z

IGNITE-6587: Refactored ServerImpl.RingMessageWorker to use GridWorker.

commit b10bcd350efb55de95792b369996ba266b3612a9
Author: Andrey Kuznetsov 
Date:   2018-05-07T15:59:56Z

IGNITE-6587: Refactored WAL manager critical threads to use GridWorker.

commit 3154112c8bab70d1ff4fe20639648e8a9c7da373
Author: Andrey Kuznetsov 
Date:   2018-05-07T18:55:25Z

IGNITE-6587: Minor improvements.

commit a44fc8064a9ba8f42e4faacde018ac9bc1193f01
Author: Andrey Kuznetsov 
Date:   2018-05-08T10:52:01Z

IGNITE-6587: Refactored CommunicationWorker to use GridWorker.

commit 0efc5354f33666ac705c738d75955258084091de
Author: Andrey Kuznetsov 
Date:   2018-05-08T15:25:56Z

IGNITE-6587: (WIP) switching to timed waits/polls, updating heartbeats.

commit 48c889441a119ef2192c1ff61485c20f80659e82
Author: Andrey Kuznetsov 
Date:   2018-05-14T13:38:47Z

IGNITE-6587: Heartbeat updates in critical WAL manager workers.

commit 69059bda2071f7d6af0cef30cf8d77b160fc56be
Author: Andrey Kuznetsov 
Date:   2018-05-14T15:55:51Z

IGNITE-6587: (WiP) More heartbeat updates in critical workers.

commit 6fb2edf1fef15bb187481f89eddb3710d5daadba
Author: Andrey Kuznetsov 
Date:   2018-05-15T13:09:16Z

IGNITE-6587: Heartbeat updates in checkpointer.

commit 9cd8cba1fdc8c21d999df4c334daaef7e226aa0f
Author: Andrey Kuznetsov 
Date:   2018-05-15T13:23:17Z

IGNITE-6587: More heartbeat updates in critical workers.

commit 5245abc0c72812c4746127b25638a28dac7af11a
Author: Andrey Kuznetsov 
Date:   2018-05-16T20:14:31Z

IGNITE-6587: Extended StripedExecutor.Stripe from GridWorker.

commit 2eb448f6a7ff7a6be423742336480a7b98793c2d
Author: Andrey Kuznetsov 
Date:   2018-05-17T11:37:08Z

IGNITE-6587: Heartbeat updates in StripedExecutor workers.

commit 8304fa92879fe293f112d1c7ba515b5bd30cc271
Author: Andrey Kuznetsov 
Date:   2018-05-17T12:33:23Z

Merge branch 'master' into ignite-6587

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/FileWriteAheadLogManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/FsyncModeFileWriteAheadLogManager.java

commit 5051aa4d44e78b5362dd0094bc5a57566eea4855
Author: Andrey Kuznetsov 
Date:   2018-05-17T12:36:23Z

IGNITE-6587: Addition to merge commit.

commit 732d2c25013d94d67188f42b2f96c786eeaf6346
Author: Andrey Kuznetsov 
Date:   2018-05-17T12:42:05Z

IGNITE-6587: Updated WAL FileDecompressors to conform uniform poll style.

commit 0c6f7762f1bc709c1444e545ff6475edc3fd6152
Author: Andrey Kuznetsov 
Date:   2018-05-18T09:54:05Z

IGNITE-6587: Added Checkpointer to worker registry.

commit d64e2f8e97e9d8a339695087ceea1443f8f75141
Author: Andrey Kuznetsov 
Date:   2018-05-18T14:43:22Z

IGNITE-6587: Added Stripe workers to worker registry.

commit fd142e80f80e73d420c0a03923ba3a4783dc7f34
Author: Andrey Kuznetsov 
Date:   2018-05-21T11:40:46Z

IGNITE-6587: Optional reference to worker registry in GridNioServer.

commit de98f8782f1728cc7e4a2852fbd0931cb21d3af9
Author: Andrey Kuznetsov 
Date:   2018-05-21T11:42:11Z

IGNITE-6587: Added worker registry to communication SPI GridNioServer.

commit f24f93abe8b8a3833f556b204c9995d28cd9cf44
Author: Andrey Kuznetsov 
Date:   2018-05-21T13:47:11Z

Merge branch 'master' into ignite-6587

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/FileWriteAheadLogManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/FsyncModeFileWriteAheadLogManager.java

commit e3a7b9aaed79d45b205715b6b281db702e7be95d
Author: Andrey Kuznetsov 
Date:   2018-05-22T12:30:30Z

IGNITE-6587: Recovering after incorrect merge commit.

commit 45c64a1ebaf5dabcfdf64e35a14542c0bddaa4c2
Author: Andrey Kuznetsov 
Date:   2018-05-22T12:56:27Z

IGNITE-6587: Moved WAL timeout constants to proper place.

commit 95f1ce0a9c3002a72fa47c616f928521570d2d40
Author: Andrey Kuznetsov 
Date:   2018-05-22T13:12:36Z

IGNITE-6587: Made WAL FileDecompressors not critical again.

commit 

IGNITE-8238

[Александр Меньшиков]

Hi, Andrew.

You suggested continuing the discussion on dev-list about IGNITE-8238 [1]
I have reworked my PR [2]. Have I moved in the right direction?

I see 57 usages of `checkpointReadLock` in the core module (without tests).
And it still unclear for me should I catch all exceptions from
`checkpointReadLock` or not?
Some places look okay like usage inside overrides of `GridWorker#body`.
But for example `GridCacheAdapter#getAllAsync0` makes me worry.

[1] https://issues.apache.org/jira/browse/IGNITE-8238
[2] https://github.com/apache/ignite/pull/3993/files

Re: [RESULT] [VOTE] Apache Ignite 2.5.0 Release (RC1)

[Andrey Gura]

RPM and DEB packages are published to bintray [1] [2]

[1] https://bintray.com/apache/ignite-rpm
[2] https://bintray.com/apache/ignite-deb

On Mon, May 28, 2018 at 5:38 PM, Andrey Gura  wrote:
> Igniters,
>
> Apache Ignite 2.5.0 release (RC1) has been accepted.
>
> 4 "+1" binding votes received:
>
> - Alexey Kuznetsov
> - Denis Magda
> - Pavel Tupitsyn
> - Valentin Kulichenko
>
> Vote thread:
>
> *http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-5-0-RC1-td30923.html
> *
>
> Ignite 2.5.0 will be released soon.

Re: Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.

[Dmitry Pavlov]

Hi Ray,

Could you also please resolve conflicts in PR?

Conflicting files
modules/spark-2.10/pom.xml

вт, 29 мая 2018 г. в 18:19, Dmitry Pavlov :

> Hi Ray,
>
> Status of this ticket is In Progress, so it is not displayed in filters.
>
> Could you please set status to Patch Available if PR is ready for review?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 28 мая 2018 г. в 8:40, Ray :
>
>> Valentin Kulichenko and Nikolay Izhikov can you please take a look at PR
>> and
>> provide comments? Other reviewers are welcome as well.
>>
>> https://github.com/apache/ignite/pull/4033
>>
>> I modified Ignite Spark module to fit Spark 2.3 APIs and removed
>> spark-2.10
>> module because Spark 2.3 stooped support for scala 2.10.
>> https://issues.apache.org/jira/browse/SPARK-19810
>>
>> Also, please find the dev list discussion thread here.
>>
>> http://apache-ignite-developers.2346864.n4.nabble.com/Discussion-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-0-td30762.html
>>
>> Ray
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>
>

[GitHub] ignite pull request #4087: IGNITE-8636 debug logging for client join scenari...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #1917: IGNITE-5011: Add validation on args and show prop...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.

[Dmitry Pavlov]

Hi Ray,

Status of this ticket is In Progress, so it is not displayed in filters.

Could you please set status to Patch Available if PR is ready for review?

Sincerely,
Dmitriy Pavlov

пн, 28 мая 2018 г. в 8:40, Ray :

> Valentin Kulichenko and Nikolay Izhikov can you please take a look at PR
> and
> provide comments? Other reviewers are welcome as well.
>
> https://github.com/apache/ignite/pull/4033
>
> I modified Ignite Spark module to fit Spark 2.3 APIs and removed spark-2.10
> module because Spark 2.3 stooped support for scala 2.10.
> https://issues.apache.org/jira/browse/SPARK-19810
>
> Also, please find the dev list discussion thread here.
>
> http://apache-ignite-developers.2346864.n4.nabble.com/Discussion-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-0-td30762.html
>
> Ray
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #4043: IGNITE-8406

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4088: ignite-7163 Validate connection from a pre-previo...

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

ignite-7163 Validate connection from a pre-previous node



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

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

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

https://github.com/apache/ignite/pull/4088.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 #4088






---

Re: IGNITE-6827 - Review needed.

[Dmitry Pavlov]

Hi Nick,

I can't find any timeouts specified for transaction creation in IGNITE-6967
code (for services cache), so I'm not sure current fix wil help. But anyway
soon it can be double-checked with 2.5 release.

I hope IGNITE-6967 will be fixed soon in the IEP-17. Vyacheslav Daradur
picked up this task. So workaround will not be necessary.

Sincerely,
Dmitriy Pavlov

чт, 17 мая 2018 г. в 20:36, npordash :

> Hi,
>
> Would IGNITE-6827 potentially be a workaround for IGNITE-6967? I understand
> that eventually IGNITE-6967 will not be applicable once the service grid
> stops using the utility cache and switches to discovery messages, but I've
> encountered odd deadlocks with PME and I'm growing more suspicious that
> it's
> happening due to IGNITE-6967 because it seems to only happen when nodes
> start flapping (f.e. due to faulty VM hardware).
>
> -Nick
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #4077: IGNITE-8624: Add reproducer to IGNITE-8624 issue.

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: IGNITE-640: multimap initial implementation

[Dmitry Pavlov]

Hi Amir,

As far as I know, several Igniters provided some feedback in ticket. Are
you agree?

Sincerely,
Dmitriy Pavlov

чт, 10 мая 2018 г. в 20:01, Dmitry Pavlov :

> Hi Amir,
>
> This is a very necessary contribution, the patch defenetely will not be
> ignored.
>
> Igniters,
>
> Who can make a review from the committers?
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 8 мая 2018 г. в 5:52, Amir Akhmedov :
>
>> Hi Igniters,
>>
>> Can someone take a look at this PR please?
>>
>> Thanks,
>> Amir
>>
>> On Mon, Apr 30, 2018 at 5:28 AM, Pavel Tupitsyn 
>> wrote:
>>
>> > Hi Amir,
>> >
>> > I have filed [1] for multimap in .NET, it will be done later.
>> > In order to fix IgniteParityTest failures, please add the following to
>> > MissingMembers array there:
>> >
>> > "multimap" // IGNITE-8425
>> >
>> > Thanks,
>> > Pavel
>> >
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-8425
>> >
>> > On Sun, Apr 29, 2018 at 11:32 PM, Amir Akhmedov <
>> amir.akhme...@gmail.com>
>> > wrote:
>> >
>> > > Hi Igniters,
>> > >
>> > > I raised a pull request [1] for Ignite multimap [2]. TC run [3] seems
>> ok
>> > to
>> > > me, some tests are failed though. Can someone review it please and
>> let me
>> > > know?
>> > >
>> > > Thanks,
>> > > Amir
>> > >
>> > > [1] https://github.com/apache/ignite/pull/3926
>> > > [2] https://issues.apache.org/jira/browse/IGNITE-640
>> > > [3]
>> > > https://ci.ignite.apache.org/viewLog.html?buildId=1255210
>> > > b=buildResultsDiv=IgniteTests24Java8_RunAll
>> > >
>> >
>>
>

[jira] [Created] (IGNITE-8639) Query with a lot of nesting causes NPE in org.h2.util.StringUtils.indent

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-8639:
---

 Summary: Query with a lot of nesting causes NPE in 
org.h2.util.StringUtils.indent
 Key: IGNITE-8639
 URL: https://issues.apache.org/jira/browse/IGNITE-8639
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.6
Reporter: Ilya Kasnacheev
 Attachments: SqlNestedQuerySelfTest.java

Worked in 1.7!

But now:
{code}
sql("WITH cacheJoin (txId, stage, tStamp)" +
  " AS (SELECT t.txId, o.stage, o.tStamp FROM txs t INNER JOIN ops 
o ON t.txId = o.txId)" +
" SELECT ou.stage, COUNT(*) as cou, SUM(CASE WHEN ou.stage = 
in.stage THEN 1 ELSE 0 END) AS ttl" +
  " FROM (SELECT txId, stage FROM cacheJoin cte GROUP BY txId, 
stage) ou" +
" INNER JOIN (SELECT mx.txId, mx.stage FROM (SELECT txId, 
tStamp, stage FROM cacheJoin cte) mx" +
  " INNER JOIN (SELECT txId, MAX(tStamp) AS maxTStamp FROM 
cacheJoin cte GROUP BY txId) mix" +
" ON mx.txId = mix.txId AND mx.tStamp = mix.maxTStamp) in 
ON ou.txId = in.txId" +
" GROUP BY ou.stage");
{code}
{code}
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
parse query. Внутренняя ошибка: "java.lang.NullPointerException"
General error: "java.lang.NullPointerException" [5-195]

at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2026)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:1796)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1652)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2035)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2030)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2578)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2044)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1990)
at 
org.apache.ignite.internal.processors.query.SqlNestedQuerySelfTest.sql(SqlNestedQuerySelfTest.java:73)
at 
org.apache.ignite.internal.processors.query.SqlNestedQuerySelfTest.testNestingQuery(SqlNestedQuerySelfTest.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2086)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2001)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.h2.jdbc.JdbcSQLException: Внутренняя ошибка: 
"java.lang.NullPointerException"
General error: "java.lang.NullPointerException" [5-195]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convert(DbException.java:295)
at org.h2.message.DbException.toSQLException(DbException.java:268)
at org.h2.message.TraceObject.logAndConvert(TraceObject.java:352)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:292)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepare0(IgniteH2Indexing.java:484)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:452)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:419)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatementAndCaches(IgniteH2Indexing.java:2008)
... 19 more
Caused by: java.lang.NullPointerException
at org.h2.util.StringUtils.indent(StringUtils.java:594)
at org.h2.util.StringUtils.indent(StringUtils.java:582)
at org.h2.table.TableView.getSQL(TableView.java:436)
at org.h2.command.dml.Select.getPlanSQL(Select.java:1083)
at org.h2.index.ViewIndex.getPlanSQL(ViewIndex.java:134)
at 

[GitHub] ignite pull request #4087: IGNITE-8636 debug logging for client join scenari...

[sergey-chugunov-1985]

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

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

IGNITE-8636 debug logging for client join scenario



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

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

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

https://github.com/apache/ignite/pull/4087.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 #4087


commit a4f650a870f23314e0ce0fdedf5e36627887bfe2
Author: Sergey Chugunov 
Date:   2018-05-29T12:05:12Z

IGNITE-8636 debug logging for client join scenario




---

[GitHub] ignite pull request #4086: IGNITE-8530 fixed onNodeLeft for InitNewCoordinat...

[akalash]

GitHub user akalash opened a pull request:

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

IGNITE-8530 fixed onNodeLeft for InitNewCoordinatorFuture



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

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

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

https://github.com/apache/ignite/pull/4086.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 #4086


commit 30e7ea547781d37248445adbd61e709ec27c9ddf
Author: Anton Kalashnikov 
Date:   2018-05-29T13:10:59Z

IGNITE-8530 fixed onNodeLeft for InitNewCoordinatorFuture




---

[jira] [Created] (IGNITE-8638) CPP Thin: Implement Cache API for C++ thin client

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-8638:
---

 Summary: CPP Thin: Implement Cache API for C++ thin client
 Key: IGNITE-8638
 URL: https://issues.apache.org/jira/browse/IGNITE-8638
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 2.5
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.6


Add Cache API for C++ thin client.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8637) Web Console: Fix the UI bugs

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-8637:
-

 Summary: Web Console: Fix the UI bugs
 Key: IGNITE-8637
 URL: https://issues.apache.org/jira/browse/IGNITE-8637
 Project: Ignite
  Issue Type: Bug
  Components: UI, wizards
Reporter: Vica Abramova
 Attachments: UI bugs.png, image-2018-05-29-15-40-04-530.png

 !UI bugs.png! 
* Move the icon to the right (margin:10px)
* Align all the texts -> see attached  !image-2018-05-29-15-40-04-530.png! 
* Move the white icons 1px upward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Ability to check and completely fill transactions on creation

[Anton Vinogradov]

Dmitriy,
I fixed design according to your and Yakov's comments, thanks again for
clear explanation.

>> 1. You use internal API in public event, i.e. you cannot have user
>> accessing to IgniteInternalTx instance through TxEvent.

Event definition changed to
public class TransactionStartedEvent extends EventAdapter {
private IgniteTransactions tx;
...
}

Not it's 100% public.

>> 2. Throwing runtime errors from listener is not documented and I doubt
if
>> it can be fully supported in the pattern you use in TxLabelTest. After
>> looking at the mentioned test user may think that throwing runtime error
>> when notified on new node join may prohibit new node joining which is
not
>> true. Do you have any example in Ignite when throwing exception from
>> listener is valid and documented.

Test's logic changed to
...
// Label
IgniteTransactions tx = evt.tx();

if (tx.label() == null)
tx.tx().rollback();
...
and
...
// Timeout
Transaction tx = evt.tx().tx();

if (tx.timeout() < 200)
tx.rollback();
...

So, tx will be rollbacked on creation and any commit attempt will cause
TransactionRollbackException

Full code listing available at
https://github.com/apache/ignite/pull/4036/files

Dmitriy, Yakov,
Could you please check and confirm changes?

чт, 24 мая 2018 г. в 16:32, Dmitriy Setrakyan :

> Anton, why do you need to *alter* event sub-system to introduce a new
> event? Yakov's issue was that you propagated private interface to public
> API, which is bad of course. Come up with a clean design and it will be
> accepted.
>
> My problem with TransactionValidator is that it only solves a small problem
> for transactions. If we do that, then we will have to add cache validators,
> compute validators, etc, etc, etc. That is why we either should use the
> existing event subsystem or come up with a holistic design that will work
> across the whole project.
>
> D.
>
> On Thu, May 24, 2018 at 1:38 AM, Anton Vinogradov  wrote:
>
> > Dmitriy,
> >
> > Yakov is against the solution based on event sub-system
> > >> I think that we should think about some other solution instead of
> > altering
> > >> event sub-system.
> >
> > Also, I checked is there any chances to fix all the issues found by Yakov
> > and see that solution becomes overcomplicated in that case.
> > That's why I'm proposing this lightweight solution.
> >
> > As for me it's a good idea to have such validator since that's a common
> > problem at huge deployments when more than one team have access to Ignite
> > cluster and there is no other way to setup tx cretion rules.
> >
> > Yakov,
> >
> > Could you please share your thoughts on that?
> >
> >
> > чт, 24 мая 2018 г. в 8:58, Dmitriy Setrakyan :
> >
> > > On Wed, May 23, 2018 at 4:08 AM, Anton Vinogradov 
> wrote:
> > >
> > > > Dmitriy, Yakov
> > > >
> > > > Are there any objections to updated design taking into account the
> > > comments
> > > > I provided?
> > > >
> > >
> > > Anton, I do not like an additional validator. I think you can
> accomplish
> > > the same with a transaction event. You just need to design it more
> > cleanly,
> > > incorporating the feedback from Yakov.
> > >
> >
>

[GitHub] ignite pull request #4072: IGNITE-8604 Avoid starting cache templates on cli...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4085: Ignite 8476 no macs

[glukos]

GitHub user glukos opened a pull request:

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

Ignite 8476 no macs



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

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

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

https://github.com/apache/ignite/pull/4085.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 #4085


commit e6346f53da593dbe6df8bd7ccfcb1b2d94bc3797
Author: Ivan Rakov 
Date:   2018-05-29T11:46:51Z

IGNITE-8476 AssertionError exception occurs when trying to remove node from 
baseline under loading

commit 2708f95746f2a4d3f2bcfca1209d163a4bba8e9e
Author: Ivan Rakov 
Date:   2018-05-29T11:49:56Z

IGNITE-8476 AssertionError exception occurs when trying to remove node from 
baseline under loading -macs fix




---

[GitHub] ignite pull request #4083: IGNITE-8476 AssertionError exception occurs when ...

[glukos]

GitHub user glukos opened a pull request:

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

IGNITE-8476 AssertionError exception occurs when trying to remove nod…



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

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

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

https://github.com/apache/ignite/pull/4083.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 #4083


commit e6346f53da593dbe6df8bd7ccfcb1b2d94bc3797
Author: Ivan Rakov 
Date:   2018-05-29T11:46:51Z

IGNITE-8476 AssertionError exception occurs when trying to remove node from 
baseline under loading




---

Re: Platform .NET add to RunAll Basic suite

[Pavel Tupitsyn]

Dmitry, the fix looks good to me, I would appreciate if you merge it.

Thanks,
Pavel

On Tue, May 29, 2018 at 12:02 AM, Dmitry Pavlov 
wrote:

> Hi Pavel,
>
> Thank you for pointing to this. We've noticed that, and Ilya K. has already
> prepared the fix,
> https://issues.apache.org/jira/browse/IGNITE-8604
> https://github.com/apache/ignite/pull/4072
>
> If you have some time you can apply the PR, or I will merge it later.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 28 мая 2018 г. в 23:45, Pavel Tupitsyn :
>
> > Hi Dmirty,
> >
> > IGNITE-5789 merge [1] introduces this bug:
> >
> > Additional cache is being started from a template (cache name ends with
> *).
> > Normally template caches are only started when a cache with matching name
> > has been requested.
> >
> > Pavel
> >
> > [1]
> >
> > https://github.com/apache/ignite/commit/d821d0999749a1be318a2106d73654
> 2272a42ab0
> >
> > On Fri, May 25, 2018 at 8:23 PM, Dmitriy Setrakyan 
> wrote:
> >
> > > Hi Pavel, can you please respond here?
> > >
> > > -- Forwarded message --
> > > From: Dmitry Pavlov 
> > > Date: Fri, May 25, 2018 at 5:08 AM
> > > Subject: Platform .NET add to RunAll Basic suite
> > > To: dev 
> > >
> > >
> > > Hi Igniters,
> > >
> > > recently we've got 60-70 new test failures in .NET
> > >
> > > For me it is not simple to say which commit has failed build, so I
> > suggest
> > > the following:
> > >
> > > 1. Add Platform .NET tests to run-all basic, it will be started by
> > > per-VCS-commit basis. Per commit run will indicate change which failed
> > the
> > > build.
> > >
> > > 2. Find out and mute flaky tests with tickets (if any).
> > >
> > > WDYT?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > >
> >
>

[jira] [Created] (IGNITE-8635) Add a method to inspect BinaryObject size

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8635:


 Summary: Add a method to inspect BinaryObject size
 Key: IGNITE-8635
 URL: https://issues.apache.org/jira/browse/IGNITE-8635
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk


Currently only concrete implementations of {{BinaryObject}} interface provide 
some information regarding the object serialized size. It makes it hard for 
users to reason about storage size and estimate required storage capacity.

We need to add a method to the {{BinaryObject}} interface itself to return the 
actual size required to store the object.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8634) Web Console: Remove shadow from "Beta" ribbon and header delimeter.

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-8634:


 Summary: Web Console: Remove shadow from "Beta" ribbon and header 
delimeter.
 Key: IGNITE-8634
 URL: https://issues.apache.org/jira/browse/IGNITE-8634
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 2.6


Lets remove shadows for better UI/UX.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)