Re: new connection event

[Oleg Ostanin]

Thank you for the response. Yes, we have a simple warning in log, but in
case SSL error needs an immediate human attention it would be better to set
a listener for such events.

вт, 11 авг. 2020 г. в 17:59, Ilya Kasnacheev :

> Hello!
>
> I'm not sure this is a good event. Events are computer-processable, while
> SSL error either needs attention from a human or none at all.
>
> Then again, sometimes it's not an SSL error (come to think or it,
> unauthorized people tend to not use SSL since success is not an option
> here) but any unexpected input. Such input will mean that something (or
> somebody) wrong is trying to connect, possibly using a wrong port or hoping
> that SSL is disabled.
>
> Maybe we need a simple warning. I guess we already have it, actually. Don't
> we?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 11 авг. 2020 г. в 14:27, Oleg Ostanin :
>
> > Hello igniters! I wonder if we can add a new event for a failed ssl
> > connection? Considering security hazards it can be quite helpful to get
> > notifications in case someone unauthorized is trying to connect to the
> > cluster. I've created a small pull-request to illustrate a possible
> > solution.
> > https://github.com/apache/ignite/pull/8139
> > Please tell me what do you think.
> >
>

new connection event

[Oleg Ostanin]

Hello igniters! I wonder if we can add a new event for a failed ssl
connection? Considering security hazards it can be quite helpful to get
notifications in case someone unauthorized is trying to connect to the
cluster. I've created a small pull-request to illustrate a possible
solution.
https://github.com/apache/ignite/pull/8139
Please tell me what do you think.

Add user defined attributes to all GridClient messages.

[Oleg Ostanin]

Hello, Igniters!

Recently we added the possibility of sending user defined attributes from
clients, and check those attributes in a custom authenticator
implementation[1]. However in some cases it's not working well for
GridClient because currently the attributes are only added to TOPOLOGY
message. I've created a ticket with a reproducer:

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

I suggest solving this problem by adding user defined attributes to other
GridClient messages such as GridClientAutheticationRequest and so on.

What do you think?

Best regards
Oleg

[1]
https://issues.apache.org/jira/browse/IGNITE-12049

[jira] [Created] (IGNITE-12891) Add userAttributes map to all GridClient messages

[Oleg Ostanin (Jira)]

Oleg Ostanin created IGNITE-12891:
-

 Summary: Add userAttributes map to all GridClient messages
 Key: IGNITE-12891
 URL: https://issues.apache.org/jira/browse/IGNITE-12891
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Currently we are only sending userAttributes map in GridClient TOPOLOGY 
message. In some particular circumstances it can lead to an authentication 
failure.

Reproducer:

https://github.com/oleg-ostanin/ignite/blob/gridclient-fail-reproducer/modules/core/src/test/java/org/apache/ignite/internal/processors/security/client/AdditionalSecurityCheckGridClientTest.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSSION] Improvement in control.sh configuration.

[Oleg Ostanin]

I'm currently working on ticket
https://issues.apache.org/jira/browse/IGNITE-12832

It's not exactly what had been suggested but it will allow to pass some
custom properties to the client configuration and to pass parameters without
length limitations using .properties file.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

contribution permissions

[Oleg Ostanin]

Hello Ignite Community!

My name is Oleg. I want to contribute to Apache Ignite and want to
start with this issue - IGNITE-12832, my JIRA username oleg-a-ostanin.
Any help on this will be appreciated.

Thanks!

[GitHub] ignite pull request #5498: IGNITE-10403 added parent guava dependency in pom...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-10403 added parent guava dependency in pom.xml



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

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

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

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


commit d06eca894fe779836a06f9491d4a3da0c1f2fbf3
Author: oleg-ostanin 
Date:   2018-11-26T07:37:34Z

IGNITE-10403 added parent guava dependency in pom.xml




---

[jira] [Created] (IGNITE-10403) Yardstick does not work without Guava 20 in the classpath

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-10403:
-

 Summary: Yardstick does not work without Guava 20 in the classpath
 Key: IGNITE-10403
 URL: https://issues.apache.org/jira/browse/IGNITE-10403
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin


{noformat}

Exception in thread "main" java.lang.NoSuchMethodError: 
com.google.common.collect.Sets$SetView.iterator()Lcom/google/common/collect/UnmodifiableIterator;
 at org.reflections.Reflections.expandSuperTypes(Reflections.java:380) at 
org.reflections.Reflections.(Reflections.java:126) at 
org.reflections.Reflections.(Reflections.java:168) at 
org.yardstickframework.impl.BenchmarkLoader.initialize(BenchmarkLoader.java:99) 
at 
org.yardstickframework.BenchmarkServerStartUp.main(BenchmarkServerStartUp.java:40)

