[jira] [Created] (IGNITE-5599) Web console: Agent should check that node URI is valid

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-5599:
-

 Summary: Web console: Agent should check that node URI is valid
 Key: IGNITE-5599
 URL: https://issues.apache.org/jira/browse/IGNITE-5599
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 2.1
Reporter: Vasiliy Sisko
Assignee: Alexey Kuznetsov
 Fix For: 2.1






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

[CVE-2017-7686] Apache Ignite Information Disclosure

[Denis Magda]

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:

* Apache Ignite 1.0.0-RC3 to 2.0

Impact:

Apache Ignite Might Transfer Sensitive Information to 3rd Party Domain

Description:

Apache Ignite uses an update notifier component to update the users about new 
project releases that include additional functionality, bug fixes and 
performance improvements. To do that the component communicates to an external 
PHP server (http://ignite.run) where it needs to send some system properties 
like Apache Ignite or Java version. Some of the properties might contain user 
sensitive information.

Mitigation:

* The domain (http://ignite.run) was moved to ASF and the server was brought 
down. No data transfer longer happens by default. No extra actions are needed 
on the end user side.

Credit:

The vulnerability was discovered by: 

* Makoto Yui of Treasure Data, Inc.

References:

* http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7686

Re: Zookeeper Discovery SPI & external IP address in AWS

[Valentin Kulichenko]

Yakov,

What do you mean by 'mixture'? :) Client obviously needs to know public
addresses to connect and I think it's natural to get them from IP finder.
Is there something wrong with this?

-Val

On Tue, Jun 27, 2017 at 5:01 AM, Yakov Zhdanov  wrote:

> >>Both will work, but frankly I like option 1 more. First of all, it's just
> >>more intuitive that IP finder contains all possible addresses that can be
> >>used to join. Second of all, option 2 introduces requirement to have
> >>address resolver for server addresses configured on client nodes - this
> is
> >>not very good from usability standpoint.
>
> Val, I see your point, but (1) means that clients should have public IPs
> for communication or server resolver should be able to resolve them. In any
> case there will be some mixture. Is that correct?
>
> --Yakov
>

Re: DataStreamer Transactional and Timestamp Implementation

[Valentin Kulichenko]

Fatih,

Can you give more details about the use case addressed by this
implementation?

-Val

On Tue, Jun 27, 2017 at 3:45 PM, Denis Magda  wrote:

> Faith,
>
> Thanks for sharing it with us.
>
> In general, we can always wrap this code up in a form of an example to be
> delivered with every Ignite release.
>
> But probably it makes sense to add it to the core streaming functionality.
> *Igniters*, what’d you think?
>
> —
> Denis
>
> > On Jun 27, 2017, at 12:29 AM, fatih  wrote:
> >
> > Hi
> >
> > We have implemented some receivers to be able to update data in data
> nodes
> > by ignite datastreamer api.
> >
> > There is an associated ticket as below already exist. We thought it
> would be
> > useful to use that implementation from ignite directly. Maybe can be
> added
> > to ignite directly.
> >
> > http://apache-ignite-users.70518.x6.nabble.com/
> Transaction-Boundary-Data-Streamer-td13803.html#a14078
> > AbstractTransactionalStreamReceiver.java
> >  AbstractTransactionalStreamReceiver.java>
> >
> > TimestampBasedUpdateStreamReceiver.java
> >  TimestampBasedUpdateStreamReceiver.java>
> >
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/DataStreamer-Transactional-and-Timestamp-
> Implementation-tp19129.html
> > Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
>
>

Re: Server stores cache data on-heap if client has near cache - IGNITE-4662

[Valentin Kulichenko]

I'm not sure this ticket is valid for 2.0. Semen, can you comment?

-Val

On Tue, Jun 27, 2017 at 1:14 AM, Vyacheslav Daradur 
wrote:

> Hi Igniters.
>
> I have some questions according to this task:
>
> 1. Does the method: GridCacheMapEntry#evictInternal do the
> eviction(on-heap
> -> off-heap)?
> 2. Is CacheOffheapEvictionManager responsible for managing the
> eviction(on-heap -> off-heap)? (if not, then who is?)
> 3. At what moment the eviction(on-heap -> off-heap) is called?
>
>
> --
> Best Regards, Vyacheslav D.
>

Re: golang client for Ignite

[Denis Magda]

Hi Aleksandr,

That looks really interesting to me. Personally, I would like to see a 
dedicated Go module in Ignite.

Do you support SQL API right now? If it’s so then you might want to switch to 
Ignite JDBC driver instead that should outperform the REST protocol.

Otherwise, if the goal is to go beyond SQL boundaries adding key-value and 
transactions to the list then we should either use the REST  or create a true 
native client. Read more about native clients development here: 
http://apache-ignite-developers.2346864.n4.nabble.com/Read-this-if-you-want-to-integrate-Ignite-with-other-platforms-Python-R-etc-td14006.html#a14028

—
Denis

> On Jun 27, 2017, at 2:29 PM, Aleksandr Sokolovskii  wrote:
> 
> Dear Ignite team,
> 
> I see there is no native client for golang.
> I tried to fix this gap a little bit and developed golang SQL driver for 
> ignite/gridgain: https://github.com/amsokol/go-ignite-client.
> Enjoy ))).
> It's in beta phase now. I’m focusing on test coverage now.
> 
> Driver uses HTTP REST API which is overhead.
> Could you please provide me specification of ignite native 
> platform-independent client-server protocol.
> I easy add it as well.
> 
> I think many people tell us thanks for golang native client and SQL driver )))
> 
> P.S.: If you are interesting in my project please let me know. I can easy 
> donate (and support) my code to your project.
> 
> Thanks,
> Aleksandr
> 
> 

Re: DataStreamer Transactional and Timestamp Implementation

[Denis Magda]

Faith,

Thanks for sharing it with us. 

In general, we can always wrap this code up in a form of an example to be 
delivered with every Ignite release. 

