Re: PRIORITY Action required: Security review for non-https dependency urls

2019-05-22 Thread Petr Ivanov 
Found only these lines (see below), though I would replace all URLs in poms and 
readmes at least to https.


http://h2database.com/m2-repo  [1]
http://hadoop.apache.org/docs/current/api/ [2]


[1] 
https://github.com/apache/ignite/blob/6e9ec03659e5f35c0f18605079fbced1e42ad130/parent/pom.xml#L233
[2] 
https://github.com/apache/ignite/blob/6e9ec03659e5f35c0f18605079fbced1e42ad130/parent/pom.xml#L339



> On 21 May 2019, at 21:38, Denis Magda  wrote:
> 
> Yeap,
> 
> This looks like a candidate for the change.
> 
> Peter, Anton, is there a quick way to prepare a list of such dependencies 
> where "http" is to be replaced with "https"?
> 
> --
> Denis Magda
> 
> 
> On Tue, May 21, 2019 at 7:17 AM Ilya Kasnacheev  > wrote:
> Hello!
> 
> I think we still have a http dependency on H2:
> 
> 
> 
> false
> 
> 
> true
> always
> ignore
> 
> h2database.com 
> Snapshot repository on h2database.com 
> 
> http://h2database.com/m2-repo 
> 
> default
> 
> 
> WDYT?
> 
> Regards,
> -- 
> Ilya Kasnacheev
> 
> 
> вт, 21 мая 2019 г. в 17:08, Denis Magda  >:
> 
> > Igniters,
> >
> > Could anybody confirm we don’t have any issues with that?
> >
> > Denis
> >
> > -- Forwarded message --
> > From: *Apache Security Team*  > >
> > Date: Tuesday, May 21, 2019
> > Subject: PRIORITY Action required: Security review for non-https dependency
> > urls
> > To: Apache Security Team mailto:secur...@apache.org>>
> >
> >
> > ASF Security received a report that a number of Apache projects have
> > build dependencies downloaded using insecure urls. The reporter states
> > this could be used in conjunction with a man-in-the-middle attack to
> > compromise project builds.  The reporter claims this a significant
> > issue and will be making an announcement on June 10th and a number of
> > press releases and industry reaction is expected.
> >
> > We have already contacted each of the projects the reporter detected.
> > However we have not run any scanning ourselves to identify any other
> > instances hence this email.
> >
> > We request that you review any build scripts and configurations for
> > insecure urls where appropriate to your projects, fix them asap, and
> > report back if you had to change anything to secur...@apache.org 
> >  by
> > the 31st May 2019.
> >
> > The most common finding was HTTP references to repos like maven.org 
> >  in
> > build files (Gradle, Maven, SBT, or other tools).  Here is an example
> > showing repositories being used with http urls that should be changed
> > to https:
> >
> > https://github.com/apache/flink/blob/d1542e9561c6235feb902c9c6d781b 
> > 
> > a416b8f784/pom.xml#L1017-L1038
> >  >  
> > >
> >
> > Note that searching for http:// might not be enough, look for http\://
> > too due to escaping.
> >
> > Although this issue is public on June 10th, please make fixes to
> > insecure urls immediately.  Also note that some repos will be moving
> > to blocking http transfers in June and later:
> >
> > https://central.sonatype.org/articles/2019/Apr/30/http- 
> > 
> > access-to-repo1mavenorg-and-repomavenapacheorg-is-being-deprecated/
> >
> > The reporter claims that a full audit of affected projects is required
> > to ensure builds were not made with tampered dependencies, and that
> > CVE names should be given to each project, however we are not
> > requiring this -- we believe it’s more likely a third party repo could
> > be compromised with a malicious build than a MITM attack.   If you
> > disagree, let us know. Projects like Lucene do checksum whitelists of
> > all their build dependencies, and you may wish to consider that as a
> > protection against threats beyond just MITM.
> >
> > Best Regards,
> > Mark J Cox
> > VP, ASF Security Team
> >
> >
> >
> > --
> > -
> > Denis
> >