{noformat}

 
Explanation from this link:
 [https://github.com/confluentinc/kafka-connect-elasticsearch/issues/143]

'This error means that you are bringing an older version of guava earlier in 
your classpath. Connect worker requires guava >= 20 for org.reflections to work 
correctly.'

Indeed adding guava 20 to Yardstick ./lib folder helps. Will create ticket in 
Ignite jira and fix ignite-yardstick pom.xml file.



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

[GitHub] ignite pull request #4812: IGNITE-9309 added runLocal

[oleg-ostanin]

Github user oleg-ostanin closed the pull request at:

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


---

[jira] [Created] (IGNITE-10346) Improve TcpDiscoveryVmIpFinder usability in Yardstick

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-10346:
-

 Summary: Improve TcpDiscoveryVmIpFinder usability in Yardstick
 Key: IGNITE-10346
 URL: https://issues.apache.org/jira/browse/IGNITE-10346
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


 

Currently we have to set IP address list in both property file and Ignite XML 
config. However using 
 cfg.customProperties().get("SERVER_HOSTS")
 before starting the node we can get that list, set it to 
TcpDiscoveryVmIpFinder and start node. I think it will improve Yardstick 
usability a little bit.



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

[GitHub] ignite pull request #4877: IGNITE-5534 added method to activate cluster

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-5534 added method to activate cluster



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

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

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

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


commit 019b4df5c9c7dfc4ea94eb7284c4bc932f33074f
Author: oleg-ostanin 
Date:   2018-10-01T07:31:50Z

IGNITE-5534 added method to activate cluster




---

[GitHub] ignite pull request #4824: IGNITE-9682 changed updatePartitionFullMap() meth...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-9682 changed updatePartitionFullMap() method to update map in …

…parallel

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

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

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

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


commit ab31afe6a234db08b5455b3b40f64d895f4c614b
Author: oleg-ostanin 
Date:   2018-09-25T09:40:25Z

IGNITE-9682 changed updatePartitionFullMap() method to update map in 
parallel




---

[jira] [Created] (IGNITE-9682) Update full partition map in parallel

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-9682:


 Summary: Update full partition map in parallel
 Key: IGNITE-9682
 URL: https://issues.apache.org/jira/browse/IGNITE-9682
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


I've noticed that we are updating full partition map for each cache 
sequentially and at the same time we cannot run much of other tasks before the 
updating is completed, so there must be some threads available for parallel 
updating. Sometimes it takes 20-30 seconds to update map for 100+ caches before 
rebalancing can even start:

[2018-09-24 16:38:49,016][INFO ][sys-#219] Received full message, will finish 
exchange [node=4d6b5921-0a61-4bfa-bf11-b8a1b8332dce, 
resVer=AffinityTopologyVersion [topVer=19, minorTopVer=2]]

...

[2018-09-24 16:39:01,217][INFO ][sys-#219] Finish exchange future 
[startVer=AffinityTopologyVersion [topVer=19, minorTopVer=2], 
resVer=AffinityTopologyVersion [topVer=19, minorTopVer=2], err=null]



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

[GitHub] ignite pull request #4812: IGNITE-9309 added runLocal

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-9309 added runLocal



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

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

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

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


commit 60d4021e8c103a2062bdfd8ad6df56bd80ccef54
Author: oleg-ostanin 
Date:   2018-09-22T14:59:47Z

IGNITE-9309 added runLocal




---

[GitHub] ignite pull request #4811: Ignite 9492 qaoo

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 9492 qaoo



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

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

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

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


commit 0d0a25364eb4dfa97f57e98fa56e1e996476c604
Author: Pavel Kovalenko 
Date:   2018-09-17T14:46:45Z

IGNITE-9492 Ignore SingleMessage updated where there is exchange in 
progress.

commit 201c9c40e35cf532c00644bf59accd78cbb2cabc
Author: Pavel Kovalenko 
Date:   2018-09-17T15:03:10Z

IGNITE-9492 Fixed condition.

commit ca6c7c8f9a8e858523eb65e91756b899fc1c9484
Author: Pavel Kovalenko 
Date:   2018-09-18T11:26:15Z

Merge branch 'master' into ignite-9492

commit 095f944b764e376e1d7450575d04d22d559e862c
Author: Pavel Kovalenko 
Date:   2018-09-18T13:43:38Z

IGNITE-9492 Reworked condition exchangeInProgress.

commit 049a9914560aac3ad79e64c3ee07cd03263758a8
Author: Pavel Kovalenko 
Date:   2018-09-21T15:47:35Z

IGNITE-9492 Reworked exchangeInProgress condition.

commit c720cc86716365a24ec69ba12627006ac6421905
Author: oleg-ostanin 
Date:   2018-09-22T11:35:00Z

IGNITE-9492 added exchangeInProgress() check to 
GridDhtPartitionsFullMessage handler

commit 3a702f1d4d73206e04de8b0f9ce37d1ebf996725
Author: oleg-ostanin 
Date:   2018-09-22T13:45:41Z

IGNITE-9492 reverted change




---

[GitHub] ignite pull request #4783: Ignite 9309 a

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 9309 a



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

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

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

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


commit 25178213f331045ef37f37bc90c828d8c3be1291
Author: oleg-ostanin 
Date:   2018-09-17T17:13:16Z

IGNITE-9309 added excange version check

commit 61721bc2e1d93d6a2446b942aa94a193c6072d7e
Author: oleg-ostanin 
Date:   2018-09-18T10:36:50Z

IGNITE-9309 checking exchangeVer




---

[GitHub] ignite pull request #4548: IGNITE-9234 fixed javadocs

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-9234 fixed javadocs



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

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

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

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


commit 38009868b5d3b39b1d4546ec28ac6acb46886fba
Author: oleg-ostanin 
Date:   2018-08-15T14:39:43Z

IGNITE-9234 fixed javadocs




---

[GitHub] ignite pull request #4323: Ignite 8322 fix

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 8322 fix



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

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

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

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


commit b6037c37cdc34ca8f964b7af30835b2474ca9db2
Author: oleg-ostanin 
Date:   2018-06-18T07:17:36Z

IGNITE-8322 changed default value for preloading option to 'false'

commit 9b6571bdfab8fb0f6b64c9f502437091347e
Author: oleg-ostanin 
Date:   2018-06-19T07:24:51Z

IGNITE-8322 changed data region name setting logic

commit 362309ba3fc3b670b0e95828dd2758c9d10e36b7
Author: oleg-ostanin 
Date:   2018-06-19T09:55:14Z

IGNITE-8322 added data region name log output

commit 6f6f9089dd88d3a22d0563fd6558ef1b4823bfab
Author: oleg-ostanin 
Date:   2018-06-19T10:04:26Z

IGNITE-8322 added data reg. cfg array checking

commit 96c156ceef8bb941ab833994f816efd7babec821
Author: oleg-ostanin 
Date:   2018-07-02T13:27:46Z

fixed Loader class

commit d83facc28d75db63aeec58a6f1eed1ff71d95290
Author: oleg-ostanin 
Date:   2018-07-06T07:28:15Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-8322-fix




---

[jira] [Created] (IGNITE-8861) Wrong method call in IgniteServise documentation snippet

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-8861:


 Summary: Wrong method call in IgniteServise documentation snippet
 Key: IGNITE-8861
 URL: https://issues.apache.org/jira/browse/IGNITE-8861
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Reporter: Oleg Ostanin


[https://apacheignite.readme.io/docs/service-example]

{{ClusterGroup cacheGrp = ignite.cluster().forCache("myCounterService");}}

{{This string does not compile if we use 2.5 version:}}

{{[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile (default-compile) 
on project poc-tester: Compilation failure}}
{{[ERROR] 
/home/oostanin/gg-qa/poc-tester/src/main/java/org/apache/ignite/scenario/ServiceTask.java:[53,51]
 cannot find symbol}}
{{[ERROR]   symbol:   method forCache(java.lang.String)}}
{{[ERROR]   location: interface org.apache.ignite.IgniteCluster}}



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

[GitHub] ignite pull request #4210: IGNITE-8322 changed default value for preloading ...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-8322 changed default value for preloading option to 'false'



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

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

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

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


commit b6037c37cdc34ca8f964b7af30835b2474ca9db2
Author: oleg-ostanin 
Date:   2018-06-18T07:17:36Z

IGNITE-8322 changed default value for preloading option to 'false'




---

[GitHub] ignite pull request #3942: Ignite 8337

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 8337



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

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

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

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


commit b67003b6faa1785ff154392ba66d603bc15b1399
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-23T11:53:33Z

added IgniteCacheThinAbstractBenchmark

commit 24182036e17686246e32eed315bd907f01f75967
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-26T09:58:17Z

added tx benchmarks

commit 3e193cc5a8e9172b15b56614b64c1ce7f7a82134
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-26T11:13:12Z

IGNITE-8337 fixed putAll benchmark

commit 55f58b0fc39e1c11fe0c4266c4dea2a85df087d3
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-26T13:50:07Z

IGNITE-8337 fixed npe in get benchmark

commit d2e2d9738d968251900d11cbdccf3f48d3533052
Author: oleg-ostanin <oostanin@...>
Date:   2018-05-03T11:10:20Z

IGNITE-8337 fixed comments




---

[GitHub] ignite pull request #3884: Ignite 8322

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 8322



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

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

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

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


commit 328d84cf25c0c607e0b37aeb82f83938f09a838a
Author: oleg-ostanin <oostanin@...>
Date:   2018-03-28T13:43:35Z

added method for data preload

commit e84aba963b704b26a1270a2f1eb327debe6d8d24
Author: oleg-ostanin <oostanin@...>
Date:   2018-03-28T14:26:56Z

added option for enabling preload

commit 6a8a877ae2d500ef61a0d9fe372bdaffdf058c5f
Author: oleg-ostanin <oostanin@...>
Date:   2018-03-29T08:47:27Z

added preloader class

commit e7fb9c1a4e09de29d4fbe5b4c733d7efa1b0eabc
Author: oleg-ostanin <oostanin@...>
Date:   2018-03-29T09:04:19Z

removed default dataregion config

commit 5f48d8cf11fcd61c3f4ec596e6814eb181c7774a
Author: oleg-ostanin <oostanin@...>
Date:   2018-03-29T11:56:43Z

added waiting for preload for clients

commit 9cbab5287c6dc4576867c984b03767751d1c8921
Author: oleg-ostanin <oostanin@...>
Date:   2018-03-30T10:21:05Z

added semaphore on preload for clients

commit 4f13833108fb58a6c9f366150bb51158abb9879e
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-19T11:52:08Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-gg-13646

commit 49f4730327126c7ac22ac095edec0434122983b4
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-19T12:14:21Z

IGNITE-8322 added some comments

commit 5137a4810a6ef57d1fd2a095b06c0db1a0ffcfe4
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-19T12:20:25Z

IGNITE-8322 fixed format




---

[jira] [Created] (IGNITE-8322) Yardstick benchmark preloading option

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-8322:


 Summary: Yardstick benchmark preloading option
 Key: IGNITE-8322
 URL: https://issues.apache.org/jira/browse/IGNITE-8322
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Yardstick has no benchmarks with eviction on the disk (PDS). For that puspose 
we need following:
1. Make new configuration and put every cache into a separate date region:
atomic,tx,atomic-index,query,compute
2. Add a new preload option for a benchmark: preload up to a size passed from 
that option. There two options:
 * total size of preload data (bytes)
 * the size of data in memory against total size (percent)



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

[jira] [Created] (IGNITE-8319) Examples do not launch from Intellij Idea because ML module is configured incorrectly.

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-8319:


 Summary: Examples do not launch from Intellij Idea because ML 
module is configured incorrectly.
 Key: IGNITE-8319
 URL: https://issues.apache.org/jira/browse/IGNITE-8319
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin


Examples do not launch from Intellij Idea because ML module is configured 
incorrectly.



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

[GitHub] ignite pull request #3825: IGNITE-8274 Changed invoking java in sqlline.sh

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-8274 Changed invoking java in sqlline.sh



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

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

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

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


commit 9adf473d1d4e86e61d3589d388afec8e1a67382e
Author: oleg-ostanin <oostanin@...>
Date:   2018-04-16T10:25:21Z

Changed invoking java in sqlline.sh




---

[jira] [Created] (IGNITE-8226) Thousands of warning messages per second in log files.

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-8226:


 Summary: Thousands of warning messages per second in log files.
 Key: IGNITE-8226
 URL: https://issues.apache.org/jira/browse/IGNITE-8226
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin


Sometimes I see this message in log file:

[2018-04-11 15:45:30,999][WARN ][sys-#454] Partition has been scheduled for 
rebalancing due to outdated update counter 
[nodeId=bed11708-090f-4e44-a1a7-e3d2b717fcb2, grp=cache_group_5, partId=239, 
haveHistory=false]

The problem is that there is about 4 messages per 2 seconds.

Also this message:

[2018-04-11 15:03:39,997][WARN ][sys-#75] Stale update for single partition map 
update (will ignore) [grp=cache_group_46, exchId=null, 
curMap=GridDhtPartitionMap [moving=1024, top=AffinityTopologyVersion [topVer=4, 
minorTopVer=1], updateSeq=6, size=1024], newMap=GridDhtPartitionMap 
[moving=1024, top=AffinityTopologyVersion [topVer=4, minorTopVer=1], 
updateSeq=6, size=1024]]

appears about 1 times per 2 seconds.

 

Can we move this messages to debug level or do something else?



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

[jira] [Created] (IGNITE-8177) Reduce weight of error messages like "Failed completing transaction" in log files.

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-8177:


 Summary: Reduce weight of error messages like "Failed completing 
transaction" in log files.
 Key: IGNITE-8177
 URL: https://issues.apache.org/jira/browse/IGNITE-8177
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin


I've got 3800 lines (16mb) of log with a messages like message below for 5 
seconds. Total weight of log files from 3 sever nodes is 3.7Gb after less than 
2 hours test run. Please reduce the weight of this error message.

[2018-04-09 12:20:01,454][ERROR][sys-stripe-12-#13] Failed completing 
transaction [commit=true, tx=GridDhtTxRemote 
[nearNodeId=6dec1aa5-17ed-448a-bc12-544d6248b93e, 
rmtFutId=eedfcb9a261-2f54084f-025b-4456-a0cc-3ead9e576fff, 
nearXidVer=GridCacheVersion [topVer=134743104, order=1523293570237, 
nodeOrder=15], storeWriteThrough=false, super=GridDistributedTxRemoteAdapter 
[explicitVers=null, started=true, commitAllowed=0, 
txState=IgniteTxRemoteStateImpl [readMap={}, writeMap=\{IgniteTxKey 
[key=KeyCacheObjectImpl [part=932, val=2980, hasValBytes=true], 
cacheId=117541902]=IgniteTxEntry [key=KeyCacheObjectImpl [part=932, val=2980, 
hasValBytes=true], cacheId=117541902, txKey=null, val=[op=NOOP, val=null], 
prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
explicitVer=null, dhtVer=null, filters=null, filtersPassed=false, 
filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=932, 
super=GridDistributedCacheEntry [super=GridCacheMapEntry 
[key=KeyCacheObjectImpl [part=932, val=2980, hasValBytes=true], 
val=o.a.i.scenario.internal.model.SampleObject [idHash=569264519, 
hash=838575193, balance=10, salary=10, fields=HashMap 
{field19=fekhluvamozpolpuctrpjpautouyeebo, 
field17=ijvsriulgbuwfofwrnycvwmmgtmqmarg, 
field18=xkonotbmnxsgtvdxrwcivnqjsbprehru, 
field22=zurypxnebmpwauausqxmfzebybgkahsb, 
field23=uxzivqctszwboarscfthdqdxcecyhdmh, 
field20=yymoxyatlkhtaqyjdxjrzludysotaroo, 
field21=eqqtzdyqtjobmweioppngmjjtwfbfwqi, 
field26=tmawokhxxebmrtlqpekdmlsvdofuzmow, 
field27=qxjdqbkkojgkxtcrocehaxgzksbstjtk, 
field24=kmkebzmszsavbghndedhxfyinxxdyubn, 
field25=siqbhamcnoxqwqlhbcalkflzmwcjxrau, 
field28=gzanxamuqkavuikqeyalmddzbrurplgx, 
field29=yjriroayongcmggaqouircgzcnavlfzb, 
field11=gjoxizdbrotbhamsorcwdtymfltpzrpz, 
field12=otfqkyxyqdrseakmioowwhgbtbohwdbc, 
field1=eefhfmkqxkukugwiaeafpngyxfoodvco, 
field31=sxosxcvbwftqmsgxhmcapjocnzuicjah, 
field0=wkudvvebdbysapxmktgcpobbumwporsh, 
field10=bfomayktwkxcgdivqgoijuphuefyvlcp, 
field15=lvmcqdebbjegljkdvbosimcphsdkfxqc, 
field16=jifgylklidyrazxwvusqfdkepkawcjra, 
field13=yphymcunicgropupvayxsuqvdgwtxfzm, 
field14=xnbmytwtqqvkmjqouxwueqsvhgdezmqu, 
field7=dhxhvfmxqwrmllxxpfxogykcnfvyodvz, 
field6=uumzgljfothbbupnednakuzrlzltzwrs, 
field9=qyfdioozvnhatuiusrwpcmeekvznogyb, 
field8=ejmdkmdrjuuboeixtzybadilgubsfhpj, 
field3=snkcwrkvvjonvzoefttbpxnttbxpabko, 
field2=kgoukehptwlckrrbryhbdfrnbfzapzes, 
field30=auanohohpnccqeaymwwxetrbljvshqji, 
field5=xuhfnajhkvttoplasklehbsfyrokhhug, 
field4=hghymdcypsqxdlkqenkilpowrxiehfmz}, key=2980], startVer=1523293570287, 
ver=GridCacheVersion [topVer=134743085, order=0, nodeOrder=1], hash=2980, 
extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=null, 
rmts=[GridCacheMvccCandidate [nodeId=6dec1aa5-17ed-448a-bc12-544d6248b93e, 
ver=GridCacheVersion [topVer=134743104, order=1523293570287, nodeOrder=20], 
threadId=713081, id=4166705, topVer=AffinityTopologyVersion [topVer=-1, 
minorTopVer=0], reentry=null, otherNodeId=ce2224a6-825c-4246-9ccd-9f2f49878dab, 
otherVer=null, mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, 
serOrder=null, key=KeyCacheObjectImpl [part=932, val=2980, hasValBytes=true], 
masks=local=0|owner=1|ready=0|reentry=0|used=1|tx=1|single_implicit=0|dht_local=0|near_local=0|removed=0|read=0,
 prevVer=null, nextVer=null, flags=2]]], prepared=0, locked=false, 
nodeId=null, locMapped=false, expiryPlc=null, transferExpiryPlc=false, flags=0, 
partUpdateCntr=0, serReadVer=null, xidVer=GridCacheVersion [topVer=134743104, 
order=1523293570287, nodeOrder=20]]}], super=IgniteTxAdapter 
[xidVer=GridCacheVersion [topVer=134743104, order=1523293570287, nodeOrder=20], 
writeVer=null, implicit=false, loc=false, threadId=24, startTime=1523265601442, 
nodeId=ce2224a6-825c-4246-9ccd-9f2f49878dab, startVer=GridCacheVersion 
[topVer=134743104, order=1523293570265, nodeOrder=1], endVer=null, 
isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, timeout=30, 
sysInvalidate=false, sys=false, plc=2, commitVer=GridCacheVersion 
[topVer=134743104, order=1523293570287, nodeOrder=20], finalizing=NONE, 
invalidParts=null, state=MARKED_ROLLBACK, timedOut=false, 
topVer=AffinityTopologyVersion [topVer=20, minorTopVer=3], duration=10ms, 
onePhaseCommit=false



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

[jira] [Created] (IGNITE-7981) Thread hangs on ignite.cluster().active(false) method call

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-7981:


 Summary: Thread hangs on ignite.cluster().active(false) method call
 Key: IGNITE-7981
 URL: https://issues.apache.org/jira/browse/IGNITE-7981
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin


ignite.cluster().active(false)

After calling this method thread hangs for more than a few hours.

There is thread dump from client node:

"CheckAffinityTask-#62%TaskPool%" #99 prio=5 os_prio=0 tid=0x7f19dd861000 
nid=0x8f5 waiting on condition [0x7f18e5001000]
 java.lang.Thread.State: WAITING (parking)
 at sun.misc.Unsafe.park(Native Method)
 at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
 at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
 at 
org.apache.ignite.internal.cluster.IgniteClusterImpl.active(IgniteClusterImpl.java:312)
 at 
org.apache.ignite.scenario.internal.AbstractTask.copyWorkDirs(AbstractTask.java:757)
 at 
org.apache.ignite.scenario.internal.AbstractTask.stopAndCollect(AbstractTask.java:750)
 - locked <0x0006408d3b68> (a java.lang.Class for 
org.apache.ignite.scenario.internal.AbstractTask)
 at 
org.apache.ignite.scenario.CheckAffinityTask.body0(CheckAffinityTask.java:111)
 at org.apache.ignite.scenario.internal.AbstractTask.body(AbstractTask.java:322)
 at org.apache.ignite.scenario.internal.TaskLooper.run(TaskLooper.java:85)
 at java.lang.Thread.run(Thread.java:748)

 

Thread dumps from server nodes can be found here:

https://drive.google.com/open?id=1fGmVrQ5Q5uggMadbdW0ChoYL5JW18T7K



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

[jira] [Created] (IGNITE-7943) Node hangs on start after failing during checkpoint.

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-7943:


 Summary: Node hangs on start after failing during checkpoint. 
 Key: IGNITE-7943
 URL: https://issues.apache.org/jira/browse/IGNITE-7943
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin


Node can restart more than 20 minutes after failing in the middle of a 
checkpoint.

 



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

[jira] [Created] (IGNITE-7344) Fix yardstick devnotes

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-7344:


 Summary: Fix yardstick devnotes
 Key: IGNITE-7344
 URL: https://issues.apache.org/jira/browse/IGNITE-7344
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin
Priority: Minor


mvn clean package -Pyardstick -pl modules/yardstick -am -DskipTests

does not build Yardstick module any more

mvn clean package -Pall-java,all-other -pl modules/yardstick -am -DskipTests

does.



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

[GitHub] ignite pull request #3142: IGNITW-7093 added plugin to build test.jar to ign...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITW-7093 added plugin to build test.jar to ignite-compatibility po…

…m.xml

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

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

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

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


commit b979ba63f2d481868f2388a97c3e80bebc9f4ed4
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-12-02T10:31:18Z

IGNITW-7093 added plugin to build test.jar to ignite-compatibility pom.xml




---

Re: Can not build from source code

[Oleg Ostanin]

I've just checked master branch (by the way it's 2.4.0-SNAPSHOT now),
everything works fine on java 1.8 and maven 3.5.0. I've also cleaned maven
local repo.

On Mon, Nov 27, 2017 at 4:17 AM, kcmvp  wrote:

> I still run into the same issue
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-6978) Failed to move temp file to a regular WAL segment file

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6978:


 Summary: Failed to move temp file to a regular WAL segment file
 Key: IGNITE-6978
 URL: https://issues.apache.org/jira/browse/IGNITE-6978
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
 Environment: CentOS
Reporter: Oleg Ostanin


1. I've started 2 server nodes on 2 hosts.
2. Started 2 client nodes, one on each host
3. Started DataStreamer from the first client with a key range 0-100 and 
from the second client with a key range 100-200

Then got this exception: 
Failed to set initial value for cache entry: DataStreamerEntry 
[key=KeyCacheObjectImpl [part=157, val=190623, hasValBytes=true], 
val=o.a.i.scenario.internal.model.SampleObject [idHash=2108267055, 
hash=2007824273, salary=1000, fields=HashMap {field19=aupygsskxq, 
field17=vghghwpdkk, field18=wapmsogviv, field22=yhsgrgxjvt, field23=bkuzgwohlp, 
field20=mzcimhrkwl, field21=bkdlrjeosd, field26=wvlypybaop, field27=wqmetfzsdm, 
field24=vpmmxinygq, field25=idbcqlchvq, field11=zkuxmemury, field12=otkuigrzqj, 
field10=uvghlcvwlx, field15=gaootfgcis, field16=abwxazoyoa, field13=flgmuzijzh, 
field14=vzsmgclizh, field39=iqhielhnon, field44=joadulhoxf, field45=bwqqkumjgf, 
field42=epwlotiwbv, field43=cvlehgeyar, field48=gnjawjgbrp, field49=ptfzndiiqm, 
field46=dkmbtdsrcr, field47=smugvczqkk, field40=kgozmlfenp, field41=bxtvofscdp, 
field28=enfjjtysvt, field29=kbzlsguqcb, field33=mbixfddhsq, field34=rygvisgdbi, 
field1=qriiuymvwe, field31=hdqfmkyofe, field0=comhcshciq, field32=lwroifzwfa, 
field37=gnooplphem, field38=zembqqqnzm, field35=pbpgfjvmhs, field36=eqbvpwenrd, 
field7=ymzwgutylc, field6=slnusxjggw, field9=psfzikqbyg, field8=exrrvedqvo, 
field3=dcilcjrprt, field2=yozawivutp, field30=ptreqavpui, field5=kxacmhbusc, 
field4=yxymejnvos}]]
org.apache.ignite.IgniteCheckedException: Failed to move temp file to a regular 
WAL segment file: 
/storage/ssd/oostanin/poc-tester/work/db/wal/poc_tester_server1/0005.wal
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.createFile(FileWriteAheadLogManager.java:987)
 ~[ignite-core-2.1.6.jar:2.1.6]
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.checkFiles(FileWriteAheadLogManager.java:1432)
 ~[ignite-core-2.1.6.jar:2.1.6]
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.access$4900(FileWriteAheadLogManager.java:89)
 ~[ignite-core-2.1.6.jar:2.1.6]
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.allocateRemainingFiles(FileWriteAheadLogManager.java:1402)
 ~[ignite-core-2.1.6.jar:2.1.6]
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileArchiver.run(FileWriteAheadLogManager.java:1187)
 ~[ignite-core-2.1.6.jar:2.1.6]
Caused by: java.nio.file.FileAlreadyExistsException: 
/storage/ssd/oostanin/poc-tester/work/db/wal/poc_tester_server1/0005.wal
at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:429) ~[?:1.8.0_151]
at 
sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) 
~[?:1.8.0_151]
at java.nio.file.Files.move(Files.java:1395) ~[?:1.8.0_151]
at 
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.createFile(FileWriteAheadLogManager.java:984)
 ~[ignite-core-2.1.6.jar:2.1.6]
... 4 more

 



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

[GitHub] ignite pull request #3058: Ignite 6927

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 6927



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

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

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

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


commit 0f92af4e44515608107495bd87f88bb50e1d6fa7
Author: Andrey Novikov <anovi...@gridgain.com>
Date:   2017-11-16T04:27:48Z

IGNITE-6927 Added Web Console direct install build.

commit 87bf305bfae3bb39c634468233e62a2a20c0a406
Author: Andrey Novikov <anovi...@gridgain.com>
Date:   2017-11-17T06:30:39Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-6927

commit b707a160eae67e263ec370d47ea08271eb135f4e
Author: Andrey Novikov <anovi...@gridgain.com>
Date:   2017-11-17T06:37:40Z

IGNITE-6927 Added build instructions.

commit 58b8be58e420bad9157503aff1035510ecb70283
Author: Andrey Novikov <anovi...@gridgain.com>
Date:   2017-11-17T06:52:19Z

IGNITE-6927 Added build instructions.

commit 5bdf0a012daa8a71143f4c76f1a195e381e4c73f
Author: Andrey Novikov <anovi...@gridgain.com>
Date:   2017-11-17T06:52:29Z

Version changed to 2.3.0-SNAPSHOT




---

[GitHub] ignite pull request #2926: IGNITE-6751 skipped upload ignite-dev-utils modul...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-6751 skipped upload ignite-dev-utils module into maven repository



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

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

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

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


commit ab97135ab0add6f97513dfebba0fa27f63dd22e8
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-25T11:53:52Z

IGNITE-6751 skipped upload ignite-dev-utils module into maven repository




---

[jira] [Created] (IGNITE-6751) Skip upload ignite-dev-utils module into maven repository

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6751:


 Summary: Skip upload ignite-dev-utils module into maven repository
 Key: IGNITE-6751
 URL: https://issues.apache.org/jira/browse/IGNITE-6751
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Skip upload ignite-dev-utils module into maven repository



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

[GitHub] ignite pull request #2920: IGNITE 6726

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE 6726



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

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

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

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


commit 9179d94933debb27b088b01843e333151232e1fc
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-24T14:47:25Z

IGNITE-6726 fixed sqlline licenses

commit fce8152a20ab5935af51cfe0c17a535a78f7dc85
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-24T14:48:48Z

IGNITE-6726 fixed sqlline licenses, fixed sqlline pom.xml




---

[jira] [Created] (IGNITE-6726) Licenses for Sqlline are missing

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6726:


 Summary: Licenses for Sqlline are missing
 Key: IGNITE-6726
 URL: https://issues.apache.org/jira/browse/IGNITE-6726
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Licenses for Sqlline are missing



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

[GitHub] ignite pull request #2911: IGNITE-6718 skipped upload sqlline and compatibil...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-6718 skipped upload sqlline and compatibility modules into  ma…

…ven central

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

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

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

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


commit c8f49fc6fa068fd202bcc73b05aef837086a855c
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-24T07:26:31Z

IGNITE-6718 skipped upload sqlline and compatibility modules into  maven 
central




---

[jira] [Created] (IGNITE-6718) Skip deploy sqlline and compatibility modules into repositiry

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6718:


 Summary: Skip deploy sqlline and compatibility modules into 
repositiry
 Key: IGNITE-6718
 URL: https://issues.apache.org/jira/browse/IGNITE-6718
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Skip deploy sqlline and compatibility modules into repositiry



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

[GitHub] ignite pull request #2902: IGNITE-6708 Remove ignite-compatibility from opti...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-6708 Remove ignite-compatibility from optional directory



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

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

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

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


commit 71a44b677a341d02a689ad82f2418d6c0f0f4d81
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-23T12:49:42Z

IGNITE-6708 Remove ignite-compatibility from optional directory




---

[GitHub] ignite pull request #2901: IGNITE-6706 Remove ignite-sqlline module from opt...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-6706 Remove ignite-sqlline module from optioanl directory



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

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

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

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


commit 678136b4932049b2b9b175005508157cd1b7def8
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-23T12:23:37Z

IGNITE-6706 Remove ignite-sqlline module from optioanl directory




---

[GitHub] ignite pull request #2879: IGNITE-6660 fixed Python Redis example (print sta...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-6660 fixed Python Redis example (print statements)



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

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

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

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


commit 5b2329fb1f75de4c41592868c58be92fa5a908da
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-18T15:16:19Z

IGNITE-6660 fixed Python Redis example (print statements)




---

[GitHub] ignite pull request #2868: IGNITE 6648

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE 6648



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

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

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

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


commit c7a7e5a71fbac0cae5b38532784ce8f162018a2a
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-17T11:04:35Z

IGNITE-6648 added ML javadoc group in parent/pom.xml

commit 1241391f6a7bbb66980c3215a3a755fb16a2ba55
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-17T11:36:02Z

Merge branch 'ignite-2.3' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-6648




---

Re: Adding sqlline tool to Apache Ignite project

[Oleg Ostanin]

New example build with sqlline:

https://ci.ignite.apache.org/viewLog.html?buildId=894407=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp


On Wed, Oct 11, 2017 at 1:00 AM, Denis Magda <dma...@apache.org> wrote:

> Oleg,
>
> Looks good to me. Please consider the notes left in the ticket. I want us
> to prepare a script for Windows, review the language for help notice and
> errors, put together documentation. Prachi will be able to help with the
> editing and documentation.
>
> —
> Denis
>
> > On Oct 9, 2017, at 10:13 AM, Oleg Ostanin <oosta...@gridgain.com> wrote:
> >
> > New build with fixed argument parsing:
> > https://ci.ignite.apache.org/viewLog.html?buildId=882282;
> tab=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> pareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp
> >
> > On Mon, Oct 9, 2017 at 5:38 PM, Denis Magda <dma...@gridgain.com> wrote:
> >
> >> I think it’s a must have for the ticket resolution.
> >>
> >> Denis
> >>
> >> On Monday, October 9, 2017, Anton Vinogradov <avinogra...@gridgain.com>
> >> wrote:
> >>
> >>> Any plans to have ignitesql.bat?
> >>>
> >>> On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin <oosta...@gridgain.com
> >>> <javascript:;>> wrote:
> >>>
> >>>> Another build with sqlline included:
> >>>> https://ci.ignite.apache.org/viewLog.html?buildId=881120;
> >>>> tab=artifacts=IgniteRelease_
> XxxFromMirrorIgniteRelease3Pre
> >>>> pareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp
> >>>>
> >>>> On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda <dma...@gridgain.com
> >>> <javascript:;>> wrote:
> >>>>
> >>>>> No more doubts on my side. +1 for Vladimir’s suggestion.
> >>>>>
> >>>>> Denis
> >>>>>
> >>>>> On Saturday, October 7, 2017, Dmitriy Setrakyan <
> >> dsetrak...@apache.org
> >>> <javascript:;>>
> >>>>> wrote:
> >>>>>
> >>>>>> I now tend to agree with Vladimir. We should always require that
> >> some
> >>>>>> address is specified. The help menu should clearly state how to
> >>> connect
> >>>>> to
> >>>>>> a localhost.
> >>>>>>
> >>>>>> D.
> >>>>>>
> >>>>>> On Sat, Oct 7, 2017 at 12:44 AM, Vladimir Ozerov <
> >>> voze...@gridgain.com <javascript:;>
> >>>>>> <javascript:;>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Denis,
> >>>>>>>
> >>>>>>> Default Ignite configuration uses multicast, this is why you do
> >> not
> >>>>> need
> >>>>>> to
> >>>>>>> change anything. Ignite node is always both a server (listens)
> >> and
> >>> a
> >>>>>> client
> >>>>>>> (connects).
> >>>>>>>
> >>>>>>> This will not work for ignitesql, as this is a client. And in
> >> real
> >>>>>>> deployments it will connect to remote nodes, not local. So the
> >>>> earlier
> >>>>> we
> >>>>>>> explain user how to do this, the better. This is why it should
> >> not
> >>>> work
> >>>>>> out
> >>>>>>> of the box connecting to 127.0.0.1. No magic for users please.
> >>>>>>>
> >>>>>>> This is what user will see (draft):
> >>>>>>>> ./ignitesql.sh
> >>>>>>>> Please specify the host: ignitesql.sh [host]; type --help for
> >>> more
> >>>>>>> information.
> >>>>>>>> ./ignitesql.sh 192.168.12.55
> >>>>>>>> Connected successfully.
> >>>>>>>
> >>>>>>> Again, specifying parameters manually is not poor UX. This is
> >>>> excellent
> >>>>>> UX,
> >>>>>>> as user learns on his own how to connect to a node in 1 minute.
> >>> Most
> >>>>>>> command line tools work this way.
> >>>>>>>
> >>>>>>> сб, 7 окт. 201

[jira] [Created] (IGNITE-6648) ML javadoc is missing in 2.2 binary release

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6648:


 Summary: ML javadoc is missing in 2.2 binary release   
 Key: IGNITE-6648
 URL: https://issues.apache.org/jira/browse/IGNITE-6648
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


ML javadoc is missing in binary releases.   




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

[GitHub] ignite pull request #2861: Ignite 5608

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 5608



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

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

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

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


commit c5d6decfaf4c8be907975531f7d7bd41dda2da4e
Author: dpavlov <dpav...@gridgain.com>
Date:   2017-10-04T06:46:16Z

IGNITE-6285 Enhance persistent store paths handling - Fixes #2775.

Signed-off-by: Alexey Goncharuk <alexey.goncha...@gmail.com>

commit 2e013fbe85da059580e97d57c15e9cbc92c0aa54
Author: dpavlov <dpav...@gridgain.com>
Date:   2017-10-04T12:05:48Z

IGNITE-6554 Atomic cache remove operations are not logged to WAL - Fixes 
#2800.

Signed-off-by: Alexey Goncharuk <alexey.goncha...@gmail.com>

commit 959bf853b1a77fa674ac8115fcf57c31feb0e6c0
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-04T14:35:50Z

Removed excluding ML from examples/src

(cherry picked from commit 78f77b1)

commit d4e5d4fd3e989b69f7bfa49986ee8f8d04cac62f
Author: tledkov-gridgain <tled...@gridgain.com>
Date:   2017-10-05T08:55:26Z

IGNITE-6529 JDBC: support column metadata 'nullable' property. This closes 
#2793.

commit 5e75aadba89761837fa0e87e36448086173a7e44
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-05T15:17:38Z

IGNITE-6561 added sqlline module

commit 2361eebffdf859e2cae278460e01e5f87b383f1f
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-06T10:02:54Z

IGNITE-6561 renamed script

commit 2d3726cf6a33a054724aa70b2d535b0e4b26ecb5
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-06T11:23:29Z

IGNITE-6561 edited script

commit b2127673104ed6525b2894fb702f467d74a84b32
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-06T13:17:09Z

IGNITE-6561 edited script parameters

commit 66521a62ddefa41b05f31c2ca7f2b7d2a3cb6616
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-07T08:50:03Z

IGNITE-6561 added header in pom

commit 58a5359643296ab778c5deb6f6f9d0e6933a5f65
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-09T09:14:21Z

IGNITE-6561 edited functions

commit 9f7c88a17b8ba6868287355cae1ff485d228a37a
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-09T11:40:30Z

IGNITE-6561 edited help

commit e2e45816ced6986dfc9ddf8fe54e17bf0ab8dd0f
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-09T12:04:45Z

IGNITE-6561 added jdbc link in help

commit 108d21c208777cb891186b5572855ab8e06cd94b
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-09T12:44:17Z

IGNITE-6561 added unknown argument handling

commit 6cddd085c643376a914be6745e319002689e6f10
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-09T16:53:38Z

    IGNITE-6561 edited parser

commit 401f21cda3ed8c88b63285224a46ab40aec7b390
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-09T17:07:15Z

IGNITE-6561 fixed error handling

commit 689a5d4961d923f6bc64450c19f7f59163b15873
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-10T08:28:52Z

IGNITE-6561 edited help

commit 6be46b003f855cac8aacd13de8438a7afd3d4142
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-10T10:35:49Z

IGNITE-6561 edited parser

commit d98b8f0af16e50d8ce5a1caed636c8dea3638b74
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-10T10:39:06Z

IGNITE-6561 edited parser options

commit 06184b346c65225b3edf55a66bde5b0fa1e89242
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-10T12:18:14Z

IGNITE-6561 edited parser and help

commit f45110280b6296c65d1dfcb332420187f3c9e702
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-10T12:52:10Z

IGNITE-6561 edited ignitesql.sh

commit f36f04c2517541e50d5dab0b769b269ce5e8299d
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-11T08:00:44Z

IGNITE-6561 added .bat script

commit e4aa9eb14ae188127e4d54ef457ea8b06099bf93
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-11T09:11:12Z

IGNITE-6561 merged master

commit b02fe6403616b4f3d09c8b108f2255d751e00fc0
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-13T08:55:55Z

IGNITE-6561 edited bat file

commit 9439b4610420a1874167f2f06f1df74d7497dbb3
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-13T09:05:28Z

IGNITE-6561 edited help

commit 1e8fa199c94526d24797780fe33379f29ab65fac
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-13T09:26:42Z

IGNITE-6561 edited 

Re: Adding sqlline tool to Apache Ignite project

[Oleg Ostanin]

New build with fixed argument parsing:
https://ci.ignite.apache.org/viewLog.html?buildId=882282=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,1esn4zrslm4po,-h8h0hn9vvvxp

On Mon, Oct 9, 2017 at 5:38 PM, Denis Magda <dma...@gridgain.com> wrote:

> I think it’s a must have for the ticket resolution.
>
> Denis
>
> On Monday, October 9, 2017, Anton Vinogradov <avinogra...@gridgain.com>
> wrote:
>
> > Any plans to have ignitesql.bat?
> >
> > On Mon, Oct 9, 2017 at 5:29 PM, Oleg Ostanin <oosta...@gridgain.com
> > <javascript:;>> wrote:
> >
> > > Another build with sqlline included:
> > > https://ci.ignite.apache.org/viewLog.html?buildId=881120;
> > > tab=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3Pre
> > > pareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp
> > >
> > > On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda <dma...@gridgain.com
> > <javascript:;>> wrote:
> > >
> > > > No more doubts on my side. +1 for Vladimir’s suggestion.
> > > >
> > > > Denis
> > > >
> > > > On Saturday, October 7, 2017, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > <javascript:;>>
> > > > wrote:
> > > >
> > > > > I now tend to agree with Vladimir. We should always require that
> some
> > > > > address is specified. The help menu should clearly state how to
> > connect
> > > > to
> > > > > a localhost.
> > > > >
> > > > > D.
> > > > >
> > > > > On Sat, Oct 7, 2017 at 12:44 AM, Vladimir Ozerov <
> > voze...@gridgain.com <javascript:;>
> > > > > <javascript:;>>
> > > > > wrote:
> > > > >
> > > > > > Denis,
> > > > > >
> > > > > > Default Ignite configuration uses multicast, this is why you do
> not
> > > > need
> > > > > to
> > > > > > change anything. Ignite node is always both a server (listens)
> and
> > a
> > > > > client
> > > > > > (connects).
> > > > > >
> > > > > > This will not work for ignitesql, as this is a client. And in
> real
> > > > > > deployments it will connect to remote nodes, not local. So the
> > > earlier
> > > > we
> > > > > > explain user how to do this, the better. This is why it should
> not
> > > work
> > > > > out
> > > > > > of the box connecting to 127.0.0.1. No magic for users please.
> > > > > >
> > > > > > This is what user will see (draft):
> > > > > > > ./ignitesql.sh
> > > > > > > Please specify the host: ignitesql.sh [host]; type --help for
> > more
> > > > > > information.
> > > > > > > ./ignitesql.sh 192.168.12.55
> > > > > > > Connected successfully.
> > > > > >
> > > > > > Again, specifying parameters manually is not poor UX. This is
> > > excellent
> > > > > UX,
> > > > > > as user learns on his own how to connect to a node in 1 minute.
> > Most
> > > > > > command line tools work this way.
> > > > > >
> > > > > > сб, 7 окт. 2017 г. в 7:12, Dmitriy Setrakyan <
> > dsetrak...@apache.org <javascript:;>
> > > > > <javascript:;>>:
> > > > > >
> > > > > > > How does the binding happen? Can we bind to everything, like we
> > do
> > > in
> > > > > > > Ignite?
> > > > > > >
> > > > > > > On Fri, Oct 6, 2017 at 2:51 PM, Denis Magda <dma...@apache.org
> > <javascript:;>
> > > > > <javascript:;>> wrote:
> > > > > > >
> > > > > > > > Thought over 127.0.0.1 as a default host once again. The bad
> > > thing
> > > > > > about
> > > > > > > > it is that the user gets a lengthy exception stack trace if
> > > Ignite
> > > > > is
> > > > > > > not
> > > > > > > > running locally and not a small error message.
> > > > > > > >
> > > > > > > > What are the other opinions on this? Do we want to follow
> > > > Vladimir’s
> > > > &

Re: Adding sqlline tool to Apache Ignite project

[Oleg Ostanin]

Another build with sqlline included:
https://ci.ignite.apache.org/viewLog.html?buildId=881120=artifacts=IgniteRelease_XxxFromMirrorIgniteRelease3PrepareVote#!1rrb2,-wpvx2aopzexz,1esn4zrslm4po,-h8h0hn9vvvxp

On Sun, Oct 8, 2017 at 5:11 PM, Denis Magda  wrote:

> No more doubts on my side. +1 for Vladimir’s suggestion.
>
> Denis
>
> On Saturday, October 7, 2017, Dmitriy Setrakyan 
> wrote:
>
> > I now tend to agree with Vladimir. We should always require that some
> > address is specified. The help menu should clearly state how to connect
> to
> > a localhost.
> >
> > D.
> >
> > On Sat, Oct 7, 2017 at 12:44 AM, Vladimir Ozerov  > >
> > wrote:
> >
> > > Denis,
> > >
> > > Default Ignite configuration uses multicast, this is why you do not
> need
> > to
> > > change anything. Ignite node is always both a server (listens) and a
> > client
> > > (connects).
> > >
> > > This will not work for ignitesql, as this is a client. And in real
> > > deployments it will connect to remote nodes, not local. So the earlier
> we
> > > explain user how to do this, the better. This is why it should not work
> > out
> > > of the box connecting to 127.0.0.1. No magic for users please.
> > >
> > > This is what user will see (draft):
> > > > ./ignitesql.sh
> > > > Please specify the host: ignitesql.sh [host]; type --help for more
> > > information.
> > > > ./ignitesql.sh 192.168.12.55
> > > > Connected successfully.
> > >
> > > Again, specifying parameters manually is not poor UX. This is excellent
> > UX,
> > > as user learns on his own how to connect to a node in 1 minute. Most
> > > command line tools work this way.
> > >
> > > сб, 7 окт. 2017 г. в 7:12, Dmitriy Setrakyan  > >:
> > >
> > > > How does the binding happen? Can we bind to everything, like we do in
> > > > Ignite?
> > > >
> > > > On Fri, Oct 6, 2017 at 2:51 PM, Denis Magda  > > wrote:
> > > >
> > > > > Thought over 127.0.0.1 as a default host once again. The bad thing
> > > about
> > > > > it is that the user gets a lengthy exception stack trace if Ignite
> > is
> > > > not
> > > > > running locally and not a small error message.
> > > > >
> > > > > What are the other opinions on this? Do we want to follow
> Vladimir’s
> > > > > suggestion forcing to set the host name/IP (port is optional) for
> the
> > > > sake
> > > > > of usability or leaver 127.0.0.1 as default?
> > > > >
> > > > > —
> > > > > Denis
> > > > >
> > > > > > On Oct 6, 2017, at 12:21 PM, Denis Magda  > > wrote:
> > > > > >
> > > > > >> But, we need to support “help” (-h, -help) argument listing all
> > the
> > > > > parameters accepted by the tools.
> > > > > >
> > > > > > Meant accepted by the ignitesql script only such as host name.
> > > > > >
> > > > > > —
> > > > > > Denis
> > > > > >
> > > > > >> On Oct 6, 2017, at 12:20 PM, Denis Magda  > > wrote:
> > > > > >>
> > > > > >> Really nice, could click through the getting started [1] in a
> > > minute!
> > > > > >>
> > > > > >> +1 to rename the script to “ignitesql”. Vladimir’s point makes
> > total
> > > > > sense.
> > > > > >>
> > > > > >> However, tend to disagree that the host has to be requested all
> > the
> > > > > times. We never request a configuration or host name for ignite.sh,
> > > visor
> > > > > or web agent scripts. I would follow this approach that’s excellent
> > for
> > > > dev
> > > > > time.
> > > > > >>
> > > > > >> But, we need to support “help” (-h, -help) argument listing all
> > the
> > > > > parameters accepted by the tools.
> > > > > >>
> > > > > >> Please consider our feedback and share the next build once it’s
> > > ready.
> > > > > >>
> > > > > >>
> > > > > >> [1] https://apacheignite-sql.readme.io/v2.1/docs/getting-
> started
> > <
> > > > > https://apacheignite-sql.readme.io/v2.1/docs/getting-started>
> > > > > >>
> > > > > >> —
> > > > > >> Denis
> > > > > >>
> > > > > >>> On Oct 6, 2017, at 9:04 AM, Anton Vinogradov <
> > > > avinogra...@gridgain.com >
> > > > > wrote:
> > > > > >>>
> > > > > >>> How about sqlconsole.sh or sqlcmd.sh ?
> > > > > >>>
> > > > > >>> On Fri, Oct 6, 2017 at 6:04 PM,  > > wrote:
> > > > > >>>
> > > > >  I like ignitesql.
> > > > > 
> > > > >  ⁣D.​
> > > > > 
> > > > >  On Oct 6, 2017, 4:49 PM, at 4:49 PM, Vladimir Ozerov <
> > > > > voze...@gridgain.com >
> > > > >  wrote:
> > > > > > Denis,
> > > > > >
> > > > > > Setting default host to 127.0.0.1 is bad idea, because it
> mean
> > > that
> > > > > in
> > > > > > practice users would have to change the script always.
> Instead,
> > > we
> > > > > > should
> > > > > > accept host name as argument. This is perfectly fine from
> > > usability
> > > > > > perspective, most tools work this way (i.e. throw 

[GitHub] ignite pull request #2801: removed excluding ML from examples/src

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

removed excluding ML from examples/src



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

$ git pull https://github.com/gridgain/apache-ignite remove-ml-excluding

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

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


commit 18b08782310d72b486c1d9d558041e958ea13cca
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-10-04T14:30:17Z

removed excluding ML from examples/src




---

Re: [DISCUSSION] Urgent Ignite bug fix release

[Oleg Ostanin]

We created the release build procedure on Apache CI server according to
this ticket:
https://issues.apache.org/jira/browse/IGNITE-5249
We also changed the checksum calculation method:
https://issues.apache.org/jira/browse/IGNITE-5817

Oleg

On Thu, Sep 7, 2017 at 9:49 AM, 李玉珏@163 <18624049...@163.com> wrote:

> Currently,the latest version is apache-ignite-fabric-2.1.0-bin.zip <
> http://mirrors.hust.edu.cn/apache//ignite/2.1.0/apache-igni
> te-fabric-2.1.0-bin.zip>.
>
> and in http://www.gridgainsystems.com/nexus/content/repositories/
> external/org/apache/ignite/ignite-core/
>
> the latest version is 2.1.4,
>
> As I understand it, add 1 on the version number of 2.1.4, and then publish
> it to the ignite main website to ensure that both versions are
> consistent,is it ok?
>
>
> 在 2017/9/1 下午6:57, Anton Vinogradov 写道:
>
>> Hi,
>>
>> Reasonable question, but I propose to keep 2.2 as a release version for
>> this urgent release, since we never released X.Y.Z version before.
>>
>> Let's discuss this at separate thread.
>> Could you please start it?
>>
>>
>> On Fri, Sep 1, 2017 at 4:49 AM, 李玉珏@163 <18624049...@163.com > 18624049...@163.com>> wrote:
>>
>> Since it's an urgent bugfix version, why can't the version number
>> be defined as 2.1.1 or 2.1.4?
>> After all, functionality has not increased and documents do not
>> require big changes.
>> If the version number is 2.1 series, there is no need to publish a
>> new version of the document.
>>
>>
>>
>> 在 2017/8/28 下午10:19, Anton Vinogradov 写道:
>>
>> Igniters,
>>
>> Seems 2.2 is a urgent bugfix release, so it should be based on
>> 2.1,
>> In this case all other issues with fixVersion = 2.2 should be
>> moved to 2.3.
>>
>> Currently, I see 835 issues with fixVersion = 2.2
>>
>> Seems we should have only 4 issues with fixVersion = 2.2:
>> - Change default max memory size from 80% to 20% -
>> https://issues.apache.org/jira/browse/IGNITE-6182
>> 
>> - Detecting low memory on ignite node startup -
>> https://issues.apache.org/jira/browse/IGNITE-6003
>> 
>> - Backport of improvements to checkpoint algorithm -
>> https://issues.apache.org/jira/browse/IGNITE-??
>> ??
>> - ML profile is missing in 2.1 binary release -
>> https://issues.apache.org/jira/browse/IGNITE-6193
>> 
>>
>> Please correct me in case I've missed something.
>>
>> Ivan,
>>
>> Let's include to the release tickets with optimizations of
>> checkpointing
>>
>> algorithm:
>>
>> https://issues.apache.org/jira/browse/IGNITE-6178
>> 
>> https://issues.apache.org/jira/browse/IGNITE-6033
>> 
>> https://issues.apache.org/jira/browse/IGNITE-5961
>> 
>> This will help users who are experiencing problems with
>> slow checkpoints.
>> Also, let's include
>> https://issues.apache.org/jira/browse/IGNITE-6183
>>  to
>>
>> soften "Ignite node crashed in the middle of checkpoint"
>> message as per
>> discussion <
>> http://apache-ignite-developers.2346864.n4.nabble.com/
>> Ignite-close-G-stop-name-true-Change-flag-cancel-to-false-td20473.html
>> > Ignite-close-G-stop-name-true-Change-flag-cancel-to-false-td20473.html>
>>
>> .
>>
>> All of these issues should have fixVersion 2.3.
>> Please create backport issue and link it to all necessary issues.
>>
>> P.s. I've created branch ignite-2.2, currently it equals to
>> ignite-2.1.
>>
>> On Mon, Aug 28, 2017 at 4:05 PM, Anton Vinogradov
>> >
>> wrote:
>>
>> Denis,
>>
>> BTW, who is considered to be the release manager of
>> this release?
>>
>> I'll do it.
>>
>> On Mon, Aug 28, 2017 at 3:54 PM, Seliverstov Igor
>> >
>> wrote:
>>
>> Ok, the check happens at the node start time or on
>> NODE_JOIN event
>>
>> in general it looks like:
>>
>> 1) calculate expected used memory = heap max + system
>> cache max + all
>> custom policies max + default policy size and put it
>>  

Re: New API docs look for Ignite.NET

[Oleg Ostanin]

Great news, thanks a lot!

On Tue, Sep 5, 2017 at 11:47 AM, Pavel Tupitsyn 
wrote:

> DocFX takes around 30 seconds on my machine.
>
> > if you already tried that
> Yes, everything is done on my side, see JIRA ticket [4] and preview [5]
> above.
>
> On Tue, Sep 5, 2017 at 11:45 AM, Ilya Suntsov 
> wrote:
>
> > Pavel, thanks!
> > It is the great news!
> > Looks like DocFX will save 30-40 min.
> >
> > 2017-09-05 11:16 GMT+03:00 Pavel Tupitsyn :
> >
> > > Igniters and users,
> > >
> > > Historically we've been using Doxygen [1] to generate .NET API
> > > documentation [2].
> > >
> > > Recently it became very slow on our code base (more than 30 minutes to
> > > generate), and I could not find any solution or tweak to fix that.
> Other
> > > issues include outdated looks and limited customization possibilities.
> > >
> > > I propose to replace it with DocFX [3] [4]:
> > > - Popular .NET Foundation project
> > > - Good looks and usability out of the box
> > > - Easy to set up
> > >
> > > Our docs will look like this: [5]
> > > Let me know if you have any objections or suggestions.
> > >
> > > Pavel
> > >
> > >
> > > [1] http://www.stack.nl/~dimitri/doxygen/
> > > [2] https://ignite.apache.org/releases/latest/dotnetdoc/index.html
> > > [3] https://dotnet.github.io/docfx/
> > > [4] https://issues.apache.org/jira/browse/IGNITE-6253
> > > [5] https://ptupitsyn.github.io/docfx-test/api/index.html
> > >
> >
> >
> >
> > --
> > Ilya Suntsov
> >
>

[GitHub] ignite pull request #2590: IGNITE-5817 Changed checksum calculation methods

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-5817 Changed checksum calculation methods

(cherry picked from commit 28fb8c8)

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

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

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

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


commit 67a9efc492091a3e1aa49d15e7db2eb8acce6f51
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-08-29T14:25:36Z

IGNITE-5817 Changed checksum calculation methods

(cherry picked from commit 28fb8c8)




---

[GitHub] ignite pull request #2585: Ignite 6237

[oleg-ostanin]

Github user oleg-ostanin closed the pull request at:

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


---

[GitHub] ignite pull request #2586: IGNITE-6237 created script for signing and upload...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-6237 created script for signing and uploading artifacts to rem…

…ote staging.

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

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

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

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


commit 991ca6af905bb2115ad39972a7aedfce27634a54
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-09-04T10:57:55Z

IGNITE-6237 created script for signing and uploading artifacts to remote 
staging.




---

[GitHub] ignite pull request #2585: Ignite 6237

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 6237



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

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

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

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


commit 737874f65d2aa143a79dd5f6b0d223e07a4eceee
Author: Ivan Rakov <ivan.glu...@gmail.com>
Date:   2017-08-29T10:24:20Z

IGNITE-6204 Backport optimizations of checkpointing algorithm into 2.2

commit abb675f3355494b1f1ab502718aa0ad2249cb78b
Author: Pavel Tupitsyn <ptupit...@apache.org>
Date:   2017-08-29T15:35:49Z

IGNITE-6204 Backport optimizations of checkpointing algorithm into 2.2 
(hotfix)

commit c06ceba8d014ded7519a37583cb8914f2ef064d9
Author: Oleg Ignatenko <oignate...@gridgain.com>
Date:   2017-08-30T11:15:32Z

IGNITE-6193 ML profile is missing in 2.1 binary release

commit d51171f11a566d0019b7482d990afc23eccc9f05
Author: Igor Seliverstov <gvvinbl...@gmail.com>
Date:   2017-09-01T09:48:38Z

IGNITE-6182 Change default max memory size from 80% to 20%

commit 991ca6af905bb2115ad39972a7aedfce27634a54
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-09-04T10:57:55Z

IGNITE-6237 created script for signing and uploading artifacts to remote 
staging.




---

[jira] [Created] (IGNITE-6237) Script for signing and uploading artifacts to remote staging.

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6237:


 Summary: Script for signing and uploading artifacts to remote 
staging.
 Key: IGNITE-6237
 URL: https://issues.apache.org/jira/browse/IGNITE-6237
 Project: Ignite
  Issue Type: Sub-task
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin
 Fix For: 2.2


Create script for signing artifacts in locally staged repository and uploading 
to the remote staging.



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

[GitHub] ignite pull request #2539: Ignite 5817 x

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 5817 x



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

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

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

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


commit 737874f65d2aa143a79dd5f6b0d223e07a4eceee
Author: Ivan Rakov <ivan.glu...@gmail.com>
Date:   2017-08-29T10:24:20Z

IGNITE-6204 Backport optimizations of checkpointing algorithm into 2.2

commit 28fb8c8ac5b6d2a24a2b394706bd5840623c5f83
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-08-29T14:25:36Z

IGNITE-5817 Changed checksum calculation methods




---
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-6209) Build Ignite.NET NuGet packages for Apache-Ignite release on CI

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6209:


 Summary: Build Ignite.NET NuGet packages for Apache-Ignite release 
on CI
 Key: IGNITE-6209
 URL: https://issues.apache.org/jira/browse/IGNITE-6209
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
 Fix For: 2.3


Create a suite to build Ignite.NET NuGet packages.



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

[jira] [Created] (IGNITE-6192) Ignite-ML does not compile

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6192:


 Summary: Ignite-ML does not compile
 Key: IGNITE-6192
 URL: https://issues.apache.org/jira/browse/IGNITE-6192
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin
Priority: Critical
 Fix For: 2.2


Ignite ML module does not compile with this error

[19:06:28]W: [Step 10/12] [ERROR] 
/data/teamcity/work/6256635eb5425b7f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/Blas.java:[21,32]
 package com.github.fommil.netlib does not exist
[19:06:28]W: [Step 10/12] [ERROR] 
/data/teamcity/work/6256635eb5425b7f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/Blas.java:[44,30]
 cannot find symbol
[19:06:28] : [Step 10/12]   symbol:   class BLAS

I've checked modules/ml/pom.xml file and I think the reason is line 

pom

in this dependency:


com.github.fommil.netlib
core
${netlibjava.version}
pom


I've double-checked three times on two different machines, after removing the 
line module does compile. 



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

Re: release procedure

[Oleg Ostanin]

Hello Igniters, I'd like to know which release option is preferred for the
community. I've done some research and some tests and I think the most
transparent way is option #3.

On Wed, Aug 9, 2017 at 11:28 PM, Konstantin Boudnik <c...@apache.org> wrote:

> There's also #4:
>  - providing an official environment, comprised of the toolchain,
> compilers, libs, etc,. The same environment (read "a container") could
> be used by an individual developer, RM, and/or in CI system for
> builds, tests, etc. And then you can have #3 pretty much for free!
>
> We are doing this in Bigtop for a much more complex environment, set
> of components and supported OS. I am sure it would be easy to do in
> Ignite.
> --
>   With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
>
>
> On Sun, Aug 6, 2017 at 5:37 AM, Oleg Ostanin <oosta...@gridgain.com>
> wrote:
> > Hi,
> >
> > I'd like to start a discussion about Apache Ignite release procedure.
> >
> > I'm working on ticket Ignite-5249 "The release build procedure should be
> > placed on the CI/CD server and available to run for the release
> engineer."
> >
> > https://issues.apache.org/jira/browse/IGNITE-5249
> >
> > Currently we have three options for release:
> >
> > 1. Release engineer can do all the necessary steps on his local machine.
> It
> > will require installing tons of soft like maven, doxigen, candle and so
> on.
> > Also building .net part of the project will require access to Windows OS.
> > Build steps will not be transparent for community. Environment will not
> be
> > the same for each release which can lead to the compatibility issues.
> >
> > 2. All the steps (including signing) can be done on the public continuous
> > integration server. Environment will be the same for each release, all
> the
> > steps will be transparent for community, but it will require uploading at
> > least one private gpg certificate on the server. This is the high
> security
> > risk and I'm mentioning this option only for the sake of completeness.
> >
> > 3. Building of the project can be performed on the public continuous
> > integration server and then artifacts can be downloaded on the local
> > machine and signed and deployed to the staging repository from that local
> > machine by running maven commands. No sharing of any credentials and
> > certificates will be needed, environment will be the same for each
> release,
> > all the steps will be transparent for community, artifacts created on the
> > CI server can be verified by check-sums after uploading to the
> repository.
> >
> > Please, let me know if you have any suggestion or any questions about
> > anything related.
>

[GitHub] ignite pull request #2498: IGNITE-6155 added new jvm flag for printing gc da...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-6155 added new jvm flag for printing gc date stamps



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

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

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

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


commit 03211d2f8f2e52886bfba7887beccc3dcc3e5f97
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-08-22T13:39:31Z

IGNITE-6155 added new jvm flag for printing gc date stamps




---
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-6155) Add GC Date Stamps to yardstick gc log

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6155:


 Summary: Add GC Date Stamps to yardstick gc log
 Key: IGNITE-6155
 URL: https://issues.apache.org/jira/browse/IGNITE-6155
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin


We need to add -XX:+PrintGCDateStamps to Jvm options in yardstick config files.



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

Re: .sha Release Distribution Policy

[Oleg Ostanin]

Hi, Denis

Yes, we have a ticket that already takes this into account:
https://issues.apache.org/jira/browse/IGNITE-5817
I think we can create both sha-256 and sha-512 checksums.

Best regards
Oleg

On Thu, Aug 17, 2017 at 1:51 AM, Denis Magda  wrote:

> Igniters, especially the release managers,
>
> Please consider these changes and recommendations for the next release. Do
> we have any ticket that already takes this into account?
>
> —
> Denis
>
> > Begin forwarded message:
> >
> > From: "Henk P. Penning" 
> > Subject: .sha Release Distribution Policy
> > Date: August 16, 2017 at 1:55:57 AM PDT
> > To: 
> > Reply-To: priv...@ignite.apache.org
> >
> > Hi PMC,
> >
> >   The Release Distribution Policy[1] changed regarding .sha files.
> >   See under "Cryptographic Signatures and Checksums Requirements" [2].
> >
> >  Old policy :
> >
> >-- use extension .sha for any SHA checksum (SHA-1, SHA-256, SHA-512)
> >
> >  New policy :
> >
> > -- use .sha1 for a SHA-1 checksum
> > -- use .sha256 for a SHA-256 checksum
> > -- use .sha512 for a SHA-512 checksum
> > -- [*] .sha should contain a SHA-1
> >
> >  Why this change ?
> >
> > -- Verifying a checksum under the old policy is/was not handy.
> >You have to inspect the .sha to find out which algorithm
> >should be used ; or try them all (SHA-1, SHA256, etc).
> >The new scheme avoids this ambiguity.
> > -- The last point[*] was only added for clarity. Most of the
> >old, stale .sha's contain a SHA-1. The relatively new .sha's
> >contain a SHA-512. The expectation is that the last catagory will
> >disappear, when active projects adapt to the 'new' convention.
> >
> >  Impact :
> >
> > -- Should be none ; many projects already use the 'new' convention.
> > -- Please ask your release managers to use .sha1, .sha256, .sha512
> >instead of the .sha extension.
> > -- Please fix your build-tools if you have any.
> >
> >  Piggyback :
> >
> > -- The policy requires a .md5 for every package ;
> >providing a .sha512 is recommended.
> >Since MD5 is essentially broken, it is to be expected that
> >in the future a .sha512 will be required.
> >Perhaps it is wize to start providing .sha512's
> >with your releases if you do not already do so.
> >
> > -- Visit http://mirror-vm.apache.org/checker/
> >to check the health of your /dist/-area ;
> >my stuff ; any feedback is most welcome.
> >
> >  Thanks ; regards,
> >
> >  Henk Penning
> >
> >   [1] http://www.apache.org/dev/release-distribution
> >   [2] http://www.apache.org/dev/release-distribution#sigs-and-sums
> >
> > 
> > Henk P. Penning ; apache.org infrastructure volunteer.
> > he...@apache.org ; http://mirror-vm.apache.org/~henkp/
>
>

release procedure

[Oleg Ostanin]

Hi,

I'd like to start a discussion about Apache Ignite release procedure.

I'm working on ticket Ignite-5249 "The release build procedure should be
placed on the CI/CD server and available to run for the release engineer."

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

Currently we have three options for release:

1. Release engineer can do all the necessary steps on his local machine. It
will require installing tons of soft like maven, doxigen, candle and so on.
Also building .net part of the project will require access to Windows OS.
Build steps will not be transparent for community. Environment will not be
the same for each release which can lead to the compatibility issues.

2. All the steps (including signing) can be done on the public continuous
integration server. Environment will be the same for each release, all the
steps will be transparent for community, but it will require uploading at
least one private gpg certificate on the server. This is the high security
risk and I'm mentioning this option only for the sake of completeness.

3. Building of the project can be performed on the public continuous
integration server and then artifacts can be downloaded on the local
machine and signed and deployed to the staging repository from that local
machine by running maven commands. No sharing of any credentials and
certificates will be needed, environment will be the same for each release,
all the steps will be transparent for community, artifacts created on the
CI server can be verified by check-sums after uploading to the repository.

Please, let me know if you have any suggestion or any questions about
anything related.

сhecksum algorythm

[Oleg Ostanin]

Hi,

We need to decide what сhecksum algorythm we should use for signing release
artifacts. Currently we use md5 and sha-1. sha-1 will be replaced by
sha-256 soon. Should we keep md5 or use only sha-256?

[jira] [Created] (IGNITE-5833) Changing maven goal from "install" to "package" for building from sources

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5833:


 Summary: Changing maven goal from "install" to "package" for 
building from sources
 Key: IGNITE-5833
 URL: https://issues.apache.org/jira/browse/IGNITE-5833
 Project: Ignite
  Issue Type: Bug
    Reporter: Oleg Ostanin
    Assignee: Oleg Ostanin


Currently we need to run 'mvn clean install' to build Apache Ignite from 
sources, otherwise we can not perform javadoc generation in the next build step 
in DEVNOTES.txt. We need to fix this issue before next release.



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

[GitHub] ignite pull request #2338: IGNITE-5807 added new profile to fix artifacts si...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-5807 added new profile to fix artifacts signing, edited DEVNOT…

…ES.txt

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

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

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

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


commit 6ea8a8262b847d4180e16567d5a8a0973bed6562
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-07-22T10:08:41Z

IGNITE-5807 added new profile to fix artifacts signing, edited DEVNOTES.txt




---
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 #2310: removed excluding ML sources from assembly file

[oleg-ostanin]

Github user oleg-ostanin closed the pull request at:

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


---
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-5807) Fixing signing artifacts

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5807:


 Summary: Fixing signing artifacts
 Key: IGNITE-5807
 URL: https://issues.apache.org/jira/browse/IGNITE-5807
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


We need to fix pom.xml file to allow gpg plugin to sign .zip artifacts after 
assembly.



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

Re: [VOTE] Apache Ignite 2.1.0 RC2

[Oleg Ostanin]

Hi Vyacheslav
Yes, we changed build procedure, please look in the DEVNOTES.txt.

On Wed, Jul 19, 2017 at 12:53 PM, Vyacheslav Daradur 
wrote:

> Hi guys.
> I've downloaded apache-ignite-2.1.0-src.zip, unpack it and execute "mvn
> package -DskipTests"
> result is succes, but the folder "target" in the root directory is empty.
> I've checked it at two diffrenet machines.
>
> Is logic of packaging changed in the release?
>
> 2017-07-19 12:36 GMT+03:00 Anton Vinogradov :
>
> > +1 (binding)
> >
> > On Wed, Jul 19, 2017 at 12:34 PM, Kozlov Maxim 
> > wrote:
> >
> > > +1
> > >
> > > > 19 июля 2017 г., в 11:33, Semyon Boikov 
> > > написал(а):
> > > >
> > > > +1 (binding)
> > > >
> > > > On Tue, Jul 18, 2017 at 9:45 PM, Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com> wrote:
> > > >
> > > >> +1 (binding)
> > > >>
> > > >> On Tue, Jul 18, 2017 at 11:40 AM, Denis Magda 
> > > wrote:
> > > >>
> > > >>> +1 (binding)
> > > >>>
> > > >>> —
> > > >>> Denis
> > > >>>
> > >  On Jul 17, 2017, at 9:42 PM, Vladimir Ozerov <
> voze...@gridgain.com>
> > > >>> wrote:
> > > 
> > >  Igniters!
> > > 
> > >  We have uploaded a 2.1.0 release candidate to
> > >  https://dist.apache.org/repos/dist/dev/ignite/2.1.0-rc2/
> > > 
> > >  Git tag name is
> > >  2.1.0-rc2
> > > 
> > >  This release includes the following changes:
> > > 
> > >  Ignite:
> > >  * Persistent cache store
> > >  * Added IgniteFuture.listenAsync() and IgniteFuture.chainAsync()
> > > >> mehtods
> > >  * Deprecated IgniteConfiguration.marshaller
> > >  * Updated Lucene dependency to version 5.5.2
> > >  * Machine learning: implemented K-means clusterization algorithm
> > > >>> optimized
> > >  for distributed storages
> > >  * SQL: CREATE TABLE and DROP TABLE commands support
> > >  * SQL: New thin JDBC driver
> > >  * SQL: Improved performance of certain queries, when affinity node
> > can
> > > >> be
> > >  calculated in advance
> > >  * SQL: Fixed return type of AVG() function
> > >  * SQL: BLOB type support added to thick JDBC driver
> > >  * SQL: Improved LocalDate, LocalTime and LocalDateTime support for
> > > >> Java 8
> > >  * SQL: Added FieldsQueryCursor interface to get fields metadata
> for
> > >  SqlFieldsQuery
> > >  * ODBC: Implemented DML statement batching
> > >  * Massive performance and stability improvements
> > > 
> > >  Ignite.NET:
> > >  * Automatic remote assembly loading
> > >  * NuGet-based standalone node deployment
> > >  * Added conditional data removeal via LINQ DeleteAll
> > >  * Added TimestampAttribute to control DateTime serialization mode
> > >  * Added local collections joins support to LINQ.
> > > 
> > >  Ignite CPP:
> > >  * Added Compute::Call and Compute::Broadcast methods
> > > 
> > >  Web Console:
> > >  * Implemented support for UNIQUE indexes for key fields on import
> > > model
> > >  from RDBMS
> > >  * Added option to show full stack trace on Queries screen
> > >  * Added PK alias generation on Models screen.
> > > 
> > >  Complete list of closed issues:
> > >  https://issues.apache.org/jira/issues/?jql=project%20%
> > > >> 3D%20IGNITE%20AND%
> > >  20fixVersion%20%3D%202.1%20AND%20(status%20%3D%
> > > >>> 20closed%20or%20status%20%3D%
> > >  20resolved)
> > > 
> > >  DEVNOTES
> > >  https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > >>> plain;f=DEVNOTES.txt;hb=refs/tags/2.1.0-rc2
> > > 
> > >  RELEASE NOTES
> > >  https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > >>> plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.1.0-rc2
> > > 
> > >  Please start voting.
> > > 
> > >  +1 - to accept Apache Ignite 2.1.0-rc2
> > >  0 - don't care either way
> > >  -1 - DO NOT accept Apache Ignite 2.1.0-rc2 (explain why)
> > > 
> > >  This vote will go for 72 hours.
> > > >>>
> > > >>>
> > > >>
> > >
> > > --
> > > Best Regards,
> > > Max K.
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
> --
> Best Regards, Vyacheslav D.
>

[GitHub] ignite pull request #2310: removed excluding ML sources from assembly file

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

removed excluding ML sources from assembly file



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2.1-include-ml-src

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

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


commit b19df5a6c6897d202e8f6a1181fc6de81015a140
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-07-17T13:01:31Z

removed excluding ML sources from assembly file




---
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 #2308: IGNITE-5762 skipping lgpl and examples deploy

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-5762 skipping lgpl and examples deploy



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

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

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

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


commit 937944861e78f67f1967fb3ce1fd8f7002d7247d
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-07-17T08:31:49Z

IGNITE-5762 skipping lgpl and examples deploy




---
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-5762) Skip deploy lgpl modules into repositiry

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5762:


 Summary: Skip deploy lgpl modules into repositiry
 Key: IGNITE-5762
 URL: https://issues.apache.org/jira/browse/IGNITE-5762
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Current build procedure is deploying lgpl-dependant modules into maven 
repository. This is Apache license violation and we need to skip deploying of 
these modules.



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

[GitHub] ignite pull request #2286: IGNITE-5740 created new benchmark for load transa...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

IGNITE-5740 created new benchmark for load transaction



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

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

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

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


commit 9502400e348c8a0184ff11a26a3c0ed893bb4d82
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-07-12T11:06:32Z

IGNITE-5740 created new benchmark for load transaction




---
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-5740) Transactional load benchmark

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5740:


 Summary: Transactional load benchmark
 Key: IGNITE-5740
 URL: https://issues.apache.org/jira/browse/IGNITE-5740
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


We need to create an additional benchmark to measure huge transactions time. 



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

[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)

Re: Suggested changes for Apache Ignite Release procedure

[Oleg Ostanin]

+1

I have assigned the ticket to myself and I did some preliminary
investigations in this matter. It seems to me the most complicated part
will be configuring tasks in such way that release commiter could use it
without exposing his credentials for Git, SVN and Maven. I suggest we
create an integration user for public Teamcity and grant him permissions to
commit and deploy in the repositories.

On Thu, Jun 8, 2017 at 6:10 AM, Denis Magda  wrote:

> +1
>
> > On Jun 7, 2017, at 3:40 AM, Sergey Kozlov  wrote:
> >
> > Hi, Igniters
> >
> > I'd start the discussion for following changes of release procedure.
> > As you may know we provided not source artifacts only but also a set of
> > binaries that makes using of the release is more friendly namely:
> > - binary farbic artifact
> > - binary hadoop artifact
> > - articats in Apache Ignite Maven repository
> > - artifacts for .Net/C++ in NuGet
> >
> > At the moment we release it by procedure [1] and some actions should be
> > processed manually (or some semi-automated way) by the release
> > lead  committer.
> >
> > I suggest to implement all such tasks on public teamcity as TC
> > configurations in a special project and allow to run them by the release
> > lead committer.
> >
> > Corresponding JIRA issue is [2]
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > [2] https://issues.apache.org/jira/browse/IGNITE-5249
> > --
> > Sergey Kozlov
>
>

[GitHub] ignite pull request #1954: ignite-gg-12199 added new variable CLEAN_WORK_DIR...

[oleg-ostanin]

Github user oleg-ostanin closed the pull request at:

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


---
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 #1954: ignite-gg-12199 added new variable CLEAN_WORK_DIR...

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

ignite-gg-12199 added new variable CLEAN_WORK_DIR in config files



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

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

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

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


commit 6c8c3cc5ad8e2c3e5c85a0ba4447978d185f2ec3
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-05-16T12:36:17Z

ignite-gg-12199 added new variable CLEAN_WORK_DIR in config files




---
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-5177) Failed javadoc generation for web-agent

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5177:


 Summary: Failed javadoc generation for web-agent
 Key: IGNITE-5177
 URL: https://issues.apache.org/jira/browse/IGNITE-5177
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin
Assignee: Andrey Novikov
 Fix For: 2.1


[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.7:run 
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException 
has occured: Execution failed due to: Class doesn't have description in file: 
/home/oostanin/gg/incubator-ignite/target/javadoc/core/org/apache/ignite/console/agent/handlers/ClusterListener.html
[ERROR] Class doesn't have description in file: 
/home/oostanin/gg/incubator-ignite/target/javadoc/core/org/apache/ignite/console/agent/handlers/DemoListener.html
[ERROR] Class doesn't have description in file: 
/home/oostanin/gg/incubator-ignite/target/javadoc/core/org/apache/ignite/console/agent/rest/RestExecutor.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1838: Ignite gg 11423 from20

[oleg-ostanin]

Github user oleg-ostanin closed the pull request at:

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


---
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 #1889: Ignite 5120

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 5120



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

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

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

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


commit 777078d377ba2f94b8f41086ecf0ad6056cdace5
Author: Alexey Kuznetsov <akuznet...@gridgain.com>
Date:   2017-04-29T14:01:47Z

IGNITE-5120 Fixed LGPL build.

commit 006a01bccc41095d660618d10845af63da4750a9
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-29T16:44:31Z

IGNITE-5120 fixed hibernate-core compilation




---
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 #1886: Ignite 2.0 temp for fix hibernate upload

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 2.0 temp for fix hibernate upload



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2.0-temp-for-fix-hibernate-upload

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

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


commit ab2a5b903b814d917065f3902169dbded8da334d
Author: Alexey Goncharuk <alexey.goncha...@gmail.com>
Date:   2017-04-28T07:38:58Z

ignite-2.0 - Fixed javadoc

commit 2872060897a9a6390d4c5cb7324a733f7b3cec56
Author: Alexey Kuznetsov <akuznet...@apache.org>
Date:   2017-04-28T07:56:53Z

IGNITE-4988 Code cleanup for ignite-2.0.

commit dc4b21efffbcc0e1f45570e89477f8a63c381d31
Author: Sergey Chugunov <sergey.chugu...@gmail.com>
Date:   2017-04-28T08:37:36Z

IGNITE-5024 code of two tests was fixed to pass new validation rules

commit 73d4e1152409026d96346fe5f5dfbc6194b97c9c
Author: Pavel Tupitsyn <ptupit...@apache.org>
Date:   2017-04-28T10:59:12Z

.NET: Cleanup unused SqlOnheapRowCacheSize mentions

commit 0e8e5dd99ec647a33f090cde02cf7cddf4a9b24c
Author: Alexey Kuznetsov <akuznet...@apache.org>
Date:   2017-04-28T11:06:41Z

IGNITE-4988 Fixed metadata import from RDBMS.

commit 6876eb3aa03ca49f124f869899adf49e40e73230
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-28T14:05:56Z

moved hibernate-core to lgpl profile




---
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 #1840: Ignite gg 11423 from20

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite gg 11423 from20



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

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

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

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


commit c2c843881e4c58877f0c482a7ec3a6a51b56b2d4
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-19T08:58:16Z

IGNITE-GG-11423 merged some changes from 1.9 to 2.0

commit 831aaa78ad400daf74047e3050dd5bf5f34d2700
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-19T12:59:49Z

IGNITE-GG-11423 fixed hibernate docs

commit 13410feac8131f5937341abc825dcde8849363f5
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-20T12:28:51Z

IGNITE-GG-11423 removed modules/benchmarks exclude

commit a0a200d806f90e7b37118531522d834a4fc6ad37
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-20T12:31:47Z

IGNITE-GG-11423 merged with ignite-2.0

commit df99233048dcb2dbf261cf6516546f7e718fb722
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-20T12:45:51Z

IGNITE-GG-11423 fixed conflict




---
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 #1838: Ignite gg 11423 from20

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite gg 11423 from20



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

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

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

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


commit d8480bdc22048ffadd3716f5d3a1f1c6a1797a0f
Author: devozerov <voze...@gridgain.com>
Date:   2017-04-18T12:24:19Z

IGNITE-4990: Removed deprecated properties from FileSystemConfiguration. 
This closes #1816.

commit eaf7350c64aabd98084df4eca337923c0208d085
Author: devozerov <voze...@gridgain.com>
Date:   2017-04-18T12:25:27Z

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

commit 3565e4ee60e705e0bc34a73045a8b9b161df2e6e
Author: Anton Vinogradov <a...@apache.org>
Date:   2017-04-18T12:32:29Z

Special profiles to set versions and check compilation across all modules

commit 862d8af0a27974eec76665a8d336a4be4c08361a
Author: Dmitriy Govorukhin <dmitriy.govoruk...@gmail.com>
Date:   2017-04-18T12:42:54Z

master - fixed SPI test

commit c4d81808c3cc002f1c71afb275361b728a84440b
Author: Dmitriy Govorukhin <dmitriy.govoruk...@gmail.com>
Date:   2017-04-18T12:44:15Z

master - Fixed jetty REST processor testIncorrectPut

commit 22580e19b7ae5d11b8c299e2b3d92f5c8b9f0e8c
Author: Alexander Belyak <alexandr.bel...@xored.com>
Date:   2017-04-18T11:56:50Z

IGNITE-4927 Write behind - add an option to skip write coalescing

Signed-off-by: nikolay_tikhonov <ntikho...@gridgain.com>

commit 58a8cb2579665c989ea9b08ebebf7b050f4d1405
Author: Pavel Tupitsyn <ptupit...@apache.org>
Date:   2017-04-18T13:01:49Z

.NET: Fix MessagingTest flakiness

commit 7038af4a7d976e59a7875b32b3ee3dfc1758908d
Author: Yury Babak <yba...@gridgain.com>
Date:   2017-04-18T13:46:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d78e071a7de1129838652e9f377ff73d3a84495d
Author: Yury Babak <yba...@gridgain.com>
Date:   2017-04-18T13:47:15Z

IGNITE-5000 Rename Ignite Math module to Ignite ML module
  added missed licenses
  renamed packages
  fixed wrong ml profile activation

commit d60cf53bbfae162ac96ec1525bcd1772b8249a79
Author: Konstantin Dudkov <kdud...@ya.ru>
Date:   2017-04-18T13:50:16Z

ignite-4982 Fixed GridIntList.

commit 43d6d7e7eb9eb146c48b843293849ac687ead216
Author: sboikov <sboi...@gridgain.com>
Date:   2017-04-18T13:50:45Z

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

commit 8ea9f83ce7f21f6ba50c0c644f62319f25b56ebd
Author: Alexey Kuznetsov <akuznet...@gridgain.com>
Date:   2017-04-18T13:39:58Z

master Fixed Visor tests.
(cherry picked from commit 36a6cd0)

commit 9e7421f261354b28119094b3b53b9490fd817b24
Author: devozerov <voze...@gridgain.com>
Date:   2017-04-18T14:04:43Z

Merge branch 'master' into ignite-2.0

commit 2edb935cbf87198993c403724e26efc655710c25
Author: devozerov <voze...@gridgain.com>
Date:   2017-04-18T14:11:34Z

IGNITE-4565: Implemented CREATE INDEX and DROP INDEX. This closes #1773. 
This closes #1804.

commit 9b21c85d6ec0cdbba8cbf2382559a8ef5a82e15c
Author: Alexey Goncharuk <alexey.goncha...@gmail.com>
Date:   2017-04-18T15:40:27Z

master - Mute test with a correct link

commit f82ed01807c80b36b7e361a5800ea131c1431c14
Author: Alexey Goncharuk <alexey.goncha...@gmail.com>
Date:   2017-04-18T15:40:55Z

master - Fix mvcc tests after CLOCK mode removal

commit 36e7e19830dc53c0ed02a0d83806b2cb5a7c7ce5
Author: Alexey Kuznetsov <akuznet...@apache.org>
Date:   2017-04-19T04:34:16Z

IGNITE-4988 Cleanup code.

commit c2c843881e4c58877f0c482a7ec3a6a51b56b2d4
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-19T08:58:16Z

    IGNITE-GG-11423 merged some changes from 1.9 to 2.0

commit 831aaa78ad400daf74047e3050dd5bf5f34d2700
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2017-04-19T12:59:49Z

IGNITE-GG-11423 fixed hibernate docs




---
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-4894) Yardstick-Cassandra

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-4894:


 Summary: Yardstick-Cassandra
 Key: IGNITE-4894
 URL: https://issues.apache.org/jira/browse/IGNITE-4894
 Project: Ignite
  Issue Type: New Feature
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin
Priority: Minor
 Fix For: 2.1


We need to create a project based on Yardstick framework which we could use to 
compare Ignite performance against Apache Cassandra.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-4822) Editing default JVM options defined in Ignite-Yardstick property files.

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-4822:


 Summary: Editing default JVM options defined in Ignite-Yardstick 
property files.
 Key: IGNITE-4822
 URL: https://issues.apache.org/jira/browse/IGNITE-4822
 Project: Ignite
  Issue Type: Improvement
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin
Priority: Minor
 Fix For: 2.0


We need to remove some predefined options from all the property files.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Apache Ignite 1.9

[Oleg Ostanin]

Denis,

please look at this version of build with Ignite-Yardstick:

https://drive.google.com/open?id=0B9teTzJ9iIvHbFFmcEtWWVpaRWs

I think the task is almost completed.

On Tue, Feb 14, 2017 at 12:21 PM, Anton Vinogradov <avinogra...@gridgain.com
> wrote:

> >
> > Can we push to 1.9 and then merge/rebase to master?
>
>
> Yes, that's *correct *too, but only *megre *should be used.
>
> On Tue, Feb 14, 2017 at 12:19 PM, Vladimir Ozerov <voze...@gridgain.com>
> wrote:
>
> > Can we push to 1.9 and then merge/rebase to master? It should be more
> > reliable than cherry-picking.
> >
> > On Tue, Feb 14, 2017 at 12:15 PM, Anton Vinogradov <
> > avinogra...@gridgain.com
> > > wrote:
> >
> > > Denis,
> > >
> > > Merge to the master first and then cherry-pick to 1.9 from there is a
> > > *correct
> > > *case.
> > >
> > > On Tue, Feb 14, 2017 at 5:24 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > > wrote:
> > >
> > > > Thanks, Denis!
> > > >
> > > > On Mon, Feb 13, 2017 at 5:49 PM, Denis Magda <dma...@apache.org>
> > wrote:
> > > >
> > > > > Well, merged Kubernetes integration to the master and cherry-picked
> > to
> > > > > 1.9. The docs and getting started for readme.io to be done soon.
> > > > >
> > > > > —
> > > > > Denis
> > > > >
> > > > > > On Feb 13, 2017, at 9:10 AM, Denis Magda <dma...@apache.org>
> > wrote:
> > > > > >
> > > > > > Do I merge to the master first and then cherry-pick to 1.9 from
> > > there?
> > > > > >
> > > > > > —
> > > > > > Denis
> > > > > >
> > > > > >> On Feb 13, 2017, at 8:21 AM, Anton Vinogradov <
> > > > avinogra...@gridgain.com>
> > > > > wrote:
> > > > > >>
> > > > > >> Igniters,
> > > > > >>
> > > > > >> We're starting release stabilization process.
> > > > > >> Branch 1.9 created and equals to master branch right now.
> > > > > >>
> > > > > >> Please make sure that your changes will be merged to both
> > branches:
> > > > > >> *ignite-1.9* and *master*.
> > > > > >>
> > > > > >> On Fri, Feb 10, 2017 at 4:53 PM, Sergey Kalashnikov <
> > > > > zkilling...@gmail.com>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> Anton,
> > > > > >>>
> > > > > >>> Here is the status for IGNITE-4523.
> > > > > >>> The work is completed, tests are OK.
> > > > > >>> Most of the changes were made by Alexey and were reviewed.
> > > > > >>> I only authored few last commits for which I would appreciate a
> > > > review.
> > > > > >>> The PR is https://github.com/apache/ignite/pull/1508
> > > > > >>>
> > > > > >>> Thank you
> > > > > >>> --
> > > > > >>> Sergey
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>> 2017-02-09 23:58 GMT+03:00 Denis Magda <dma...@apache.org>:
> > > > > >>>
> > > > > >>>> Anton,
> > > > > >>>>
> > > > > >>>> You can expect Kubernetes support from me in time.
> > > > > >>>>
> > > > > >>>> —
> > > > > >>>> Denis
> > > > > >>>>
> > > > > >>>>> On Feb 9, 2017, at 1:52 AM, Anton Vinogradov <a...@apache.org>
> > > > wrote:
> > > > > >>>>>
> > > > > >>>>> Igniters,
> > > > > >>>>>
> > > > > >>>>> We're on a half way to Ignite 1.9.
> > > > > >>>>> Development phase will be finished 17th of February.
> > > > > >>>>>
> > > > > >>>>> Here <https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > >>>> Apache+Ignite+1.9> is
> > > > > >>>>> a status page for upcoming rele

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Oleg Ostanin]

I'm sorry, there wasn't any problem with the build, it was local problem on
my machine.

On Fri, Feb 10, 2017 at 11:54 AM, Oleg Ostanin <oosta...@gridgain.com>
wrote:

> Hi.
>
> I just discovered that some functionality does not work correctly. I will
> present fixed version later.
>
> On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin <oosta...@gridgain.com>
> wrote:
>
>> https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c
>>
>> On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin <oosta...@gridgain.com>
>> wrote:
>>
>>> I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample
>>> benchmark configuration file to benchmark-sample.properties.
>>> Please look for the results:
>>>
>>>
>>> On Tue, Jan 31, 2017 at 9:18 PM, Denis Magda <dma...@apache.org> wrote:
>>>
>>>> Oleg,
>>>>
>>>> Thanks for the clarification.
>>>>
>>>> My opinion is that we should leave ‘modules/yardstick/README.txt’ and
>>>> ‘modules/yardstick/DEVNOTES.txt’ either unchanged or have only those
>>>> instructions there that explain how to build and run benchmarks from
>>>> ‘modules/yardstick’. This existing files can refer to the sources and
>>>> compiled benchmarks that are in Ignite binary releases but this should be a
>>>> couple of statements, no more.
>>>>
>>>> As for the instructions related to the sources and binaries added to
>>>> Ignite binaries, preferably they need to be added to auto-generated
>>>> README.txt. *Anton*, is it feasible to do?
>>>>
>>>> Finally, when apply the reviews notes please build and share Ignite
>>>> binaries with your patch. Want to see the new project structure and final
>>>> version of the instructions. Presently I can’t merge your changes due to
>>>> some conflicts.
>>>>
>>>> *Anton*, please review modifications in the build procedures.
>>>>
>>>> —
>>>> Denis
>>>>
>>>> > On Jan 31, 2017, at 3:12 AM, Oleg Ostanin <oosta...@gridgain.com>
>>>> wrote:
>>>> >
>>>> > Hi Denis,
>>>> >
>>>> > Yes, we have included Ignite Yardstick source files with its pom.xml
>>>> in
>>>> > Ignite binary release. "Building from standalone sources" is the
>>>> building
>>>> > instruction for these source files. "Building from Ignite Sources" is
>>>> the
>>>> > instruction for building Ignite Yardstick from `modules/yardstick` in
>>>> > Ignite source files.
>>>> >
>>>> > On Tue, Jan 31, 2017 at 3:31 AM, Denis Magda <dma...@apache.org>
>>>> wrote:
>>>> >
>>>> >> Hi Oleg,
>>>> >>
>>>> >> Great progress, thanks for keep driving this!
>>>> >>
>>>> >> I’ve left some minor notes in GitHub’s pull-request. I have the
>>>> following
>>>> >> questions aside:
>>>> >>
>>>> >> - What is the difference between "Building from standalone sources"
>>>> and
>>>> >> "Building from Ignite Sources"? In my understanding, a user downloads
>>>> >> Apache Ignite release that has all the sources locally.
>>>> >>
>>>> >> - I do remember we planned to add the benchmarks sources in a form
>>>> of a
>>>> >> ready to be used project with its own pom.xml (similar to examples).
>>>> Did
>>>> >> you put this task off?
>>>> >>
>>>> >> —
>>>> >> Denis
>>>> >>
>>>> >>> On Jan 27, 2017, at 2:13 AM, Oleg Ostanin <oosta...@gridgain.com>
>>>> wrote:
>>>> >>>
>>>> >>> Hi!
>>>> >>>
>>>> >>> I've changed the README.txt and DEVNOTES.txt files. Also added a
>>>> simple
>>>> >>> config file for quick and easy start. Please take a look at them
>>>> and tell
>>>> >>> me what you think.
>>>> >>>
>>>> >>> https://github.com/apache/ignite/pull/1471
>>>> >>>
>>>> >>> On Wed, Dec 28, 2016 at 8:59 AM, Ilya Suntsov <
>>>> isunt...@gridgain.com>
>>>> >> wrote:
>>>> &g

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Oleg Ostanin]

