Re: GA Grid: Request to contribute GA library to Apache Ignite

[Denis Magda]

Hi guys,

Yes, in my opinion genetic algorithms developed by Turik perfectly fit our ML 
component as a separate package. Look, *ML* is a building block on top of 
Ignite distributed storage and compute grid. Same is true about GA grid. So, 
why don’t we merge GA into ML?

Nikita, Yuri and the rest of ML folks please chime in.

—
Denis


> On Nov 2, 2017, at 5:02 PM, techbysample  wrote:
> 
> Dmitriy,
> 
> Hello. Unfortunately, I am not sure that I fully understand your comments:  
> 
> "..Is my understanding correct that GA Grid is a vertical component for 
> genetic algorithms?  So far Ignite has been a horizontal product without any 
> vertical functionality. I personally would like to keep it this way.."
> 
> Would you please clarify?
> 
> I simply view GA Grid as a software component that implements a distributive
> Genetic Algorithm (GA). 
> GA Grid relies on Apache Ignite's major features: advanced clustering,
> compute grid, data grid, etc.
> 
> Here is a diagram of how GA Grid relates to other components within Ignite:
> 
> 
>  
> 
> Based my earlier discussion with Denis M., I assumed GA Grid could be added
> to the collection of ML algorithms within ML Grid, since GA's are a type of
> 'Machine Learning" algorithms.  
> 
> If it is determined that GA Grid would not fit into Apache Ignite
> architecturally, I would consider including
> it as separate Apache project.
> 
> Denis, would you please add your feedback as well?
> 
> Please advise.
> 
> Best,
> Turik 
> 
> 
> 
> 
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: GA Grid: Request to contribute GA library to Apache Ignite

[techbysample]

Dmitriy,

Hello. Unfortunately, I am not sure that I fully understand your comments:  

"..Is my understanding correct that GA Grid is a vertical component for 
genetic algorithms?  So far Ignite has been a horizontal product without any 
vertical functionality. I personally would like to keep it this way.."

Would you please clarify?

I simply view GA Grid as a software component that implements a distributive
Genetic Algorithm (GA). 
GA Grid relies on Apache Ignite's major features: advanced clustering,
compute grid, data grid, etc.

Here is a diagram of how GA Grid relates to other components within Ignite:


 

Based my earlier discussion with Denis M., I assumed GA Grid could be added
to the collection of ML algorithms within ML Grid, since GA's are a type of
'Machine Learning" algorithms.  

If it is determined that GA Grid would not fit into Apache Ignite
architecturally, I would consider including
it as separate Apache project.

Denis, would you please add your feedback as well?

Please advise.

Best,
Turik 




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

[GitHub] ignite pull request #2848: IGNITE-6626

[devozerov]

Github user devozerov closed the pull request at:

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


---

[GitHub] ignite pull request #2975: Ignite-6083

[voipp]

GitHub user voipp opened a pull request:

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

Ignite-6083



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

$ git pull https://github.com/voipp/ignite ignite-6083

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

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


commit 5154819c58d221ecf810f85370426007cdce083d
Author: voipp 
Date:   2017-11-02T17:30:20Z

test added

commit 8a6c816e8122327645ccd7f6c76002d330b990f2
Author: voipp 
Date:   2017-11-02T17:26:37Z

draft fix




---

[GitHub] ignite pull request #2974: Ignite 2.1.7.b1

[kdudkov]

GitHub user kdudkov opened a pull request:

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

Ignite 2.1.7.b1



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

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

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

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


commit 8dbdd03143362bb39d96242b23975efb22412709
Author: Ivan Rakov 
Date:   2017-08-22T14:03:42Z

IGNITE-6154 also fixed check for WAL record

commit afad8e0fc58160f7876925dc6c3051be7a168155
Author: Ilya Lantukh 
Date:   2017-08-23T09:18:44Z

Muted hanging test.

commit ad38f7b4b5e6845b2d7eb888f805484504f5
Author: Ilya Lantukh 
Date:   2017-08-23T11:12:42Z

gg-12662 : Fixed JDBC backward compatibility.

commit 28c906e3e0c51e6f1a4a95b2027d248f9b5035c2
Author: Sergey Chugunov 
Date:   2017-08-02T15:14:46Z

IGNITE-5542 CacheGroup configuration from cluster is merged with local 
settings

(cherry picked from commit 88818ec)

commit caeb11936fa3534b9468d443c11744362044cae5
Author: sboikov 
Date:   2017-08-23T12:19:52Z

ignite-6124 Guard logging with isInfoEnabled

(cherry picked from commit bebe4d8)

