[jira] [Resolved] (IGNITE-3977) Process failing OSGI tests.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov resolved IGNITE-3977.
--
Resolution: Fixed

> Process failing OSGI tests.
> ---
>
> Key: IGNITE-3977
> URL: https://issues.apache.org/jira/browse/IGNITE-3977
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-3977) Process failing OSGI tests.

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-3977:
-
Fix Version/s: (was: 2.1)
   2.0

> Process failing OSGI tests.
> ---
>
> Key: IGNITE-3977
> URL: https://issues.apache.org/jira/browse/IGNITE-3977
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4539) RocketMQ data streamer

[Roman Shtykh (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15974104#comment-15974104
 ] 

Roman Shtykh commented on IGNITE-4539:
--

Hi Alexey,

I fixed the issue. Please have a look.


> RocketMQ data streamer
> --
>
> Key: IGNITE-4539
> URL: https://issues.apache.org/jira/browse/IGNITE-4539
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: important
> Fix For: 2.0
>
>
> Streamer for RocketMQ (https://github.com/rocketmq)



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

[jira] [Issue Comment Deleted] (IGNITE-4414) Add JUnit test for local queries against a partitoned cache with 2 backups

[Andrew Mashenkov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Mashenkov updated IGNITE-4414:
-
Comment: was deleted

(was: It seems there are 2 bugs in 1.8 release.  

1. Local SqlFieldsQuery run without filtering primary\backup partitions at all. 
It was fixed in [Ignite-4379|https://issues.apache.org/jira/browse/IGNITE-4379].
2. Second one was missed. Local SqlFieldsQuery ignores readFromBackup option.

[~skozlov], should I create separate ticket for fix or I can take this one? 
Anyway, unit test can and will be implemented along with a fix.)

> Add JUnit test for local queries against a partitoned cache with 2 backups
> --
>
> Key: IGNITE-4414
> URL: https://issues.apache.org/jira/browse/IGNITE-4414
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.8
>Reporter: Sergey Kozlov
> Fix For: 2.1
>
>
> Add the JUnit test covers the following case:
>  - partitioned cache with 2 backups (may be include backups=0,1 as well)
>  - put 100 entries
> When I execute a local sql field query it returns more entries than the local 
> size depending on the number of backup.



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

[jira] [Created] (IGNITE-5021) visorcmd: log command - incorrect chronology in file

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5021:
--

 Summary: visorcmd: log command - incorrect chronology in file
 Key: IGNITE-5021
 URL: https://issues.apache.org/jira/browse/IGNITE-5021
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Minor


Events are configured in the grid
{code}











{code}

log -l -t=1
{code}
04/19/17, 11:42:25 | Log started.
04/19/17, 11:42:26 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:27 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:28 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:29 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:30 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:31 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:32 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:33 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:34 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:35 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:36:57 |  => NODE_LEFT: id8=66e8fb9f, ip=0:0:0:0:0:0:0:1
04/19/17, 11:37:05 |  => NODE_JOINED: id8=c0031666, ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:02 |  => NODE_LEFT: id8=be032f32, ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:07 |  => CLIENT_NODE_DISCONNECTED: id8=12dfc0d3, 
ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:14 |  => CLIENT_NODE_RECONNECTED: id8=12dfc0d3, 
ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:18 |  => NODE_JOINED: id8=f9466d50, ip=0:0:0:0:0:0:0:1
04/19/17, 11:38:19 |  => NODE_JOINED: id8=3a0dadb7, ip=0:0:0:0:0:0:0:1
04/19/17, 11:42:36 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:37 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:38 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:39 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:40 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:41 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:42 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:43 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:44 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:45 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:46 | H/N/C|1   |3   |8   |^...|
04/19/17, 11:42:47 | H/N/C|1   |3   |8   |^...|

{code}



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

[jira] [Updated] (IGNITE-4988) Web Console: Cleanup and refactor VisorXxx tasks and DTO for ignite-2.0

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-4988:
-
Fix Version/s: 2.0

> Web Console: Cleanup and refactor VisorXxx tasks and DTO for ignite-2.0
> ---
>
> Key: IGNITE-4988
> URL: https://issues.apache.org/jira/browse/IGNITE-4988
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-5020) Client node failed with NPE

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-5020:
---
Attachment: ignite-b252f532.0.log
ignite-d11f70e0.0.log
ignite-a48cdc72.0.log
ignite-be032f32.0.log

> Client node failed with NPE
> ---
>
> Key: IGNITE-5020
> URL: https://issues.apache.org/jira/browse/IGNITE-5020
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Pavel Konstantinov
>Priority: Blocker
> Fix For: 2.0
>
> Attachments: ignite-a48cdc72.0.log, ignite-b252f532.0.log, 
> ignite-be032f32.0.log, ignite-d11f70e0.0.log
>
>
> Start 2 server nodes
> Start client
> Stop server nodes
> {code}
> [11:12:58,181][INFO][tcp-client-disco-msg-worker-#5%tester%][TcpDiscoverySpi] 
> Client node disconnected from cluster, will try to reconnect with new id 
> [newId=62cb8b71-4fe1-4fc7-b60b-236063ce9571, 
> prevId=a48cdc72-d9b2-46db-b07f-3250610df1f8, locNode=TcpDiscoveryNode 
> [id=a48cdc72-d9b2-46db-b07f-3250610df1f8, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 192.168.1.40, 192.168.56.1], sockAddrs=[/192.168.1.40:0, /0:0:0:0:0:0:0:1:0, 
> /127.0.0.1:0, /192.168.56.1:0], discPort=0, order=4, intOrder=0, 
> lastExchangeTime=1492575133264, loc=true, ver=2.0.0#20170418-sha1:6a1d263d, 
> isClient=true]]
> [11:12:59,580][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
> igfs-data
> [11:12:59,586][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
> offheap-sorted-100
> [11:12:59,588][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
> c_replicated
> [11:12:59,591][INFO][sys-#30%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned2
> [11:12:59,591][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
> offheap-fifo-100
> [11:12:59,597][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
> oh_partitioned
> [11:12:59,597][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
> near-lru-100
> [11:12:59,601][INFO][sys-#35%tester%][GridCacheProcessor] Stopped cache: 
> ttl_partitioned
> [11:12:59,603][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned3
> [11:12:59,603][INFO][sys-#33%tester%][GridCacheProcessor] Stopped cache: 
> offheap-lru-100
> [11:12:59,604][INFO][sys-#27%tester%][GridCacheProcessor] Stopped cache: 
> near-sorted-100
> [11:12:59,608][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned
> [11:12:59,608][SEVERE][exchange-worker-#36%tester%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7, 
> minorTopVer=0], nodeId=62cb8b71, evt=NODE_JOINED]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.fetchAffinityOnJoin(CacheAffinitySharedManager.java:953)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onClientEvent(CacheAffinitySharedManager.java:649)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClientNodeEvent(GridDhtPartitionsExchangeFuture.java:739)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:549)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Start server node



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

[jira] [Updated] (IGNITE-5020) Client node failed with NPE

[Pavel Konstantinov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Konstantinov updated IGNITE-5020:
---
Description: 
Start 2 server nodes
Start client
Stop server nodes
{code}
[11:12:58,181][INFO][tcp-client-disco-msg-worker-#5%tester%][TcpDiscoverySpi] 
Client node disconnected from cluster, will try to reconnect with new id 
[newId=62cb8b71-4fe1-4fc7-b60b-236063ce9571, 
prevId=a48cdc72-d9b2-46db-b07f-3250610df1f8, locNode=TcpDiscoveryNode 
[id=a48cdc72-d9b2-46db-b07f-3250610df1f8, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
192.168.1.40, 192.168.56.1], sockAddrs=[/192.168.1.40:0, /0:0:0:0:0:0:0:1:0, 
/127.0.0.1:0, /192.168.56.1:0], discPort=0, order=4, intOrder=0, 
lastExchangeTime=1492575133264, loc=true, ver=2.0.0#20170418-sha1:6a1d263d, 
isClient=true]]
[11:12:59,580][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
igfs-data
[11:12:59,586][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
offheap-sorted-100
[11:12:59,588][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
c_replicated
[11:12:59,591][INFO][sys-#30%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned2
[11:12:59,591][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
offheap-fifo-100
[11:12:59,597][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
oh_partitioned
[11:12:59,597][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
near-lru-100
[11:12:59,601][INFO][sys-#35%tester%][GridCacheProcessor] Stopped cache: 
ttl_partitioned
[11:12:59,603][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned3
[11:12:59,603][INFO][sys-#33%tester%][GridCacheProcessor] Stopped cache: 
offheap-lru-100
[11:12:59,604][INFO][sys-#27%tester%][GridCacheProcessor] Stopped cache: 
near-sorted-100
[11:12:59,608][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned
[11:12:59,608][SEVERE][exchange-worker-#36%tester%][GridDhtPartitionsExchangeFuture]
 Failed to reinitialize local partitions (preloading will be stopped): 
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7, 
minorTopVer=0], nodeId=62cb8b71, evt=NODE_JOINED]
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.fetchAffinityOnJoin(CacheAffinitySharedManager.java:953)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onClientEvent(CacheAffinitySharedManager.java:649)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClientNodeEvent(GridDhtPartitionsExchangeFuture.java:739)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:549)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}
Start server node

  was:
{code}
[11:12:58,181][INFO][tcp-client-disco-msg-worker-#5%tester%][TcpDiscoverySpi] 
Client node disconnected from cluster, will try to reconnect with new id 
[newId=62cb8b71-4fe1-4fc7-b60b-236063ce9571, 
prevId=a48cdc72-d9b2-46db-b07f-3250610df1f8, locNode=TcpDiscoveryNode 
[id=a48cdc72-d9b2-46db-b07f-3250610df1f8, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
192.168.1.40, 192.168.56.1], sockAddrs=[/192.168.1.40:0, /0:0:0:0:0:0:0:1:0, 
/127.0.0.1:0, /192.168.56.1:0], discPort=0, order=4, intOrder=0, 
lastExchangeTime=1492575133264, loc=true, ver=2.0.0#20170418-sha1:6a1d263d, 
isClient=true]]
[11:12:59,580][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
igfs-data
[11:12:59,586][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
offheap-sorted-100
[11:12:59,588][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
c_replicated
[11:12:59,591][INFO][sys-#30%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned2
[11:12:59,591][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
offheap-fifo-100
[11:12:59,597][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
oh_partitioned
[11:12:59,597][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
near-lru-100
[11:12:59,601][INFO][sys-#35%tester%][GridCacheProcessor] Stopped cache: 
ttl_partitioned
[11:12:59,603][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned3
[11:12:59,603][INFO][sys-#33%tester%][GridCacheProcessor] Stopped cache: 
offheap-lru-100
[11:12:59,604][INFO][sys-#27%tester%][GridCacheProcessor] Stopped cache: 
near-sorted-100
[11:12:59,608][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned
[11:12:59,608][SEVERE][exchange-worker-#36%tester%][GridDhtPartitionsExchangeFuture]
 Failed to reinitialize local partitions (preloading will be stopped

[jira] [Created] (IGNITE-5020) Client node failed with NPE

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5020:
--

 Summary: Client node failed with NPE
 Key: IGNITE-5020
 URL: https://issues.apache.org/jira/browse/IGNITE-5020
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.0
Reporter: Pavel Konstantinov
Priority: Blocker
 Fix For: 2.0


{code}
[11:12:58,181][INFO][tcp-client-disco-msg-worker-#5%tester%][TcpDiscoverySpi] 
Client node disconnected from cluster, will try to reconnect with new id 
[newId=62cb8b71-4fe1-4fc7-b60b-236063ce9571, 
prevId=a48cdc72-d9b2-46db-b07f-3250610df1f8, locNode=TcpDiscoveryNode 
[id=a48cdc72-d9b2-46db-b07f-3250610df1f8, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
192.168.1.40, 192.168.56.1], sockAddrs=[/192.168.1.40:0, /0:0:0:0:0:0:0:1:0, 
/127.0.0.1:0, /192.168.56.1:0], discPort=0, order=4, intOrder=0, 
lastExchangeTime=1492575133264, loc=true, ver=2.0.0#20170418-sha1:6a1d263d, 
isClient=true]]
[11:12:59,580][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
igfs-data
[11:12:59,586][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
offheap-sorted-100
[11:12:59,588][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
c_replicated
[11:12:59,591][INFO][sys-#30%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned2
[11:12:59,591][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
offheap-fifo-100
[11:12:59,597][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
oh_partitioned
[11:12:59,597][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
near-lru-100
[11:12:59,601][INFO][sys-#35%tester%][GridCacheProcessor] Stopped cache: 
ttl_partitioned
[11:12:59,603][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned3
[11:12:59,603][INFO][sys-#33%tester%][GridCacheProcessor] Stopped cache: 
offheap-lru-100
[11:12:59,604][INFO][sys-#27%tester%][GridCacheProcessor] Stopped cache: 
near-sorted-100
[11:12:59,608][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
c_partitioned
[11:12:59,608][SEVERE][exchange-worker-#36%tester%][GridDhtPartitionsExchangeFuture]
 Failed to reinitialize local partitions (preloading will be stopped): 
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7, 
minorTopVer=0], nodeId=62cb8b71, evt=NODE_JOINED]
java.lang.NullPointerException
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.fetchAffinityOnJoin(CacheAffinitySharedManager.java:953)
at 
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onClientEvent(CacheAffinitySharedManager.java:649)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClientNodeEvent(GridDhtPartitionsExchangeFuture.java:739)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:549)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
{code}



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

[jira] [Updated] (IGNITE-1403) forOldest() cluster group returns predicate that is not updated when topology changes

[Valentin Kulichenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Valentin Kulichenko updated IGNITE-1403:

Fix Version/s: (was: 2.1)
   2.0

> forOldest() cluster group returns predicate that is not updated when topology 
> changes
> -
>
> Key: IGNITE-1403
> URL: https://issues.apache.org/jira/browse/IGNITE-1403
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 2.0
>
>
> {{AgeClusterGroup}} that implements {{forOldest()}} and {{forYoungest}} 
> cluster groups is dynamically updated when topology changes. But the 
> predicate that can be acquired from this group via {{predicate()}} method is 
> static, which is incorrect.



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

[jira] [Commented] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973399#comment-15973399
 ] 

Denis Magda commented on IGNITE-3429:
-

Binary resolvers based workaround is no longer applicable for 2.0. The issue 
has to be fixed differently. See the discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/Stable-binary-key-representation-td15904.html

> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache, Hibernate L2 cache
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>Priority: Blocker
> Fix For: 2.0
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries 
> in the Hibernate L2 cache. This class contains {{type}} field and custom 
> {{equals}} logic where the type is used as a helper and does not participate 
> in comparison. Instances of the same type are producing different hash codes 
> in different JVMs, which actually breaks comparison when binary format is 
> used, where byte arrays are compared.
> The issue is described in more detail here: 
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities



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

[jira] [Updated] (IGNITE-3429) org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda updated IGNITE-3429:

Priority: Blocker  (was: Major)

> org.hibernate.cache.spi.CacheKey not properly serialized by binary marshaller
> -
>
> Key: IGNITE-3429
> URL: https://issues.apache.org/jira/browse/IGNITE-3429
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache, Hibernate L2 cache
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>Priority: Blocker
> Fix For: 2.0
>
>
> {{org.hibernate.cache.spi.CacheKey}} is a class used as a key for all entries 
> in the Hibernate L2 cache. This class contains {{type}} field and custom 
> {{equals}} logic where the type is used as a helper and does not participate 
> in comparison. Instances of the same type are producing different hash codes 
> in different JVMs, which actually breaks comparison when binary format is 
> used, where byte arrays are compared.
> The issue is described in more detail here: 
> http://stackoverflow.com/questions/38132263/apache-ignite-as-hibernate-l2-cache-storing-duplicate-entities



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

[jira] [Assigned] (IGNITE-4898) Add path to ODBC driver installers to platforms\cpp\odbc\README.txt

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-4898:
---

Assignee: Denis Magda  (was: Igor Sapego)

> Add path to ODBC driver installers to platforms\cpp\odbc\README.txt
> ---
>
> Key: IGNITE-4898
> URL: https://issues.apache.org/jira/browse/IGNITE-4898
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Irina Zaporozhtseva
>Assignee: Denis Magda
> Fix For: 2.0
>
>
> Add path to ODBC driver installers (/cpp/bin/odbc/) to 
> platforms\cpp\odbc\README.txt:
> "There are two ways to install ODBC driver currently. The first one is to use
> 32-bit or 64-bit installer. This is the most simple way and you are 
> recommended to stick to it by default."



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

[jira] [Updated] (IGNITE-2216) Duplicate field names with aliases do not work in queries.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2216:

Fix Version/s: (was: 2.0)
   2.1

> Duplicate field names with aliases do not work in queries.
> --
>
> Key: IGNITE-2216
> URL: https://issues.apache.org/jira/browse/IGNITE-2216
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, SQL
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-5010) DLL: Add dynamic index create-drop tests for geo-spacial indexes

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5010:

Summary: DLL: Add dynamic index create-drop tests for geo-spacial indexes  
(was: Add dynamic index create-drop tests for geo-spacial indexes)

> DLL: Add dynamic index create-drop tests for geo-spacial indexes
> 
>
> Key: IGNITE-5010
> URL: https://issues.apache.org/jira/browse/IGNITE-5010
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>
> Simple create-drop tests should be enough. They should reside in 
> {{ignite-geospatial}} module.



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

[jira] [Updated] (IGNITE-4997) DDL: Make sure dynamic schema state is re-created properly after client re-connect

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4997:

Summary: DDL: Make sure dynamic schema state is re-created properly after 
client re-connect  (was: Make sure dynamic schema state is re-created properly 
after client re-connect)

> DDL: Make sure dynamic schema state is re-created properly after client 
> re-connect
> --
>
> Key: IGNITE-4997
> URL: https://issues.apache.org/jira/browse/IGNITE-4997
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-3521) IGFS: Remove "max space" notion.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3521:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Remove "max space" notion.
> 
>
> Key: IGNITE-3521
> URL: https://issues.apache.org/jira/browse/IGNITE-3521
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> We have "max space" concept in IGFS which governs maximum amount of local 
> data available for IGFS. This concept looks a bit weird because we do not 
> have the same thing in caches. 
> Moreover, we have several conflicting configuration parameters:
> 1) {{IgfsPerBlockLruEvictionPolicy}} where we also can specify maximum size.
> 2) {{CacheConfiguration.offheapMaxMemory}} which also governs evictions.
> It looks like we should simply remove "max space" property from IGFS 
> configuration and do not control it anyhow.



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

[jira] [Updated] (IGNITE-3520) IGFS: Remove task execution methods.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3520:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Remove task execution methods.
> 
>
> Key: IGNITE-3520
> URL: https://issues.apache.org/jira/browse/IGNITE-3520
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> We have several task execution methods on IGFS API. They were never used in 
> practice because normally users will achieve the same things using Hadoop or 
> Spark frameworks. 
> I propose to remove them altogether. This way we will be able to focus solely 
> on file system semantics.



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

[jira] [Updated] (IGNITE-3549) IGFS: Switch "accessTime" and "modification" time in setTimes() method.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3549:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Switch "accessTime" and "modification" time in setTimes() method.
> ---
>
> Key: IGNITE-3549
> URL: https://issues.apache.org/jira/browse/IGNITE-3549
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> This way we will be more similar to Hadoop {{FileSystem}} API where 
> modification time comes first.



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

[jira] [Resolved] (IGNITE-3550) IGFS: Improve usability for Apache Ignite 2.0.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-3550.
-
Resolution: Fixed

> IGFS: Improve usability for Apache Ignite 2.0.
> --
>
> Key: IGNITE-3550
> URL: https://issues.apache.org/jira/browse/IGNITE-3550
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.0
>
>
> This is an umbrella ticket to host all IGFS usability improvements targeted 
> for Apache Ignite 2.0.



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

[jira] [Updated] (IGNITE-3524) IGFS: Do not allow nulls for FileSystemConfiguration.name.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3524:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Do not allow nulls for FileSystemConfiguration.name.
> --
>
> Key: IGNITE-3524
> URL: https://issues.apache.org/jira/browse/IGNITE-3524
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> As a part of our general approach, let's do not allow nulls as IGFS names.



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

[jira] [Updated] (IGNITE-3523) IGFS: Remove "initialize default path modes" feature.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3523:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Remove "initialize default path modes" feature.
> -
>
> Key: IGNITE-3523
> URL: https://issues.apache.org/jira/browse/IGNITE-3523
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Currently IGFS can create several paths by default, which will forcefully 
> work in different modes. This will never require in practice, but caused some 
> problems, e.g. performance degradation in our Hadoop FileSystem implementaions
> Let's just remove that feature along with relevant property in 
> {{FileSystemConfiguration}}.



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

[jira] [Updated] (IGNITE-4767) rollback exception hides the origin exception (e.g. commit)

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4767:

Fix Version/s: (was: 2.0)
   2.1

> rollback exception hides the origin exception (e.g. commit)
> ---
>
> Key: IGNITE-4767
> URL: https://issues.apache.org/jira/browse/IGNITE-4767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, general
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
>
> There is too much code places like:
> {noformat}
> try {
>   return txFuture.get();
> }
> catch (IgniteCheckedException e) {
>   tx.rollbackAsync();
>   throw e;
> }
> {noformat}
> where an error upon rollback hides the actual exception {{e}}.
> This should be implemented in the way like try-with-resources does:
> {noformat}
> try {
>   return txFuture.get();
> }
> catch (IgniteCheckedException e1) {
>   try {
>   tx.rollbackAsync();
>   }
>   catch (Throwable inner) {
>   e.addSuppressed(inner);
>   }
>   throw e;
> }
> {noformat}



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

[jira] [Commented] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973362#comment-15973362
 ] 

Vladimir Ozerov commented on IGNITE-4523:
-

[~ascherbakov], [~sergi.vladykin], I propose to move the ticket to {{2.1}}. Too 
late for major changes in {{2.0}} scope.

> Allow distributed SQL query execution over explicit set of partitions
> -
>
> Key: IGNITE-4523
> URL: https://issues.apache.org/jira/browse/IGNITE-4523
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, SQL
>Affects Versions: 1.8
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>  Labels: important
> Fix For: 2.0
>
>
> 3Currently distributed SQL query is executed on all nodes containing primary 
> partitions for a cache, sending map query requests on all nodes in grid.
> Sometimes we know in advance which partitions hold a data for query, on 
> example, in case of custom affinity function. 
> Therefore it's possible to reduce number of nodes receiving map query request 
> by providing explicit set of partitions, which will give significant 
> performance advantage and traffic reduction in case of very large clusters.
> Internally we already have such functionality, so the only necessary thing is 
> to provide public API for what.



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

[jira] [Assigned] (IGNITE-3469) Get rid of deprecated APIs and entities

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov reassigned IGNITE-3469:
---

Assignee: (was: Alexey Kuznetsov)

> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>  Labels: important
> Fix For: 2.1
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Commented] (IGNITE-3469) Get rid of deprecated APIs and entities

[Vladimir Ozerov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973358#comment-15973358
 ] 

Vladimir Ozerov commented on IGNITE-3469:
-

[~agoncharuk], we did what we can. As it is time to freeze code changes, let's 
move the ticket to the next release. It is necessary to review outstanding 
deprecations and see what can be done. Most probably all remaining deprecations 
will be removed in AI 3.0.

> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
>  Labels: important
> Fix For: 2.1
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Updated] (IGNITE-3469) Get rid of deprecated APIs and entities

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3469:

Fix Version/s: (was: 2.0)
   2.1

> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kuznetsov
>  Labels: important
> Fix For: 2.1
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Resolved] (IGNITE-4547) Apache Ignite 2.0 quick and needed tasks

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-4547.
-
Resolution: Fixed

> Apache Ignite 2.0 quick and needed tasks
> 
>
> Key: IGNITE-4547
> URL: https://issues.apache.org/jira/browse/IGNITE-4547
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Denis Magda
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> The ticket contains a list of quick tasks that have to be resolved in Apache 
> 2.0 release.
> All the tickets have to be merged into ignite-2.0 branch. Forks have to be 
> created from ignite-2.0 as well:
> http://apache-ignite-developers.2346864.n4.nabble.com/What-branch-to-use-for-Apache-Ignite-2-0-development-td12800.html
> Need more details? Ask Ignite developers:
> https://ignite.apache.org/community/resources.html#ask



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

[jira] [Updated] (IGNITE-4501) Improvement of connection in a cluster of new node

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4501:

Labels: important  (was: )

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
>  Labels: important
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



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

[jira] [Updated] (IGNITE-2313) Need to add a mode to fail atomic operations within a transaction

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-2313:

Fix Version/s: (was: 2.0)
   2.1

> Need to add a mode to fail atomic operations within a transaction
> -
>
> Key: IGNITE-2313
> URL: https://issues.apache.org/jira/browse/IGNITE-2313
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ryabov Dmitrii
>Priority: Blocker
> Fix For: 2.1
>
>
> Currently atomic operations within a transaction succeed without alarming a 
> user that no transaction really occurs. We should add a mode to fail such 
> operations (such mode should be turned off by default).
> New transaction configuration flag (default is {{false}}):
> {code}TransactionConfiguration.isAllowAtomicUpdatesInTransaction(){code}
> If the flag is violated, we should throw an exception with the following 
> error message: {{Transaction spans operations on atomic cache (consider 
> setting TransactionConfiguration.isAllowAttomicUpdatesInTransaction() flag to 
> true)}}



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

[jira] [Updated] (IGNITE-3558) Affinity task hangs when Collision SPI produces a lot of job rejections & Failover SPI produces many attempts

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3558:

Fix Version/s: (was: 2.0)
   2.1

> Affinity task hangs when Collision SPI produces a lot of job rejections & 
> Failover SPI produces many attempts
> -
>
> Key: IGNITE-3558
> URL: https://issues.apache.org/jira/browse/IGNITE-3558
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>  Time Spent: 3h
>  Remaining Estimate: 0h
>
> The test to reproduce:
> {{IgniteCacheLockPartitionOnAffinityRunWithCollisionSpiTest.testJobFinishing}}
> *Root cause*
> {{GridJobExecuteResponse}} isn't set from target node because there is a 
> confusion with {{GridJobWorker}} instances in the {{CollisionContext}}.
> *Suggestion*
> The method {{GridJobProcessor.CollisionJobContext.cancel()}}
> use {{passiveJobs.remove(jobWorker.getJobId(), jobWorker)}}. 
> *passiveJobs* is a ConcurrentHashMap and {{GridJobWorker.equals()}} 
> implements as a equation of jobId.
> So, when two thread try to cancel the two workers with *the same jobIds* we 
> have the case:
> - thread0 remove jobWorker0 & cancel jobWorker0.
> - thread0 put jobWorker1 (because jobWorker0 already removed);
> - thread1: (has a copy of jobWorker0) and try to cancel it.
> - thread1: remove jobWorker1 instead of jobWorker0 (because jobId is used to 
> identify);
> - thread1: doesn't send ExecuteResponse because jobWorker0 has been canceled.
> *Proposal*
> Try to use system default equals for the GridJobWorker



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

[jira] [Updated] (IGNITE-1267) JobStealingCollisionSpi never sends jobs to a node that joined after task was executed

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1267:

Fix Version/s: (was: 2.0)
   2.1

> JobStealingCollisionSpi never sends jobs to a node that joined after task was 
> executed
> --
>
> Key: IGNITE-1267
> URL: https://issues.apache.org/jira/browse/IGNITE-1267
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>  Labels: user-request
> Fix For: 2.1
>
>
> Corresponding user thread (contains detailed description of the scenario that 
> doesn't work): 
> http://apache-ignite-users.70518.x6.nabble.com/Dynamic-ComputeTask-distribution-with-new-nodes-td997.html
> Essentially, {{JobStealingCollisionSpi}} always skips jobs that are not in 
> task topology (see line 713). Task topology is static and created when task 
> is executed, so newly joined node can't steal jobs. I think it should be able 
> to do this if it satisfies initial cluster group predicate.



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

[jira] [Updated] (IGNITE-1403) forOldest() cluster group returns predicate that is not updated when topology changes

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1403:

Fix Version/s: (was: 2.0)
   2.1

> forOldest() cluster group returns predicate that is not updated when topology 
> changes
> -
>
> Key: IGNITE-1403
> URL: https://issues.apache.org/jira/browse/IGNITE-1403
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
> Fix For: 2.1
>
>
> {{AgeClusterGroup}} that implements {{forOldest()}} and {{forYoungest}} 
> cluster groups is dynamically updated when topology changes. But the 
> predicate that can be acquired from this group via {{predicate()}} method is 
> static, which is incorrect.



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

[jira] [Updated] (IGNITE-3939) Compact long zero values binary representation

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3939:

Fix Version/s: (was: 2.0)
   2.1

> Compact long zero values binary representation
> --
>
> Key: IGNITE-3939
> URL: https://issues.apache.org/jira/browse/IGNITE-3939
> Project: Ignite
>  Issue Type: Improvement
>  Components: binary
>Affects Versions: 1.7
>Reporter: Andrew Mashenkov
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.1
>
>
> We can use separate type for Long zero values and exclude 8-byte value from 
> binary representation. This will reduce memory footprint and network load.
> Compatibility with previous versions MUST be preserved.



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

[jira] [Updated] (IGNITE-4865) Non-informative error message on using GridClientOptimizedMarshaller with unknown task classes

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4865:

Fix Version/s: (was: 2.0)
   2.1

> Non-informative error message on using GridClientOptimizedMarshaller with 
> unknown task classes
> --
>
> Key: IGNITE-4865
> URL: https://issues.apache.org/jira/browse/IGNITE-4865
> Project: Ignite
>  Issue Type: Improvement
>  Components: rest
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Vladimir Ozerov
> Fix For: 2.1
>
>
> Upon {{GridClientCompute.execute()}} I get non-informative error if a task 
> class is not present in {{classnames.properties}}. It occurs when 
> {{GridClient}} was configured to use {{GridClientOptimizedMarshaller}}.
> {noformat}
> Closing NIO session because of unhandled exception [cls=class 
> o.a.i.i.util.nio.GridNioException, msg=class o.a.i.IgniteCheckedException: 
> Failed to deserialize object with given class loader: null]
> {noformat}
> There is two problems:
> * Actual problem was hidden
> {noformat}
> Caused by: java.lang.UnsupportedOperationException
> at 
> org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller$ClientMarshallerContext.className(GridClientOptimizedMarshaller.java:137)
> at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:174)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedMarshallerUtils.classDescriptor(OptimizedMarshallerUtils.java:266)
> at 
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readObjectOverride(OptimizedObjectInputStream.java:318)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:367)
> {noformat}
> * Even reading the cause we don't understand what is wrong
> What to do:
> * Log stacktrace every time
> * Throw UnsupportedOperationException with informative message.



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

[jira] [Updated] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture()

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-1948:

Fix Version/s: (was: 2.0)
   2.1

> ClusterTopologyCheckedException can return null for retryReadyFuture()
> --
>
> Key: IGNITE-1948
> URL: https://issues.apache.org/jira/browse/IGNITE-1948
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Alexander Menshikov
> Fix For: 2.1
>
>
> It was noted that {{ClusterTopologyCheckedException}} ready future can be 
> null.
> Go though all the places where this kind of exception is being initialized 
> and check why the ready future is not set in some cases.



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

[jira] [Commented] (IGNITE-1439) CPP: Implement futures.

[Igor Sapego (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973180#comment-15973180
 ] 

Igor Sapego commented on IGNITE-1439:
-

Implemented prototype for Windows. As we have to support Windows XP I can't use 
Condition Variables 
(https://msdn.microsoft.com/en-us/library/windows/desktop/ms682052(v=vs.85).aspx),
 which would be perfect for cross-platform solution. So instead I used 
Manual-reset Event objects 
(https://msdn.microsoft.com/en-us/library/windows/desktop/ms682655(v=vs.85).aspx)
 and critical sections. Current implementation seems to be correct though I 
have not tested it properly yet.

Some details of current implementation:
To create {{Future}} one needs to first create {{Promise}} object. {{Promise}} 
is object which used to set value or error for the linked {{Future}} objects.
Once {{Promise}} created, one can call {{Promise::GetFuture()}} to get instance 
of related {{Future}} object. There may be unlimited number of futures for 
every {{Promise}}. {{Promise}} can't be copied though. Error or value can be 
set only once for the {{Promise}}. If someone tries to set value or error to a 
set {{Promise}} this will result in exception. If {{Promise}} instance gets 
destructed before any value or error has been set error is automatically set 
for all linked {{Future}} objects.

On any {{Future}} object user can call either {{Wait}}, {{WaitFor}} or {{Get}} 
methods. All these methods are blocking. If {{Get}} called on future for which 
error has been set this will result in exception.

Obviously enough, {{Future}} class is a part of public API, while {{Promise}} 
is internal class.

> CPP: Implement futures.
> ---
>
> Key: IGNITE-1439
> URL: https://issues.apache.org/jira/browse/IGNITE-1439
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-4952) Delete swap-related functionality

[Dmitriy Govorukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Govorukhin updated IGNITE-4952:
---
Labels: general  (was: )

> Delete swap-related functionality
> -
>
> Key: IGNITE-4952
> URL: https://issues.apache.org/jira/browse/IGNITE-4952
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>  Labels: general
> Fix For: 2.0
>
>
> h2. Notes
> As swap storage was removed in 
> [IGNITE-3477|https://issues.apache.org/jira/browse/IGNITE-3477] there is no 
> need to keep swap-related functionality in Ignite codebase.
> h2. Acceptance Criteria
> # Swap-related functionality is removed from codebase.
> # All tests verifying swap functionality are removed from tests set.



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

[jira] [Updated] (IGNITE-4952) Delete swap-related functionality

[Dmitriy Govorukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Govorukhin updated IGNITE-4952:
---
Fix Version/s: 2.0

> Delete swap-related functionality
> -
>
> Key: IGNITE-4952
> URL: https://issues.apache.org/jira/browse/IGNITE-4952
> Project: Ignite
>  Issue Type: Task
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>  Labels: general
> Fix For: 2.0
>
>
> h2. Notes
> As swap storage was removed in 
> [IGNITE-3477|https://issues.apache.org/jira/browse/IGNITE-3477] there is no 
> need to keep swap-related functionality in Ignite codebase.
> h2. Acceptance Criteria
> # Swap-related functionality is removed from codebase.
> # All tests verifying swap functionality are removed from tests set.



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

[jira] [Assigned] (IGNITE-4961) Document Page Memory API, Architecture and Behavior

[Denis Magda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Denis Magda reassigned IGNITE-4961:
---

Assignee: Prachi Garg  (was: Alexey Goncharuk)

> Document Page Memory API, Architecture and Behavior
> ---
>
> Key: IGNITE-4961
> URL: https://issues.apache.org/jira/browse/IGNITE-4961
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.0
>
>
> The goal of this ticket is to provide extensive documentation around the new 
> page memory architecture introduced in Apache Ignite 2.0.
> Refer to IGNITE-3477 and do the following as a part of this ticket:
> * page memory architecture, advantages, and usage.
> * page memory policies (IGNITE-4960).
> * rework or discontinue Off-Heap Memory page 
> (https://apacheignite.readme.io/docs/off-heap-memory) that lists all the 
> memory tiers supported in versions 1.x. For instance, the swap space is no 
> longer available (IGNITE-4736) and the Java heap is no more a default one and 
> used just as a cache of the page memory (IGNITE-4535).
> Once the Java documentation is ready, assign the ticket to [~ptupitsyn] and 
> [~isapego] who will create .NET and C++ counterparts following a Java 
> template.



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

[jira] [Commented] (IGNITE-4961) Document Page Memory API, Architecture and Behavior

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973032#comment-15973032
 ] 

Denis Magda commented on IGNITE-4961:
-

[~pgarg], please start reviewing the doc. Ignore, "TODO" occurrences for now, 
they will be fixed later.

> Document Page Memory API, Architecture and Behavior
> ---
>
> Key: IGNITE-4961
> URL: https://issues.apache.org/jira/browse/IGNITE-4961
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.0
>
>
> The goal of this ticket is to provide extensive documentation around the new 
> page memory architecture introduced in Apache Ignite 2.0.
> Refer to IGNITE-3477 and do the following as a part of this ticket:
> * page memory architecture, advantages, and usage.
> * page memory policies (IGNITE-4960).
> * rework or discontinue Off-Heap Memory page 
> (https://apacheignite.readme.io/docs/off-heap-memory) that lists all the 
> memory tiers supported in versions 1.x. For instance, the swap space is no 
> longer available (IGNITE-4736) and the Java heap is no more a default one and 
> used just as a cache of the page memory (IGNITE-4535).
> Once the Java documentation is ready, assign the ticket to [~ptupitsyn] and 
> [~isapego] who will create .NET and C++ counterparts following a Java 
> template.



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

[jira] [Updated] (IGNITE-5019) Deadlock in GridCacheVariableTopologySelfTest.testNodeStop

[Dmitriy Govorukhin (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Govorukhin updated IGNITE-5019:
---
Attachment: threads_report.txt

> Deadlock in GridCacheVariableTopologySelfTest.testNodeStop
> --
>
> Key: IGNITE-5019
> URL: https://issues.apache.org/jira/browse/IGNITE-5019
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
> Attachments: threads_report.txt
>
>




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

[jira] [Commented] (IGNITE-4719) Add documentation of current checks at Ignite-startup

[Vyacheslav Daradur (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973027#comment-15973027
 ] 

Vyacheslav Daradur commented on IGNITE-4719:


[~dmagda],
The reason of this task is [Yakov 
comment|https://issues.apache.org/jira/browse/IGNITE-4374?focusedCommentId=15861253=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15861253]
bq. it would be cool if you document current checks on readme.io
I thought about the task as about descriptions of the suggestions which are 
outputed at Ignite startup.

bq. Could you prepare a list of recommendations that are not on the page above?
In this case this task doesn't make sense, because all the described checks 
relate to the article:
- all OS suggestions are already listed;
- almost all JVM suggestions are already listed as list of recommended JVM 
options without explanation;

In that case it makes sense just add "-XX:MaxDirectMemorySize" with predefined 
value to described configurations at the article and close the task as 
unnecessary or duplicated.

> Add documentation of current checks at Ignite-startup
> -
>
> Key: IGNITE-4719
> URL: https://issues.apache.org/jira/browse/IGNITE-4719
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Attachments: suggestions.docx
>
>




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

[jira] [Created] (IGNITE-5019) Deadlock in GridCacheVariableTopologySelfTest.testNodeStop

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5019:
--

 Summary: Deadlock in GridCacheVariableTopologySelfTest.testNodeStop
 Key: IGNITE-5019
 URL: https://issues.apache.org/jira/browse/IGNITE-5019
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Dmitriy Govorukhin
Assignee: Dmitriy Govorukhin
 Fix For: 2.0






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

[jira] [Created] (IGNITE-5018) review and improve javadocs in ML module

[Oleg Ignatenko (JIRA)]

Oleg Ignatenko created IGNITE-5018:
--

 Summary: review and improve javadocs in ML module
 Key: IGNITE-5018
 URL: https://issues.apache.org/jira/browse/IGNITE-5018
 Project: Ignite
  Issue Type: Task
Reporter: Oleg Ignatenko
Assignee: Oleg Ignatenko
Priority: Minor
 Fix For: 2.0


Review and improve javadocs in Ignite ML module (added per IGNITE-4572). To 
name a few, add descriptions for constructor parameters in classes 
{{CacheMatrix}}, {{CacheMatrixStorage}}, {{RandomVector}}. Etc.



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

[jira] [Commented] (IGNITE-4719) Add documentation of current checks at Ignite-startup

[Denis Magda (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972966#comment-15972966
 ] 

Denis Magda commented on IGNITE-4719:
-

[~daradurvs], thanks! However, looks like some of the suggestions are already 
listed there:
https://apacheignite.readme.io/docs/jvm-and-system-tuning

Could you prepare a list of recommendations that are not on the page above?

> Add documentation of current checks at Ignite-startup
> -
>
> Key: IGNITE-4719
> URL: https://issues.apache.org/jira/browse/IGNITE-4719
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Attachments: suggestions.docx
>
>




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

[jira] [Updated] (IGNITE-4964) Document Machine Learning Grid (Distributed Algebra Implementation)

[Oleg Ignatenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Ignatenko updated IGNITE-4964:
---
Attachment: ignite-ml.readme-io.txt

> Document Machine Learning Grid (Distributed Algebra Implementation)
> ---
>
> Key: IGNITE-4964
> URL: https://issues.apache.org/jira/browse/IGNITE-4964
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Denis Magda
>Assignee: Oleg Ignatenko
> Fix For: 2.0
>
> Attachments: ignite-ml.readme-io.txt, ignite-ml.readme-io.txt, 
> ignite-ml.readme-io.txt
>
>
> In Apache Ignite 2.0 we introduce support for distributed algebra on top of 
> Ignite. This considered to be a foundation of Ignite's Machine Learning 
> framework discussed here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Adding-ML-to-Ignite-IGNITE-4572-td13936.html
> Let's make an overview of the current implementation, its usage, and refer to 
> developed examples as a part of the readme.io documentation. Here is an 
> invisible page created for this purpose:
> https://dash.readme.io/project/apacheignite/v1.9/docs/distributed-algebra
> Please assign the ticket on [~dmagda] for the final review.



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

[jira] [Updated] (IGNITE-5001) .NET: Tests cleanup

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-5001:
---
Description: 
* Use {{GetTestConfiguration}} where possible
* Make sure {{Localhost}} is set in all other cases to avoid external node 
discovery
* Remove binary type configuration where it is not necessary
* Get rid of Spring XML where it is not needed (Events, Messaging, etc)
* Replace try-catch with {{Assert.Throws}} where possible
* Make sure {{Ignition.StopAll}} is present where needed

  was:
* Use {{GetTestConfiguration}} where possible
* Make sure {{Localhost}} is set in all other cases to avoid external node 
discovery
* Remove binary type configuration where it is not necessary
* Get rid of Spring XML where it is not needed (Events, Messaging, etc)


> .NET: Tests cleanup
> ---
>
> Key: IGNITE-5001
> URL: https://issues.apache.org/jira/browse/IGNITE-5001
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
> Fix For: 2.1
>
>
> * Use {{GetTestConfiguration}} where possible
> * Make sure {{Localhost}} is set in all other cases to avoid external node 
> discovery
> * Remove binary type configuration where it is not necessary
> * Get rid of Spring XML where it is not needed (Events, Messaging, etc)
> * Replace try-catch with {{Assert.Throws}} where possible
> * Make sure {{Ignition.StopAll}} is present where needed



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

[jira] [Commented] (IGNITE-4719) Add documentation of current checks at Ignite-startup

[Vyacheslav Daradur (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972868#comment-15972868
 ] 

Vyacheslav Daradur commented on IGNITE-4719:


[~pgarg], [~dmagda] please review the attached file.
I think it needs to be added under 
https://apacheignite.readme.io/docs/preparing-for-production
Thanks!

> Add documentation of current checks at Ignite-startup
> -
>
> Key: IGNITE-4719
> URL: https://issues.apache.org/jira/browse/IGNITE-4719
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Attachments: suggestions.docx
>
>




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

[jira] [Updated] (IGNITE-4719) Add documentation of current checks at Ignite-startup

[Vyacheslav Daradur (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Daradur updated IGNITE-4719:
---
Attachment: (was: suggestions.docx)

> Add documentation of current checks at Ignite-startup
> -
>
> Key: IGNITE-4719
> URL: https://issues.apache.org/jira/browse/IGNITE-4719
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Attachments: suggestions.docx
>
>




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

[jira] [Updated] (IGNITE-4719) Add documentation of current checks at Ignite-startup

[Vyacheslav Daradur (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Daradur updated IGNITE-4719:
---
Attachment: suggestions.docx

> Add documentation of current checks at Ignite-startup
> -
>
> Key: IGNITE-4719
> URL: https://issues.apache.org/jira/browse/IGNITE-4719
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Attachments: suggestions.docx
>
>




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

[jira] [Updated] (IGNITE-4719) Add documentation of current checks at Ignite-startup

[Vyacheslav Daradur (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vyacheslav Daradur updated IGNITE-4719:
---
Attachment: suggestions.docx

> Add documentation of current checks at Ignite-startup
> -
>
> Key: IGNITE-4719
> URL: https://issues.apache.org/jira/browse/IGNITE-4719
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Attachments: suggestions.docx
>
>




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

[jira] [Commented] (IGNITE-5008) Page Memory Throws Meaningless OOM exception if there is an issue in config

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972835#comment-15972835
 ] 

ASF GitHub Bot commented on IGNITE-5008:


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

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

IGNITE-5008 message of IgniteOutOfMemoryException was detailed



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

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

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

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


commit d6fc207693d0928ef615cc409054af067d5a079b
Author: Sergey Chugunov 
Date:   2017-04-18T14:37:59Z

IGNITE-5008 message of IgniteOutOfMemoryException was detailed




> Page Memory Throws Meaningless OOM exception if there is an issue in config
> ---
>
> Key: IGNITE-5008
> URL: https://issues.apache.org/jira/browse/IGNITE-5008
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Sergey Chugunov
>Priority: Blocker
>
> The ticket was created as a result of this discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/Memory-policies-examples-fails-td16717.html
> Presently a page memory can throw an OOM exception due to a misconfiguration. 
> The message of the exception has to point out to a problematic place directly 
> (size, ect.) so that the user can quickly fix it.



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

[jira] [Updated] (IGNITE-4479) Remove startTime() and duration() methods from IgniteFuture

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4479:

Fix Version/s: (was: 2.0)
   2.1

> Remove startTime() and duration() methods from IgniteFuture
> ---
>
> Key: IGNITE-4479
> URL: https://issues.apache.org/jira/browse/IGNITE-4479
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> These methods are of no use for users and should not be in future API. THe 
> only place where they are used is cache exchange manager. 
> We should remove these methods form all futures and leave them only for cache 
> exchange logic.



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

[jira] [Updated] (IGNITE-4480) Incorrect cancellation semantics in IgniteFuture

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4480:

Fix Version/s: (was: 2.0)
   2.1

> Incorrect cancellation semantics in IgniteFuture
> 
>
> Key: IGNITE-4480
> URL: https://issues.apache.org/jira/browse/IGNITE-4480
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> *Problem*
> Normally, if user invoke "cancel()" on future, he expects that it will be 
> completed immediately. E.g. this is how JDK {{CompletableFuture}} works. 
> However, this is not the case for Ignite - we inform user about cancellation 
> through flag, which is also not set properly in most cases.
> *Solution*
> 1) {{cancel()}} must complete future with special "CancellationException" 
> immediately.
> 2) {{isCancelled()}} method should be either removed or deprecated.
> 3{ We should add {{isCompletedExceptionally()}} method which will return 
> {{true}} in case future was completed with any kind of exception. This will 
> work similar to JDK {{CompletableFuture}}.



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

[jira] [Updated] (IGNITE-4890) Unable to create tables automatically because 'unconfigured columnfamily' error is not handled for older Cassandra versions

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4890:

Fix Version/s: (was: 2.0)
   2.1

> Unable to create tables automatically because 'unconfigured columnfamily' 
> error is not handled for older Cassandra versions
> ---
>
> Key: IGNITE-4890
> URL: https://issues.apache.org/jira/browse/IGNITE-4890
> Project: Ignite
>  Issue Type: Bug
>  Components: compatibility
>Affects Versions: 1.9
>Reporter: Venky Kandaswamy
>  Labels: patch
> Fix For: 2.1
>
>
> PROBLEM:
> When running Ignite with older Cassandra versions (i.e DSE 4.8.10, Cassandra 
> 2.1.6 or older), we noticed that only the first tabel in an Ignite config is 
> created and the others fail with 'unconfigured columnfamily' exception.
> SUGGESTED FIX:
> It appears that the error from Cassandra is changed in newer versions to 
> 'unconfigured table ...' and this is handled.  The conditions checked in 
> org.apache.ignite.cache.store.cassandra.common.CassandraHelper needs to be 
> modified to handle the older Cassandra errors. 
> We are submitting a patch to do that. 
> 13:44:28,753 ERROR com.walmartlabs.qarth.ignite.tests.utils.CacheStoreHelper 
> [main] - Failed to execute Cassandra CQL statement: insert into 
> "test1"."blob_test2" ("key", "value") values (?,?);
> class org.apache.ignite.IgniteException: Failed to execute Cassandra CQL 
> statement: insert into "test1"."blob_test2" ("key", "value") values (?,?);
>   at 
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:163)
>   at 
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore.write(CassandraCacheStore.java:276)
>   at 
> com.walmartlabs.qarth.ignite.tests.cassandra.CassandraDirectPersistenceTest.blobStrategyTest(CassandraDirectPersistenceTest.java:233)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at 
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
>   at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: class org.apache.ignite.IgniteException: Failed to prepare 
> Cassandra CQL statement: insert into "test1"."blob_test2" ("key", "value") 
> values (?,?);
>   at 
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.prepareStatement(CassandraSessionImpl.java:615)
>   at 
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:133)
>   ... 27 more
> Caused by: com.datastax.driver.core.exceptions.InvalidQueryException: 
> unconfigured columnfamily blob_test2
>   at 
> 

[jira] [Updated] (IGNITE-4645) Best effort to avoid extra copying in binary marshaller

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4645:

Fix Version/s: (was: 2.0)
   2.1

> Best effort to avoid extra copying in binary marshaller
> ---
>
> Key: IGNITE-4645
> URL: https://issues.apache.org/jira/browse/IGNITE-4645
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Reporter: Yakov Zhdanov
>Assignee: Igor Seliverstov
> Fix For: 2.1
>
>
> If we marshal a class that contain only primitives then we can predict the 
> final byte array size and avoid copies to grow array and final trimming.



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

[jira] [Updated] (IGNITE-3401) "Remote node ID is not as expected" errors at driver during load test

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3401:

Fix Version/s: (was: 2.0)
   2.1

> "Remote node ID is not as expected" errors at driver during load test
> -
>
> Key: IGNITE-3401
> URL: https://issues.apache.org/jira/browse/IGNITE-3401
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Ksenia Rybakova
> Fix For: 2.1
>
>
> A lot of errors at some drivers after several minutes after grid is up during 
> load test:
> {noformat}
> [14:33:42] (err) Failed to execute compound future reducer: Compound future 
> listener []class org.apache.ignite.IgniteCheckedException: Failed to send 
> message (node may have left the grid or TCP connection cannot be established 
> due to fir
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1193)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.submit(DataStreamerImpl.java:1378)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.update(DataStreamerImpl.java:1173)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.load0(DataStreamerImpl.java:756)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addDataInternal(DataStreamerImpl.java:568)
> at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:604)
> at 
> org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark$1.run(IgniteCacheRandomOperationBenchmark.java:383)
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to send 
> message to remote node: TcpDiscoveryNode 
> [id=11da20f5-87c5-4321-8163-ffef85f2d54c, addrs=[10.20.0.215, 127.0.0.1], 
> sockAddrs=[/127.0.0.1:47503, fosters-215/10.20.0
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1986)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1926)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1124)
> ... 7 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to connect 
> to node (is node still alive?). Make sure that each GridComputeTask and 
> GridCacheTransaction has a timeout set in order to prevent parties from 
> waiting forever
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2489)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2130)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2024)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:1960)
> ... 9 more
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> connect to address: fosters-215/10.20.0.215:47103
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2494)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> read remote node recovery handshake (connection closed).
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2699)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2361)
> ... 12 more
> Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> connect to address: /127.0.0.1:47103
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2494)
> ... 12 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Remote 
> node ID is not as expected [expected=11da20f5-87c5-4321-8163-ffef85f2d54c, 
> rcvd=03bc7d54-4fec-481d-af24-6f5408b32fe2]
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:2604)
> at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2361)
> ... 12 more
> {noformat}
> Tested version: 1.5.27
> Load config:
> - 7 hosts with 4 servers and 3 drivers each (28 servers and 21 

[jira] [Updated] (IGNITE-3526) IGFS: Review "perNodeBatchSize" and "perNodeParallelBatchCount" properties.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3526:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Review "perNodeBatchSize" and "perNodeParallelBatchCount" properties.
> ---
>
> Key: IGNITE-3526
> URL: https://issues.apache.org/jira/browse/IGNITE-3526
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> These properties are extremely weird form user perspective. We need to review 
> how they are actually used inside IGFS code and either remove them or 
> refactor to something more useful.



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

[jira] [Updated] (IGNITE-3526) IGFS: Review "perNodeBatchSize" and "perNodeParallelBatchCount" properties.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3526:

Fix Version/s: (was: 2.0)
   2.1

> IGFS: Review "perNodeBatchSize" and "perNodeParallelBatchCount" properties.
> ---
>
> Key: IGNITE-3526
> URL: https://issues.apache.org/jira/browse/IGNITE-3526
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> These properties are extremely weird form user perspective. We need to review 
> how they are actually used inside IGFS code and either remove them or 
> refactor to something more useful.



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

[jira] [Closed] (IGNITE-4927) Write behind - add an option to skip write coalescing

[Alexander Belyak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Belyak closed IGNITE-4927.


> Write behind - add an option to skip write coalescing
> -
>
> Key: IGNITE-4927
> URL: https://issues.apache.org/jira/browse/IGNITE-4927
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> Currently, the write-behind store is backed by a map, therefore when several 
> updates come to the same key, they are coalesced. 
> We need to introduce optional mode and back write-behind with a queue and 
> pass each  to a database.



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

[jira] [Resolved] (IGNITE-4927) Write behind - add an option to skip write coalescing

[Alexander Belyak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Belyak resolved IGNITE-4927.
--
Resolution: Duplicate  (was: Fixed)

> Write behind - add an option to skip write coalescing
> -
>
> Key: IGNITE-4927
> URL: https://issues.apache.org/jira/browse/IGNITE-4927
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> Currently, the write-behind store is backed by a map, therefore when several 
> updates come to the same key, they are coalesced. 
> We need to introduce optional mode and back write-behind with a queue and 
> pass each  to a database.



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

[jira] [Created] (IGNITE-5017) HTML formatted releases notes

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-5017:
-

 Summary: HTML formatted releases notes
 Key: IGNITE-5017
 URL: https://issues.apache.org/jira/browse/IGNITE-5017
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.9
Reporter: Sergey Kozlov
 Fix For: 2.0






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

[jira] [Closed] (IGNITE-4933) Need to add an option to write all updates in write-behind store

[Alexander Belyak (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Belyak closed IGNITE-4933.


> Need to add an option to write all updates in write-behind store
> 
>
> Key: IGNITE-4933
> URL: https://issues.apache.org/jira/browse/IGNITE-4933
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Yakov Zhdanov
> Fix For: 2.0
>
>  Time Spent: 16h
>  Remaining Estimate: 0h
>
> Currently if there are several updates for the same key, write behind store 
> will write only one of them within a single batch. I.e. second update will 
> override the first one if the latter is not written to DB yet.
> This is good from performance and memory consumption standpoint, however 
> sometimes it's required to write all updates that happen in cache.
> We can add parameter to {{CacheConfiguration}} that will switch this behavior 
> and implement it in {{GridCacheWriteBehindStore}}. Default behavior should 
> remain the same.



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

[jira] [Commented] (IGNITE-5015) In TcpCommunicationSpi use IgniteConfiguration.clientFailureDetectionTimeout

[Alexander Belyak (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972785#comment-15972785
 ] 

Alexander Belyak commented on IGNITE-5015:
--

In 4799 new configuration parameters will be created

> In TcpCommunicationSpi use IgniteConfiguration.clientFailureDetectionTimeout
> 
>
> Key: IGNITE-5015
> URL: https://issues.apache.org/jira/browse/IGNITE-5015
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexander Belyak
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> Need to use new IgniteConfiguration.clientFailureDetectionTimeout in 
> CommunicationSpi when interacting with client nodes.



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

[jira] [Updated] (IGNITE-3545) IGFS: Review exceptions in secondary file system interface.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3545:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Review exceptions in secondary file system interface.
> ---
>
> Key: IGNITE-3545
> URL: https://issues.apache.org/jira/browse/IGNITE-3545
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Possible solutions:
> 1) Throw {{IgniteException}} - looks to broad, but who cares?
> 2) Throw {{IOException}} - better fits into general understanding of what 
> file system is. Having it in the interface will reduce try-catch boilerplate 
> in concrete implementations.
> Any other ideas?



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

[jira] [Created] (IGNITE-5016) SQL: Support LEFT JOIN from replicated table to a partitioned.

[Sergi Vladykin (JIRA)]

Sergi Vladykin created IGNITE-5016:
--

 Summary: SQL: Support LEFT JOIN from replicated table to a 
partitioned.
 Key: IGNITE-5016
 URL: https://issues.apache.org/jira/browse/IGNITE-5016
 Project: Ignite
  Issue Type: Bug
Reporter: Sergi Vladykin
Assignee: Sergi Vladykin


Now we return duplicates:

IgniteCacheJoinPartitionedAndReplicatedTest.testReplicatedToPartitionedLeftJoin



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

[jira] [Updated] (IGNITE-3545) IGFS: Review exceptions in secondary file system interface.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3545:

Fix Version/s: (was: 2.0)
   2.1

> IGFS: Review exceptions in secondary file system interface.
> ---
>
> Key: IGNITE-3545
> URL: https://issues.apache.org/jira/browse/IGNITE-3545
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Possible solutions:
> 1) Throw {{IgniteException}} - looks to broad, but who cares?
> 2) Throw {{IOException}} - better fits into general understanding of what 
> file system is. Having it in the interface will reduce try-catch boilerplate 
> in concrete implementations.
> Any other ideas?



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

[jira] [Commented] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972766#comment-15972766
 ] 

ASF GitHub Bot commented on IGNITE-5000:


Github user ybabak closed the pull request at:

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


> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



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

[jira] [Created] (IGNITE-5015) In TcpCommunicationSpi use IgniteConfiguration.clientFailureDetectionTimeout

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-5015:


 Summary: In TcpCommunicationSpi use 
IgniteConfiguration.clientFailureDetectionTimeout
 Key: IGNITE-5015
 URL: https://issues.apache.org/jira/browse/IGNITE-5015
 Project: Ignite
  Issue Type: Bug
Reporter: Alexander Belyak


Need to use new IgniteConfiguration.clientFailureDetectionTimeout in 
CommunicationSpi when interacting with client nodes.



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

[jira] [Updated] (IGNITE-3528) IGFS: Review IgfsSecondaryFileSystem.open() method return type.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3528:

Fix Version/s: (was: 2.0)
   2.1

> IGFS: Review IgfsSecondaryFileSystem.open() method return type.
> ---
>
> Key: IGNITE-3528
> URL: https://issues.apache.org/jira/browse/IGNITE-3528
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently we return weird {{IgfsSecondaryFileSystemPositionedReadable}} 
> interface. It's goal is clear - we need to have a seekable stream. Need to 
> review it accurately and decide whether any changes or renamings are required 
> here.



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

[jira] [Updated] (IGNITE-3528) IGFS: Review IgfsSecondaryFileSystem.open() method return type.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3528:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Review IgfsSecondaryFileSystem.open() method return type.
> ---
>
> Key: IGNITE-3528
> URL: https://issues.apache.org/jira/browse/IGNITE-3528
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently we return weird {{IgfsSecondaryFileSystemPositionedReadable}} 
> interface. It's goal is clear - we need to have a seekable stream. Need to 
> review it accurately and decide whether any changes or renamings are required 
> here.



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

[jira] [Updated] (IGNITE-3546) IGFS: Review events subsystem.

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3546:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Review events subsystem.
> --
>
> Key: IGNITE-3546
> URL: https://issues.apache.org/jira/browse/IGNITE-3546
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently we have different event types for various file system operations. 
> But we do not fire them always. E.g. if the path {{/a}} is removed, then we 
> will fire only one event. We will not fire events for {{/a/b}}.
> Is it fine or not? Do we need these events at all or not? May be we want to 
> configure event handling somehow? May be users would like to listen such 
> events? Need to think about it.



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

[jira] [Updated] (IGNITE-3527) IGFS: Review "rename", "delete" and "mkdirs" return types in IgniteFileSystem and IgfsSecondaryFileSystem:

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-3527:

Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-3550)

> IGFS: Review "rename", "delete" and "mkdirs" return types in IgniteFileSystem 
> and IgfsSecondaryFileSystem:
> --
>
> Key: IGNITE-3527
> URL: https://issues.apache.org/jira/browse/IGNITE-3527
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently their semantics are not clear:
> - boolean delete()
> - void mkdirs()
> - void rename();
> They all must have the same return type and semantics. The question is which 
> semantics to choose:
> 1) Return boolean and (almost) never throw exceptions. This is "JDK way". I 
> personally do not like it because user will have to both check for true/false 
> and use try/catch.
> 2) Return void and throw exception if something went wrong. 



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

[jira] [Resolved] (IGNITE-3544) IGFS: Review info() semantics - should it return null or throw exception if file doesn't exist?

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-3544.
-
Resolution: Won't Fix

> IGFS: Review info() semantics - should it return null or throw exception if 
> file doesn't exist?
> ---
>
> Key: IGNITE-3544
> URL: https://issues.apache.org/jira/browse/IGNITE-3544
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> 1) Throw exception: clean and simple semantics, but if Hadoop/Spark/etc. 
> products return null in this case, we could end up with hot path where 
> exception is thrown. This would render bad performance.
> 2) Return null: always good perf, but additional null-checks will be required.
> Alternatively:
> - Have a method with exception semantics on public API, but use method with 
> null semantics for {{IgniteHadoopFileSystem}}.



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

[jira] [Closed] (IGNITE-3544) IGFS: Review info() semantics - should it return null or throw exception if file doesn't exist?

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-3544.
---

> IGFS: Review info() semantics - should it return null or throw exception if 
> file doesn't exist?
> ---
>
> Key: IGNITE-3544
> URL: https://issues.apache.org/jira/browse/IGNITE-3544
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> 1) Throw exception: clean and simple semantics, but if Hadoop/Spark/etc. 
> products return null in this case, we could end up with hot path where 
> exception is thrown. This would render bad performance.
> 2) Return null: always good perf, but additional null-checks will be required.
> Alternatively:
> - Have a method with exception semantics on public API, but use method with 
> null semantics for {{IgniteHadoopFileSystem}}.



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

[jira] [Closed] (IGNITE-2357) IGFS: Create factory for IgfsSecondaryFileSystem

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov closed IGNITE-2357.
---

> IGFS: Create factory for IgfsSecondaryFileSystem
> 
>
> Key: IGNITE-2357
> URL: https://issues.apache.org/jira/browse/IGNITE-2357
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.1
>
>
> Most of our pluggable components are serializable, so that 
> IgniteConfiguration can be converted to bytes and transferred over wire.
> This is not the case for IgfsSecondaryFileSystem. 
> There are several ways to fix that:
> 1) Mark IgfsSecondaryFileSystem as Serializable - simple and straightforward 
> solution. But what if user cannot serialize some internals of his file system 
> implementation?
> 2) Abstract out file system and user serializable Factory instead - this is 
> how things work in some other places (e.g. cache store factory).



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

[jira] [Resolved] (IGNITE-2357) IGFS: Create factory for IgfsSecondaryFileSystem

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov resolved IGNITE-2357.
-
Resolution: Won't Fix

> IGFS: Create factory for IgfsSecondaryFileSystem
> 
>
> Key: IGNITE-2357
> URL: https://issues.apache.org/jira/browse/IGNITE-2357
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.1
>
>
> Most of our pluggable components are serializable, so that 
> IgniteConfiguration can be converted to bytes and transferred over wire.
> This is not the case for IgfsSecondaryFileSystem. 
> There are several ways to fix that:
> 1) Mark IgfsSecondaryFileSystem as Serializable - simple and straightforward 
> solution. But what if user cannot serialize some internals of his file system 
> implementation?
> 2) Abstract out file system and user serializable Factory instead - this is 
> how things work in some other places (e.g. cache store factory).



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

[jira] [Created] (IGNITE-5014) Do not used partition exchange worker for CREATE/DROP INDEX

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-5014:
---

 Summary: Do not used partition exchange worker for CREATE/DROP 
INDEX
 Key: IGNITE-5014
 URL: https://issues.apache.org/jira/browse/IGNITE-5014
 Project: Ignite
  Issue Type: Task
  Components: cache, SQL
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
Priority: Minor
 Fix For: 2.1


It was used for historical reasons. But looks like it is not needed anymore.



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

[jira] [Assigned] (IGNITE-5012) Implement ordinary least squares (OLS) linear regression.

[Artem Malykh (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Malykh reassigned IGNITE-5012:


Assignee: Artem Malykh

> Implement ordinary least squares (OLS) linear regression.
> -
>
> Key: IGNITE-5012
> URL: https://issues.apache.org/jira/browse/IGNITE-5012
> Project: Ignite
>  Issue Type: Task
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>
> Implement ordinary least squares (OLS) linear regression using ignite 
> ml.math. This is a useful, but simple basic machine learning algorithm which 
> is a good candidate for testing math implemented in ml module on real machine 
> learning tasks.



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

[jira] [Created] (IGNITE-5013) Allow pass custom types to Cassandra store

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-5013:
---

 Summary: Allow pass custom types to Cassandra store
 Key: IGNITE-5013
 URL: https://issues.apache.org/jira/browse/IGNITE-5013
 Project: Ignite
  Issue Type: Improvement
  Components: ignite-cassandra
Affects Versions: 2.0
Reporter: Dmitry Karachentsev
 Fix For: 2.1


Any type that is not in 
org.apache.ignite.cache.store.cassandra.common.PropertyMappingHelper#JAVA_TO_CASSANDRA_MAPPING
 will be serialized even if user specified custom codec for Cassandra. 

Should be ability to configure and bypass custom types to Cassandra.



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

[jira] [Created] (IGNITE-5012) Implement ordinary least squares (OLS) linear regression.

[Artem Malykh (JIRA)]

Artem Malykh created IGNITE-5012:


 Summary: Implement ordinary least squares (OLS) linear regression.
 Key: IGNITE-5012
 URL: https://issues.apache.org/jira/browse/IGNITE-5012
 Project: Ignite
  Issue Type: Task
Reporter: Artem Malykh


Implement ordinary least squares (OLS) linear regression using ignite ml.math. 
This is a useful, but simple basic machine learning algorithm which is a good 
candidate for testing math implemented in ml module on real machine learning 
tasks.



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

[jira] [Commented] (IGNITE-4954) Timeout in ignite-cassandra SessionPool is not configurable

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972729#comment-15972729
 ] 

ASF GitHub Bot commented on IGNITE-4954:


Github user asfgit closed the pull request at:

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


> Timeout in ignite-cassandra SessionPool is not configurable
> ---
>
> Key: IGNITE-4954
> URL: https://issues.apache.org/jira/browse/IGNITE-4954
> Project: Ignite
>  Issue Type: Bug
>  Components: ignite-cassandra
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: 2.0
>
>
> Cassandra cache store implementation uses {{SessionPool}} class which kills 
> idle sessions after 5 minutes. Need to make this timeout configurable.



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

[jira] [Commented] (IGNITE-5002) fix tests in master

[Konstantin Dudkov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972707#comment-15972707
 ] 

Konstantin Dudkov commented on IGNITE-5002:
---

keep fixing tests

> fix tests in master
> ---
>
> Key: IGNITE-5002
> URL: https://issues.apache.org/jira/browse/IGNITE-5002
> Project: Ignite
>  Issue Type: Task
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
>




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

[jira] [Comment Edited] (IGNITE-4990) Remove deprecated properties from FileSystemConfiguration

[Taras Ledkov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972473#comment-15972473
 ] 

Taras Ledkov edited comment on IGNITE-4990 at 4/18/17 1:11 PM:
---

Tests 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1816%2Fhead]
 are OK with me


was (Author: tledkov-gridgain):
Waits for TC 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1816%2Fhead]

> Remove deprecated properties from FileSystemConfiguration
> -
>
> Key: IGNITE-4990
> URL: https://issues.apache.org/jira/browse/IGNITE-4990
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: important
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4539) RocketMQ data streamer

[Alexey Goncharuk (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972629#comment-15972629
 ] 

Alexey Goncharuk commented on IGNITE-4539:
--

Hi Roman,

I tried to run the unit-test you provided, but it fails with the following 
exception:
{code}
org.apache.rocketmq.client.exception.MQClientException: create new topic failed
For more information, please visit the url, http://rocketmq.apache.org/docs/faq/
at 
org.apache.rocketmq.client.impl.MQAdminImpl.createTopic(MQAdminImpl.java:129)
at 
org.apache.rocketmq.tools.admin.DefaultMQAdminExtImpl.createTopic(DefaultMQAdminExtImpl.java:897)
at 
org.apache.rocketmq.tools.admin.DefaultMQAdminExt.createTopic(DefaultMQAdminExt.java:97)
at 
org.apache.rocketmq.tools.admin.DefaultMQAdminExt.createTopic(DefaultMQAdminExt.java:92)
at org.apache.rocketmq.test.util.MQAdmin.createTopic(MQAdmin.java:46)
at 
org.apache.ignite.stream.rocketmq.RocketMQStreamerTest$2.apply(RocketMQStreamerTest.java:203)
at 
org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1600)
at 
org.apache.ignite.stream.rocketmq.RocketMQStreamerTest.initTopic(RocketMQStreamerTest.java:201)
at 
org.apache.ignite.stream.rocketmq.RocketMQStreamerTest.produceData(RocketMQStreamerTest.java:171)
at 
org.apache.ignite.stream.rocketmq.RocketMQStreamerTest.testStreamer(RocketMQStreamerTest.java:137)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1928)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:125)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1843)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.rocketmq.client.exception.MQClientException: CODE: 17  
DESC: No topic route info in name server for the topic: testCluster
See http://rocketmq.apache.org/docs/faq/ for further details.
at 
org.apache.rocketmq.client.impl.MQClientAPIImpl.getTopicRouteInfoFromNameServer(MQClientAPIImpl.java:1212)
at 
org.apache.rocketmq.client.impl.MQAdminImpl.createTopic(MQAdminImpl.java:81)
... 18 more
{code}

Can you take a look?

> RocketMQ data streamer
> --
>
> Key: IGNITE-4539
> URL: https://issues.apache.org/jira/browse/IGNITE-4539
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: important
> Fix For: 2.0
>
>
> Streamer for RocketMQ (https://github.com/rocketmq)



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

[jira] [Commented] (IGNITE-4927) Write behind - add an option to skip write coalescing

[Nikolay Tikhonov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972608#comment-15972608
 ] 

Nikolay Tikhonov commented on IGNITE-4927:
--

[~sbberkov]
I've merged your changes to master. Thank you for your contribution!

> Write behind - add an option to skip write coalescing
> -
>
> Key: IGNITE-4927
> URL: https://issues.apache.org/jira/browse/IGNITE-4927
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> Currently, the write-behind store is backed by a map, therefore when several 
> updates come to the same key, they are coalesced. 
> We need to introduce optional mode and back write-behind with a queue and 
> pass each  to a database.



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

[jira] [Closed] (IGNITE-4927) Write behind - add an option to skip write coalescing

[Nikolay Tikhonov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Tikhonov closed IGNITE-4927.


> Write behind - add an option to skip write coalescing
> -
>
> Key: IGNITE-4927
> URL: https://issues.apache.org/jira/browse/IGNITE-4927
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> Currently, the write-behind store is backed by a map, therefore when several 
> updates come to the same key, they are coalesced. 
> We need to introduce optional mode and back write-behind with a queue and 
> pass each  to a database.



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

[jira] [Resolved] (IGNITE-4986) .NET possible affinity resource leak

[Alexey Goncharuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Goncharuk resolved IGNITE-4986.
--
   Resolution: Won't Fix
Fix Version/s: 2.0

There was an issue in the test

> .NET possible affinity resource leak
> 
>
> Key: IGNITE-4986
> URL: https://issues.apache.org/jira/browse/IGNITE-4986
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.0
>
>
> Test fails with 
> {code}
> TearDown method failed. HandleRegistry is not empty in grid '' (expected 5, 
> actual 6):
>  '[1025, 
> Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+RendezvousAffinityFunctionEx]
> [1026, 
> Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+SimpleAffinityFunction]
> [1027, 
> Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+SimpleAffinityFunction]
> [1028, 
> Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+FailInGetPartitionAffinityFunction]
> [1029, 
> Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest+RendezvousAffinityFunctionEx]'
>at NUnit.Framework.Assert.Fail(String message, Object[] args)
>at Apache.Ignite.Core.Tests.TestUtils.AssertHandleRegistryHasItems(IIgnite 
> grid, Int32 expectedCount, Int32 timeout) in 
> c:\BuildAgent\work\a9543228d3ee824c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\TestUtils.cs:line
>  292
>at 
> Apache.Ignite.Core.Tests.Cache.Affinity.AffinityFunctionTest.FixtureTearDown()
>  in 
> c:\BuildAgent\work\a9543228d3ee824c\modules\platforms\dotnet\Apache.Ignite.Core.Tests\Cache\Affinity\AffinityFunctionTest.cs:line
>  95
> {code}
> which might indicate that affinity resource is not released in Ignite



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

[jira] [Comment Edited] (IGNITE-4501) Improvement of connection in a cluster of new node

[Alexander Menshikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972575#comment-15972575
 ] 

Alexander Menshikov edited comment on IGNITE-4501 at 4/18/17 12:27 PM:
---

[~yzhdanov],

And one new case can happen. When message reaches the coordinator, and the 
coordinator sends it to next node, and the coordinator crashes after that, and 
some node in the middle are becoming a new coordinator, and message will reach 
this new coordinator, after that all nodes after new coordinator will not see 
the added message.

It can happen because candidates for coordinators sorted in the ring in the 
different order than nodes.

The simplest solution is a sending added messages in the old order.


was (Author: sharpler):
[~yzhdanov],

And one new case can happen. When message reaches the coordinator, and the 
coordinator sends it to next node, and the coordinator crashes after that, and 
some node in the middle are becoming a new coordinator, and message will reach 
this new coordinator, after that all nodes after new coordinator will not see 
the added message.

It can happen because candidates for coordinators sorted in the ring in the 
different order than nodes.

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



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

[jira] [Commented] (IGNITE-4501) Improvement of connection in a cluster of new node

[Alexander Menshikov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972575#comment-15972575
 ] 

Alexander Menshikov commented on IGNITE-4501:
-

[~yzhdanov],

And one new case can happen. When message reaches the coordinator, and the 
coordinator sends it to next node, and the coordinator crashes after that, and 
some node in the middle are becoming a new coordinator, and message will reach 
this new coordinator, after that all nodes after new coordinator will not see 
the added message.

It can happen because candidates for coordinators sorted in the ring in the 
different order than nodes.

> Improvement of connection in a cluster of new node
> --
>
> Key: IGNITE-4501
> URL: https://issues.apache.org/jira/browse/IGNITE-4501
> Project: Ignite
>  Issue Type: Improvement
>  Components: messaging
>Affects Versions: 1.8
>Reporter: Vyacheslav Daradur
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> h3. Main description:
> Cluster nodes connect a ring.
> For example: we have 6 nodes: A, B, C, D, E, F. 
> They can connect a ring in any possible way: A-B-C-D-E-F-A, or A-F-B-E-C-D-A, 
> etc.
> If some node leaves topology, adjacent nodes must reconnect. 
> If nodes A, B, C are in same physical place, nodes D, E, F are in other 
> place, and places lost connect each other, we will have many ways of 
> reconnections.
> At best case, if we had a ring: A-B-CxD-E-FxA ('x' means disconnect) -- then 
> we have only one reconnect (C
> will be connected to A or F will be connected to D -- depends on what part of 
> the cluster was alive.
> Also, if we had a not ring: AxFxBxExCxDxA -- then we have a lot of 
> reconnections (A to B, B to C, C to A -- in general n/2 reconnections, where 
> n -- number of nodes). 
> h3. Approach:
> It is necessary to develop approach of node insertion to the correct place 
> for creation of the correct ring-topology.
> h3. Solutions:
> Main idea is a sorting according to latency.
> * group nodes in arcs on an ARC_ID. (manualy?)
> * implement NodeComparator (nodes on the same host : nodes on the same subnet 
> : other nodes). We will use it when we connect a new node.
> * [dev list 
> thread|http://mail-archives.apache.org/mod_mbox/ignite-dev/201612.mbox/%3CCAN+WSNyWYXSXEBpGErVt72zTgi2pTQzUWLv8JY=ke83-5-r...@mail.gmail.com%3E]
> Update Dec, 29 Yakov Zhdanov:
> # introduce CLUSTER_REGION_ID node attribute. This can be done by adding 
> public static final constant to TcpDiscoverySpi.
> # Alter 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNodesRing#nextNode(java.util.Collection)
>  to order basing on per node attribute value
> # Node comparison should be stable and consistent. E.g. if CLUSTER_REGION_IDs 
> are equal then we should compare nodes' IDs. This way we have consistent 
> order on all nodes in topology.
> # Also nextNode() has to group nodes on same host and in same subnet. This 
> can be postponed and implemented after we have other points done.



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

[jira] [Created] (IGNITE-5011) Add validation of input params of disco command

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5011:
--

 Summary: Add validation of input params of disco command
 Key: IGNITE-5011
 URL: https://issues.apache.org/jira/browse/IGNITE-5011
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Priority: Trivial


{code}
visor> disco -t=0h
java.lang.IllegalArgumentException: Time frame size is not positive in: 0h
at org.apache.ignite.visor.visor$.timeFilter(visor.scala:2671)
at 
org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand.disco(VisorDiscoveryCommand.scala:127)
at 
org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
at 
org.apache.ignite.visor.commands.disco.VisorDiscoveryCommand$$anonfun$4.apply(VisorDiscoveryCommand.scala:282)
at 
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:217)
at 
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:329)
at 
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:318)
at scala.Function0$class.apply$mcV$sp(Function0.scala:34)
at 
scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.collection.immutable.List.foreach(List.scala:381)
at 
scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
at scala.App$class.main(App.scala:76)
at 
org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:318)
at 
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
(wrn) : Invalid command name: 'disco -t=0h'
(wrn) : Type 'help' to print commands list.
{code}



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

[jira] [Commented] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[Yury Babak (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972548#comment-15972548
 ] 

Yury Babak commented on IGNITE-5000:


[~avinogradov], could you please review new pull request?
https://github.com/apache/ignite/pull/1818

> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



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

[jira] [Commented] (IGNITE-5000) Rename Ignite Math module to Ignite ML module

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972546#comment-15972546
 ] 

ASF GitHub Bot commented on IGNITE-5000:


GitHub user ybabak opened a pull request:

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

IGNITE-5000 (Rename Ignite Math module to Ignite ML module):

  added missed licenses
  renamed packages
  fixed wrong ml profile activation

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

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

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

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


commit 4a8cce31ff390fedf2dfef90926e86251e163428
Author: Yury Babak 
Date:   2017-04-18T11:50:55Z

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




> Rename Ignite Math module to Ignite ML module
> -
>
> Key: IGNITE-5000
> URL: https://issues.apache.org/jira/browse/IGNITE-5000
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.0
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.0
>
>
> We want to rename math module to ml(machine learning) because it's a main 
> planned functionality for this module.
> Update: also we want to extract math related examples to separate source 
> folder/profile for tests convenience.



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

[jira] [Commented] (IGNITE-314) Ensure that GridCacheDrManager.receiveEnabled() is called correctly.

[neeraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972530#comment-15972530
 ] 

neeraj commented on IGNITE-314:
---

Please give more details so that I can fix the bug

> Ensure that GridCacheDrManager.receiveEnabled() is called correctly.
> 
>
> Key: IGNITE-314
> URL: https://issues.apache.org/jira/browse/IGNITE-314
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: sprint-2
>Reporter: Vladimir Ozerov
>Priority: Minor
>




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

[jira] [Commented] (IGNITE-4626) GridDhtPartitionTopologyImpl refactoring

[Konstantin Dudkov (JIRA)]

[ 
https://issues.apache.org/jira/browse/IGNITE-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972522#comment-15972522
 ] 

Konstantin Dudkov commented on IGNITE-4626:
---

new benchmarks:
Servers: 4 Clients: 8

|| ||rev: 203aab4a|| ||rev: 49cae051 (master)||
|atomic-put |140850 |27.36%|110592|
|atomic-put-get |80213.3 |15.23%|69609.4|
|atomic-put-getEntry |79404.2 |15.49%|68757|
|atomic-putAll |5097.82 |40.56%|3626.72|

today I rebased branch onto master, waiting for tests & benchmarks

> GridDhtPartitionTopologyImpl refactoring
> 
>
> Key: IGNITE-4626
> URL: https://issues.apache.org/jira/browse/IGNITE-4626
> Project: Ignite
>  Issue Type: Task
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
> Fix For: 2.1
>
>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl#nodes(int,
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion)
> Need to refactor this method to use Object[] - partId->List



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

[jira] [Updated] (IGNITE-4551) Reconsider cache key/value peer class loading

[Vladimir Ozerov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-4551:

Fix Version/s: (was: 2.0)
   2.1

> Reconsider cache key/value peer class loading
> -
>
> Key: IGNITE-4551
> URL: https://issues.apache.org/jira/browse/IGNITE-4551
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Nikolay Tikhonov
> Fix For: 2.1
>
>
> In new cache implementation after entry is written in offheap information 
> about key/value classloaders in lost (before classloader ids were stored in 
> swap/offheap see GridCacheMapEntry.swap in 'master').
> Need decide how it should work with new architecture (maybe single type per 
> cache can simplify implementation).



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

[jira] [Updated] (IGNITE-4463) Web console: Send mail on password change from Profile page.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-4463:
-
Fix Version/s: (was: 2.0)
   2.1

> Web console: Send mail on password change from Profile page.
> 
>
> Key: IGNITE-4463
> URL: https://issues.apache.org/jira/browse/IGNITE-4463
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-3895) Web console: Should split large generated XML and Java files.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-3895:
-
Fix Version/s: (was: 2.0)
   2.1

> Web console: Should split large generated XML and Java files.
> -
>
> Key: IGNITE-3895
> URL: https://issues.apache.org/jira/browse/IGNITE-3895
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Vasiliy Sisko
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-4453) Web console: On click by any dropdown page showed as changed.

[Alexey Kuznetsov (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Kuznetsov updated IGNITE-4453:
-
Fix Version/s: (was: 2.0)
   2.1

> Web console: On click by any dropdown page showed as changed.
> -
>
> Key: IGNITE-4453
> URL: https://issues.apache.org/jira/browse/IGNITE-4453
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 1.9
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
> Fix For: 2.1
>
>




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