Hi.

I just discovered that some functionality does not work correctly. I will
present fixed version later.

On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin <oosta...@gridgain.com>
wrote:

> https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c
>
> On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin <oosta...@gridgain.com>
> wrote:
>
>> I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample
>> benchmark configuration file to benchmark-sample.properties.
>> Please look for the results:
>>
>>
>> On Tue, Jan 31, 2017 at 9:18 PM, Denis Magda <dma...@apache.org> wrote:
>>
>>> Oleg,
>>>
>>> Thanks for the clarification.
>>>
>>> My opinion is that we should leave ‘modules/yardstick/README.txt’ and
>>> ‘modules/yardstick/DEVNOTES.txt’ either unchanged or have only those
>>> instructions there that explain how to build and run benchmarks from
>>> ‘modules/yardstick’. This existing files can refer to the sources and
>>> compiled benchmarks that are in Ignite binary releases but this should be a
>>> couple of statements, no more.
>>>
>>> As for the instructions related to the sources and binaries added to
>>> Ignite binaries, preferably they need to be added to auto-generated
>>> README.txt. *Anton*, is it feasible to do?
>>>
>>> Finally, when apply the reviews notes please build and share Ignite
>>> binaries with your patch. Want to see the new project structure and final
>>> version of the instructions. Presently I can’t merge your changes due to
>>> some conflicts.
>>>
>>> *Anton*, please review modifications in the build procedures.
>>>
>>> —
>>> Denis
>>>
>>> > On Jan 31, 2017, at 3:12 AM, Oleg Ostanin <oosta...@gridgain.com>
>>> wrote:
>>> >
>>> > Hi Denis,
>>> >
>>> > Yes, we have included Ignite Yardstick source files with its pom.xml in
>>> > Ignite binary release. "Building from standalone sources" is the
>>> building
>>> > instruction for these source files. "Building from Ignite Sources" is
>>> the
>>> > instruction for building Ignite Yardstick from `modules/yardstick` in
>>> > Ignite source files.
>>> >
>>> > On Tue, Jan 31, 2017 at 3:31 AM, Denis Magda <dma...@apache.org>
>>> wrote:
>>> >
>>> >> Hi Oleg,
>>> >>
>>> >> Great progress, thanks for keep driving this!
>>> >>
>>> >> I’ve left some minor notes in GitHub’s pull-request. I have the
>>> following
>>> >> questions aside:
>>> >>
>>> >> - What is the difference between "Building from standalone sources"
>>> and
>>> >> "Building from Ignite Sources"? In my understanding, a user downloads
>>> >> Apache Ignite release that has all the sources locally.
>>> >>
>>> >> - I do remember we planned to add the benchmarks sources in a form of
>>> a
>>> >> ready to be used project with its own pom.xml (similar to examples).
>>> Did
>>> >> you put this task off?
>>> >>
>>> >> —
>>> >> Denis
>>> >>
>>> >>> On Jan 27, 2017, at 2:13 AM, Oleg Ostanin <oosta...@gridgain.com>
>>> wrote:
>>> >>>
>>> >>> Hi!
>>> >>>
>>> >>> I've changed the README.txt and DEVNOTES.txt files. Also added a
>>> simple
>>> >>> config file for quick and easy start. Please take a look at them and
>>> tell
>>> >>> me what you think.
>>> >>>
>>> >>> https://github.com/apache/ignite/pull/1471
>>> >>>
>>> >>> On Wed, Dec 28, 2016 at 8:59 AM, Ilya Suntsov <isunt...@gridgain.com
>>> >
>>> >> wrote:
>>> >>>
>>> >>>> Denis,
>>> >>>>
>>> >>>> I think we can remove all configs except:
>>> >>>>
>>> >>>> benchmark-multicast.properties
>>> >>>>
>>> >>>> benchmark.properties
>>> >>>>
>>> >>>> ignite-base-config.xml
>>> >>>>
>>> >>>> ignite-localhost-config.xml
>>> >>>>
>>> >>>> ignite-multicast-config.xml
>>>

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Oleg Ostanin]