commit 6f407ebabb9dc27459fdbee6423640132b995b1d
Author: tledkov-gridgain 
Date:   2017-08-23T12:46:23Z

IGNITE-6169: Fixed thin JDBC driver compatibility problem.

commit 9dac636c4eef494fe612389c19218eec92057fc0
Author: Ilya Kasnacheev 
Date:   2017-08-23T13:26:58Z

IGNITE-4643: Fixed NPE in  JdbcDatabaseMetadata.getIndexInfo(). This closes 
#2481.

commit 77241cdc45c90ee9bab4a7a0f3d5a1a7664e3426
Author: sboikov 
Date:   2017-08-23T13:45:34Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit a5e376f63886696331e5be0c457dc0624c49e3d4
Author: sboikov 
Date:   2017-08-23T13:44:04Z

ignite-6124 Added missed initialization of merged join exchanges in 
GridDhtPartitionsExchangeFuture.onBecomeCoordinator

(cherry picked from commit 0c5dca9)

commit be5589db9e0600b295b745ddab5e7aae390ac7ae
Author: Ilya Lantukh 
Date:   2017-08-23T14:25:33Z

ignite-5986 : Fixed failing .NET test.

commit 43e4ff2c0ecd1ef30d18cf1fbc9052f5ba703d05
Author: sboikov 
Date:   2017-07-18T14:52:51Z

Fixed test IgniteClusterActivateDeactivateTestWithPersistence.

(cherry picked from commit 54585ab)

commit d596b7806db3f002f83da5a02bc882d03dae3dfd
Author: Ilya Lantukh 
Date:   2017-08-23T15:23:06Z

Updated classnames.properties.

commit 3e08cd401d598a34832e72afc5e6c94a3a9ab081
Author: sboikov 
Date:   2017-08-23T15:29:52Z

ignite-6174 Temporary changed test until issue not fixed

(cherry picked from commit 4fe8f76)

commit 44e0b4cd62142dce8cf39f826449b9a04e22e1cf
Author: Alexey Kuznetsov 
Date:   2017-08-24T07:57:36Z

IGNITE-6136 Fixed version for demo.
(cherry picked from commit e1bf8d7)

commit 8d1838b03d6c1e5f86dfbb7f41c59895775e20c1
Author: Dmitry Pavlov 
Date:   2017-07-27T11:51:25Z

Adjusted memory policy to prevent OOM.

commit a3ec54b16bce1a569fbefba17188ccb4702b82a4
Author: sboikov 
Date:   2017-08-24T11:09:12Z

ignite-6124 DataStreamerImpl: do not wait for exchange future inside cache 
gateway.

(cherry picked from commit 3ab523c)

commit 30e6d019a21f4a045a50d7d95a04507e3b646e69
Author: sboikov 
Date:   2017-08-24T11:10:34Z

Merge remote-tracking branch 'community/ignite-2.1.4' into ignite-2.1.4

commit 41f574a7372ffc04b69809298798f24fb34c161f
Author: Dmitriy Govorukhin 
Date:   2017-08-24T12:58:27Z

Fixed test.

commit 943736b36d67381157fc2807cd7af4b03d44fef3
Author: nikolay_tikhonov 
Date:   2017-08-24T15:58:16Z

Revert "IGNITE-5947 Fixed "ClassCastException when two-dimensional array is 
fetched from cache".
* Due to this changes break compatibility with .NET;
* This fix doesn't cover all cases.

Signed-off-by: nikolay_tikhonov 

commit c2e836b5b9b183404f4507c64c13ab5c05653d24
Author: EdShangGG 
Date:   2017-08-24T16:15:24Z

ignite-6175 JVM Crash in Ignite Binary Objects Simple Mapper Basic suite

Signed-off-by: Andrey Gura 

commit b2b596b4f59bcf7a1b7397a6fd681a0ae47092db
Author: Andrey Novikov 
Date:   2017-08-25T03:48:15Z

IGNITE-5200 Web Console: Don't cache generated chunks in production.
   

[GitHub] ignite pull request #2973: 2.1.3-p6

[ilantukh]

GitHub user ilantukh opened a pull request:

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

2.1.3-p6

For testing only.

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

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

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

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






---

[jira] [Created] (IGNITE-6823) Sporadic Redis python and php examples failures

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-6823:
---

 Summary: Sporadic Redis python and php examples failures
 Key: IGNITE-6823
 URL: https://issues.apache.org/jira/browse/IGNITE-6823
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Affects Versions: 2.1
Reporter: Ksenia Rybakova
Priority: Normal


Sporadic Redis python examples failure
{noformat}
['python3', 'examples/redis/redis-example.py']
Traceback (most recent call last):
  File "examples/redis/redis-example.py", line 30, in 