But probably it makes sense to add it to the core streaming functionality. 
*Igniters*, what’d you think?

—
Denis 

> On Jun 27, 2017, at 12:29 AM, fatih  wrote:
> 
> Hi 
> 
> We have implemented some receivers to be able to update data in data nodes
> by ignite datastreamer api.
> 
> There is an associated ticket as below already exist. We thought it would be
> useful to use that implementation from ignite directly. Maybe can be added
> to ignite directly.
> 
> http://apache-ignite-users.70518.x6.nabble.com/Transaction-Boundary-Data-Streamer-td13803.html#a14078
> AbstractTransactionalStreamReceiver.java
> 
>   
> 
> TimestampBasedUpdateStreamReceiver.java
> 
>   
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-ignite-developers.2346864.n4.nabble.com/DataStreamer-Transactional-and-Timestamp-Implementation-tp19129.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

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

[Denis Magda]

Yakov,

No, the mentioned discussion didn’t turn into a JIRA ticket.

Alex K., please follow to some thoughts from there and wrap them up in a form 
of the ticket.

—
Denis

> On Jun 26, 2017, at 2:58 AM, Yakov Zhdanov  wrote:
> 
> Guys, I remember we discussed this some time ago.
> 
> http://apache-ignite-developers.2346864.n4.nabble.com/Tasks-Scheduling-and-Chaining-td14293.html
> 
> Denis, do you have any ticket or SoW?
> 
> --Yakov

Re: cannot build ignite 2.1.0

[Denis Magda]

Aleksey,

What’s the command you use to trigger the build?

—
Denis

> On Jun 23, 2017, at 9:24 AM, ALEKSEY KUZNETSOV  
> wrote:
> 
> Cannot build apache ignite 2.1.0 package. Build fails on ignite-hadoop
> module :
> Could not find artifact org.apache.ignite:ignite-core:jar:2.1.0-SNAPSHOT in
> h2database.com (http://h2database.com/m2-repo)
> 
> http://h2database.com/m2-repo/org/apache/ignite/ignite-core/2.1.0-SNAPSHOT/ignite-core-2.1.0-SNAPSHOT.jar
> 
> -- 
> 
> *Best Regards,*
> 
> *Kuznetsov Aleksey*

Ignite Persistent Store: Ready for merge?

[Denis Magda]

Guys,

According to the discussions I see on the @dev list the donated Ignite 
Persistent Store [1] is stable and ready to be rolled out to our users.

Considering that we’ve been already getting to know the donation for a while 
and had the webinar dedicated to the functionality trying to answer on all the 
technical questions and resolve uncertainties, do you think it’s a good time to 
merge it to the master branch and start thinking of the feature release? Is 
there anyone who needs more time to look into the donation?

[1] 
http://incubator.apache.org/ip-clearance/persistent-distributed-store-ignite.html

—
Denis

Re: daemon nodes

[Dmitriy Setrakyan]

Daemon nodes are nodes that join the cluster, but do not store data or
execute computations or perform any other of the Ignite API-based
functionality. Visor node is a good example of a daemon node, because it
wants to join the cluster and receive metrics from other nodes, but does
not need to participate in computation or data related functionality.

D.

On Tue, Jun 27, 2017 at 2:49 AM, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:

> Hi Igniters,
>
> Can somebody explain what does mean  daemon node? I thought that exist
> only client and server node, but node may can be daemon (server daemon
> or client daemon).  As is can see, command line visor join in topology
> as server daemon. Can this be an outdated functionality?
>

FW: golang client for Ignite

[Aleksandr Sokolovskii]

Dear Ignite team,

I see there is no native client for golang.
I tried to fix this gap a little bit and developed golang SQL driver for 
ignite/gridgain: https://github.com/amsokol/go-ignite-client.
Enjoy ))).
It's in beta phase now. I’m focusing on test coverage now.

Driver uses HTTP REST API which is overhead.
Could you please provide me specification of ignite native platform-independent 
client-server protocol.
I easy add it as well.

I think many people tell us thanks for golang native client and SQL driver )))

P.S.: If you are interesting in my project please let me know. I can easy 
donate (and support) my code to your project.

Thanks,
Aleksandr

[GitHub] ignite pull request #2208: for test purposes

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

for test purposes



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

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

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

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


commit 708cc8c6849b21063a555895671f6f820d92184a
Author: Andrey V. Mashenkov 
Date:   2016-12-22T09:48:58Z

IGNITE-4408: Allow BinaryObjects pass to IndexingSpi. This closes #1353.

commit 6e71ef26d8e3c6f86d1f0b9f4bec97b7e33d0b2e
Author: Valentin Kulichenko 
Date:   2016-12-22T21:05:35Z

IGNITE-4439 - Attribute based node filter

commit babfc2f051f8471f541bd054650a47cceb3cc09e
Author: sboikov 
Date:   2016-12-23T09:02:24Z

AttributeNodeFilter: added serialVersionUID.

commit 2b3a180ff7692c0253da3ff7c32d65c09f9488d2
Author: Andrey Novikov 
Date:   2016-12-23T09:34:10Z

Web console beta-7.

(cherry picked from commit 8e7c852)

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

Implemented Visor tasks for Services.

(cherry picked from commit fdf1f4b)

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

Updated classnames for ignite-1.7.5.

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

Fixed broken links.

(cherry picked from commit 6ca8670)

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

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

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

ignite-4167 Do not log cache key/values

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

Fixed Visor queries for BinaryObjects.

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

1.8.0-SNAPSHOT

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

IGNITE-4442 Implemented cache affinity configuration.

(cherry picked from commit f4a1e6c)

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

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

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

Removed duplicated benchmark.

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

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

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

IGNITE-4424 REPLICATED cache isn't synced across nodes

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

Merge branch 'ignite-1.8.2' into ignite-1.8.3

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

Merge branch 'ignite-1.7.5' into ignite-1.8.3

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

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