https://drive.google.com/open?id=0B9teTzJ9iIvHckl6eVQ3N0R4a3c

On Fri, Feb 10, 2017 at 12:43 AM, Oleg Ostanin <oosta...@gridgain.com>
wrote:

> I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample
> benchmark configuration file to benchmark-sample.properties.
> Please look for the results:
>
>
> On Tue, Jan 31, 2017 at 9:18 PM, Denis Magda <dma...@apache.org> wrote:
>
>> Oleg,
>>
>> Thanks for the clarification.
>>
>> My opinion is that we should leave ‘modules/yardstick/README.txt’ and
>> ‘modules/yardstick/DEVNOTES.txt’ either unchanged or have only those
>> instructions there that explain how to build and run benchmarks from
>> ‘modules/yardstick’. This existing files can refer to the sources and
>> compiled benchmarks that are in Ignite binary releases but this should be a
>> couple of statements, no more.
>>
>> As for the instructions related to the sources and binaries added to
>> Ignite binaries, preferably they need to be added to auto-generated
>> README.txt. *Anton*, is it feasible to do?
>>
>> Finally, when apply the reviews notes please build and share Ignite
>> binaries with your patch. Want to see the new project structure and final
>> version of the instructions. Presently I can’t merge your changes due to
>> some conflicts.
>>
>> *Anton*, please review modifications in the build procedures.
>>
>> —
>> Denis
>>
>> > On Jan 31, 2017, at 3:12 AM, Oleg Ostanin <oosta...@gridgain.com>
>> wrote:
>> >
>> > Hi Denis,
>> >
>> > Yes, we have included Ignite Yardstick source files with its pom.xml in
>> > Ignite binary release. "Building from standalone sources" is the
>> building
>> > instruction for these source files. "Building from Ignite Sources" is
>> the
>> > instruction for building Ignite Yardstick from `modules/yardstick` in
>> > Ignite source files.
>> >
>> > On Tue, Jan 31, 2017 at 3:31 AM, Denis Magda <dma...@apache.org> wrote:
>> >
>> >> Hi Oleg,
>> >>
>> >> Great progress, thanks for keep driving this!
>> >>
>> >> I’ve left some minor notes in GitHub’s pull-request. I have the
>> following
>> >> questions aside:
>> >>
>> >> - What is the difference between "Building from standalone sources" and
>> >> "Building from Ignite Sources"? In my understanding, a user downloads
>> >> Apache Ignite release that has all the sources locally.
>> >>
>> >> - I do remember we planned to add the benchmarks sources in a form of a
>> >> ready to be used project with its own pom.xml (similar to examples).
>> Did
>> >> you put this task off?
>> >>
>> >> —
>> >> Denis
>> >>
>> >>> On Jan 27, 2017, at 2:13 AM, Oleg Ostanin <oosta...@gridgain.com>
>> wrote:
>> >>>
>> >>> Hi!
>> >>>
>> >>> I've changed the README.txt and DEVNOTES.txt files. Also added a
>> simple
>> >>> config file for quick and easy start. Please take a look at them and
>> tell
>> >>> me what you think.
>> >>>
>> >>> https://github.com/apache/ignite/pull/1471
>> >>>
>> >>> On Wed, Dec 28, 2016 at 8:59 AM, Ilya Suntsov <isunt...@gridgain.com>
>> >> wrote:
>> >>>
>> >>>> Denis,
>> >>>>
>> >>>> I think we can remove all configs except:
>> >>>>
>> >>>> benchmark-multicast.properties
>> >>>>
>> >>>> benchmark.properties
>> >>>>
>> >>>> ignite-base-config.xml
>> >>>>
>> >>>> ignite-localhost-config.xml
>> >>>>
>> >>>> ignite-multicast-config.xml
>> >>>>
>> >>>> 2016-12-28 2:49 GMT+03:00 Denis Magda <dma...@apache.org>:
>> >>>>
>> >>>>> I would have only those configs that are useful. Ilya Suntsov,
>> basing
>> >> on
>> >>>>> your experience, please suggest which configs makes sense to include
>> >> into
>> >>>>> every Ignite release.
>> >>>>>
>> >>>>> Oleg, also please note that community decided to include not only
>> the
>> >>>>> benchmarking binaries but the sources as well into ever

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Oleg Ostanin]