r.set('k1', 1)
  File "c:\program files\python34\lib\site-packages\redis\client.py", line 
1171, in set
return self.execute_command('SET', *pieces)
  File "c:\program files\python34\lib\site-packages\redis\client.py", line 668, 
in execute_command
return self.parse_response(connection, command_name, **options)
  File "c:\program files\python34\lib\site-packages\redis\client.py", line 680, 
in parse_response
response = connection.read_response()
  File "c:\program files\python34\lib\site-packages\redis\connection.py", line 
624, in read_response
response = self._parser.read_response()
  File "c:\program files\python34\lib\site-packages\redis\connection.py", line 
292, in read_response
(str(byte), str(response)))
redis.exceptions.InvalidResponse: Protocol Error: E, b'RROR'
Command '['python3', 'examples/redis/redis-example.py']' returned non-zero exit 
status 1
{noformat}

and Redis php
{noformat}
['php', 'examples/redis/redis-example.php']
>>> Successfully connected to Redis. 
>>> Couldn't connected to Redis.Unknown response prefix: 'E'. 
>>> [tcp://localhost:11211]
{noformat}



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

[jira] [Created] (IGNITE-6822) IgfsMapReduceExample raise exception in multi nodes run

[Aleksey Chetaev (JIRA)]

Aleksey Chetaev created IGNITE-6822:
---

 Summary: IgfsMapReduceExample raise exception in multi nodes run
 Key: IGNITE-6822
 URL: https://issues.apache.org/jira/browse/IGNITE-6822
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Aleksey Chetaev
Priority: Minor


All logs in attachments.
Exception:

{code:java}
class org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep 
interrupted
at org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7538)
at 
org.apache.ignite.internal.MarshallerMappingFileStore.fileLock(MarshallerMappingFileStore.java:254)
at 
org.apache.ignite.internal.MarshallerMappingFileStore.writeMapping(MarshallerMappingFileStore.java:95)
at org.apache.ignite.internal.MappingStoreTask.run(MappingStoreTask.java:57)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6687)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}



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

IGNITE-6679 Clean up some deprecated cache metrics

[Nikita Amelchev]

Hello, Igniters.

I have removed deprecated metrics [1]. Please, review [2]. Tests look good
[3].

1. https://issues.apache.org/jira/browse/IGNITE-6679
2. https://reviews.ignite.apache.org/ignite/review/IGNT-CR-390
3.
https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2962%2Fhead

-- 
Best wishes,
Amelchev Nikita

[GitHub] ignite pull request #2972: Ignite 8266 test failing GridTcpCommunicationSpiC...

[alamar]

GitHub user alamar opened a pull request:

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

Ignite 8266 test failing  
GridTcpCommunicationSpiConfigSelfTest.testLocalPortRange test



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

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

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

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


commit db88d6ba39920ace74720f7dc0e0741cfb38c450
Author: Pavel Tupitsyn 
Date:   2017-09-14T18:40:48Z

IGNITE-6258: Thin client: binary metadata protocol. This closes #2662. This 
closes #2667.

commit b2c61b64dd764ea1684f7aba7c3a8458c498cc9e
Author: Alexey Kuznetsov 
Date:   2017-09-15T04:47:53Z

IGNITE-6367 Restrict files search by IGNITE_HOME.

commit 50c70022eb30474aed770efbf0bd4a53375f5e81
Author: sboikov 
Date:   2017-09-15T08:00:25Z

Code style.

commit 91cf66e7083e4e73b2bcd08e81fdb29cf06ddc59
Author: Denis Mekhanikov 
Date:   2017-09-15T08:19:18Z

ignite-6289 Remove "allOrNone" flag from IgniteServices#deployAll method

commit 319aa840201f907c0a31fceb17837dfd2ba43fc1
Author: EdShangGG 
Date:   2017-09-15T08:59:48Z

IGNITE-6277 Added ability to convert WAL to human readable form - Fixes 
#2605.

Signed-off-by: Alexey Goncharuk 

commit 8610471ed8d28c600268407be1a2d6ddfbf45f6c
Author: sboikov 
Date:   2017-09-15T10:49:56Z

ignite-6137: CAS logic fix in async commit
This closes #2496.

commit 1fcc96d624356b04de78f79b831d9e0049b8928b
Author: sboikov 
Date:   2017-09-15T10:50:14Z

Merge remote-tracking branch 'origin/master'

commit 8741acce15f50f978257da193cce2a5e2c5bd816
Author: vsisko 
Date:   2017-09-15T11:02:59Z

IGNITE-6251 Clear selection from removed rows.