Re: [VOTE] Accept Apache Ignite 2.7.5-rc3

2019-05-22 Thread Denis Magda 
The next Ignite release will go with much more changes and fixes sitting in
the waiting queue while this maintenance release was baked for several
months.

Dmitriy P. are there any blockers, should we restart the vote?

Denis


On Wednesday, May 22, 2019, Andrey Gura  wrote:

> Denis,
>
> I really don't see any reason for releasing the next Apache Ignitie
> version only for this minor fix. Release process is complex enough and
> it seems that easier way is issue fix and build rc4.
>
> Anyway, if we didn't commit about Java 12 support in this version so
> I'm okay with this issue in current build.
>
> On Wed, May 22, 2019 at 4:20 AM Denis Magda  wrote:
> >
> > Andrey,
> >
> > I would encourage us to roll this release out and consider this change
> for
> > the next one. We’re free to make the next release as soon as needed,
> even a
> > couple of weeks after.
> >
> > Do you agree?
> >
> > Denis
> >
> > On Tuesday, May 21, 2019, Andrey Gura  wrote:
> >
> > > Ilya, do you have any estimation for fix Java 12 with SSL issue?
> > >
> > > On Tue, May 21, 2019 at 10:26 PM Denis Magda 
> wrote:
> > > >
> > > > Ignite PMC and committers, please cast your vote. It's time to roll
> the
> > > release out.
> > > >
> > > > --
> > > > Denis Magda
> > > >
> > > >
> > > > -- Forwarded message -
> > > > From: Denis A. Magda 
> > > > Date: Tue, May 21, 2019 at 7:26 AM
> > > > Subject: Re: [VOTE] Accept Apache Ignite 2.7.5-rc3
> > > > To: 
> > > >
> > > >
> > > > + 1 (binding)
> > > >
> > > > Denis
> > > >
> > > > On 2019/05/17 13:49:17, Dmitriy Pavlov  wrote:
> > > > > Dear Sirs!
> > > > >
> > > > > We have uploaded release candidate to
> > > > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
> > > > >
> > > > > The following staging can be used for a dependent project for
> testing:
> > > > > https://repository.apache.org/content/repositories/
> > > orgapacheignite-1438/
> > > > >
> > > > > This is half-release before 2.8 containing Java 11 support and
> fixes
> > > for
> > > > > Native Persistence storage.
> > > > >
> > > > > Tag name is 2.7.5-rc3:
> > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;
> > > h=refs/tags/2.7.5-rc3
> > > > >
> > > > > 2.7.5 changes:
> > > > > * Added Java 11 support
> > > > > * Fixed infinite looping during SSL handshake, affecting Java
> > > 11/Windows
> > > > > * Fixed storage corruption case after incorrectly rotated page
> > > > > * Erroneous WAL record after incorrectly rotated page processed
> > > > > automatically
> > > > > * Addressed ignite.sh failure on Mac OS and Linux, affecting Java
> 11
> > > > > * Launch scripts and some Ignite initialization steps were fixed
> for
> > > Java 12
> > > > > * Fixed indexes corruption on node stop under load
> > > > > * Fixed case of node crash during node deactivation
> > > > > * Error message with advice about required JVM parameters printed
> when
> > > Java
> > > > > 9+ is used
> > > > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > > > >
> > > > > Complete list of closed issues:
> > > > > https://issues.apache.org/jira/issues/?jql=(project%20%
> > > 3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%
> 20AND%20status%20IN%20(
> > > Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%
> > > 20%20%20%20%20%20%20%20%20%20%20
> > > > >
> > > > >
> > > > > DEVNOTES
> > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;
> > > f=DEVNOTES.txt;h=307189059ae70834ead4c127cc1829
> 5ce4d0735a;hb=ignite-2.7.5
> > > > >
> > > > > RELEASE NOTES
> > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;
> > > f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f16579
> > > 40fa12f972;hb=ignite-2.7.5
> > > > >
> > > > > The vote is formal, see voting guidelines
> > > > > https://www.apache.org/foundation/voting.html
> > > > >
> > > > > +1 - to accept Apache Ignite 2.7.5-rc3
> > > > > 0 - don't care either way
> > > > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc3 (explain why)
> > > > >
> > > > > This vote will be open for 6 days till May 23, 14:00 UTC.
> > > > > https://www.timeanddate.com/countdown/to?year=2019&month=
> > > 5&day=23&hour=14&min=0&sec=0&p0=utc-1
> > > > >
> > > > > Best Regards,
> > > > > Dmitriy Pavlov
> > > > >
> > >
> >
> >
> > --
> > -
> > Denis
>


-- 
--
Denis Magda

Re: [VOTE] Accept Apache Ignite 2.7.5-rc3

2019-05-22 Thread Ilya Kasnacheev 
Hello!

Just wanted to point out that it likely affects Java 11, too.

Regards,
-- 
Ilya Kasnacheev


ср, 22 мая 2019 г. в 20:52, Andrey Gura :

> Denis,
>
> I really don't see any reason for releasing the next Apache Ignitie
> version only for this minor fix. Release process is complex enough and
> it seems that easier way is issue fix and build rc4.
>
> Anyway, if we didn't commit about Java 12 support in this version so
> I'm okay with this issue in current build.
>
> On Wed, May 22, 2019 at 4:20 AM Denis Magda  wrote:
> >
> > Andrey,
> >
> > I would encourage us to roll this release out and consider this change
> for
> > the next one. We’re free to make the next release as soon as needed,
> even a
> > couple of weeks after.
> >
> > Do you agree?
> >
> > Denis
> >
> > On Tuesday, May 21, 2019, Andrey Gura  wrote:
> >
> > > Ilya, do you have any estimation for fix Java 12 with SSL issue?
> > >
> > > On Tue, May 21, 2019 at 10:26 PM Denis Magda 
> wrote:
> > > >
> > > > Ignite PMC and committers, please cast your vote. It's time to roll
> the
> > > release out.
> > > >
> > > > --
> > > > Denis Magda
> > > >
> > > >
> > > > -- Forwarded message -
> > > > From: Denis A. Magda 
> > > > Date: Tue, May 21, 2019 at 7:26 AM
> > > > Subject: Re: [VOTE] Accept Apache Ignite 2.7.5-rc3
> > > > To: 
> > > >
> > > >
> > > > + 1 (binding)
> > > >
> > > > Denis
> > > >
> > > > On 2019/05/17 13:49:17, Dmitriy Pavlov  wrote:
> > > > > Dear Sirs!
> > > > >
> > > > > We have uploaded release candidate to
> > > > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
> > > > >
> > > > > The following staging can be used for a dependent project for
> testing:
> > > > > https://repository.apache.org/content/repositories/
> > > orgapacheignite-1438/
> > > > >
> > > > > This is half-release before 2.8 containing Java 11 support and
> fixes
> > > for
> > > > > Native Persistence storage.
> > > > >
> > > > > Tag name is 2.7.5-rc3:
> > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;
> > > h=refs/tags/2.7.5-rc3
> > > > >
> > > > > 2.7.5 changes:
> > > > > * Added Java 11 support
> > > > > * Fixed infinite looping during SSL handshake, affecting Java
> > > 11/Windows
> > > > > * Fixed storage corruption case after incorrectly rotated page
> > > > > * Erroneous WAL record after incorrectly rotated page processed
> > > > > automatically
> > > > > * Addressed ignite.sh failure on Mac OS and Linux, affecting Java
> 11
> > > > > * Launch scripts and some Ignite initialization steps were fixed
> for
> > > Java 12
> > > > > * Fixed indexes corruption on node stop under load
> > > > > * Fixed case of node crash during node deactivation
> > > > > * Error message with advice about required JVM parameters printed
> when
> > > Java
> > > > > 9+ is used
> > > > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > > > >
> > > > > Complete list of closed issues:
> > > > > https://issues.apache.org/jira/issues/?jql=(project%20%
> > >
> 3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(
> > > Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%
> > > 20%20%20%20%20%20%20%20%20%20%20
> > > > >
> > > > >
> > > > > DEVNOTES
> > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;
> > >
> f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> > > > >
> > > > > RELEASE NOTES
> > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;
> > > f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f16579
> > > 40fa12f972;hb=ignite-2.7.5
> > > > >
> > > > > The vote is formal, see voting guidelines
> > > > > https://www.apache.org/foundation/voting.html
> > > > >
> > > > > +1 - to accept Apache Ignite 2.7.5-rc3
> > > > > 0 - don't care either way
> > > > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc3 (explain why)
> > > > >
> > > > > This vote will be open for 6 days till May 23, 14:00 UTC.
> > > > > https://www.timeanddate.com/countdown/to?year=2019&month=
> > > 5&day=23&hour=14&min=0&sec=0&p0=utc-1
> > > > >
> > > > > Best Regards,
> > > > > Dmitriy Pavlov
> > > > >
> > >
> >
> >
> > --
> > -
> > Denis
>

Re: [VOTE] Accept Apache Ignite 2.7.5-rc3

2019-05-22 Thread Andrey Gura 
Denis,

I really don't see any reason for releasing the next Apache Ignitie
version only for this minor fix. Release process is complex enough and
it seems that easier way is issue fix and build rc4.

Anyway, if we didn't commit about Java 12 support in this version so
I'm okay with this issue in current build.

On Wed, May 22, 2019 at 4:20 AM Denis Magda  wrote:
>
> Andrey,
>
> I would encourage us to roll this release out and consider this change for
> the next one. We’re free to make the next release as soon as needed, even a
> couple of weeks after.
>
> Do you agree?
>
> Denis
>
> On Tuesday, May 21, 2019, Andrey Gura  wrote:
>
> > Ilya, do you have any estimation for fix Java 12 with SSL issue?
> >
> > On Tue, May 21, 2019 at 10:26 PM Denis Magda  wrote:
> > >
> > > Ignite PMC and committers, please cast your vote. It's time to roll the
> > release out.
> > >
> > > --
> > > Denis Magda
> > >
> > >
> > > -- Forwarded message -
> > > From: Denis A. Magda 
> > > Date: Tue, May 21, 2019 at 7:26 AM
> > > Subject: Re: [VOTE] Accept Apache Ignite 2.7.5-rc3
> > > To: 
> > >
> > >
> > > + 1 (binding)
> > >
> > > Denis
> > >
> > > On 2019/05/17 13:49:17, Dmitriy Pavlov  wrote:
> > > > Dear Sirs!
> > > >
> > > > We have uploaded release candidate to
> > > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
> > > >
> > > > The following staging can be used for a dependent project for testing:
> > > > https://repository.apache.org/content/repositories/
> > orgapacheignite-1438/
> > > >
> > > > This is half-release before 2.8 containing Java 11 support and fixes
> > for
> > > > Native Persistence storage.
> > > >
> > > > Tag name is 2.7.5-rc3:
> > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;
> > h=refs/tags/2.7.5-rc3
> > > >
> > > > 2.7.5 changes:
> > > > * Added Java 11 support
> > > > * Fixed infinite looping during SSL handshake, affecting Java
> > 11/Windows
> > > > * Fixed storage corruption case after incorrectly rotated page
> > > > * Erroneous WAL record after incorrectly rotated page processed
> > > > automatically
> > > > * Addressed ignite.sh failure on Mac OS and Linux, affecting Java 11
> > > > * Launch scripts and some Ignite initialization steps were fixed for
> > Java 12
> > > > * Fixed indexes corruption on node stop under load
> > > > * Fixed case of node crash during node deactivation
> > > > * Error message with advice about required JVM parameters printed when
> > Java
> > > > 9+ is used
> > > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > > >
> > > > Complete list of closed issues:
> > > > https://issues.apache.org/jira/issues/?jql=(project%20%
> > 3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(
> > Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%
> > 20%20%20%20%20%20%20%20%20%20%20
> > > >
> > > >
> > > > DEVNOTES
> > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;
> > f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> > > >
> > > > RELEASE NOTES
> > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;
> > f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f16579
> > 40fa12f972;hb=ignite-2.7.5
> > > >
> > > > The vote is formal, see voting guidelines
> > > > https://www.apache.org/foundation/voting.html
> > > >
> > > > +1 - to accept Apache Ignite 2.7.5-rc3
> > > > 0 - don't care either way
> > > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc3 (explain why)
> > > >
> > > > This vote will be open for 6 days till May 23, 14:00 UTC.
> > > > https://www.timeanddate.com/countdown/to?year=2019&month=
> > 5&day=23&hour=14&min=0&sec=0&p0=utc-1
> > > >
> > > > Best Regards,
> > > > Dmitriy Pavlov
> > > >
> >
>
>
> --
> -
> Denis

[jira] [Created] (IGNITE-11866) Add ability to activate cluster in read-only mode

2019-05-22 Thread Sergey Antonov (JIRA) 
Sergey Antonov created IGNITE-11866:
---

 Summary: Add ability to activate cluster in read-only mode
 Key: IGNITE-11866
 URL: https://issues.apache.org/jira/browse/IGNITE-11866
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergey Antonov


After IGNITE-11256 we have cluster read-only mode. We should have ability to 
activate cluster  and enable read-only mode like atomic operation.



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

[jira] [Created] (IGNITE-11865) FailureProcessor treats tcp-comm-worker as blocked when it works on reestablishing connect to failed client node

2019-05-22 Thread Sergey Chugunov (JIRA) 
Sergey Chugunov created IGNITE-11865:


 Summary: FailureProcessor treats tcp-comm-worker as blocked when 
it works on reestablishing connect to failed client node
 Key: IGNITE-11865
 URL: https://issues.apache.org/jira/browse/IGNITE-11865
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.8


When client node fails tcp-comm-worker thread on server keeps trying to 
reestablish connection to the client until failed node is removed from topology 
(on expiration of clientFailureDetectionTimeout).

As tcp-comm-worker thread doesn't update its heartbeats from internal loops 
FailureProcessor considers it as blocked and prints out misleading message to 
logs along with full thread dump.

To avoid polluting logs with unnecessary messages we need to teach 
tcp-comm-worker how to update its heartbeat timestamp in FailureProcessor.



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

Re: [VOTE] Accept Apache Ignite 2.7.5-rc3

2019-05-22 Thread Anton Vinogradov 
See huge difference [1] between releases.
The weird thing is that I see only additions.

Dmitriy, please make sure everything is correct.

[1]
https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/3911989:id/results/result.log

On Wed, May 22, 2019 at 2:05 PM Petr Ivanov  wrote:

> I've modified Compare w/Previous Release build and run it on 2.7.5 vs
> 2.7.0 config.
> Is everything is ok?
>
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=3911989&buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency
>
>
> > On 17 May 2019, at 17:36, Anton Vinogradov  wrote:
> >
> > Dmitriy,
> >
> > Could you please check release using special TC tasks [1] "Compare w/
> > Previous Release" and "Check RC"
> > Also, I see you used some new task [2] to assembly the release.
> > What's the difference with original task [3]?
> > Please make sure correct task used and remove obsolete one. Don't forget
> to
> > fix task's naming.
> >
> > [1]
> >
> https://ci.ignite.apache.org/project.html?projectId=Releases_ApacheIgniteMain&tab=projectOverview&branch_Releases_ApacheIgniteMain=ignite-2.7.5
> > [2]
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild&branch_Releases_ApacheIgniteMain=ignite-2.7.5&tab=buildTypeStatusDiv
> > [3]
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote&branch_Releases_ApacheIgniteMain=ignite-2.7.5&tab=buildTypeStatusDiv
> >
> >
> > On Fri, May 17, 2019 at 4:49 PM Dmitriy Pavlov 
> wrote:
> >
> >> Dear Sirs!
> >>
> >> We have uploaded release candidate to
> >> https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
> >>
> >> The following staging can be used for a dependent project for testing:
> >>
> https://repository.apache.org/content/repositories/orgapacheignite-1438/
> >>
> >> This is half-release before 2.8 containing Java 11 support and fixes for
> >> Native Persistence storage.
> >>
> >> Tag name is 2.7.5-rc3:
> >>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.7.5-rc3
> >>
> >> 2.7.5 changes:
> >> * Added Java 11 support
> >> * Fixed infinite looping during SSL handshake, affecting Java 11/Windows
> >> * Fixed storage corruption case after incorrectly rotated page
> >> * Erroneous WAL record after incorrectly rotated page processed
> >> automatically
> >> * Addressed ignite.sh failure on Mac OS and Linux, affecting Java 11
> >> * Launch scripts and some Ignite initialization steps were fixed for
> Java
> >> 12
> >> * Fixed indexes corruption on node stop under load
> >> * Fixed case of node crash during node deactivation
> >> * Error message with advice about required JVM parameters printed when
> Java
> >> 9+ is used
> >> * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> >>
> >> Complete list of closed issues:
> >>
> >>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20
> >>
> >>
> >> DEVNOTES
> >>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> >>
> >> RELEASE NOTES
> >>
> >>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f1657940fa12f972;hb=ignite-2.7.5
> >>
> >> The vote is formal, see voting guidelines
> >> https://www.apache.org/foundation/voting.html
> >>
> >> +1 - to accept Apache Ignite 2.7.5-rc3
> >> 0 - don't care either way
> >> -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc3 (explain why)
> >>
> >> This vote will be open for 6 days till May 23, 14:00 UTC.
> >>
> >>
> https://www.timeanddate.com/countdown/to?year=2019&month=5&day=23&hour=14&min=0&sec=0&p0=utc-1
> >>
> >> Best Regards,
> >> Dmitriy Pavlov
> >>
>
>

[jira] [Created] (IGNITE-11864) Log FileNotFoundException on restore if no segments were found.

2019-05-22 Thread Ivan Bessonov (JIRA) 
Ivan Bessonov created IGNITE-11864:
--

 Summary: Log FileNotFoundException on restore if no segments were 
found.
 Key: IGNITE-11864
 URL: https://issues.apache.org/jira/browse/IGNITE-11864
 Project: Ignite
  Issue Type: Improvement
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov






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

[jira] [Created] (IGNITE-11863) .NET: Add clurster read-only mode API (status, run-time change)

2019-05-22 Thread Sergey Antonov (JIRA) 
Sergey Antonov created IGNITE-11863:
---

 Summary: .NET: Add clurster read-only mode API (status, run-time 
change)
 Key: IGNITE-11863
 URL: https://issues.apache.org/jira/browse/IGNITE-11863
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Sergey Antonov


We would introduce at IGNITE-11256 new methods in IgniteCluster.

We need their support in .Net side.



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

Re: [VOTE] Accept Apache Ignite 2.7.5-rc3

2019-05-22 Thread Petr Ivanov 
I've modified Compare w/Previous Release build and run it on 2.7.5 vs 2.7.0 
config.
Is everything is ok?


https://ci.ignite.apache.org/viewLog.html?buildId=3911989&buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency


> On 17 May 2019, at 17:36, Anton Vinogradov  wrote:
> 
> Dmitriy,
> 
> Could you please check release using special TC tasks [1] "Compare w/
> Previous Release" and "Check RC"
> Also, I see you used some new task [2] to assembly the release.
> What's the difference with original task [3]?
> Please make sure correct task used and remove obsolete one. Don't forget to
> fix task's naming.
> 
> [1]
> https://ci.ignite.apache.org/project.html?projectId=Releases_ApacheIgniteMain&tab=projectOverview&branch_Releases_ApacheIgniteMain=ignite-2.7.5
> [2]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild&branch_Releases_ApacheIgniteMain=ignite-2.7.5&tab=buildTypeStatusDiv
> [3]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote&branch_Releases_ApacheIgniteMain=ignite-2.7.5&tab=buildTypeStatusDiv
> 
> 
> On Fri, May 17, 2019 at 4:49 PM Dmitriy Pavlov  wrote:
> 
>> Dear Sirs!
>> 
>> We have uploaded release candidate to
>> https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
>> 
>> The following staging can be used for a dependent project for testing:
>> https://repository.apache.org/content/repositories/orgapacheignite-1438/
>> 
>> This is half-release before 2.8 containing Java 11 support and fixes for
>> Native Persistence storage.
>> 
>> Tag name is 2.7.5-rc3:
>> 
>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.7.5-rc3
>> 
>> 2.7.5 changes:
>> * Added Java 11 support
>> * Fixed infinite looping during SSL handshake, affecting Java 11/Windows
>> * Fixed storage corruption case after incorrectly rotated page
>> * Erroneous WAL record after incorrectly rotated page processed
>> automatically
>> * Addressed ignite.sh failure on Mac OS and Linux, affecting Java 11
>> * Launch scripts and some Ignite initialization steps were fixed for Java
>> 12
>> * Fixed indexes corruption on node stop under load
>> * Fixed case of node crash during node deactivation
>> * Error message with advice about required JVM parameters printed when Java
>> 9+ is used
>> * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
>> 
>> Complete list of closed issues:
>> 
>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20
>> 
>> 
>> DEVNOTES
>> 
>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
>> 
>> RELEASE NOTES
>> 
>> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f1657940fa12f972;hb=ignite-2.7.5
>> 
>> The vote is formal, see voting guidelines
>> https://www.apache.org/foundation/voting.html
>> 
>> +1 - to accept Apache Ignite 2.7.5-rc3
>> 0 - don't care either way
>> -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc3 (explain why)
>> 
>> This vote will be open for 6 days till May 23, 14:00 UTC.
>> 
>> https://www.timeanddate.com/countdown/to?year=2019&month=5&day=23&hour=14&min=0&sec=0&p0=utc-1
>> 
>> Best Regards,
>> Dmitriy Pavlov
>>

[jira] [Created] (IGNITE-11862) Cache stopping on supplier during rebalance causes NPE and supplying failure.

2019-05-22 Thread Alexei Scherbakov (JIRA) 
Alexei Scherbakov created IGNITE-11862:
--

 Summary: Cache stopping on supplier during rebalance causes NPE 
and supplying failure.
 Key: IGNITE-11862
 URL: https://issues.apache.org/jira/browse/IGNITE-11862
 Project: Ignite
  Issue Type: Bug
Reporter: Alexei Scherbakov


{noformat}
[21:12:14]W: [org.apache.ignite:ignite-core] [2019-05-20 
21:12:14,376][ERROR][sys-#60310%distributed.CacheParallelStartTest0%][GridDhtPartitionSupplier]
 Failed to continue supplying [grp=static-cache-group45, 
demander=ed1c0109-8721-4cd8-80d9-d36e8251, top
Ver=AffinityTopologyVersion [topVer=2, minorTopVer=0], topic=0]
[21:12:14]W: [org.apache.ignite:ignite-core] java.lang.NullPointerException
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.CacheGroupContext.addRebalanceSupplyEvent(CacheGroupContext.java:525)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:422)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:397)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:455)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:440)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1141)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$800(GridCacheIoManager.java:109)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1706)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1566)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:129)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2795)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1523)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4500(GridIoManager.java:129)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1492)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[21:12:14]W: [org.apache.ignite:ignite-core] at 
java.lang.Thread.run(Thread.java:748)
{noformat}



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