I've fixed README.txt and created new DEVNOTES.txt. Also renamed sample
benchmark configuration file to benchmark-sample.properties.
Please look for the results:


On Tue, Jan 31, 2017 at 9:18 PM, Denis Magda <dma...@apache.org> wrote:

> Oleg,
>
> Thanks for the clarification.
>
> My opinion is that we should leave ‘modules/yardstick/README.txt’ and
> ‘modules/yardstick/DEVNOTES.txt’ either unchanged or have only those
> instructions there that explain how to build and run benchmarks from
> ‘modules/yardstick’. This existing files can refer to the sources and
> compiled benchmarks that are in Ignite binary releases but this should be a
> couple of statements, no more.
>
> As for the instructions related to the sources and binaries added to
> Ignite binaries, preferably they need to be added to auto-generated
> README.txt. *Anton*, is it feasible to do?
>
> Finally, when apply the reviews notes please build and share Ignite
> binaries with your patch. Want to see the new project structure and final
> version of the instructions. Presently I can’t merge your changes due to
> some conflicts.
>
> *Anton*, please review modifications in the build procedures.
>
> —
> Denis
>
> > On Jan 31, 2017, at 3:12 AM, Oleg Ostanin <oosta...@gridgain.com> wrote:
> >
> > Hi Denis,
> >
> > Yes, we have included Ignite Yardstick source files with its pom.xml in
> > Ignite binary release. "Building from standalone sources" is the building
> > instruction for these source files. "Building from Ignite Sources" is the
> > instruction for building Ignite Yardstick from `modules/yardstick` in
> > Ignite source files.
> >
> > On Tue, Jan 31, 2017 at 3:31 AM, Denis Magda <dma...@apache.org> wrote:
> >
> >> Hi Oleg,
> >>
> >> Great progress, thanks for keep driving this!
> >>
> >> I’ve left some minor notes in GitHub’s pull-request. I have the
> following
> >> questions aside:
> >>
> >> - What is the difference between "Building from standalone sources" and
> >> "Building from Ignite Sources"? In my understanding, a user downloads
> >> Apache Ignite release that has all the sources locally.
> >>
> >> - I do remember we planned to add the benchmarks sources in a form of a
> >> ready to be used project with its own pom.xml (similar to examples). Did
> >> you put this task off?
> >>
> >> —
> >> Denis
> >>
> >>> On Jan 27, 2017, at 2:13 AM, Oleg Ostanin <oosta...@gridgain.com>
> wrote:
> >>>
> >>> Hi!
> >>>
> >>> I've changed the README.txt and DEVNOTES.txt files. Also added a simple
> >>> config file for quick and easy start. Please take a look at them and
> tell
> >>> me what you think.
> >>>
> >>> https://github.com/apache/ignite/pull/1471
> >>>
> >>> On Wed, Dec 28, 2016 at 8:59 AM, Ilya Suntsov <isunt...@gridgain.com>
> >> wrote:
> >>>
> >>>> Denis,
> >>>>
> >>>> I think we can remove all configs except:
> >>>>
> >>>> benchmark-multicast.properties
> >>>>
> >>>> benchmark.properties
> >>>>
> >>>> ignite-base-config.xml
> >>>>
> >>>> ignite-localhost-config.xml
> >>>>
> >>>> ignite-multicast-config.xml
> >>>>
> >>>> 2016-12-28 2:49 GMT+03:00 Denis Magda <dma...@apache.org>:
> >>>>
> >>>>> I would have only those configs that are useful. Ilya Suntsov, basing
> >> on
> >>>>> your experience, please suggest which configs makes sense to include
> >> into
> >>>>> every Ignite release.
> >>>>>
> >>>>> Oleg, also please note that community decided to include not only the
> >>>>> benchmarking binaries but the sources as well into every Apache
> Ignite
> >>>>> release. I’ve update the ticket before. Hope you followed the
> >> discussion
> >>>> ;)
> >>>>> https://issues.apache.org/jira/browse/IGNITE-4212?
> >>>>> focusedCommentId=15765151=com.atlassian.jira.
> >>>>> plugin.system.issuetabpanels:comment-tabpanel#comment-15765151
> >>>>>
> >>>>> —
> >>>>> Denis
> >>>>>
> >>>>>> On Dec 27, 2016, at 5:35 AM, Oleg Ostanin <oosta...@gridgain.com>
> >&g

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Oleg Ostanin]