commit a00052e94531528c5df0dc4485d8882514b40af4
Author: Pavel Tupitsyn 
Date:   2017-09-15T11:05:53Z

IGNITE-6368: Initial .NET part of thin client. This closes #2670.

commit 8936a0db52d1d290a482f9f0044908e3076dc899
Author: Pavel Tupitsyn 
Date:   2017-09-15T11:17:30Z

.NET: Remove unused imports

commit 39b903013f564f4229ff3284e22e46001a4f9b46
Author: dpavlov 
Date:   2017-09-15T11:47:03Z

IGNITE-6235 Added ability to handle CacheObject from DataRecord in 
standalone WAL iterator - Fixes #2620.

Signed-off-by: Alexey Goncharuk 

commit fe06b5983fb7edf7ea36d7881a22ba6d5a97ee00
Author: YuriBabak 
Date:   2017-09-15T13:41:11Z

IGNITE-6394: Fixed creation of off-heap matrix with size over 2 Gb
(int overflow in DenseOffHeapMatrixStorage.allocateMemory)

commit 4a88ec3ec2a6a5d5004187a3424f5832217fda9c
Author: Andrey V. Mashenkov 
Date:   2017-09-15T13:45:02Z

IGNITE-6256: DiscoCache always contains local node.

Signed-off-by: Andrey Gura 

commit 8bcd69dd4ef14f747b7d7c582b89b14fda961348
Author: tledkov-gridgain 
Date:   2017-09-15T14:25:26Z

IGNITE-6395: Remove old test. This closes #2673.

commit 1b5ca4446f7961e6c1b3f9c6bab0d8dc540b932f
Author: Denis Magda 
Date:   2017-09-15T16:54:44Z

Updated Ignite description

commit cb4195fabb637c405b40fd613f1abbeae93a70bd
Author: Denis Magda 
Date:   2017-09-15T16:59:24Z

Updated Ignite description

commit 2da8861a252a8d5b68f75aae07ed394b52cc1390
Author: Denis Magda 
Date:   2017-09-15T17:01:41Z

Updated Ignite description

commit b86153208f28cfd76c9d21b6170d228e23deaead
Author: Denis Magda 
Date:   2017-09-15T20:31:19Z

Updated Ignite description

commit 9fd82212e528a6287cf89d279416aefa92c0cad5
Author: devozerov 
Date:   2017-09-16T11:57:55Z

IGNITE-6327: Added thin client configuration. This closes #2672.

commit 7c4d0bc2a84cfcc9c240f41c48aa129b5f60eca0
Author: Alexander Paschenko 
Date:   2017-09-16T14:41:34Z

IGNITE-5620: Implemented SQLSTATE error code for server-side logic and JDBC 
thin client. This closes #2541.

commit 40597a030b95d3d678d858237054e4af2637d267
Author: vsisko 
Date:   2017-09-18T07:09:22Z

IGNITE-6417 Fixed missed binary configuration.

commit 64b4abe52fcc5b506529d063cd43db43943e0f14
Author: Ivan Rakov 
Date:   2017-09-18T08:35:17Z

IGNITE-6385 Offheap page eviction doesn't work if data is loaded without 
data streamer - Fixes #2666.

Signed-off-by: Alexey Goncharuk 

[jira] [Created] (IGNITE-6821) Add test for cross-cache transactions between in-memory and persistent caches

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-6821:


 Summary: Add test for cross-cache transactions between in-memory 
and persistent caches
 Key: IGNITE-6821
 URL: https://issues.apache.org/jira/browse/IGNITE-6821
 Project: Ignite
  Issue Type: Test
  Security Level: Public (Viewable by anyone)
  Components: 2.3
Affects Versions: 2.4
Reporter: Alexey Goncharuk
Assignee: Ivan Rakov
Priority: Major


Need to add tests that will make sure that we do not log data records for 
persistence-disabled caches and can successfully recover for 
persistence-enabled caches when a transaction hits both caches.



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

[jira] [Created] (IGNITE-6820) Add data regions to data structures configuration

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-6820:


 Summary: Add data regions to data structures configuration
 Key: IGNITE-6820
 URL: https://issues.apache.org/jira/browse/IGNITE-6820
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: cache
Affects Versions: 2.3
Reporter: Alexey Goncharuk
Priority: Major
 Fix For: 2.4


Data structures configuration has cache group name but misses data region name. 
This makes it tricky to move data structures to a different data region. More 
specifically, it's hard to have default data region with persistence disabled 
but configure data structures to be persistent.



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

[GitHub] ignite pull request #2968: IGNITE-6640: Introduction of models import/export

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #2971: IGNITE-6690 DiscoverySpi: Clientmode Ignite shoul...