IGNITE-3966: Hadoop: add 

Re: Problem with setting up .NET dev environment

[Guru Stron]

Sorry, Vyacheslav =))

On 27 June 2017 at 22:37, Guru Stron  wrote:

> Hi Vadim,
>
> Just to be sure, what is considered root directory? Cause I've always been
> running the command in the topmost directory of the repo with all the .git,
> .pom, readme and all other files and folders?
>
> On 27 June 2017 at 19:57, Vyacheslav Daradur  wrote:
>
>> Hi, looks like you call command within wrong directory.
>>
>> Please make sure that directory (where you call maven comand) is the
>> root-folder of the project.
>>
>> 2017-06-27 16:11 GMT+03:00 Guru Stron :
>>
>> > Hi igniters,
>> >
>> > I have problem with setting up dev environment on one of my
>> machines(using
>> > fresh master). The maven build step from Ignite.NET+Development
>> > > NET+Development
>> > >
>> > manual
>> > page fails. My old dev environment on other machine works just fine.
>> >
>> > I use "*mvn clean package -DskipTests*" command as stated and it fails
>> with
>> > a bunch of errors like:
>> >
>> > [ERROR] [ERROR] Some problems were encountered while processing the
>> POMs:
>> > > [FATAL] Non-resolvable parent POM for
>> > > org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
>> > > org.apache.ignite:ignite-parent:pom:1 in
>> > > https://repo.maven.apache.org/maven2 was cached in the local
>> repository,
>> > > resolution will not be reattempted until the update interval of
>> central
>> > has
>> > > elapsed or updates are forced and 'parent.relativePath' points at
>> wrong
>> > > local POM @ line 26, column 13
>> > > [FATAL] Non-resolvable parent POM for
>> > > org.apache.ignite:ignite-core:2.1.0-SNAPSHOT: Failure to find
>> > > org.apache.ignite:ignite-parent:pom:1 in
>> > > file://${basedir}/src/test/binaries/repo was cached in the local
>> > > repository, resolution will not be reattempted until the update
>> interval
>> > of
>> > > ignite-binaries-test-repo has elapsed or updates are forced and
>> > > 'parent.relativePath' points at wrong local POM @ line 26, column 13
>> > > [FATAL] Non-resolvable parent POM for
>> > > org.apache.ignite:ignite-hadoop:2.1.0-SNAPSHOT: Failure to find
>> > > org.apache.ignite:ignite-parent:pom:1 in
>> > > https://repo.maven.apache.org/maven2 was cached in the local
>> repository,
>> > > resolution will not be reattempted until the update interval of
>> central
>> > has
>> > > elapsed or updates are forced and 'parent.relativePath' points at
>> wrong
>> > > local POM @ line 26, column 13
>> > > ...
>> > > [ERROR] The build could not read 48 projects -> [Help 1]
>> > > org.apache.maven.project.ProjectBuildingException: Some problems were
>> > > encountered while processing the POMs:
>> > > [FATAL] Non-resolvable parent POM for
>> > > org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
>> > > org.apache.ignite:ignite-parent:pom:1 in
>> > > https://repo.maven.apache.org/maven2 was cached in the local
>> repository,
>> > > resolution will not be reattempted until the update interval of
>> central
>> > has
>> > > elapsed or updates are forced and 'parent.relativePath' points at
>> wrong
>> > > local POM @ line 26, column 13
>> > >
>> > > ...
>> > > [FATAL] Non-resolvable parent POM for
>> > > org.apache.ignite:ignite-visor-plugins:2.1.0-SNAPSHOT: Failure to
>> find
>> > > org.apache.ignite:ignite-parent:pom:1 in
>> > > https://repo.maven.apache.org/maven2 was cached in the local
>> repository,
>> > > resolution will not be reattempted until the update interval of
>> central
>> > has
>> > > elapsed or updates are forced and 'parent.relativePath' points at
>> wrong
>> > > local POM @ line 26, column 13
>> > > at
>> > > org.apache.maven.project.DefaultProjectBuilder.build(
>> > DefaultProjectBuilder.java:382)
>> > > at
>> > > org.apache.maven.graph.DefaultGraphBuilder.collectProjects(
>> > DefaultGraphBuilder.java:400)
>> > > at
>> > > org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMav
>> enReactor(
>> > DefaultGraphBuilder.java:391)
>> > > at
>> > > org.apache.maven.graph.DefaultGraphBuilder.build(
>> > DefaultGraphBuilder.java:78)
>> > > at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:511)
>> > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:221)
>> > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> > > 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)
>> > 

Re: Problem with setting up .NET dev environment

[Guru Stron]

Hi Vadim,

Just to be sure, what is considered root directory? Cause I've always been
running the command in the topmost directory of the repo with all the .git,
.pom, readme and all other files and folders?

On 27 June 2017 at 19:57, Vyacheslav Daradur  wrote:

> Hi, looks like you call command within wrong directory.
>
> Please make sure that directory (where you call maven comand) is the
> root-folder of the project.
>
> 2017-06-27 16:11 GMT+03:00 Guru Stron :
>
> > Hi igniters,
> >
> > I have problem with setting up dev environment on one of my
> machines(using
> > fresh master). The maven build step from Ignite.NET+Development
> >  Ignite.NET+Development
> > >
> > manual
> > page fails. My old dev environment on other machine works just fine.
> >
> > I use "*mvn clean package -DskipTests*" command as stated and it fails
> with
> > a bunch of errors like:
> >
> > [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> > > [FATAL] Non-resolvable parent POM for
> > > org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> > > org.apache.ignite:ignite-parent:pom:1 in
> > > https://repo.maven.apache.org/maven2 was cached in the local
> repository,
> > > resolution will not be reattempted until the update interval of central
> > has
> > > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > > local POM @ line 26, column 13
> > > [FATAL] Non-resolvable parent POM for
> > > org.apache.ignite:ignite-core:2.1.0-SNAPSHOT: Failure to find
> > > org.apache.ignite:ignite-parent:pom:1 in
> > > file://${basedir}/src/test/binaries/repo was cached in the local
> > > repository, resolution will not be reattempted until the update
> interval
> > of
> > > ignite-binaries-test-repo has elapsed or updates are forced and
> > > 'parent.relativePath' points at wrong local POM @ line 26, column 13
> > > [FATAL] Non-resolvable parent POM for
> > > org.apache.ignite:ignite-hadoop:2.1.0-SNAPSHOT: Failure to find
> > > org.apache.ignite:ignite-parent:pom:1 in
> > > https://repo.maven.apache.org/maven2 was cached in the local
> repository,
> > > resolution will not be reattempted until the update interval of central
> > has
> > > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > > local POM @ line 26, column 13
> > > ...
> > > [ERROR] The build could not read 48 projects -> [Help 1]
> > > org.apache.maven.project.ProjectBuildingException: Some problems were
> > > encountered while processing the POMs:
> > > [FATAL] Non-resolvable parent POM for
> > > org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> > > org.apache.ignite:ignite-parent:pom:1 in
> > > https://repo.maven.apache.org/maven2 was cached in the local
> repository,
> > > resolution will not be reattempted until the update interval of central
> > has
> > > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > > local POM @ line 26, column 13
> > >
> > > ...
> > > [FATAL] Non-resolvable parent POM for
> > > org.apache.ignite:ignite-visor-plugins:2.1.0-SNAPSHOT: Failure to find
> > > org.apache.ignite:ignite-parent:pom:1 in
> > > https://repo.maven.apache.org/maven2 was cached in the local
> repository,
> > > resolution will not be reattempted until the update interval of central
> > has
> > > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > > local POM @ line 26, column 13
> > > at
> > > org.apache.maven.project.DefaultProjectBuilder.build(
> > DefaultProjectBuilder.java:382)
> > > at
> > > org.apache.maven.graph.DefaultGraphBuilder.collectProjects(
> > DefaultGraphBuilder.java:400)
> > > at
> > > org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(
> > DefaultGraphBuilder.java:391)
> > > at
> > > org.apache.maven.graph.DefaultGraphBuilder.build(
> > DefaultGraphBuilder.java:78)
> > > at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:511)
> > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:221)
> > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> > > 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
> > > org.codehaus.plexus.classworlds.launcher.Launcher.
> > launchEnhanced(Launcher.java:289)
> > > at
> > > org.codehaus.plexus.classworlds.launcher.Launcher.
> > launch(Launcher.java:229)
> > > at
> > > 

[jira] [Created] (IGNITE-5598) WAL Iteration stopped with exception after writting log with background mode

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5598:
--

 Summary: WAL Iteration stopped with exception after writting log 
with background mode
 Key: IGNITE-5598
 URL: https://issues.apache.org/jira/browse/IGNITE-5598
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov


Need to research if it is problem of IGNITE-5558 implementation or standalone 
issue

Exception is logged into stderr:
{noformat}
java.lang.RuntimeException: java.io.EOFException

at 
org.apache.ignite.internal.processors.cache.persistence.wal.reader.StandaloneWalRecordsIterator.handleRecordException(StandaloneWalRecordsIterator.java:168)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:166)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:121)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:106)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:42)
at 
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
at 
org.apache.ignite.internal.processors.cache.persistence.db.wal.reader.IgniteWalReaderTest.testFillWalAndReadRecords(IgniteWalReaderTest.java:179)
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:1994)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1909)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput.ensure(FileInput.java:104)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:288)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readByte(FileInput.java:361)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.readUnsignedByte(FileInput.java:370)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:677)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:657)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:156)
... 14 more
Suppressed: class 
org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
 val: 771559538 writtenCrc: 0
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileInput$Crc32CheckingFileInput.close(FileInput.java:305)
at 
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readRecord(RecordV1Serializer.java:664)
... 15 more
{noformat}



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

Re: Problem with setting up .NET dev environment

[Vyacheslav Daradur]

Hi, looks like you call command within wrong directory.

Please make sure that directory (where you call maven comand) is the
root-folder of the project.

2017-06-27 16:11 GMT+03:00 Guru Stron :