Denis,

Yes, the same identical README.txt as in the pull request will be placed in
both benchmarks binaries and Ignite Yardstick module.

I've also created two DEVNOTES.txt with related building instructions.

On Wed, Feb 1, 2017 at 10:31 PM, Denis Magda <dma...@apache.org> wrote:

> Anton,
>
> I’m absolutely fine to make a single README if its instructions will be
> identical for benchmarks binaries delivered in Ignite binary releases and
> assembled with yardstick module directly. Oleg, is it feasible?
>
> If to skip auto-generation idea then DEVNOTES split suggested by you is
> the only option.
>
> —
> Denis
>
> > On Feb 1, 2017, at 1:45 AM, Anton Vinogradov <avinogra...@gridgain.com>
> wrote:
> >
> > Denis,
> >
> > I don't like autogeneration.
> >
> > In my view, we have to keep one README and ret rid of "Installation
> > instructions" inside it.
> > README should explain how to work with assembled yardstick. So, same
> README
> > will be uses at sources and inside release assembly.
> >
> > Also we have to have to split DEVNOTES to DEVNOTES and
> DEVNOTES.standalone,
> > to explain how to assembly yardstick from sources.
> >
> > Thoughts?
> >
> > On Tue, Jan 31, 2017 at 9:18 PM, Denis Magda <dma...@apache.org> wrote:
> >
> >> Oleg,
> >>
> >> Thanks for the clarification.
> >>
> >> My opinion is that we should leave ‘modules/yardstick/README.txt’ and
> >> ‘modules/yardstick/DEVNOTES.txt’ either unchanged or have only those
> >> instructions there that explain how to build and run benchmarks from
> >> ‘modules/yardstick’. This existing files can refer to the sources and
> >> compiled benchmarks that are in Ignite binary releases but this should
> be a
> >> couple of statements, no more.
> >>
> >> As for the instructions related to the sources and binaries added to
> >> Ignite binaries, preferably they need to be added to auto-generated
> >> README.txt. *Anton*, is it feasible to do?
> >>
> >> Finally, when apply the reviews notes please build and share Ignite
> >> binaries with your patch. Want to see the new project structure and
> final
> >> version of the instructions. Presently I can’t merge your changes due to
> >> some conflicts.
> >>
> >> *Anton*, please review modifications in the build procedures.
> >>
> >> —
> >> Denis
> >>
> >>> On Jan 31, 2017, at 3:12 AM, Oleg Ostanin <oosta...@gridgain.com>
> wrote:
> >>>
> >>> Hi Denis,
> >>>
> >>> Yes, we have included Ignite Yardstick source files with its pom.xml in
> >>> Ignite binary release. "Building from standalone sources" is the
> building
> >>> instruction for these source files. "Building from Ignite Sources" is
> the
> >>> instruction for building Ignite Yardstick from `modules/yardstick` in
> >>> Ignite source files.
> >>>
> >>> On Tue, Jan 31, 2017 at 3:31 AM, Denis Magda <dma...@apache.org>
> wrote:
> >>>
> >>>> Hi Oleg,
> >>>>
> >>>> Great progress, thanks for keep driving this!
> >>>>
> >>>> I’ve left some minor notes in GitHub’s pull-request. I have the
> >> following
> >>>> questions aside:
> >>>>
> >>>> - What is the difference between "Building from standalone sources"
> and
> >>>> "Building from Ignite Sources"? In my understanding, a user downloads
> >>>> Apache Ignite release that has all the sources locally.
> >>>>
> >>>> - I do remember we planned to add the benchmarks sources in a form of
> a
> >>>> ready to be used project with its own pom.xml (similar to examples).
> Did
> >>>> you put this task off?
> >>>>
> >>>> —
> >>>> Denis
> >>>>
> >>>>> On Jan 27, 2017, at 2:13 AM, Oleg Ostanin <oosta...@gridgain.com>
> >> wrote:
> >>>>>
> >>>>> Hi!
> >>>>>
> >>>>> I've changed the README.txt and DEVNOTES.txt files. Also added a
> simple
> >>>>> config file for quick and easy start. Please take a look at them and
> >> tell
> >>>>> me what you think.
> >>>>>
> >>>>> https://github.com/apache/ignite/pull/1471
> >