Re: [VOTE] Accept Apache Ignite 2.7.5-rc3

2019-05-22 Thread Ilya Kasnacheev 
Hello!

I have an one-liner fix ready:
https://github.com/apache/ignite/pull/6557

I have validated that it fixes the issue for Java and C++ nodes, but
unfortunately tests on TC seem to be broken.

Regards,
-- 
Ilya Kasnacheev


ср, 22 мая 2019 г. в 00:56, Andrey Gura :

> Ilya, do you have any estimation for fix Java 12 with SSL issue?
>
> On Tue, May 21, 2019 at 10:26 PM Denis Magda  wrote:
> >
> > Ignite PMC and committers, please cast your vote. It's time to roll the
> release out.
> >
> > --
> > Denis Magda
> >
> >
> > -- Forwarded message -
> > From: Denis A. Magda 
> > Date: Tue, May 21, 2019 at 7:26 AM
> > Subject: Re: [VOTE] Accept Apache Ignite 2.7.5-rc3
> > To: 
> >
> >
> > + 1 (binding)
> >
> > Denis
> >
> > On 2019/05/17 13:49:17, Dmitriy Pavlov  wrote:
> > > Dear Sirs!
> > >
> > > We have uploaded release candidate to
> > > https://dist.apache.org/repos/dist/dev/ignite/2.7.5-rc3/
> > >
> > > The following staging can be used for a dependent project for testing:
> > >
> https://repository.apache.org/content/repositories/orgapacheignite-1438/
> > >
> > > This is half-release before 2.8 containing Java 11 support and fixes
> for
> > > Native Persistence storage.
> > >
> > > Tag name is 2.7.5-rc3:
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.7.5-rc3
> > >
> > > 2.7.5 changes:
> > > * Added Java 11 support
> > > * Fixed infinite looping during SSL handshake, affecting Java
> 11/Windows
> > > * Fixed storage corruption case after incorrectly rotated page
> > > * Erroneous WAL record after incorrectly rotated page processed
> > > automatically
> > > * Addressed ignite.sh failure on Mac OS and Linux, affecting Java 11
> > > * Launch scripts and some Ignite initialization steps were fixed for
> Java 12
> > > * Fixed indexes corruption on node stop under load
> > > * Fixed case of node crash during node deactivation
> > > * Error message with advice about required JVM parameters printed when
> Java
> > > 9+ is used
> > > * Introduced SYSTEM_CRITICAL_OPERATION_TIMEOUT failure type
> > >
> > > Complete list of closed issues:
> > >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20in%20('2.7.5')%20AND%20status%20IN%20(Resolved%2C%20Closed))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20
> > >
> > >
> > > DEVNOTES
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=DEVNOTES.txt;h=307189059ae70834ead4c127cc18295ce4d0735a;hb=ignite-2.7.5
> > >
> > > RELEASE NOTES
> > >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;h=0a7d2d395b3c9ca1a69ce3f8f1657940fa12f972;hb=ignite-2.7.5
> > >
> > > The vote is formal, see voting guidelines
> > > https://www.apache.org/foundation/voting.html
> > >
> > > +1 - to accept Apache Ignite 2.7.5-rc3
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite Ignite 2.7.5-rc3 (explain why)
> > >
> > > This vote will be open for 6 days till May 23, 14:00 UTC.
> > >
> https://www.timeanddate.com/countdown/to?year=2019&month=5&day=23&hour=14&min=0&sec=0&p0=utc-1
> > >
> > > Best Regards,
> > > Dmitriy Pavlov
> > >
>