[apopovgg]

GitHub user apopovgg opened a pull request:

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

IGNITE-6690 DiscoverySpi: Clientmode Ignite should not fail on handshake 
errors

test fixes

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

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

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

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


commit 224e2343c12ad80417eb1094a67b63f3ec56c2a7
Author: apopov 
Date:   2017-11-02T07:22:28Z

fixed tests broken by IGNITE-6690 and IGNITE-5860 incompatibility

commit 126a25ef8f3125415c743acaea0b5e47fe1f047b
Author: apopov 
Date:   2017-11-02T08:22:03Z

fixed tests broken by IGNITE-6690 and IGNITE-5860 incompatibility




---

[jira] [Created] (IGNITE-6819) Better test coverage for PagesList basic functionality

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-6819:
---

 Summary: Better test coverage for PagesList basic functionality
 Key: IGNITE-6819
 URL: https://issues.apache.org/jira/browse/IGNITE-6819
 Project: Ignite
  Issue Type: Test
  Security Level: Public (Viewable by anyone)
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
Priority: Major


Working on IGNITE-6641 I faced an issue that serious bug introduced to 
PagesListNodeIO didn't cause obvious test failures and was spotted by chance 
from memory leak test failures.

It means that test coverage of pages management code base lacks tests for 
invariants that has to be preserved in any use cases.

We need to introduce such tests starting with set of tests verifying that 
certain pages go to certain buckets on data entries put/remove operations.



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

[jira] [Created] (IGNITE-6818) In case of incoming communication connection ping the old one if it's alive

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-6818:
---

 Summary: In case of incoming communication connection ping the old 
one if it's alive
 Key: IGNITE-6818
 URL: https://issues.apache.org/jira/browse/IGNITE-6818
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Affects Versions: 2.3
Reporter: Dmitry Karachentsev
Assignee: Dmitry Karachentsev
Priority: Critical
 Fix For: 2.4


Assume the following scenario:
1. Client opens connection to the server.
2. Server checks that it is a first connection to that node and accepts it.
3. By some reason firewall starts rejecting client messages with TCP reset flag 
set.
4. Client closes connection, but server doesn't know about it.
5. Client tries connect again.
6. Server rejects new connection, because it already has connection to that 
node.

Possible fix: on step 6 server must check old connection if it's alive by 
sending some communication message and check response. If old connection is 
dead - close it and accept new one.



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

Re: Set gitter aside

[Pavel Tupitsyn]

Sure, done.

On Thu, Nov 2, 2017 at 10:10 AM, Dmitry Pavlov 
wrote:

> Hi Pavel, thank you. Could you please do the same for this modules?
> I can remove gitter but I am not sure about CI server links correctness.
>
> чт, 2 нояб. 2017 г. в 9:38, Pavel Tupitsyn :
>
> > Denis, Dmitry,
> >
> > Looks like you forgot
> > https://github.com/apache/ignite/tree/master/modules/platforms/dotnet
> > and
> > https://github.com/apache/ignite/tree/master/modules/platforms/cpp
> >
> > Thanks,
> > Pavel
> >
> > On Thu, Nov 2, 2017 at 9:16 AM, Dmitry Pavlov 
> > wrote:
> >
> > > Denis, thank you for review and merge!
> > > Link was removed also from https://github.com/apache/ignite repository
> > > main
> > > page.
> > >
> > > Also link to TeamCity builds was updated. Dynamic build status SVG
> > provided
> > > by TC won't be displayed correctly by github because github performs
> > image
> > > caching, but link is now correct. TC SVG from readme.md can be
> displayed
> > > by
> > > other markdown viewers.
> > >
> > >
> > > пт, 27 окт. 2017 г. в 22:59, Denis Magda :
> > >
> > > > Gitter channel evaporated from the Ignite site. Exhale folks...
> > > >
> > > > —
> > > > Denis
> > > >
> > > > > On Oct 27, 2017, at 2:55 AM, Konstantin Dudkov 
> > wrote:
> > > > >
> > > > > Agree.
> > > > >
> > > > > IMHO we should remove link to gitter from everywhere and keep
> > answering
> > > > there, but for questions about product usage we should ask to ask the
> > > > question in userlist.
> > > > >
> > > > > 27/10/2017 02:10, Dmitriy Setrakyan пишет:
> > > > >> How about we continue to have the Gitter channel, but remove the
> > link
> > > > from
> > > > >> the website?
> > > > >> On Thu, Oct 26, 2017 at 3:05 PM, Yakov Zhdanov <
> yzhda...@apache.org
> > >
> > > > wrote:
> > > > >>> I would consider moving decent questions to mailing lists asking
> to
> > > do
> > > > so
> > > > >>> in response to gitter requests and at some point stop gitter.
> > > > >>>
> > > > >>> --Yakov
> > > > >>>
> > > > >
> > > > > --
> > > > > Regards, Konstantin.
> > > >
> > > >
> > >
> >
>