Re: How to improve SQL testing

[Oleg Ostanin]

Hi,

If there are no objections, I'd like implement this feature.

Oleg

On Tue, Jan 31, 2017 at 12:07 AM, Denis Magda  wrote:

> Hi,
>
> That’s true that the utility/testing framework needs to be as flexible as
> possible. If the community can’t reuse an existing one let’s make it up.
>
> As for VoltDB SQL Coverage Suite, if it’s Python based then can we
> implement those Python APIs directly calling Ignite.C++?
>
> —
> Denis
>
> > On Jan 30, 2017, at 4:39 AM, Sergey Kozlov  wrote:
> >
> > Alexey, I suppose that it's a hard way to do that and at least see a few
> > disadvantages below:
> >
> > 1. The VoltDB has no multithreaded mode. It means huge execution time
> > consumption (say we talk about thousands statement multiplied on caches
> > count, it's the millions of queries).
> > 2. We should add support of Ignite.
> > 3. We should add support of H2 as base engine for us (MySQL/Postgress
> have
> > less priority)
> > 4. They run it under Jenkins so we need to integrate it with TC somehow.
> >
> > From my standpoint better to make the utility in Ignite than spending
> time
> > and efforts to adopt an existing tool. At least we have good (or even
> best)
> > Java experts/developers in community and the task doesn't look a complex
> > one.
> >
> >
> > On Mon, Jan 30, 2017 at 2:58 PM, Alexey Kuznetsov  >
> > wrote:
> >
> >> Sergey,
> >>
> >> Could we use http://www.jython.org/ to make it works as-is?
> >>
> >> On Mon, Jan 30, 2017 at 6:06 PM, Sergey Kozlov 
> >> wrote:
> >>
> >>> Hi
> >>>
> >>> Hi reviewed the links below (thanks for Vova Ozerov to pointing me) and
> >>> found that the provided solution is really excellent!
> >>> Unfortunately we can't use it as is (from my standpoint) due lacks of
> >>> Python support in Ignite but we can re-use that idea for Ignite and
> make
> >>> SQL combinations coverage significantly better.
> >>>
> >>> I filed the ticket IGNITE-4627 Tester for SQL functionality
> >>> 
> >>>
> >>> Please share your thoughts and ideas.
> >>>
> >>> [1] https://www.voltdb.com/blog/testing-voltdb-sqlcoverage
> >>> [2] https://github.com/VoltDB/voltdb/tree/master/tests/sqlcoverage
> >>>
> >>> --
> >>> Sergey Kozlov
> >>> www.gridgain.com
> >>>
> >>
> >>
> >>
> >> --
> >> Alexey Kuznetsov
> >>
> >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
>
>

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Oleg Ostanin]