> Hi igniters,
>
> I have problem with setting up dev environment on one of my machines(using
> fresh master). The maven build step from Ignite.NET+Development
>  >
> manual
> page fails. My old dev environment on other machine works just fine.
>
> I use "*mvn clean package -DskipTests*" command as stated and it fails with
> a bunch of errors like:
>
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> > [FATAL] Non-resolvable parent POM for
> > org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> > org.apache.ignite:ignite-parent:pom:1 in
> > https://repo.maven.apache.org/maven2 was cached in the local repository,
> > resolution will not be reattempted until the update interval of central
> has
> > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > local POM @ line 26, column 13
> > [FATAL] Non-resolvable parent POM for
> > org.apache.ignite:ignite-core:2.1.0-SNAPSHOT: Failure to find
> > org.apache.ignite:ignite-parent:pom:1 in
> > file://${basedir}/src/test/binaries/repo was cached in the local
> > repository, resolution will not be reattempted until the update interval
> of
> > ignite-binaries-test-repo has elapsed or updates are forced and
> > 'parent.relativePath' points at wrong local POM @ line 26, column 13
> > [FATAL] Non-resolvable parent POM for
> > org.apache.ignite:ignite-hadoop:2.1.0-SNAPSHOT: Failure to find
> > org.apache.ignite:ignite-parent:pom:1 in
> > https://repo.maven.apache.org/maven2 was cached in the local repository,
> > resolution will not be reattempted until the update interval of central
> has
> > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > local POM @ line 26, column 13
> > ...
> > [ERROR] The build could not read 48 projects -> [Help 1]
> > org.apache.maven.project.ProjectBuildingException: Some problems were
> > encountered while processing the POMs:
> > [FATAL] Non-resolvable parent POM for
> > org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> > org.apache.ignite:ignite-parent:pom:1 in
> > https://repo.maven.apache.org/maven2 was cached in the local repository,
> > resolution will not be reattempted until the update interval of central
> has
> > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > local POM @ line 26, column 13
> >
> > ...
> > [FATAL] Non-resolvable parent POM for
> > org.apache.ignite:ignite-visor-plugins:2.1.0-SNAPSHOT: Failure to find
> > org.apache.ignite:ignite-parent:pom:1 in
> > https://repo.maven.apache.org/maven2 was cached in the local repository,
> > resolution will not be reattempted until the update interval of central
> has
> > elapsed or updates are forced and 'parent.relativePath' points at wrong
> > local POM @ line 26, column 13
> > at
> > org.apache.maven.project.DefaultProjectBuilder.build(
> DefaultProjectBuilder.java:382)
> > at
> > org.apache.maven.graph.DefaultGraphBuilder.collectProjects(
> DefaultGraphBuilder.java:400)
> > at
> > org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(
> DefaultGraphBuilder.java:391)
> > at
> > org.apache.maven.graph.DefaultGraphBuilder.build(
> DefaultGraphBuilder.java:78)
> > at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:511)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:221)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> > 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
> > org.codehaus.plexus.classworlds.launcher.Launcher.
> launchEnhanced(Launcher.java:289)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.
> launch(Launcher.java:229)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.
> mainWithExitCode(Launcher.java:415)
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.
> main(Launcher.java:356)
> > [ERROR]
> > [ERROR]   The project org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT
> > (C:\Misc\myuser\Projects\Ignite\src\modules\tools\pom.xml) has 1 error
> > [ERROR] Non-resolvable parent POM for
> > org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> > org.apache.ignite:ignite-parent:pom:1 in
> > 

[jira] [Created] (IGNITE-5597) Wrong javadoc in Affinity and AffinityFunction for REPLICATED cache

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-5597:
-

 Summary: Wrong javadoc in Affinity and AffinityFunction for 
REPLICATED cache
 Key: IGNITE-5597
 URL: https://issues.apache.org/jira/browse/IGNITE-5597
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.7
Reporter: Evgenii Zhuravlev


RendezvoudAffinityFunction.getPartitions() Javadoc says:

{code:java}
 * Note that for fully replicated caches this method should always
 * return {@code 1}.
{code}
but it's not true, it works the same as PARTITIONED cache.

Affinity.mapKeyToNode(K key) javadoc says:

{code:java}

 * 
 *  For fully replicated caches first node ID returned by {@link 
AffinityFunction}
 *  is returned.
 * 
 * For partitioned caches, primary node for the given key is 
returned.

{code}

it looks confusing, while REPLICATED cache has primary nodes for keys as 
PRATITIONED.

Also,  

{code:java}
* Provides affinity information to detect which node is primary and which nodes 
are
 * backups for a partitioned cache.
{code}

Affinity matter for REPLICATED cache too.




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

[GitHub] ignite pull request #448: ignite-2536 reproducer test

[agura]

Github user agura closed the pull request at:

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


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

[GitHub] ignite pull request #387: ignite-2307 Reproducer test

[agura]

Github user agura closed the pull request at:

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


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

[GitHub] ignite pull request #2207: Ignite 5589: Archive WAL segment after significan...

[dspavlov]

GitHub user dspavlov opened a pull request:

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

Ignite 5589: Archive WAL segment after significant period of grid inactivity

Please don't merge. PR is for TC run

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

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

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

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


commit 468033cc060cff8bdb7c74054eb47500d25732af
Author: dpavlov 
Date:   2017-06-21T14:10:04Z

IGNITE-5558: mock based test iterator created: Add ability to read WAL 
outside of an Ignite node

commit 3c1e28e46c3d5095ce00638e225768a10163a307
Author: dpavlov 
Date:   2017-06-21T15:00:25Z

IGNITE-5558: change to run on TC

commit defda5b4003bf990e6ca10ffef20ea0d35ee546b
Author: dpavlov 
Date:   2017-06-22T11:42:50Z

IGNITE-5558: first non-mockito based iterator implementation

commit 55fdb9ba2ecd46c4f701c11deb0cc2fea7ab5ff4
Author: dpavlov 
Date:   2017-06-22T12:10:46Z

IGNITE-5558: update for running on teamcity

commit 8e61faeb1a4eaa541c7ae7257721c302b966fbf5
Author: dpavlov 
Date:   2017-06-22T13:20:56Z

IGNITE-5558: WAL iterator creation moved to standalone class

commit b7024715585735a7011defafade5d267fe3f86e3
Author: dpavlov 
Date:   2017-06-22T14:24:41Z

IGNITE-5558: Mock factory extracted as standalone class

commit fed81a079b82d3445793fef37c61ef16a40c9446
Author: dpavlov 
Date:   2017-06-22T15:00:42Z

IGNITE-5558: compile fix

commit 9a844a8e7b80d6cde2247780500878a5ab70128a
Author: dpavlov 
Date:   2017-06-22T16:47:32Z

IGNITE-5558: WAL reader was moved to core, main() method was created

commit c6cbb4b910a29135e73298a7f64a63dbb354dfa0
Author: dpavlov 
Date:   2017-06-22T17:49:26Z

IGNITE-5558: WAL reader: correct close, record exception printing, file 
headers, javadoc

commit 1be55120fd9d56f9ef28fd691a526a3482ceef48
Author: dpavlov 
Date:   2017-06-22T18:35:03Z

IGNITE-5558: WAL reader: 2 modes were created: directory and files

commit 9df9b12297fd103a8f5564f600a90814961d94c1
Author: dpavlov 
Date:   2017-06-23T10:38:22Z

IGNITE-5558: WAL reader NPE fix and javadocs

commit 79d934d36e768430376655c05517f83386028cae
Author: dpavlov 
Date:   2017-06-23T12:36:52Z