Re: Set gitter aside

[Dmitry Pavlov]

Hi Pavel, thank you. Could you please do the same for this modules?
I can remove gitter but I am not sure about CI server links correctness.

чт, 2 нояб. 2017 г. в 9:38, Pavel Tupitsyn :

> Denis, Dmitry,
>
> Looks like you forgot
> https://github.com/apache/ignite/tree/master/modules/platforms/dotnet
> and
> https://github.com/apache/ignite/tree/master/modules/platforms/cpp
>
> Thanks,
> Pavel
>
> On Thu, Nov 2, 2017 at 9:16 AM, Dmitry Pavlov 
> wrote:
>
> > Denis, thank you for review and merge!
> > Link was removed also from https://github.com/apache/ignite repository
> > main
> > page.
> >
> > Also link to TeamCity builds was updated. Dynamic build status SVG
> provided
> > by TC won't be displayed correctly by github because github performs
> image
> > caching, but link is now correct. TC SVG from readme.md can be displayed
> > by
> > other markdown viewers.
> >
> >
> > пт, 27 окт. 2017 г. в 22:59, Denis Magda :
> >
> > > Gitter channel evaporated from the Ignite site. Exhale folks...
> > >
> > > —
> > > Denis
> > >
> > > > On Oct 27, 2017, at 2:55 AM, Konstantin Dudkov 
> wrote:
> > > >
> > > > Agree.
> > > >
> > > > IMHO we should remove link to gitter from everywhere and keep
> answering
> > > there, but for questions about product usage we should ask to ask the
> > > question in userlist.
> > > >
> > > > 27/10/2017 02:10, Dmitriy Setrakyan пишет:
> > > >> How about we continue to have the Gitter channel, but remove the
> link
> > > from
> > > >> the website?
> > > >> On Thu, Oct 26, 2017 at 3:05 PM, Yakov Zhdanov  >
> > > wrote:
> > > >>> I would consider moving decent questions to mailing lists asking to
> > do
> > > so
> > > >>> in response to gitter requests and at some point stop gitter.
> > > >>>
> > > >>> --Yakov
> > > >>>
> > > >
> > > > --
> > > > Regards, Konstantin.
> > >
> > >
> >
>

Re: Let's keep Apache Ignite docs up-to-date

[Dmitry Pavlov]

I don't like git docs idea, it will require to follow whole
PR-review-process that requires long time. IMO it is odd work.
If readme.io provides review process, I suggest to keep it as-is.

чт, 2 нояб. 2017 г. в 9:57, Dmitriy Setrakyan :

> On Wed, Nov 1, 2017 at 11:27 PM, Vladimir Ozerov 
> wrote:
>
> > +1 for moving docs under Git provided that we find a way to update docs
> > outside of AI release as it is possible now with readme.io.
> >
>
> I am HUGE +1 for that. The whole problem is that we haven't found a way
> yet. All I want is to update a page and have it commit to GIT and become
> available to public right away. Does anyone know any tool that supports it?
>

Re: Let's keep Apache Ignite docs up-to-date

[Dmitriy Setrakyan]

On Wed, Nov 1, 2017 at 11:27 PM, Vladimir Ozerov 
wrote:

> +1 for moving docs under Git provided that we find a way to update docs
> outside of AI release as it is possible now with readme.io.
>

I am HUGE +1 for that. The whole problem is that we haven't found a way
yet. All I want is to update a page and have it commit to GIT and become
available to public right away. Does anyone know any tool that supports it?

Re: [DISUCSS] Ticket filing process

[Dmitriy Setrakyan]

Vladimir,

In that case can you suggest a better process. I currently have a high
confidence that unless I assign the next release version to a ticket, it
will never be looked at. How do we fix it?

D.

On Wed, Nov 1, 2017 at 11:32 PM, Vladimir Ozerov 
wrote:

> -1
>
> Ideally ticket should have a version only if we understand that it should
> go to certain release. All other tickets should not have versions, because
> otherwise it is hard to see the scope of the next release, and we woulld
> need to move dozens of tickets from version to version constantly.
>
> On Thu, Nov 2, 2017 at 2:25 AM, Dmitriy Setrakyan 
> wrote:
>
> > Igniters,
> >
> > Currently, most new Jira tickets do not get reviewed and often get lost
> > unless some user complains about it.
> >
> > In my view, the community must review all recently filed ticket and make
> > sure that we address most critical or most useful ones. Often an issue is
> > not critical from correctness standpoint, but is very useful from
> usability
> > stand point.
> >
> > What if we always assigned the next release version to all the newly
> filed
> > tickets. This will force someone to look at the tickets before every
> > release and move some of them to the next release.
> >
> > Thoughts?
> >
> > D.
> >
>

[jira] [Created] (IGNITE-6817) CME in GridCacheIoManager.cacheHandlers access

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-6817:


 Summary: CME in GridCacheIoManager.cacheHandlers access
 Key: IGNITE-6817
 URL: https://issues.apache.org/jira/browse/IGNITE-6817
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: general
Affects Versions: 2.1
Reporter: Alexander Belyak


Got exception:
{noformat}
java.util.ConcurrentModificationException: null

at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437)

at java.util.HashMap$EntryIterator.next(HashMap.java:1471)

at java.util.HashMap$EntryIterator.next(HashMap.java:1469)

at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:355)

   at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)

at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)

at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)

at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1562)

at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1190)

at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)

at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)

at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:505)

at java.lang.Thread.run(Thread.java:748)
{noformat}
becouse in GridCacheIoManager.handleMessage access to 
GridCacheIoManager.cacheHandles protected by GridCacheIoManager.rw.readLock, 
but in GridCacheIoManager.addHandler same collection modify without 
rw.writeLock accuiring and idxClsHandlers is just HashMap in 
GridCacheioManager.MessageHandlers class.



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

Re: Set gitter aside

[Pavel Tupitsyn]

Denis, Dmitry,

Looks like you forgot
https://github.com/apache/ignite/tree/master/modules/platforms/dotnet
and
https://github.com/apache/ignite/tree/master/modules/platforms/cpp

Thanks,
Pavel

On Thu, Nov 2, 2017 at 9:16 AM, Dmitry Pavlov  wrote:

> Denis, thank you for review and merge!
> Link was removed also from https://github.com/apache/ignite repository
> main
> page.
>
> Also link to TeamCity builds was updated. Dynamic build status SVG provided
> by TC won't be displayed correctly by github because github performs image
> caching, but link is now correct. TC SVG from readme.md can be displayed
> by
> other markdown viewers.
>
>
> пт, 27 окт. 2017 г. в 22:59, Denis Magda :
>
> > Gitter channel evaporated from the Ignite site. Exhale folks...
> >
> > —
> > Denis
> >
> > > On Oct 27, 2017, at 2:55 AM, Konstantin Dudkov  wrote:
> > >
> > > Agree.
> > >
> > > IMHO we should remove link to gitter from everywhere and keep answering
> > there, but for questions about product usage we should ask to ask the
> > question in userlist.
> > >
> > > 27/10/2017 02:10, Dmitriy Setrakyan пишет:
> > >> How about we continue to have the Gitter channel, but remove the link
> > from
> > >> the website?
> > >> On Thu, Oct 26, 2017 at 3:05 PM, Yakov Zhdanov 
> > wrote:
> > >>> I would consider moving decent questions to mailing lists asking to
> do
> > so
> > >>> in response to gitter requests and at some point stop gitter.
> > >>>
> > >>> --Yakov
> > >>>
> > >
> > > --
> > > Regards, Konstantin.
> >
> >
>

Re: [DISUCSS] Ticket filing process

[Vladimir Ozerov]

-1

Ideally ticket should have a version only if we understand that it should
go to certain release. All other tickets should not have versions, because
otherwise it is hard to see the scope of the next release, and we woulld
need to move dozens of tickets from version to version constantly.

On Thu, Nov 2, 2017 at 2:25 AM, Dmitriy Setrakyan 
wrote:

> Igniters,
>
> Currently, most new Jira tickets do not get reviewed and often get lost
> unless some user complains about it.
>
> In my view, the community must review all recently filed ticket and make
> sure that we address most critical or most useful ones. Often an issue is
> not critical from correctness standpoint, but is very useful from usability
> stand point.
>
> What if we always assigned the next release version to all the newly filed
> tickets. This will force someone to look at the tickets before every
> release and move some of them to the next release.
>
> Thoughts?
>
> D.
>

Re: Let's keep Apache Ignite docs up-to-date

[Vladimir Ozerov]

+1 for moving docs under Git provided that we find a way to update docs
outside of AI release as it is possible now with readme.io.

On Thu, Nov 2, 2017 at 8:57 AM, Pavel Tupitsyn  wrote:

> > I can edit a document and it is visible to the whole world once I click a
> save button
> I see this as a huge downside.
> Anyone can screw up entire documentation with a single misplaced click,
> and you can't even see the history or have an ability to restore the
> previous version.
>
> Right now I can go and remove any page, and you would not even know who did
> that.
> (or am I missing something? can you revert and restore things?)
>
>
> On Thu, Nov 2, 2017 at 2:35 AM, Dmitriy Setrakyan 
> wrote:
>
> > I am going to repeat my previous comment, since it somehow got lost in
> the
> > discussion:
> >
> > The main value of readme is that I can edit a document and it is visible
> to
> > the whole world once I click a save button, without any git commands or
> > builds. If anyone in the community can suggest a tool that will work the
> > same way with Apache git repository directly, please send it here.
> >
> > D.
> >
> > On Wed, Nov 1, 2017 at 4:26 AM, Anton Vinogradov <
> avinogra...@gridgain.com
> > >
> > wrote:
> >
> > > +1 to Pavel's proposal,
> > >
> > > > Markdown can also be visualized by many IDEs, so it is easy to edit
> > > locally.
> > > IDEA shows Markdown out of the box.
> > >
> > > Yakov,
> > >
> > > > having docs under separate git repository
> > > We should not use separate git repo, Apache Ignite repo should be used.
> > > Documentation should be a part of pull request.
> > >
> > > On Wed, Nov 1, 2017 at 10:08 AM, Pavel Tupitsyn 
> > > wrote:
> > >
> > > > Denis,
> > > >
> > > > > Could you show me any example of such a documentation where docs
> are
> > > > stored in git and can be visualized by GitHub (dev stage) and 3rd
> party
> > > > engine (release on the site)?
> > > >
> > > > 1) Apache Spark
> > > > Source: https://github.com/apache/spark/tree/master/docs
> > > > Docs: https://spark.apache.org/documentation.html
> > > > (uses Jekyll)
> > > >
> > > > 2) Microsoft .NET
> > > > Source: https://github.com/dotnet/docs
> > > > Docs: https://docs.microsoft.com/en-us/dotnet/
> > > > (uses DocFX)
> > > >
> > > >
> > > > Both of these engines (Jekyll and DocFX) use markdown, which can be
> > > > visualized by github, and converted to HTML for the web site.
> > > > Markdown can also be visualized by many IDEs, so it is easy to edit
> > > > locally.
> > > >
> > > > Ideally, API docs (javadoc) should be integrated with the rest of the
> > > docs,
> > > > so users can navigate to the corresponding APIs.
> > > > This can't be achieved nicely with readme.io.
> > > >
> > > >
> > > > > having docs under separate git repository
> > > > I don't think we need a separate repo, we can just create branches in
> > our
> > > > main repo for that.
> > > > It is nice to have everything in one place.
> > > >
> > > > On Wed, Nov 1, 2017 at 6:30 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >
> > > > wrote:
> > > >
> > > > > On Tue, Oct 31, 2017 at 8:15 PM, Yakov Zhdanov <
> yzhda...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > I would also consider having docs under separate git repository.
> > > > Separate
> > > > > > since we need to have an opportunity to revisit documentation for
> > > > already
> > > > > > released versions.
> > > > > >
> > > > >
> > > > > This should not be a problem.
> > > > >
> > > >
> > >
> >
>

Re: Set gitter aside

[Dmitry Pavlov]

Denis, thank you for review and merge!
Link was removed also from https://github.com/apache/ignite repository main
page.

Also link to TeamCity builds was updated. Dynamic build status SVG provided
by TC won't be displayed correctly by github because github performs image
caching, but link is now correct. TC SVG from readme.md can be displayed by
other markdown viewers.


пт, 27 окт. 2017 г. в 22:59, Denis Magda :

> Gitter channel evaporated from the Ignite site. Exhale folks...
>
> —
> Denis
>
> > On Oct 27, 2017, at 2:55 AM, Konstantin Dudkov  wrote:
> >
> > Agree.
> >
> > IMHO we should remove link to gitter from everywhere and keep answering
> there, but for questions about product usage we should ask to ask the
> question in userlist.
> >
> > 27/10/2017 02:10, Dmitriy Setrakyan пишет:
> >> How about we continue to have the Gitter channel, but remove the link
> from
> >> the website?
> >> On Thu, Oct 26, 2017 at 3:05 PM, Yakov Zhdanov 
> wrote:
> >>> I would consider moving decent questions to mailing lists asking to do
> so
> >>> in response to gitter requests and at some point stop gitter.
> >>>
> >>> --Yakov
> >>>
> >
> > --
> > Regards, Konstantin.
>
>