I mean removing those configs from binary assembly, not from repository.

On Tue, Dec 27, 2016 at 4:28 PM, Oleg Ostanin <oosta...@gridgain.com> wrote:

> Hello Igniters.
> I think it would be better to remove some configuration files from
> benchmarks/config:
>
> ignite-base-load-config.xml
> ignite-cache-load-config.xml
> ignite-failover-base-config.xml
> ignite-failover-localhost-config.xml
> benchmark-cache-load.properties
> benchmark-cache-load-win.properties
> benchmark-failover.properties
>
> because those configs do not relate to any of performance tests.
>
> On Tue, Dec 20, 2016 at 11:24 PM, Denis Magda <dma...@apache.org> wrote:
>
>> Summarized the discussion updating the ticket
>> https://issues.apache.org/jira/browse/IGNITE-4212# <
>> https://issues.apache.org/jira/browse/IGNITE-4212#>
>>
>> —
>> Denis
>>
>> > On Dec 19, 2016, at 12:26 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
>> wrote:
>> >
>> > Sergey,
>> >
>> > I am not sure I like "extras". I am voting for "benchmarks" folder right
>> > under the root folder.
>> >
>> > D.
>> >
>> > On Mon, Dec 19, 2016 at 12:07 PM, Sergey Kozlov <skoz...@gridgain.com>
>> > wrote:
>> >
>> >> Formatting has cut lines:
>> >>
>> >> — apache_ignite_root_folder
>> >>  — bin
>> >>  — examples
>> >>  — extras
>> >>   — benchmarks
>> >> — bin
>> >> — src (benchmarks sources with pom.xml)
>> >> — config
>> >> — libs (compiled benchmarks)
>> >>
>> >>
>> >>
>> >> On Mon, Dec 19, 2016 at 11:04 PM, Sergey Kozlov <skoz...@gridgain.com>
>> >> wrote:
>> >>
>> >>> Denis,
>> >>>
>> >>> Mostly yes. But I look ahead and think that we may include more
>> things in
>> >>> future than yardstick only. It's why I suggest something like that:
>> >>> — apache_ignite_root_folder
>> >>>— bin
>> >>>— examples
>> >>>— extras
>> >>>— benchmarks
>> >>>— bin
>> >>>— src (benchmarks sources with pom.xml)
>> >>>— config
>> >>>— libs (compiled benchmarks)
>> >>>
>> >>> On Mon, Dec 19, 2016 at 10:15 PM, Denis Magda <dma...@apache.org>
>> wrote:
>> >>>
>> >>>> Well, if to refer to Dmitriy suggestion we can have the following
>> >>>> structure
>> >>>>
>> >>>> — apache_ignite_root_folder
>> >>>>— examples
>> >>>>— bin
>> >>>>— benchmarks
>> >>>>— bin
>> >>>>— src (benchmarks sources with pom.xml)
>> >>>>— config
>> >>>>— libs (compiled benchmarks)
>> >>>>
>> >>>> Sergey, will it cover all the use case you’ve met previously?
>> >>>>
>> >>>> —
>> >>>> Denis
>> >>>>
>> >>>>> On Dec 19, 2016, at 9:59 AM, Sergey Kozlov <skoz...@gridgain.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> Yardstick requires own scripts/configurations (/bin, /config, /libs)
>> >> and
>> >>>>> creates work/logs directory under yardstick root. "libs/optional" is
>> >> for
>> >>>>> optional modules but in general we can't say that for Yardstick.
>> Also
>> >> it
>> >>>>> may break the current user understanding of "libs/optional"
>> directory
>> >> as
>> >>>>> place for additonal functionality activated by copying in "libs".
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Mon, Dec 19, 2016 at 7:53 PM, Dmitriy Setrakyan <
>> >>>> dsetrak...@apache.org>
>> >>>>> wrote:
>> >>>>>
>> >>>>>> I would be against using libs/optional or libs/ folder for anything
>> >>>>>> benchmark related. I am also against adding any yardstick libraries
>> >>>> without
>> >>>>>> providing code.
>> >&g

Re: IGNITE-4212 (Ignite Benchmarking Simplification and Automation)

[Oleg Ostanin]

;>> wrote:
> >>>>>>
> >>>>>>> Actually, “libs/optional” is already a kind of extra for me. Why do
> >> we
> >>>>>>> need this new folder if “libs/optional” semantic works well?
> >>>>>>>
> >>>>>>> Is there anyone else who is concerned about “libs/optional”? If
> >>>> there’re
> >>>>>>> not, I would agree on this and get down to the implementation.
> >>>>>>>
> >>>>>>> —
> >>>>>>> Denis
> >>>>>>>
> >>>>>>>> On Dec 19, 2016, at 1:10 AM, Sergey Kozlov <skoz...@gridgain.com>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Hi
> >>>>>>>>
> >>>>>>>> What's about to introduce the new root folder called 'extras' with
> >>>>>>>> subfolder 'ignite-yardstick' and put there yardstick binaries?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Sun, Dec 18, 2016 at 10:02 PM, Denis Magda <dma...@apache.org>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Dmitriy,
> >>>>>>>>>
> >>>>>>>>> Please have a look at IGNITE-4212 description (
> >>>>>>> https://issues.apache.org/
> >>>>>>>>> jira/browse/IGNITE-4212).
> >>>>>>>>>
> >>>>>>>>> The whole purpose of the ticket is to automate benchmarks
> >> execution
> >>>>>> for
> >>>>>>>>> the end user for a specific Ignite release. Now he/she needs to
> go
> >>>>>>> through
> >>>>>>>>> a number of steps like build, configure, run strictly following
> >>>>>> lengthy
> >>>>>>>>> Yardstick guidance.
> >>>>>>>>>
> >>>>>>>>> Ideally, once a specific release is downloaded it should be
> >> possible
> >>>>>> to
> >>>>>>>>> run a concrete benchmark with a ready-to-use script. The script
> >>>> needs
> >>>>>>>>> benchmarks' lib which makes sense to put under “libs/optional”
> >>>> folder.
> >>>>>>>>>
> >>>>>>>>> If someone wants to modify the source of an existed benchmark or
> >>>> add a
> >>>>>>> new
> >>>>>>>>> one then he/she needs to follow existed Yardstick guidance. So,
> no
> >>>>>> need
> >>>>>>> to
> >>>>>>>>> release benchmarks’s sources as a part of Ignite release.
> >>>>>>>>>
> >>>>>>>>> —
> >>>>>>>>> Denis
> >>>>>>>>>
> >>>>>>>>>> On Dec 18, 2016, at 7:08 AM, Dmitriy Setrakyan <
> >>>>>> dsetrak...@apache.org>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> On Sun, Dec 18, 2016 at 2:53 AM, Oleg Ostanin <
> >>>> oosta...@gridgain.com
> >>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Dmitriy, ignite-yardstick allows user to run plenty of useful
> >>>>>>> Yardstick
> >>>>>>>>>>> benchmarks, which can be used to check Ignite performance.
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> In that case, why would it be under the "libs" folder at all? Do
> >> we
> >>>>>>>>> really
> >>>>>>>>>> need to include benchmarks into Ignite? If yes, then I would
> >>>> create a
> >>>>>>>>>> benchmarks folder under "examples" and add all the benchmarks
> >>>> there.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, Dec 16, 2016 at 11:49 PM, Dmitriy Setrakyan <
> >>>>>>>>> dsetrak...@apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Oleg, what does ignite-yardstick module do?
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Fri, Dec 16, 2016 at 12:37 AM, Oleg Ostanin <
> >>>>>>> oosta...@gridgain.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Hello Igniters!
> >>>>>>>>>>>>> I'm working on ticket IGNITE-4212 "Ignite Benchmarking
> >>>>>>> Simplification
> >>>>>>>>>>> and
> >>>>>>>>>>>>> Automation" and I'd like to ask your opinion about
> >>>>>> ignite-yardstick:
> >>>>>>>>>>>> where
> >>>>>>>>>>>>> do you think is the most appropriate place to put a compiled
> >>>>>>>>>>>>> ignite-yardstick module in the apache-ignite binary assembly?
> >> We
> >>>>>> can
> >>>>>>>>>>> put
> >>>>>>>>>>>> it
> >>>>>>>>>>>>> in the libs/optional along with an others optional libraries,
> >> or
> >>>>>> we
> >>>>>>>>> can
> >>>>>>>>>>>>> create a new directory named "tools" in the root directory
> and
> >>>> put
> >>>>>>>>>>>>> "ignite-yardstick" in it, or we can find another solution.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Best regards
> >>>>>>>>>>>>> Oleg
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Sergey Kozlov
> >>>>>>>> GridGain Systems
> >>>>>>>> www.gridgain.com
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sergey Kozlov
> >>>>> GridGain Systems
> >>>>> www.gridgain.com
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Sergey Kozlov
> >>> GridGain Systems
> >>> www.gridgain.com
> >>>
> >>
> >>
> >>
> >> --
> >> Sergey Kozlov
> >> GridGain Systems
> >> www.gridgain.com
> >>
>
>

[jira] [Created] (IGNITE-4481) Part of IGNITE-4212

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-4481:


 Summary: Part of IGNITE-4212
 Key: IGNITE-4481
 URL: https://issues.apache.org/jira/browse/IGNITE-4481
 Project: Ignite
  Issue Type: Sub-task
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


The goal of this subtask is to resolve this part of original task:

Every deliverable must contain an executable (bat or sh file) with a clear 
instruction on how to start a specific benchmark from the console.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4478) Part of IGNITE-4212

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-4478:


 Summary: Part of IGNITE-4212
 Key: IGNITE-4478
 URL: https://issues.apache.org/jira/browse/IGNITE-4478
 Project: Ignite
  Issue Type: Sub-task
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


The goal of this subtask is to resolve the first part of original task:

Ignite-yardstick benchmarks have to be pre-compiled and available with every 
Ignite deliverable.

We need to create "benchmarks" folder and put it under the root of an Apache 
Ignite distribution. The structure of this folder is shown below.
apache_ignite_root_folder
– bin
– examples
...
– benchmarks
— bin (contains scripts needed to run the benchmarks)
— src (contains benchmarks sources and a pom.xml in order to create a project 
in an IDE instantaneously)
— config (configs for amazon and well as for local benchmarks execution)
— libs (compiled and ready-to-run benchmarks)
— README.txt (instructions how to run the benchmarks)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request #1365: Ignite 3292

[oleg-ostanin]

GitHub user oleg-ostanin opened a pull request:

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

Ignite 3292



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

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

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

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


commit bfb00b6e61f9709718c30971997aeb0ac79e86b4
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-18T20:12:28Z

IgniteTcpCommunicationBigClusterTest added

commit 02dd92e605b9b53f5a16c7ec5f8e7b5698b15ba4
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-18T21:55:37Z

IgniteTcpCommunicationBigClusterTest update

commit 6acf193a3d356d1bad4c02a53ac76833ed1008d0
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-19T09:55:45Z

Have got TcpCommunicationSpi error

commit 4fd39653d24f62f19f70b4dffba8497185cc46fb
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-19T16:39:10Z

Some discovery have been done

commit c2c181922c7c24ea457577e32d2af897c8bec87f
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-19T20:11:28Z

Prove that problem is not in the onFirstMessage hang

commit f8076edba097f6077229b2090ee3ff1a3369878c
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-19T20:26:37Z

Revert: Prove that problem is not in the onFirstMessage hang

commit 6e1f2dfc2acb3dbb8f24aa51ed67b2ee447b4585
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-21T08:55:09Z

Revert: pushing unnecessary changes to the master

commit ed794ca815f6bb1471af15779279d287576b39cc
Author: Alexandr Kuramshin <akurams...@gridgain.com>
Date:   2016-11-21T09:08:00Z

Revert: pushing unnecessary changes to the master

commit a4b8233c1c64a962aca57bd8685048696c48341f
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2016-12-19T11:52:59Z

IGNITE-3292 change output format

commit d28f4989c172c718c4ca3109c344652c2f6ae556
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2016-12-20T12:38:45Z

Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite 
into ignite-3292

merge master

commit 3ccfd346d21172a41bac25c0e2618d39f4f3cf32
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2016-12-20T12:42:57Z

Merge branch 'master' of https://github.com/gridgain/apache-ignite into 
ignite-3292

merge master

commit f0444ab2e2f98b260e32e0d7e68060b566bf36e0
Author: oleg-ostanin <oosta...@gridgain.com>
Date:   2016-12-20T13:16:32Z

IGNITE-3292 minor




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