IGNITE-5558: cosmetic & javadocs

commit 7b00272edf9dbcd35c9f2a6697253c61bbb7f80c
Author: dpavlov 
Date:   2017-06-26T14:16:46Z

IGNITE-5587: Generate File WAL Segment Archive Completed Event

commit 13a3b1a52cfb561011df96dda32eb41c2551ce26
Author: dpavlov 
Date:   2017-06-26T15:07:34Z

IGNITE-5587: Javadoc and cosmetic: Generate File WAL Segment Archive 
Completed Event

commit dce18c0581f9e3caff39c13cf0b681daa43934fc
Author: dpavlov 
Date:   2017-06-26T16:42:55Z

IGNITE-5587: Generate File WAL Segment Archive Completed Event

commit 69bbd6e7eedb90382128023a0ed478dd9cc42492
Author: dpavlov 
Date:   2017-06-26T16:57:56Z

IGNITE-5591: WAL queue flusher for background mode was replaced with 
Timeout processor

commit 91eb1e926500c0eb9d4c87f0686372dfa4ad0cef
Author: dpavlov 
Date:   2017-06-26T17:22:09Z

IGNITE-5591: serial version ID added

commit 552e379b5238cdbedbb818f3d56ea04207deb984
Author: dpavlov 
Date:   2017-06-27T13:54:00Z

IGNITE-5589: Archive WAL segment after significant period of grid inactivity




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

[GitHub] ignite pull request #2206: IGNITE-5340 AssertionError in index name check

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5340  AssertionError in index name check



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

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

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

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


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

IGNITE-5267 Deserialize binary object explicitly instead of calling cache. 
Small refactoring.

commit 95257a16aef0bc0bbacdee03503ee483ffc75bda
Author: Pavel Kovalenko 
Date:   2017-06-08T21:34:37Z

IGNITE-5267 Small test refactoring and speeding up

commit e2354cb5ea8965276c3696895c86e51315765571
Author: Pavel Kovalenko 
Date:   2017-06-08T21:37:38Z

IGNITE-5267 Fixed and simplified test

commit 41cea0bc2f887881a78436e54143313af27e7fa8
Author: Pavel Kovalenko 
Date:   2017-06-08T21:38:55Z

IGNITE-5267 Make partitionMapExchange timeout configurable

commit 8e1439782b993c8ccb974bcdbd55d4f2b28a5489
Author: Pavel Kovalenko 
Date:   2017-06-08T21:40:53Z

IGNITE-5267 Use owners instead of nodes to properly check finishing of 
partitionMapExchange

commit ef732dae02673c2ce79575b57454a573f0d1d591
Author: Pavel Kovalenko 
Date:   2017-06-08T21:42:00Z

IGNITE-5267 Provide entry key explicitly in cache queries. Fixed test.

commit 5eb40528bd6e52b4c13a4c21ecca74407b081898
Author: Pavel Kovalenko 
Date:   2017-06-08T21:42:34Z

IGNITE-5267 Explicitly fail test with known issue

commit e4f203b512cba1dc8ae82b506cadebfed3fd7f65
Author: sboikov 
Date:   2017-06-13T13:58:12Z

review

commit fd7050c72c8125ed1dd213ef781bdb9971d00413
Author: Dmitriy Govorukhin 
Date:   2017-06-13T14:02:54Z

ignite-2.1.1 Add joining node tests in suit

commit 3e509aa604ca342b3f42a73e771a5a4f678d7132
Author: Ivan Rakov 
Date:   2017-06-13T14:13:43Z

ignite-2.1.1 Fixing compilation in tests

commit dea416fa65874d4e33b37b46368f9e476a3904f4
Author: dpavlov 
Date:   2017-06-13T15:00:32Z

Merge fix: 4.ea2 into 5267: remove node is loopback check

commit b52a84e885b0f88971290200942e0bbe01252ff6
Author: sboikov 
Date:   2017-06-13T15:09:41Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-2.1.1

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/IgniteDiagnosticAware.java
#   
modules/core/src/main/java/org/apache/ignite/internal/IgniteDiagnosticMessage.java
#   modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCacheIoManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/GridPartitionedSingleGetFuture.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/atomic/GridDhtAtomicCache.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/colocated/GridDhtColocatedLockFuture.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/preloader/GridDhtPartitionsExchangeFuture.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/IgniteTxImplicitSingleStateImpl.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cache/transactions/IgniteTxStateImpl.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/cluster/ClusterProcessor.java
#   
modules/core/src/main/java/org/apache/ignite/internal/util/nio/GridNioServer.java
#   
modules/core/src/main/java/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.java
#   
modules/core/src/test/java/org/apache/ignite/internal/managers/IgniteDiagnosticMessagesTest.java
#   
modules/web-console/web-agent/src/main/java/org/apache/ignite/console/agent/handlers/ClusterListener.java

commit fb2e6d4ab00e3e443bdd896918e812d6fa6119ba
Author: sboikov 
Date:   2017-06-13T15:10:18Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-2.1.1

# Conflicts:
#   

Problem with setting up .NET dev environment

[Guru Stron]

Hi igniters,

I have problem with setting up dev environment on one of my machines(using
fresh master). The maven build step from Ignite.NET+Development

manual
page fails. My old dev environment on other machine works just fine.

I use "*mvn clean package -DskipTests*" command as stated and it fails with
a bunch of errors like:

[ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for
> org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> org.apache.ignite:ignite-parent:pom:1 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced and 'parent.relativePath' points at wrong
> local POM @ line 26, column 13
> [FATAL] Non-resolvable parent POM for
> org.apache.ignite:ignite-core:2.1.0-SNAPSHOT: Failure to find
> org.apache.ignite:ignite-parent:pom:1 in
> file://${basedir}/src/test/binaries/repo was cached in the local
> repository, resolution will not be reattempted until the update interval of
> ignite-binaries-test-repo has elapsed or updates are forced and
> 'parent.relativePath' points at wrong local POM @ line 26, column 13
> [FATAL] Non-resolvable parent POM for
> org.apache.ignite:ignite-hadoop:2.1.0-SNAPSHOT: Failure to find
> org.apache.ignite:ignite-parent:pom:1 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced and 'parent.relativePath' points at wrong
> local POM @ line 26, column 13
> ...
> [ERROR] The build could not read 48 projects -> [Help 1]
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [FATAL] Non-resolvable parent POM for
> org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> org.apache.ignite:ignite-parent:pom:1 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced and 'parent.relativePath' points at wrong
> local POM @ line 26, column 13
>
> ...
> [FATAL] Non-resolvable parent POM for
> org.apache.ignite:ignite-visor-plugins:2.1.0-SNAPSHOT: Failure to find
> org.apache.ignite:ignite-parent:pom:1 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced and 'parent.relativePath' points at wrong
> local POM @ line 26, column 13
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:382)
> at
> org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:400)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:391)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:78)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:511)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:221)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> 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
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [ERROR]
> [ERROR]   The project org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT
> (C:\Misc\myuser\Projects\Ignite\src\modules\tools\pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM for
> org.apache.ignite:ignite-tools:2.1.0-SNAPSHOT: Failure to find
> org.apache.ignite:ignite-parent:pom:1 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced and 'parent.relativePath' points at wrong
> local POM @ line 26, column 13 -> [Help 2]
> org.apache.maven.model.resolution.UnresolvableModelException: Failure to
> find org.apache.ignite:ignite-parent:pom:1 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> 

[jira] [Created] (IGNITE-5596) Exchange time measurement

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5596:


 Summary: Exchange time measurement
 Key: IGNITE-5596
 URL: https://issues.apache.org/jira/browse/IGNITE-5596
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin


Need to log exchange start and finish 

Messages should look like this:

Started exchange completion, topVer=.., minorTopVer=.., timestamp = ..

Finished exchange completion, topVer=.., minorTopVer=.., timestamp = ..



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

[GitHub] ignite pull request #2192: fix metadata update

[sboikov]

Github user sboikov closed the pull request at:

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


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

[jira] [Created] (IGNITE-5595) Optimize 'client' event exchanges

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-5595:


 Summary: Optimize 'client' event exchanges
 Key: IGNITE-5595
 URL: https://issues.apache.org/jira/browse/IGNITE-5595
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 2.1


When client node joins/leaves GridDhtPartitionsExchangeFuture is still created 
and it seems some executed actions are not necessary:
- there is no need to call detectLostPartitions
- lots of actions in GridDhtPartitionTopology.beforeExchange are not needed




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

Re: Zookeeper Discovery SPI & external IP address in AWS

[Yakov Zhdanov]

>>Both will work, but frankly I like option 1 more. First of all, it's just
>>more intuitive that IP finder contains all possible addresses that can be
>>used to join. Second of all, option 2 introduces requirement to have
>>address resolver for server addresses configured on client nodes - this is
>>not very good from usability standpoint.

Val, I see your point, but (1) means that clients should have public IPs
for communication or server resolver should be able to resolve them. In any
case there will be some mixture. Is that correct?

--Yakov

[jira] [Created] (IGNITE-5594) Ignite test framework intervenes into configuration of Ignite node internal component

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5594:
---

 Summary: Ignite test framework intervenes into configuration of 
Ignite node internal component
 Key: IGNITE-5594
 URL: https://issues.apache.org/jira/browse/IGNITE-5594
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.2


h2. Notes
Class *IgniteTestResources* participates in configuring ignite nodes managed by 
test framework and makes some configurations which may mask real issues with 
configuring nodes IRL.

E.g. jUnit test supposed to reproduce some issue passes but the real problem 
isn't fixed.

h2. Acceptance Criteria
# Malicious configuration actions are cleaned up from *IgniteTestResources* 
# No new test failures are introduced because of this change.



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

[GitHub] ignite pull request #2204: IGNITE-5279

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

IGNITE-5279



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

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

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

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


commit 89be7b8c148fc06971855e9afbfbda6fb8c85db9
Author: Alexander Paschenko 
Date:   2017-06-23T18:59:39Z

IGNITE-5279 Name case sensitivity tests for CREATE INDEX and CREATE TABLE.

commit db32a2635cf912ca524f07f7b7226a480aa9b75b
Author: Alexander Paschenko 
Date:   2017-06-27T10:19:42Z

Merge remote-tracking branch 'apache/master' into ignite-5279




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

[GitHub] ignite pull request #2203: IGNITE-5456 JDBC thin driver: the statement produ...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5456 JDBC thin driver: the statement produces multiple result …

…sets must be handled correct

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

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

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

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


commit 7c9c7abc1d7a2091de5fad19f76a85b7c828a976
Author: tledkov-gridgain 
Date:   2017-06-27T10:06:19Z

IGNITE-5456 JDBC thin driver: the statement produces multiple result sets 
must be handled correct




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

daemon nodes

[Dmitriy Govorukhin]

Hi Igniters,

Can somebody explain what does mean  daemon node? I thought that exist
only client and server node, but node may can be daemon (server daemon
or client daemon).  As is can see, command line visor join in topology
as server daemon. Can this be an outdated functionality?

[GitHub] ignite pull request #2202: IGNITE-5076: improved multi-threaded start of nod...

[sk0x50]

GitHub user sk0x50 opened a pull request:

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

IGNITE-5076: improved multi-threaded start of nodes



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

$ git pull https://github.com/sk0x50/ignite ignite-5076-master

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

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






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

[GitHub] ignite pull request #2201: IGNITE-5521: Large near caches lead to cluster in...

[mcherkasov]

GitHub user mcherkasov opened a pull request:

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

IGNITE-5521: Large near caches lead to cluster instability with metrics 
enabled



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

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

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

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






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

[GitHub] ignite pull request #2199: Ignite gg 12347 1

[sergey-chugunov-1985]

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

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

Ignite gg 12347 1



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

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

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

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


commit 9bf26ac75ddb4c91dabcd117eb0e92be9d2b735d
Author: Ilya Lantukh 
Date:   2017-06-08T14:18:00Z

Minor fixes, refactoring.

(cherry picked from commit f670be2)

commit 975c9bc480decb5a06d7cda5434745e5b264d401
Author: Ilya Lantukh 
Date:   2017-06-08T14:47:46Z

Javadoc.

commit cd4d04007ca7ad1bfbd7f358f9182f970d38ec3e
Author: Alexey Goncharuk 
Date:   2017-06-08T16:10:54Z

IGNITE-5267 - Moved WAL system properties to WAL configuration

commit 15f3c4eeb7642791845ca19cce7e47c5e61c5139
Author: Ilya Lantukh 
Date:   2017-06-08T19:25:32Z

Made data structure name unique per group.

commit 4b89ae0197ca4acc4d1ee730d296d0e1693674f7
Author: Alexey Goncharuk 
Date:   2017-06-09T11:23:48Z

IGNITE-5267 - Cleaning public API

commit ee5c5ca765d778bccae444db1f8db6ae88a95253
Author: Ilya Lantukh 
Date:   2017-06-09T12:34:16Z

API

commit d099d82b1b37aaa2ec12291902b79e04d30c0693
Author: Ilya Lantukh 
Date:   2017-06-09T12:34:39Z

Merge remote-tracking branch 'community/ignite-5267-ds' into ignite-5267-ds

commit 87551427c5796a5d48f60a412a770b810269b797
Author: Konstantin Dudkov 
Date:   2017-06-09T13:21:31Z

IGNITE-5306 - Persist SQL context along with cache configuration

commit 7977052e45907b8d36340b41ba07bb1d9769af11
Author: Ilya Lantukh 
Date:   2017-06-09T13:27:30Z

Named default group.

commit b6c736172006814eb848bc5abc9dd515bcfec8fb
Author: Alexey Goncharuk 
Date:   2017-06-09T13:43:48Z

Merge branch master into ignite-5267

commit fbb51b01caa666ec9625b9c7f05f80020b05d647
Author: Alexey Goncharuk 
Date:   2017-06-09T14:17:47Z

Merge from ignite-5267

commit ffe1a010c9452954aabd091b25e3dc47128acdcd
Author: Alexey Goncharuk 
Date:   2017-06-09T14:20:07Z

Merge from ignite-5267

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

ignite-5324 : Volatile data structures.

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

IGNITE-5267 - Fixed NPE in checkpointer

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

IGNITE-5392 - Joining node must accept cluster active status

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

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

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

IGNITE-5267 - Added missing class

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

IGNITE-5267 - Activate nodes after start

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

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

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

ignite-2.1.1 fix java doc

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

ignite-2.1.1 fix import

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

ignite-2.1.1 fixing pds tests

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

ignite-2.1.1 fixing pds tests

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

IGNITE-5267 Snapshots support.

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

Merge with ignite-5267-merge.

commit 4342f46ab4258f8219e45f4b69435f38b6d0f2b5
Author: Ilya Lantukh 
Date:   

Re: JIRA Access - Ignite

[Alexey Kuznetsov]

Hi Ankur,

What is your JIRA ID?

On Tue, Jun 27, 2017 at 3:42 PM, Ankur Kumar  wrote:

> I can access Apache Ignite but can not assign any defect to myself. Can I
> get permission to assign issues to myself to work on these items?
>
> Regards,
>
> Ankur Kumar
>



-- 
Alexey Kuznetsov

JIRA Access - Ignite

[Ankur Kumar]

I can access Apache Ignite but can not assign any defect to myself. Can I
get permission to assign issues to myself to work on these items?

Regards,

Ankur Kumar

DataStreamer Transactional and Timestamp Implementation

[fatih]

Hi 

We have implemented some receivers to be able to update data in data nodes
by ignite datastreamer api.

There is an associated ticket as below already exist. We thought it would be
useful to use that implementation from ignite directly. Maybe can be added
to ignite directly.

http://apache-ignite-users.70518.x6.nabble.com/Transaction-Boundary-Data-Streamer-td13803.html#a14078
AbstractTransactionalStreamReceiver.java

  

TimestampBasedUpdateStreamReceiver.java

  




--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/DataStreamer-Transactional-and-Timestamp-Implementation-tp19129.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[jira] [Created] (IGNITE-5593) Affinity change message leak on massive topology updates

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5593:


 Summary: Affinity change message leak on massive topology updates
 Key: IGNITE-5593
 URL: https://issues.apache.org/jira/browse/IGNITE-5593
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.7
Reporter: Alexey Goncharuk
Priority: Critical
 Fix For: 2.1


When late affinity assignment is enabled, we complete the exchange future with 
custom discovery event. Since discovery topology events usually are much faster 
than exchange futures completion, it is possible that a newly joined node can 
'see' the affinity change messages that are related to previous topology 
versions when this node even was not present in the topology.

When this message is received, an exchange future is created and this message 
is added to discoEvts list. However, this future never completes on this node 
because init() is never called. This means that this exchange future sits in 
the exchange set with the affinity change message.

Since the number of topology changes (and, thus, messages) can be quite large, 
this leads to excessive memory consumption on the starting node. I've observed 
~3Gb of heap wasted on one of the nodes when > 200 nodes were restarted.



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

Server stores cache data on-heap if client has near cache - IGNITE-4662

[Vyacheslav Daradur]

Hi Igniters.

I have some questions according to this task:

1. Does the method: GridCacheMapEntry#evictInternal do the eviction(on-heap
-> off-heap)?
2. Is CacheOffheapEvictionManager responsible for managing the
eviction(on-heap -> off-heap)? (if not, then who is?)
3. At what moment the eviction(on-heap -> off-heap) is called?


-- 
Best Regards, Vyacheslav D.