[jira] [Assigned] (IGNITE-7461) Web console: incorrect code generation

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-7461:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Web console: incorrect code generation
> --
>
> Key: IGNITE-7461
> URL: https://issues.apache.org/jira/browse/IGNITE-7461
> Project: Ignite
>  Issue Type: Bug
> Environment: Error:(81, 23) java: cannot find symbol
>   symbol:   method setCheckpointPageBufferSize(long)
>   location: variable dataStorageCfg of type 
> org.apache.ignite.configuration.DataStorageConfiguration
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> Do not forget to change generation of XML configuration



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

[jira] [Comment Edited] (IGNITE-7461) Web console: incorrect code generation

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-7461 at 1/18/18 7:52 AM:


Updated configuration for data storage configuration in Web console.

Added fields walBufferSize and walCompactionEnabled.

Removed checkpointPageBufferSize from data storage configuration.


was (Author: vsisko):
Updated configuration for data storage configuration in Web console.

> Web console: incorrect code generation
> --
>
> Key: IGNITE-7461
> URL: https://issues.apache.org/jira/browse/IGNITE-7461
> Project: Ignite
>  Issue Type: Bug
> Environment: Error:(81, 23) java: cannot find symbol
>   symbol:   method setCheckpointPageBufferSize(long)
>   location: variable dataStorageCfg of type 
> org.apache.ignite.configuration.DataStorageConfiguration
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.4
>
>
> Do not forget to change generation of XML configuration



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

[jira] [Commented] (IGNITE-7458) NPE occurs after node restart with native persistence enabled.

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin commented on IGNITE-7458:
--

It seems that specified NPE already fixed in 2.4, look at this change 
https://github.com/apache/ignite/commit/78109702ca47dbf960ccf23c551bca2941891242#diff-fbcf2bbf68a1ae967c15e2ec5794938dR542
But I'm not sure about the root cause.

> NPE occurs after node restart with native persistence enabled.
> --
>
> Key: IGNITE-7458
> URL: https://issues.apache.org/jira/browse/IGNITE-7458
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
>
> We have a report from a user:
> [http://apache-ignite-users.70518.x6.nabble.com/NPE-from-the-native-persistence-enable-node-td19555.html]
>  
> it says that NPE occurred after node restart with native persistence enabled.



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

[jira] [Commented] (IGNITE-7461) Web console: incorrect code generation

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-7461:
---

Updated configuration for data storage configuration in Web console.

> Web console: incorrect code generation
> --
>
> Key: IGNITE-7461
> URL: https://issues.apache.org/jira/browse/IGNITE-7461
> Project: Ignite
>  Issue Type: Bug
> Environment: Error:(81, 23) java: cannot find symbol
>   symbol:   method setCheckpointPageBufferSize(long)
>   location: variable dataStorageCfg of type 
> org.apache.ignite.configuration.DataStorageConfiguration
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.4
>
>
> Do not forget to change generation of XML configuration



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

[jira] [Comment Edited] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[liu xionghao (JIRA)]

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

liu xionghao edited comment on IGNITE-4750 at 1/18/18 7:30 AM:
---

 It occurs errors when using +count(*distinct* ...)+ and +group_concat(...)+ in 
same select clause.  But if key word +*distinct*+ omited, it works.

example:
{code:java}
// code placeholder
select count(distinct a) as num, group_concat(a) as strs
from test
group by b{code}
table *test* data: 
||id (int)||a (varchar)||b (varchar)||
|1|1|2|
|2|3|2|
|3|1|3|

{color:#FF}error: {color}
{code:java}
[18-Jan-2018 15:23:11][ERROR][client-connector-#54][JdbcRequestHandler] Failed 
to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=PUBLIC, 
pageSize=1024, maxRows=0, sqlQry=select count(distinct a) as num, 
group_concat(a) as strs
from test
group by b, args=[], stmtType=ANY_STATEMENT_TYPE]]
javax.cache.CacheException: Failed to run map query remotely.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:747)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1282)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
{code}
 

 


was (Author: xionghao):
 

 

It occurs errors when using +count(*distinct* ...)+ and +group_concat(...)+ in 
same select clause.  But if key word +*distinct*+ omited, it works.

example:
{code:java}
// code placeholder
select count(distinct a) as num, group_concat(a) as strs
from test
group by b{code}
 

where `test` schema:

 
||id (int)||a (varchar)||b (varchar)||
|1|1|2|
|2|3|2|
|3|1|3|

error:

 

 
{code:java}
[18-Jan-2018 15:23:11][ERROR][client-connector-#54][JdbcRequestHandler] Failed 
to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=PUBLIC, 
pageSize=1024, maxRows=0, sqlQry=select count(distinct a) as num, 
group_concat(a) as strs
from test
group by b, args=[], stmtType=ANY_STATEMENT_TYPE]]
javax.cache.CacheException: Failed to run map query remotely.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:747)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1282)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
{code}
 

 

> SQL: Support GROUP_CONCAT function
> --
>
> Key: IGNITE-4750
> URL: https://issues.apache.org/jira/browse/IGNITE-4750
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> GROUP_CONCAT function is not supported at the moment. Makes sense to fill 
> this gap:
> http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html
> Presently the function doc is hidden:
> https://apacheignite-sql.readme.io/docs/group_concat
> Open it up once the ticket is released.



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

[jira] [Commented] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[liu xionghao (JIRA)]

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

liu xionghao commented on IGNITE-4750:
--

 

 

It occurs errors when using +count(*distinct* ...)+ and +group_concat(...)+ in 
same select clause.  But if key word +*distinct*+ omited, it works.

example:
{code:java}
// code placeholder
select count(distinct a) as num, group_concat(a) as strs
from test
group by b{code}
 

where `test` schema:

 
||id (int)||a (varchar)||b (varchar)||
|1|1|2|
|2|3|2|
|3|1|3|

error:

 

 
{code:java}
[18-Jan-2018 15:23:11][ERROR][client-connector-#54][JdbcRequestHandler] Failed 
to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=PUBLIC, 
pageSize=1024, maxRows=0, sqlQry=select count(distinct a) as num, 
group_concat(a) as strs
from test
group by b, args=[], stmtType=ANY_STATEMENT_TYPE]]
javax.cache.CacheException: Failed to run map query remotely.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:747)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$8.iterator(IgniteH2Indexing.java:1282)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:95)
{code}
 

 

> SQL: Support GROUP_CONCAT function
> --
>
> Key: IGNITE-4750
> URL: https://issues.apache.org/jira/browse/IGNITE-4750
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.5
>
>
> GROUP_CONCAT function is not supported at the moment. Makes sense to fill 
> this gap:
> http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html
> Presently the function doc is hidden:
> https://apacheignite-sql.readme.io/docs/group_concat
> Open it up once the ticket is released.



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

[jira] [Comment Edited] (IGNITE-6853) Cassandra cache store does not clean prepared statements cache when remove old cassandra session

[Igor Rudyak (JIRA)]

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

Igor Rudyak edited comment on IGNITE-6853 at 1/18/18 7:15 AM:
--

Hi [~jason@gmail.com],

I added my comment to your PR.


was (Author: irudyak):
Hi Jason,

I added my comment to your PR.

> Cassandra cache store does not clean prepared statements cache when remove 
> old cassandra session
> 
>
> Key: IGNITE-6853
> URL: https://issues.apache.org/jira/browse/IGNITE-6853
> Project: Ignite
>  Issue Type: Bug
>  Components: cassandra
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Jason Man
>Priority: Major
>  Labels: important
> Fix For: 2.4
>
> Attachments: CassandraSessionImplTest.java
>
>
> Cassandra cache store does not clean prepared statements cache when remove 
> old cassandra session which can lead to:
>  Prepared
> statement cluster error detected, refreshing Cassandra session
> com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute
> unknown prepared query : 0xcad5832309a512feeb602eec67408130. You may have
> used a PreparedStatement that was created with another Cluster instance.



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

[jira] [Commented] (IGNITE-6853) Cassandra cache store does not clean prepared statements cache when remove old cassandra session

[Igor Rudyak (JIRA)]

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

Igor Rudyak commented on IGNITE-6853:
-

Hi Jason,

I added my comment to your PR.

> Cassandra cache store does not clean prepared statements cache when remove 
> old cassandra session
> 
>
> Key: IGNITE-6853
> URL: https://issues.apache.org/jira/browse/IGNITE-6853
> Project: Ignite
>  Issue Type: Bug
>  Components: cassandra
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Jason Man
>Priority: Major
>  Labels: important
> Fix For: 2.4
>
> Attachments: CassandraSessionImplTest.java
>
>
> Cassandra cache store does not clean prepared statements cache when remove 
> old cassandra session which can lead to:
>  Prepared
> statement cluster error detected, refreshing Cassandra session
> com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute
> unknown prepared query : 0xcad5832309a512feeb602eec67408130. You may have
> used a PreparedStatement that was created with another Cluster instance.



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

[jira] [Updated] (IGNITE-7196) Exchange can stuck and wait while new node restoring state from disk and starting caches

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7196:

Fix Version/s: (was: 2.4)
   2.5

> Exchange can stuck and wait while new node restoring state from disk and 
> starting caches
> 
>
> Key: IGNITE-7196
> URL: https://issues.apache.org/jira/browse/IGNITE-7196
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.5
>
>
> Exchange can stuck and wait while new node restoring state from disk and 
> starting caches, there's a log snippet from a just joined new node that shows 
> the issue:
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][time] Started 
> exchange init [topVer=AffinityTopologyVersion [topVer=57, minorTopVer=0], 
> crd=false, evt=NODE_JOINED, evtNode=3ac1160e-0de4-41bc-a366-59292c9f03c1, 
> customEvt=null, allowMerge=true]
> [21:36:13,023][INFO][exchange-worker-#62%statement_grid%][FilePageStoreManager]
>  Resolved page store work directory: 
> /mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
>  Resolved write ahead log work directory: 
> /mnt/wal/WAL/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,024][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
>  Resolved write ahead log archive directory: 
> /mnt/wal/WAL_archive/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463
> [21:36:13,046][INFO][exchange-worker-#62%statement_grid%][FileWriteAheadLogManager]
>  Started write-ahead log manager [mode=DEFAULT]
> [21:36:13,065][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] 
> Started page memory [memoryAllocated=100.0 MiB, pages=6352, tableSize=373.4 
> KiB, checkpointBuffer=100.0 MiB]
> [21:36:13,105][INFO][exchange-worker-#62%statement_grid%][PageMemoryImpl] 
> Started page memory [memoryAllocated=32.0 GiB, pages=2083376, tableSize=119.6 
> MiB, checkpointBuffer=896.0 MiB]
> [21:36:13,428][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
>  Read checkpoint status 
> [startMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930965253-306c0895-1f5f-4237-bebf-8bf2b49682af-START.bin,
>  
> endMarker=/mnt/store/node00-d1eb270c-d2cc-4550-87aa-64f6df2a9463/cp/1512930869357-1c24b6dc-d64c-4b83-8166-11edf1bfdad3-END.bin]
> [21:36:13,429][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
>  Checking memory state [lastValidPos=FileWALPointer [idx=3582, 
> fileOffset=59186076, len=9229, forceFlush=false], lastMarked=FileWALPointer 
> [idx=3629, fileOffset=50829700, len=9229, forceFlush=false], 
> lastCheckpointId=306c0895-1f5f-4237-bebf-8bf2b49682af]
> [21:36:13,429][WARNING][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
>  Ignite node stopped in the middle of checkpoint. Will restore memory state 
> and finish checkpoint on node start.
> [21:36:18,312][INFO][grid-nio-worker-tcp-comm-0-#41%statement_grid%][TcpCommunicationSpi]
>  Accepted incoming communication connection [locAddr=/172.31.20.209:48100, 
> rmtAddr=/172.31.17.115:57148]
> [21:36:21,619][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
>  Found last checkpoint marker [cpId=306c0895-1f5f-4237-bebf-8bf2b49682af, 
> pos=FileWALPointer [idx=3629, fileOffset=50829700, len=9229, 
> forceFlush=false]]
> [21:36:21,620][INFO][exchange-worker-#62%statement_grid%][GridCacheDatabaseSharedManager]
>  Finished applying memory changes [changesApplied=165103, time=8189ms]
> [21:36:22,403][INFO][grid-nio-worker-tcp-comm-1-#42%statement_grid%][TcpCommunicationSpi]
>  Accepted incoming communication connection [locAddr=/172.31.20.209:48100, 
> rmtAddr=/172.31.28.10:47964]
> [21:36:23,414][INFO][grid-nio-worker-tcp-comm-2-#43%statement_grid%][TcpCommunicationSpi]
>  Accepted incoming communication connection [locAddr=/172.31.20.209:48100, 
> rmtAddr=/172.31.27.101:46000]
> [21:36:33,019][WARNING][main][GridCachePartitionExchangeManager] Failed to 
> wait for initial partition map exchange. Possible reasons are:
> ^-- Transactions in deadlock.
> ^-- Long running transactions (ignore if this is the case).
> ^-- Unreleased explicit locks.
> [21:36:53,021][WARNING][main][GridCachePartitionExchangeManager] Still 
> waiting for initial partition map exchange 
> [fut=GridDhtPartitionsExchangeFuture [firstDiscoEvt=DiscoveryEvent 
> [evtNode=TcpDiscoveryNode [id=3ac1160e-0de4-41bc-a366-59292c9f03c1, 
> addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 172.31.20.209], 
> sockAddrs=[/0:0:0:0:0:0:0:1%lo:48500, /127.0.0.1:48500, 
> 

[jira] [Updated] (IGNITE-7284) Introduce DEV_ONLY marker to IgniteLogger

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7284:

Fix Version/s: (was: 2.4)
   2.5

> Introduce DEV_ONLY marker to IgniteLogger
> -
>
> Key: IGNITE-7284
> URL: https://issues.apache.org/jira/browse/IGNITE-7284
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Assignee: Stanislav Lukyanov
>Priority: Major
> Fix For: 2.5
>
>
> Need to add markers support to {{IgniteLogger}} and then introduce 
> {{DEV_ONLY}} marker for warnings that can be suppressed in prod environments.
> Problem and solution are discussed in more detail here: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Suppressing-quot-development-quot-warning-td25195.html
> Make sure to update Loggers documentation explaining how the parameter works 
> and what's it for:
> https://apacheignite.readme.io/docs/logging



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

[jira] [Updated] (IGNITE-5655) Introduce pluggable string encoder/decoder

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5655:

Fix Version/s: (was: 2.4)
   2.5

> Introduce pluggable string encoder/decoder
> --
>
> Key: IGNITE-5655
> URL: https://issues.apache.org/jira/browse/IGNITE-5655
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Andrey Kuznetsov
>Priority: Major
>  Labels: iep-2, important
> Fix For: 2.5
>
>
> Currently binary marshaller encodes strings in UTF-8. However, sometimes it 
> makes sense to serialize strings with different encodings to save space. 
> Let's add global property to control String encoding and customize our binary 
> protocol to support it. For instance, we can add another flag 
> {{ENCODED_STRING}}, which will write strings as follows:
> [flag][encoding_flag][str_len][str_bytes]
> First implementation should set preferred encoding for strings in 
> BinaryConfiguration. This setting is optional, default encoding is UTF-8. 
> Currently, the same BinaryConfiguration is used for all cluster nodes, thus 
> no encoding clashes are possible.



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

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

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6237:

Fix Version/s: (was: 2.4)
   2.5

> Script for signing and uploading artifacts to remote staging.
> -
>
> Key: IGNITE-6237
> URL: https://issues.apache.org/jira/browse/IGNITE-6237
> Project: Ignite
>  Issue Type: Sub-task
>  Components: build
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
>Priority: Major
> Fix For: 2.5
>
>
> Create script for signing artifacts in locally staged repository and 
> uploading to the remote staging.



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

[jira] [Updated] (IGNITE-5804) ScanQuery transformer applies to first results page only.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5804:

Fix Version/s: (was: 2.4)
   2.5

> ScanQuery transformer applies to first results page only.
> -
>
> Key: IGNITE-5804
> URL: https://issues.apache.org/jira/browse/IGNITE-5804
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.5
>
>
> Issue is successfully reproduces on GridCacheQueryTransformerSelfTest if 
> set ScanQuery.pageSize much lower then cache size.
> We should rework GridCacheQueryTransformerSelfTest to run test on larger 
> dataset 
> to make pagination used as well.
> http://apache-ignite-users.70518.x6.nabble.com/Transformer-not-called-on-every-ScanQuery-td15171.html



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

[jira] [Updated] (IGNITE-7177) Custom discovery messages from plugins are handled incorrectly

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7177:

Fix Version/s: (was: 2.4)
   2.5

> Custom discovery messages from plugins are handled incorrectly
> --
>
> Key: IGNITE-7177
> URL: https://issues.apache.org/jira/browse/IGNITE-7177
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> We call onServerNodeJoin for custom messages which do not change affinity



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

[jira] [Updated] (IGNITE-7152) Failure detection timeout don't work on permanent send message errors causing infinite loop

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7152:

Fix Version/s: (was: 2.4)
   2.5

> Failure detection timeout don't work on permanent send message errors causing 
> infinite loop
> ---
>
> Key: IGNITE-7152
> URL: https://issues.apache.org/jira/browse/IGNITE-7152
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Alexandr Kuramshin
>Priority: Critical
> Fix For: 2.5
>
> Attachments: testFailureDetectionOnReceiptError.patch
>
>
> Relative to {{RingMessageWorker.sendMessageAcrossRing}} implementation.
> {{IgniteSpiOperationTimeoutHelper}} reinitialized every time the socket 
> successfully connected.
> If any of {{IOException, IgniteCheckedException}} occurs upon message send 
> the socket will be closed and old {{IgniteSpiOperationTimeoutHelper}} will be 
> used to reconnect.
> But after successful reconnect the new one will be created and the cycle 
> repeat. With a permanent send message error this causes an infinite loop.
> The only send error which may cause to exit out of the loop and the next node 
> failure is {{IgniteSpiOperationTimeoutException, SocketTimeoutException, 
> SocketException}}.



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

[jira] [Updated] (IGNITE-7236) SQL: create tests for optimized INSERT and MERGE operations

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7236:

Fix Version/s: (was: 2.4)
   2.5

> SQL: create tests for optimized INSERT and MERGE operations
> ---
>
> Key: IGNITE-7236
> URL: https://issues.apache.org/jira/browse/IGNITE-7236
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Major
> Fix For: 2.5
>
>
> Important optimization IGNITE-4490 was added to the product. However, it 
> lacks excessive tests coverage. We need to test the following scenarios:
> 1) Various data types (especially dates)
> 2) Single updates vs batched updates
> 3) Constants and nulls (e.g. {{INSERT INTO ... VALUES (a, b)}})
> 4) Parameters (e.g. {{INSERT INTO ... VALUES (?, ?)}})
> 5) Multiple SQL statements at once (e.g. {{INSERT INTO ...; INSERT INTO ...}})
> 6) Insert multiple lines at once ({{INSERT INTO ... VALUES (a1, b1), (a2, 
> b2)}})
> 7) Insert multiple lines with parameters
> 8) Invalid parameters count in different query types - need to make sure that 
> we throw correct errors.
> All tests except of p.8 should check both correctness and the fact that query 
> was executed without H2 involvement (e.g. using some code hack).



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

[jira] [Updated] (IGNITE-7083) Reduce memory usage of CachePartitionFullCountersMap

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7083:

Fix Version/s: (was: 2.4)
   2.5

> Reduce memory usage of CachePartitionFullCountersMap
> 
>
> Key: IGNITE-7083
> URL: https://issues.apache.org/jira/browse/IGNITE-7083
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.3
> Environment: Any
>Reporter: Sunny Chan
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The Cache Partition Exchange Manager kept a copy of the already completed 
> exchange. However, we have found that it uses a significant amount of memory. 
> Upon further investigation using heap dump we have found that a large amount 
> of memory is used by the CachePartitionFullCountersMap. We have also observed 
> in most cases, these maps contains only 0s.
> Therefore I propose an optimization for this: Initially the long arrays to 
> store initial update counter and update counter in the CPFCM will be null, 
> and when you get the value and see these tables are null then we will return 
> 0 for the counter. We only allocate the long arrays when there is any 
> non-zero updates to the the map.
> In our tests, the amount of heap used by GridCachePartitionExchangeManager 
> was around 70MB (67 copies of these CPFCM), after we apply the optimization 
> it drops to around 9MB.



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

[jira] [Updated] (IGNITE-7099) Cache public API should generate exceptions when cluster is not active.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7099:

Fix Version/s: (was: 2.4)
   2.5

> Cache public API should generate exceptions when cluster is not active.
> ---
>
> Key: IGNITE-7099
> URL: https://issues.apache.org/jira/browse/IGNITE-7099
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>
> For example 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor#jcaches return 
> empty list.



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

[jira] [Updated] (IGNITE-7042) Test written in scala doesn't executed on TC

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7042:

Fix Version/s: (was: 2.4)
   2.5

> Test written in scala doesn't executed on TC 
> -
>
> Key: IGNITE-7042
> URL: https://issues.apache.org/jira/browse/IGNITE-7042
> Project: Ignite
>  Issue Type: Bug
>  Components: spark
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
> Fix For: 2.5
>
>
> Tests from module `spark` and `spark_2.10` written in scala don't executes on 
> TC.



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

[jira] [Updated] (IGNITE-7024) Introduce some kind of network compression

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7024:

Fix Version/s: (was: 2.4)
   2.5

> Introduce some kind of network compression
> --
>
> Key: IGNITE-7024
> URL: https://issues.apache.org/jira/browse/IGNITE-7024
> Project: Ignite
>  Issue Type: New Feature
>Affects Versions: 2.3
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.5
>
>
> Introduce some kind of pluggable compression at network level
> The main idea is using in-line compression and writes encoded bytes in
> network channel by bytes array buffer. It allows us avoiding expensive
> memory allocation.
> A solution may be implemented at TcpCommunicationSpi level.
> For example, introduce Compressor interface which will allow us to describe 
> our compression strategy, for example, exclude some small messages, choose 
> compression algorithm and other…



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

[jira] [Updated] (IGNITE-5733) Activate/deactivate cluster through http-rest api

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5733:

Fix Version/s: (was: 2.4)
   2.5

> Activate/deactivate cluster through http-rest api
> -
>
> Key: IGNITE-5733
> URL: https://issues.apache.org/jira/browse/IGNITE-5733
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Critical
>  Labels: usability
> Fix For: 2.5
>
>
> Need to add command to get/set cluster active flag into http rest api.



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

[jira] [Updated] (IGNITE-6527) Deadlock detection works incorrectly with some timeouts that haven't caused by deadlocks.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6527:

Fix Version/s: (was: 2.4)
   2.5

> Deadlock detection works incorrectly with some timeouts that haven't caused 
> by deadlocks.
> -
>
> Key: IGNITE-6527
> URL: https://issues.apache.org/jira/browse/IGNITE-6527
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Fix For: 2.5
>
> Attachments: TxOptimisticDeadlockDetectionIncorrectMessageTest.java
>
>
> Deadlock detection works incorrectly with timeouts that haven't caused by 
> deadlocks. In case of a deadlock in future. Or can detect another deadlock 
> which was not the cause of timeout.
> *requested keys:* keys primary for the same node and blocking in sequential 
> order during the timeout (or all keys that haven't locked by an optimistic 
> transaction in case of near cache).
> *candidates:* keys candidates to be locked on a primary node (entries 
> contains in  GridDhtTxLocal). 
> In the process of updating the Wait-For-Graph requested keys used as 
> candidates.  But "TxDeadlock.toString" method use candidates which were 
> received from messages. 
> 1) It causes an incorrect error message.
> Example: 
> K1: TX1 holds lock, TX2 waits lock.
> K2: TX3 holds lock, TX1 waits lock.
> Transactions:
> TX1 [txId=GridCacheVersion [topVer=118090802, order=1506610794980, 
> nodeOrder=1], nodeId=f03b1ae3-a100-479c-9671-11d5cef0, threadId=455]
> TX2 [txId=GridCacheVersion [topVer=118090802, order=1506610794980, 
> nodeOrder=2], nodeId=2c0c0e78-cab2-4b23-a985-4965e421, threadId=456]
> TX3 [txId=GridCacheVersion [topVer=118090802, order=1506610794980, 
> nodeOrder=3], nodeId=3340dc48-f1a1-4ea8-8742-19b31432, threadId=457]
> Keys:
> K1 [key=6, cache=cache]
> K2 [key=1, cache=cache]
> 2) DD can detect another deadlock which was not the cause of timeout but it 
> would be the cause if the current deadlock did not happen.
> These are very rare situations, but they can happen.
> I see several solutions:
> * Just make a correct message.
> * log warn and continue detecting.



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

[jira] [Updated] (IGNITE-79) Illegal state exception in affinity assignment cache

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-79:
--
Fix Version/s: (was: 2.4)
   2.5

> Illegal state exception in affinity assignment cache
> 
>
> Key: IGNITE-79
> URL: https://issues.apache.org/jira/browse/IGNITE-79
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Yakov Zhdanov
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.5
>
> Attachments: GridServiceProcessorMultiNodeConfigSelfTest#testAll.log
>
>
> {noformat}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated 
> [locNodeId=41caf5c2-3827-4566-9e52-22dabf51f864, topVer=179, head=180]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:328)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:294)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.GridCacheAffinityManager.primaryPartitions(GridCacheAffinityManager.java:349)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:478)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at 
> org.gridgain.grid.kernal.processors.cache.distributed.dht.preloader.GridDhtPartitionDemandPool$ExchangeWorker.body(GridDhtPartitionDemandPool.java:1285)
>  ~[gridgain-core-6.2.1-p1.jar:na]
>   at org.gridgain.grid.util.worker.GridWorker.run(GridWorker.java:151) 
> ~[gridgain-core-6.2.1-p1.jar:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
> {noformat}



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

[jira] [Updated] (IGNITE-6629) Make service automatic redeployment configurable in ServiceConfiguration

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6629:

Fix Version/s: (was: 2.4)
   2.5

> Make service automatic redeployment configurable in ServiceConfiguration
> 
>
> Key: IGNITE-6629
> URL: https://issues.apache.org/jira/browse/IGNITE-6629
> Project: Ignite
>  Issue Type: Improvement
>  Components: managed services
>Affects Versions: 2.3
>Reporter: Ivan Rakov
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: Muted_test
> Fix For: 2.5
>
>
> Before 2.3, if persistence was enabled globally, services were recovered 
> along with system cache. But in 2.3, persistence can be enabled for per data 
> region (IGNITE-6030), and system data region is not persistent.
> We should add feaure to configure service redeployment after restart. 
> Service-related information should be stored in Metastore instead of system 
> cache.
> IgniteChangeGlobalStateServiceTest#testDeployService should be fixed under 
> this ticket.



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

[jira] [Updated] (IGNITE-5678) Need to document and test supported and unsupported SQL features

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5678:

Fix Version/s: (was: 2.4)
   2.5

> Need to document and test supported and unsupported SQL features
> 
>
> Key: IGNITE-5678
> URL: https://issues.apache.org/jira/browse/IGNITE-5678
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, sql
>Reporter: Dmitriy Setrakyan
>Assignee: Sergey Kozlov
>Priority: Major
> Fix For: 2.5
>
>
> We should provide supported and unsupported feature documentation, similar to 
> PostgreSQL: https://www.postgresql.org/docs/devel/static/features.html
> We can do the following:
> * Have a very detailed documented list of all the supported/unsupported 
> features in Ignite SQL engine.
> * Once the list is created, ensure that we have sufficient test coverage for 
> all the supported features.



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

[jira] [Updated] (IGNITE-6679) Clean up some deprecated cache metrics

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6679:

Fix Version/s: (was: 2.4)
   2.5

> Clean up some deprecated cache metrics 
> ---
>
> Key: IGNITE-6679
> URL: https://issues.apache.org/jira/browse/IGNITE-6679
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Sergey Puchnin
>Assignee: Amelchev Nikita
>Priority: Trivial
>  Labels: Newbie
> Fix For: 2.5
>
>
> An old optimistic serializable mode implementation was removed in 2.0 but 
> some cache metrics still present in CacheMetrics interface. 
> Need to clean up and remove these metrics:
> *TxCommitQueueSize*
> *TxPrepareQueueSize*
> *TxStartVersionCountsSize*
> *TxDhtCommitQueueSize*
> *TxDhtPrepareQueueSize*
> *TxDhtStartVersionCountsSize*
> An algorithm for page eviction was changed and metric 
> *DhtEvictQueueCurrentSize* should be removed also.



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

[jira] [Updated] (IGNITE-6464) ignite.active() == true, but ignite.utilityCache() may return null

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6464:

Fix Version/s: (was: 2.4)
   2.5

> ignite.active() == true, but ignite.utilityCache() may return null
> --
>
> Key: IGNITE-6464
> URL: https://issues.apache.org/jira/browse/IGNITE-6464
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Alexey Kuznetsov
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Updated] (IGNITE-6630) Incorrect time units of average transaction commit/rollback duration cache metrics.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6630:

Fix Version/s: (was: 2.5)
   2.4

> Incorrect time units of average transaction commit/rollback duration cache 
> metrics.
> ---
>
> Key: IGNITE-6630
> URL: https://issues.apache.org/jira/browse/IGNITE-6630
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Minor
>  Labels: metrics, newbie
> Fix For: 2.4
>
>
> AverageTxCommitTime and AverageTxRollbackTime metrics in CacheMetrics counts 
> in milliseconds instead of microseconds as pointed in javadoc.
> Simple junit reproducer:
> {code:java}
> public class CacheMetricsTxAvgTimeTest extends GridCommonAbstractTest {
> /** */
> private  CacheConfiguration cacheConfiguration(String name) {
> CacheConfiguration cacheConfiguration = new 
> CacheConfiguration<>(name);
> cacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
> cacheConfiguration.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> cacheConfiguration.setStatisticsEnabled(true);
> return cacheConfiguration;
> }
> /** */
> public void testTxCommitDuration() throws Exception {
> try ( Ignite node = startGrid(0)) {
> IgniteCache cache = 
> node.createCache(cacheConfiguration(DEFAULT_CACHE_NAME));
> try (Transaction tx = node.transactions().txStart()) {
> cache.put(1, 1);
> // Await 1 second.
> U.sleep(1_000);
> tx.commit();
> }
> // Documentation says that this metric is in microseconds.
> float commitTime = cache.metrics().getAverageTxCommitTime();
> // But this assertion will fail because it in milliseconds and 
> returns only ~1000.
> assert commitTime >= 1_000_000;
> }
> }
> }
> {code}



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

[jira] [Updated] (IGNITE-6135) java.sql.Date is serialized using OptimizedMarshaller

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6135:

Fix Version/s: (was: 2.4)
   2.5

> java.sql.Date is serialized using OptimizedMarshaller
> -
>
> Key: IGNITE-6135
> URL: https://issues.apache.org/jira/browse/IGNITE-6135
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.1
>Reporter: Valentin Kulichenko
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.5
>
>
> For some reason, if an object has a field of {{java.sql.Date}}, it's 
> serialized with {{OptimizedMarshaller}}. It should be a first class citizen, 
> similar to {{java.util.Date}}.
> In addition, it's possible to write a field using builder like this:
> {code}
> builder.setField(name, val, java.util.Date.class)
> {code}
> where {{val}} is instance of {{java.sql.Date}}. This leads to an exception 
> during deserialization, because {{java.util.Date}} would be expected.
> More context and code reproducing the issue can be found here: 
> http://apache-ignite-users.70518.x6.nabble.com/JDBC-store-Date-deserialization-problem-td16276.html



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

[jira] [Updated] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5979:

Fix Version/s: (was: 2.4)
   2.5

> [Test Failed]  
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
> 
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Example of failing  - 
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key 
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false, 
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but 
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}



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

[jira] [Commented] (IGNITE-2894) Binary object inside of Externalizable still serialized with OptimizedMarshaller

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-2894:
-

Out of scope for 2.4 release. Makes sense to re-target to 2.5 because I of 
serious impact.

> Binary object inside of Externalizable still serialized with 
> OptimizedMarshaller
> 
>
> Key: IGNITE-2894
> URL: https://issues.apache.org/jira/browse/IGNITE-2894
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Amelchev Nikita
>Priority: Critical
>  Labels: community, customer, iep-2
> Fix For: 2.5
>
>
> When binary marshaller meets an Externalizable object, it switches to 
> optimized marshaller. And if there is a regular object inside, it's still 
> serialized with optimized, even if its type is declared in binary 
> configuration with custom mapper, etc.
> Essentially, binary marshaller should fully support Java serialization, 
> including {{Externalizable}} and {{writeObject}}/{{readObject}}.



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

[jira] [Updated] (IGNITE-5357) Replicated cache reads load balancing.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5357:

Fix Version/s: (was: 2.4)
   2.5

> Replicated cache reads load balancing.
> --
>
> Key: IGNITE-5357
> URL: https://issues.apache.org/jira/browse/IGNITE-5357
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Mikhail Lipkovich
>Priority: Major
>  Labels: newbie
> Fix For: 2.5
>
>
> Currently all read requests from client node to replicated cache will go 
> through primary node for key.
> Need to select random affinity node in topology and send request here (only 
> if readFromBackups=true)
> If where are server nodes collocated on same host with client, must select 
> target node from them.



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

[jira] [Updated] (IGNITE-6630) Incorrect time units of average transaction commit/rollback duration cache metrics.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6630:

Fix Version/s: (was: 2.4)
   2.5

> Incorrect time units of average transaction commit/rollback duration cache 
> metrics.
> ---
>
> Key: IGNITE-6630
> URL: https://issues.apache.org/jira/browse/IGNITE-6630
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Minor
>  Labels: metrics, newbie
> Fix For: 2.5
>
>
> AverageTxCommitTime and AverageTxRollbackTime metrics in CacheMetrics counts 
> in milliseconds instead of microseconds as pointed in javadoc.
> Simple junit reproducer:
> {code:java}
> public class CacheMetricsTxAvgTimeTest extends GridCommonAbstractTest {
> /** */
> private  CacheConfiguration cacheConfiguration(String name) {
> CacheConfiguration cacheConfiguration = new 
> CacheConfiguration<>(name);
> cacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
> cacheConfiguration.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
> cacheConfiguration.setStatisticsEnabled(true);
> return cacheConfiguration;
> }
> /** */
> public void testTxCommitDuration() throws Exception {
> try ( Ignite node = startGrid(0)) {
> IgniteCache cache = 
> node.createCache(cacheConfiguration(DEFAULT_CACHE_NAME));
> try (Transaction tx = node.transactions().txStart()) {
> cache.put(1, 1);
> // Await 1 second.
> U.sleep(1_000);
> tx.commit();
> }
> // Documentation says that this metric is in microseconds.
> float commitTime = cache.metrics().getAverageTxCommitTime();
> // But this assertion will fail because it in milliseconds and 
> returns only ~1000.
> assert commitTime >= 1_000_000;
> }
> }
> }
> {code}



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

[jira] [Updated] (IGNITE-6557) Test IgniteTxRemoveTimeoutObjectsTest has flaky fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6557:

Fix Version/s: (was: 2.4)
   2.5

> Test IgniteTxRemoveTimeoutObjectsTest has flaky fails
> -
>
> Key: IGNITE-6557
> URL: https://issues.apache.org/jira/browse/IGNITE-6557
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Build log:
> {noformat}
> [org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.testTxRemoveTimeoutObjects]
>  junit.framework.AssertionFailedError: Grids contain LockTimeoutObjects.
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.TestCase.fail(TestCase.java:227)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.assertDoesNotContainLockTimeoutObjects(IgniteTxRemoveTimeoutObjectsTest.java:135)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteTxRemoveTimeoutObjectsTest.testTxRemoveTimeoutObjects(IgniteTxRemoveTimeoutObjectsTest.java:92)
> {noformat}



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

[jira] [Updated] (IGNITE-2894) Binary object inside of Externalizable still serialized with OptimizedMarshaller

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2894:

Fix Version/s: (was: 2.4)
   2.5

> Binary object inside of Externalizable still serialized with 
> OptimizedMarshaller
> 
>
> Key: IGNITE-2894
> URL: https://issues.apache.org/jira/browse/IGNITE-2894
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Amelchev Nikita
>Priority: Critical
>  Labels: community, customer, iep-2
> Fix For: 2.5
>
>
> When binary marshaller meets an Externalizable object, it switches to 
> optimized marshaller. And if there is a regular object inside, it's still 
> serialized with optimized, even if its type is declared in binary 
> configuration with custom mapper, etc.
> Essentially, binary marshaller should fully support Java serialization, 
> including {{Externalizable}} and {{writeObject}}/{{readObject}}.



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

[jira] [Updated] (IGNITE-6116) Easy way to enable metrics for default memory region

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6116:

Fix Version/s: (was: 2.4)
   2.5

> Easy way to enable metrics for default memory region
> 
>
> Key: IGNITE-6116
> URL: https://issues.apache.org/jira/browse/IGNITE-6116
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Denis Magda
>Assignee: Aleksei Zaitsev
>Priority: Major
>  Labels: usability
> Fix For: 2.5
>
>
> Presently it's a bit challenging to enable memory metrics for the default 
> memory region unless you define a new one. Add the following two methods to 
> {{MemoryConfiguration}} to address the issue.
> {code}
> MemoryConfiguration.setDefaultMemoryPolicyMetricsEnabled(boolean)
> boolean MemoryConfiguration.isDefaultMemoryPolicyMetricsEnabled()
> {code}
> Discussion on @dev list: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Enabling-memory-and-persistence-metrics-td19582.html



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

[jira] [Updated] (IGNITE-5983) REST: Memory policy metrics should be available via REST.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5983:

Fix Version/s: (was: 2.4)
   2.5

> REST: Memory policy metrics should be available via REST.
> -
>
> Key: IGNITE-5983
> URL: https://issues.apache.org/jira/browse/IGNITE-5983
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.5
>
>
> For now it is possible to get some of cache metrics via REST, but not memory 
> metrics.



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

[jira] [Updated] (IGNITE-1678) IgniteAtomicSequence: make following reservations in advance

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1678:

Fix Version/s: (was: 2.4)
   2.5

> IgniteAtomicSequence: make following reservations in advance
> 
>
> Key: IGNITE-1678
> URL: https://issues.apache.org/jira/browse/IGNITE-1678
> Project: Ignite
>  Issue Type: Improvement
>  Components: data structures
>Affects Versions: ignite-1.4
>Reporter: Denis Magda
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.5
>
> Attachments: Screenshot from 2016-12-15 10-50-22.png
>
>
> In current implementation a new reservation is made when the current local 
> sequence boundary is exceeded.
> In cases when there are many nodes that use the same atomic sequence there 
> can be a situation when all the nodes start doing a new reservation at the 
> same time. This can lead to performance drops.
> As a performance optimization it makes sense to start reserving new sequence 
> slot in advance (in background), like when around 80% of current reservation 
> has already been used. Probably we should add a special parameter to 
> {{AtomicConfiguration}} that will manage such behavior.



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

[jira] [Updated] (IGNITE-6504) Very quick checkpoint can cause AssertionError on next start from LFS

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6504:

Fix Version/s: (was: 2.4)
   2.5

> Very quick checkpoint can cause AssertionError on next start from LFS
> -
>
> Key: IGNITE-6504
> URL: https://issues.apache.org/jira/browse/IGNITE-6504
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
>  Labels: newbie
> Fix For: 2.5
>
>
> Checkpoint markers are compared using their timestamps. If checkpoint took 
> less than 1 millisecond, two subsequent markers will have same timestamp, 
> which will lead to error:
> {noformat}
> java.lang.AssertionError: 
> o1=/data/teamcity/tmpfs/work/db/127_0_0_1_47503/cp/1506338145591-c4f23411-e1b1-4468-856a-4419003bba93-END.bin,
>  
> o2=/data/teamcity/tmpfs/work/db/127_0_0_1_47503/cp/1506338145591-f76c023b-9982-40d7-a1eb-855a33b710f2-END.bin
> at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$4.compare(GridCacheDatabaseSharedManager.java:216)
> at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$4.compare(GridCacheDatabaseSharedManager.java:195)
> at java.util.TimSort.binarySort(TimSort.java:265)
> at java.util.TimSort.sort(TimSort.java:208)
> at java.util.TimSort.sort(TimSort.java:173)
> at java.util.Arrays.sort(Arrays.java:659)
> at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$CheckpointHistory.loadHistory(GridCacheDatabaseSharedManager.java:2704)
> at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$CheckpointHistory.access$2600(GridCacheDatabaseSharedManager.java:2685)
> at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreMemory(GridCacheDatabaseSharedManager.java:1468)
> at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:562)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:722)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:613)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2289)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Updated] (IGNITE-6405) Deadlock is not detected if timed out on client.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6405:

Fix Version/s: (was: 2.4)
   2.5

> Deadlock is not detected if timed out on client.
> 
>
> Key: IGNITE-6405
> URL: https://issues.apache.org/jira/browse/IGNITE-6405
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexei Scherbakov
>Assignee: Andrey Gura
>Priority: Minor
> Fix For: 2.5
>
>
> Timeout exception is thrown instead.
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.transactions;
> import java.util.Collections;
> import java.util.concurrent.CountDownLatch;
> import javax.cache.CacheException;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.TransactionConfiguration;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionDeadlockException;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static 
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static 
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> /**
>  * Tests an ability to eagerly rollback timed out transactions.
>  */
> public class TxPessimisticDeadlockDetectionClient extends 
> GridCommonAbstractTest {
> /** */
> private static final long TX_MIN_TIMEOUT = 1;
> /** */
> private static final long TX_TIMEOUT = 300;
> /** */
> private static final long TX_DEFAULT_TIMEOUT = 3_000;
> /** */
> private static final String CACHE_NAME = "test";
> /** IP finder. */
> private static final TcpDiscoveryVmIpFinder IP_FINDER = new 
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 3;
> /** */
> private final CountDownLatch blocked = new CountDownLatch(1);
> /** */
> private final CountDownLatch unblocked = new CountDownLatch(1);
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setClientMode("client".equals(igniteInstanceName));
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
> TransactionConfiguration txCfg = new TransactionConfiguration();
> txCfg.setDefaultTxTimeout(TX_DEFAULT_TIMEOUT);
> cfg.setTransactionConfiguration(txCfg);
> CacheConfiguration ccfg = new CacheConfiguration(CACHE_NAME);
> ccfg.setAtomicityMode(TRANSACTIONAL);
> ccfg.setBackups(2);
> cfg.setCacheConfiguration(ccfg);
> return cfg;
> }
> /** {@inheritDoc} */
> @Override protected void beforeTest() throws Exception {
> super.beforeTest();
> startGridsMultiThreaded(GRID_CNT);
> }
> /** {@inheritDoc} */
> @Override protected void afterTest() throws Exception {
> super.afterTest();
> stopAllGrids();
> }
> /** */
> protected void validateException(Exception e) {
> assertEquals("Deadlock report is expected",
> TransactionDeadlockException.class, 
> e.getCause().getCause().getClass());
> }
> /**
>  * Tests if deadlock is resolved on timeout with correct message.
>  *
>  * @throws Exception If failed.
>  */
> public void testDeadlockUnblockedOnTimeout() 

[jira] [Updated] (IGNITE-4773) Web Console: Create New Design Concept

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4773:

Fix Version/s: (was: 2.4)
   2.5

> Web Console: Create New Design Concept
> --
>
> Key: IGNITE-4773
> URL: https://issues.apache.org/jira/browse/IGNITE-4773
> Project: Ignite
>  Issue Type: Improvement
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
>Priority: Major
> Fix For: 2.5
>
>
> Don't forget to support multi-clustering.



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

[jira] [Created] (IGNITE-7463) .NET: Thin client: OP_BINARY_TYPE_GET uses writeIntArray for schemas

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7463:
--

 Summary: .NET: Thin client: OP_BINARY_TYPE_GET uses writeIntArray 
for schemas
 Key: IGNITE-7463
 URL: https://issues.apache.org/jira/browse/IGNITE-7463
 Project: Ignite
  Issue Type: Bug
  Components: platforms, thin client
Affects Versions: 2.4
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.4


OP_BINARY_TYPE_GET uses writeIntArray for schemas, which is not consistent with 
OP_BINARY_TYPE_PUT.



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

[jira] [Updated] (IGNITE-7463) .NET: Thin client: OP_BINARY_TYPE_GET uses writeIntArray for schemas

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-7463:
---
Description: 
OP_BINARY_TYPE_GET uses writeIntArray for schemas, which is not consistent with 
OP_BINARY_TYPE_PUT.

Make sure to fix the spec and readme.io doc.

  was:OP_BINARY_TYPE_GET uses writeIntArray for schemas, which is not 
consistent with OP_BINARY_TYPE_PUT.


> .NET: Thin client: OP_BINARY_TYPE_GET uses writeIntArray for schemas
> 
>
> Key: IGNITE-7463
> URL: https://issues.apache.org/jira/browse/IGNITE-7463
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.4
>
>
> OP_BINARY_TYPE_GET uses writeIntArray for schemas, which is not consistent 
> with OP_BINARY_TYPE_PUT.
> Make sure to fix the spec and readme.io doc.



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

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7107:


Github user asfgit closed the pull request at:

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


> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



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

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7107:


Merged to master: {{e7e0f5abd2a69d304a5ce516b8b3288837e7445a}}.
Cherry-picked to ignite-2.4: {{d753298b4012894b56f5c9218325211cd84a21d5}}.

> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



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

[jira] [Updated] (IGNITE-7420) Too thick modal body

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7420:
-
Fix Version/s: 2.4

> Too thick modal body
> 
>
> Key: IGNITE-7420
> URL: https://issues.apache.org/jira/browse/IGNITE-7420
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Alexander Kalinin
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
> Attachments: yz0r1o.jpg
>
>
> !yz0r1o.jpg!



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

[jira] [Assigned] (IGNITE-7462) Web console: remove invoking of depricated methods from code generation

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-7462:
-

Assignee: Vasiliy Sisko

> Web console: remove invoking of depricated methods from code generation
> ---
>
> Key: IGNITE-7462
> URL: https://issues.apache.org/jira/browse/IGNITE-7462
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Minor
> Fix For: 2.4
>
>
> e.g. Warning:(2867, 13) java: setLongQueryWarningTimeout(long) in 
> org.apache.ignite.configuration.CacheConfiguration has been deprecated



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

[jira] [Updated] (IGNITE-7462) Web console: remove invoking of depricated methods from code generation

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7462:
---
Fix Version/s: 2.4

> Web console: remove invoking of depricated methods from code generation
> ---
>
> Key: IGNITE-7462
> URL: https://issues.apache.org/jira/browse/IGNITE-7462
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> e.g. Warning:(2867, 13) java: setLongQueryWarningTimeout(long) in 
> org.apache.ignite.configuration.CacheConfiguration has been deprecated



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

[jira] [Assigned] (IGNITE-7036) Web console: Wrong export of grouped users

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7036:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

> Web console: Wrong export of grouped users
> --
>
> Key: IGNITE-7036
> URL: https://issues.apache.org/jira/browse/IGNITE-7036
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> On export of grouped users when group is collapsed in table only header row 
> is exported.



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

[jira] [Created] (IGNITE-7462) Web console: remove invoking of depricated methods from code generation

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-7462:
--

 Summary: Web console: remove invoking of depricated methods from 
code generation
 Key: IGNITE-7462
 URL: https://issues.apache.org/jira/browse/IGNITE-7462
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


e.g. Warning:(2867, 13) java: setLongQueryWarningTimeout(long) in 
org.apache.ignite.configuration.CacheConfiguration has been deprecated



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

[jira] [Updated] (IGNITE-7461) Web console: incorrect code generation

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko updated IGNITE-7461:
--
Fix Version/s: 2.4

> Web console: incorrect code generation
> --
>
> Key: IGNITE-7461
> URL: https://issues.apache.org/jira/browse/IGNITE-7461
> Project: Ignite
>  Issue Type: Bug
> Environment: Error:(81, 23) java: cannot find symbol
>   symbol:   method setCheckpointPageBufferSize(long)
>   location: variable dataStorageCfg of type 
> org.apache.ignite.configuration.DataStorageConfiguration
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.4
>
>
> Do not forget to change generation of XML configuration



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

[jira] [Updated] (IGNITE-7461) Web console: incorrect code generation

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7461:
---
Description: Do not forget to change generation of XML configuration

> Web console: incorrect code generation
> --
>
> Key: IGNITE-7461
> URL: https://issues.apache.org/jira/browse/IGNITE-7461
> Project: Ignite
>  Issue Type: Bug
> Environment: Error:(81, 23) java: cannot find symbol
>   symbol:   method setCheckpointPageBufferSize(long)
>   location: variable dataStorageCfg of type 
> org.apache.ignite.configuration.DataStorageConfiguration
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
>Priority: Major
>
> Do not forget to change generation of XML configuration



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

[jira] [Updated] (IGNITE-7460) Web console: revise inputs with step for correct validation

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7460:
-
Component/s: wizards

> Web console: revise inputs with step for correct validation
> ---
>
> Key: IGNITE-7460
> URL: https://issues.apache.org/jira/browse/IGNITE-7460
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Priority: Minor
>
> For example Cluster-Data storage configuration-Default data region.
> 'Eviction threshold' input become invalid if value = 0.89 due to it's step=0.5
> So you need to enter the value multiple of 0.5



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

[jira] [Created] (IGNITE-7461) Web console: incorrect code generation

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-7461:
--

 Summary: Web console: incorrect code generation
 Key: IGNITE-7461
 URL: https://issues.apache.org/jira/browse/IGNITE-7461
 Project: Ignite
  Issue Type: Bug
 Environment: Error:(81, 23) java: cannot find symbol
  symbol:   method setCheckpointPageBufferSize(long)
  location: variable dataStorageCfg of type 
org.apache.ignite.configuration.DataStorageConfiguration

Reporter: Pavel Konstantinov
Assignee: Vasiliy Sisko






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

[jira] [Created] (IGNITE-7460) Web console: revise inputs with step for correct validation

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-7460:
--

 Summary: Web console: revise inputs with step for correct 
validation
 Key: IGNITE-7460
 URL: https://issues.apache.org/jira/browse/IGNITE-7460
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


For example Cluster-Data storage configuration-Default data region.
'Eviction threshold' input become invalid if value = 0.89 due to it's step=0.5
So you need to enter the value multiple of 0.5



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

[jira] [Commented] (IGNITE-6607) Thin client: protocol documentation

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-6607:
-

[~dmagda], Please review the following pages:

[https://apacheignite.readme.io/docs/binary-client-protocol]

[https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-key-value-operations]

[https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-sql-operations]

[https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-binary-type-operations]

https://apacheignite.readme.io/v2.3/docs/binary-client-protocol-cache-configuration-operations

 

 

 

> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Prachi Garg
>Priority: Blocker
> Fix For: 2.4
>
>
> Document thin client protocol on Apache Ignite readme.op:
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect
> A list of supported commands can be taken from here:
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/client/ClientMessageParser.java
> The protocol documentation format can be similar to REST API:
> https://apacheignite.readme.io/docs/rest-api



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

[jira] [Assigned] (IGNITE-6607) Thin client: protocol documentation

[Prachi Garg (JIRA)]

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

Prachi Garg reassigned IGNITE-6607:
---

Assignee: Denis Magda  (was: Prachi Garg)

> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 2.4
>
>
> Document thin client protocol on Apache Ignite readme.op:
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect
> A list of supported commands can be taken from here:
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/platform/client/ClientMessageParser.java
> The protocol documentation format can be similar to REST API:
> https://apacheignite.readme.io/docs/rest-api



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

[jira] [Updated] (IGNITE-7231) Cassandra-sessions-pool is running after Ignition.stop

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7231:
--
Priority: Minor  (was: Major)

> Cassandra-sessions-pool is running after Ignition.stop
> --
>
> Key: IGNITE-7231
> URL: https://issues.apache.org/jira/browse/IGNITE-7231
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Mikhail Cherkasov
>Priority: Minor
> Fix For: 2.4
>
> Attachments: ThreadDump.txt
>
>
> Cassandra-sessions-pool is running after Ignition.stop.



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

[jira] [Assigned] (IGNITE-7274) Web Agent: Support multiple statements on Queries screen.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-7274:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Merged to master and 2.4.

To test: open Web Console "Queries" screen and execute multiple statements from 
example block.

> Web Agent: Support multiple statements on Queries screen.
> -
>
> Key: IGNITE-7274
> URL: https://issues.apache.org/jira/browse/IGNITE-7274
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> See IGNITE-6046 for API



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

[jira] [Updated] (IGNITE-7274) Web Agent: Support multiple statements on Queries screen.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-7274:
-
Component/s: wizards

> Web Agent: Support multiple statements on Queries screen.
> -
>
> Key: IGNITE-7274
> URL: https://issues.apache.org/jira/browse/IGNITE-7274
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> See IGNITE-6046 for API



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

[jira] [Updated] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7459:
---
Attachment: screenshot-1.png

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Updated] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7459:
---
Attachment: (was: screenshot-1.png)

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Updated] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7459:
---
Description: 
Currently we print result title (below result table) for scan before it was 
actually ended.
It looks confusing if scan with filter is executing
Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
printed below result table but table shows content from previous scan
 !screenshot-1.png! 

  was:
Currently we print result title (below result table) for scan before it was 
actually ended.
It looks confusing if scan with filter is executing
Look at the screenshot - I set filter = '12957' and it alredy printed below 
result table but it shows content from previous scan
 !screenshot-1.png! 


> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and click Scan and it alredy 
> printed below result table but table shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Updated] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7459:
---
Description: 
Currently we print result title (below result table) for scan before it was 
actually ended.
It looks confusing if scan with filter is executing
Look at the screenshot - I set filter = '12957' and it alredy printed below 
result table but it shows content from previous scan
 !screenshot-1.png! 

  was:
Currently we print result title (below result table) for scan before it was 
actually ended.
It looks confusing if scan with filter is executing

 !screenshot-1.png! 


> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
> Look at the screenshot - I set filter = '12957' and it alredy printed below 
> result table but it shows content from previous scan
>  !screenshot-1.png! 



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

[jira] [Updated] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7459:
---
Description: 
Currently we print result title (below result table) for scan before it was 
actually ended.
It looks confusing if scan with filter is executing

 !screenshot-1.png! 

  was:
Currently we print result title (below result table) for scan before it was 
actually ended.

It looks confusing if scan with filter is executing


> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing
>  !screenshot-1.png! 



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

[jira] [Updated] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7459:
---
Attachment: screenshot-1.png

> Web console: do not show result title until query end
> -
>
> Key: IGNITE-7459
> URL: https://issues.apache.org/jira/browse/IGNITE-7459
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Minor
> Attachments: screenshot-1.png
>
>
> Currently we print result title (below result table) for scan before it was 
> actually ended.
> It looks confusing if scan with filter is executing



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

[jira] [Created] (IGNITE-7459) Web console: do not show result title until query end

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-7459:
--

 Summary: Web console: do not show result title until query end
 Key: IGNITE-7459
 URL: https://issues.apache.org/jira/browse/IGNITE-7459
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


Currently we print result title (below result table) for scan before it was 
actually ended.

It looks confusing if scan with filter is executing



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

[jira] [Commented] (IGNITE-7413) SqlDmlExample: Incorrect result for Delete if run with standalone nodes (Java & .NET)

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7413:
-

@Pavel Tupitsyn, please merge the changes.

> SqlDmlExample: Incorrect result for Delete if run with standalone nodes (Java 
> & .NET)
> -
>
> Key: IGNITE-7413
> URL: https://issues.apache.org/jira/browse/IGNITE-7413
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Irina Zaporozhtseva
>Assignee: Denis Magda
>Priority: Minor
>  Labels: .NET
> Fix For: 2.4
>
>
> Datagrid.QueryDmlExample: Incorrect result for Delete if run with standalone 
> nodes
>  
> without standalone nodes:
> {code}
> >>> Delete non-ASF employees 
> >>> 1: John Doe, ASF, 4400 
> >>> 2: Jane Roe, ASF, 5500
> {code}
>  
> with standalone nodes:
> {code}
> >>> Delete non-ASF employees 
> >>> 1: John Doe, ASF, 4400
> >>> 4: Richard Miles, Eclipse, 3000 
> >>> 2: Jane Roe, ASF, 5500
> {code}



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

[jira] [Assigned] (IGNITE-7413) SqlDmlExample: Incorrect result for Delete if run with standalone nodes (Java & .NET)

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7413:
---

Assignee: Pavel Tupitsyn  (was: Denis Magda)

> SqlDmlExample: Incorrect result for Delete if run with standalone nodes (Java 
> & .NET)
> -
>
> Key: IGNITE-7413
> URL: https://issues.apache.org/jira/browse/IGNITE-7413
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Irina Zaporozhtseva
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET
> Fix For: 2.4
>
>
> Datagrid.QueryDmlExample: Incorrect result for Delete if run with standalone 
> nodes
>  
> without standalone nodes:
> {code}
> >>> Delete non-ASF employees 
> >>> 1: John Doe, ASF, 4400 
> >>> 2: Jane Roe, ASF, 5500
> {code}
>  
> with standalone nodes:
> {code}
> >>> Delete non-ASF employees 
> >>> 1: John Doe, ASF, 4400
> >>> 4: Richard Miles, Eclipse, 3000 
> >>> 2: Jane Roe, ASF, 5500
> {code}



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

[jira] [Assigned] (IGNITE-7413) SqlDmlExample: Incorrect result for Delete if run with standalone nodes (Java & .NET)

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7413:
---

Assignee: Denis Magda  (was: Pavel Tupitsyn)

> SqlDmlExample: Incorrect result for Delete if run with standalone nodes (Java 
> & .NET)
> -
>
> Key: IGNITE-7413
> URL: https://issues.apache.org/jira/browse/IGNITE-7413
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Irina Zaporozhtseva
>Assignee: Denis Magda
>Priority: Minor
>  Labels: .NET
> Fix For: 2.4
>
>
> Datagrid.QueryDmlExample: Incorrect result for Delete if run with standalone 
> nodes
>  
> without standalone nodes:
> {code}
> >>> Delete non-ASF employees 
> >>> 1: John Doe, ASF, 4400 
> >>> 2: Jane Roe, ASF, 5500
> {code}
>  
> with standalone nodes:
> {code}
> >>> Delete non-ASF employees 
> >>> 1: John Doe, ASF, 4400
> >>> 4: Richard Miles, Eclipse, 3000 
> >>> 2: Jane Roe, ASF, 5500
> {code}



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

[jira] [Closed] (IGNITE-7353) Document CREATE TABLE ... DEFAULT feature

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-7353.
---

> Document CREATE TABLE ... DEFAULT feature
> -
>
> Key: IGNITE-7353
> URL: https://issues.apache.org/jira/browse/IGNITE-7353
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>




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

[jira] [Assigned] (IGNITE-7376) Document optional SQL on-heap row cache

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7376:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Document optional SQL on-heap row cache
> ---
>
> Key: IGNITE-7376
> URL: https://issues.apache.org/jira/browse/IGNITE-7376
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Taras Ledkov
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
>
> Add documentation for on-heap row cache implemented at IGNITE-7173



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

[jira] [Commented] (IGNITE-7376) Document optional SQL on-heap row cache

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7376:
-

[~tledkov-gridgain] , thanks for documentation. I've finished with the review 
on my side doing minor improvements.

 

[~pgarg] , please do a final review of the section below and close the ticket:

https://apacheignite-sql.readme.io/v2.3/docs/performance-and-debugging_24_hidden#sql-on-heap-row-cache

> Document optional SQL on-heap row cache
> ---
>
> Key: IGNITE-7376
> URL: https://issues.apache.org/jira/browse/IGNITE-7376
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Taras Ledkov
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> Add documentation for on-heap row cache implemented at IGNITE-7173



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

[jira] [Closed] (IGNITE-5336) Add documentation for JDBC thick driver BLOB support

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-5336.
---

> Add documentation for JDBC thick driver BLOB support
> 
>
> Key: IGNITE-5336
> URL: https://issues.apache.org/jira/browse/IGNITE-5336
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Prachi Garg
>Priority: Critical
> Fix For: 2.4
>
>
> Need to add documentation to readme.io about IGNITE-5203.
> The documentation domain was moved:
> https://apacheignite-sql.readme.io/docs/jdbc-client-driver



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

[jira] [Resolved] (IGNITE-5336) Add documentation for JDBC thick driver BLOB support

[Prachi Garg (JIRA)]

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

Prachi Garg resolved IGNITE-5336.
-
Resolution: Not A Problem

After the discussion with Andrey, we decided that there is nothing to document.

> Add documentation for JDBC thick driver BLOB support
> 
>
> Key: IGNITE-5336
> URL: https://issues.apache.org/jira/browse/IGNITE-5336
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Prachi Garg
>Priority: Critical
> Fix For: 2.4
>
>
> Need to add documentation to readme.io about IGNITE-5203.
> The documentation domain was moved:
> https://apacheignite-sql.readme.io/docs/jdbc-client-driver



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

[jira] [Updated] (IGNITE-6784) Document cluster activation via REST protocol

[Prachi Garg (JIRA)]

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

Prachi Garg updated IGNITE-6784:

Fix Version/s: (was: 2.4)
   2.5

> Document cluster activation via REST protocol
> -
>
> Key: IGNITE-6784
> URL: https://issues.apache.org/jira/browse/IGNITE-6784
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 2.4
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.5
>
>
> Starting Ignite 2.3 cluster can be activated with REST protocol. The 
> following commands are supported:
> - {{activate}} - actives the cluster.
> - {{deactivate}} - deactivates the cluster.
> - {{currentstate}} - checks current cluster state.
> Update both pages below:
> https://apacheignite.readme.io/docs/rest-api
> https://apacheignite.readme.io/v2.2/docs/cluster-activation



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

[jira] [Updated] (IGNITE-7458) NPE occurs after node restart with native persistence enabled.

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7458:
--
Description: 
We have a report from a user:

[http://apache-ignite-users.70518.x6.nabble.com/NPE-from-the-native-persistence-enable-node-td19555.html]

 

it says that NPE occurred after node restart with native persistence enabled.

> NPE occurs after node restart with native persistence enabled.
> --
>
> Key: IGNITE-7458
> URL: https://issues.apache.org/jira/browse/IGNITE-7458
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
>
> We have a report from a user:
> [http://apache-ignite-users.70518.x6.nabble.com/NPE-from-the-native-persistence-enable-node-td19555.html]
>  
> it says that NPE occurred after node restart with native persistence enabled.



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

[jira] [Updated] (IGNITE-7458) NPE occurs after node restart with native persistence enabled.

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7458:
--
Summary: NPE occurs after node restart with native persistence enabled.  
(was: NPE after node restart with native persistence enabled.)

> NPE occurs after node restart with native persistence enabled.
> --
>
> Key: IGNITE-7458
> URL: https://issues.apache.org/jira/browse/IGNITE-7458
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.3
> Environment: We have a report from a user:
> [http://apache-ignite-users.70518.x6.nabble.com/NPE-from-the-native-persistence-enable-node-td19555.html]
>  
> it says that NPE occurred after node restart with native persistence enabled.
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Updated] (IGNITE-7458) NPE occurs after node restart with native persistence enabled.

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-7458:
--
Environment: (was: We have a report from a user:

[http://apache-ignite-users.70518.x6.nabble.com/NPE-from-the-native-persistence-enable-node-td19555.html]

 

it says that NPE occurred after node restart with native persistence enabled.)

> NPE occurs after node restart with native persistence enabled.
> --
>
> Key: IGNITE-7458
> URL: https://issues.apache.org/jira/browse/IGNITE-7458
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Created] (IGNITE-7458) NPE after node restart with native persistence enabled.

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7458:
-

 Summary: NPE after node restart with native persistence enabled.
 Key: IGNITE-7458
 URL: https://issues.apache.org/jira/browse/IGNITE-7458
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.3
 Environment: We have a report from a user:

[http://apache-ignite-users.70518.x6.nabble.com/NPE-from-the-native-persistence-enable-node-td19555.html]

 

it says that NPE occurred after node restart with native persistence enabled.
Reporter: Mikhail Cherkasov
 Fix For: 2.5






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

[jira] [Commented] (IGNITE-1401) Introduce special local node discovery events

[Andrey Kornev (JIRA)]

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

Andrey Kornev commented on IGNITE-1401:
---

Vladimir, as I explained in the description, the aim of this enhancements was 
to ensure that the new EVT_LOCAL_NODE_JOINED and EVT_LOCAL_NODE_LEFT events be 
delivered on the same thread as the rest of the discovery events, thus ensuring 
their correct ordering. Also, these new events would equally apply to client as 
well server nodes.

In fact, Ignite already tracks local node membership in GridDiscoveryManager: 

{noformat}
// If this is a local join event, just save it and do not notify listeners.
if (locJoinEvt) {
...
}
{noformat}

All is needed is to actually add a line to notify the listeners.


> Introduce special local node discovery events
> -
>
> Key: IGNITE-1401
> URL: https://issues.apache.org/jira/browse/IGNITE-1401
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Andrey Kornev
>Priority: Minor
>  Labels: easyfix
>
> Currently, Ignite doesn't record the EVT_NODE_JOINED event for the local 
> node. In general, it might be useful to know when the local node has joined 
> the cluster as well as when the local node has left the cluster (or has 
> failed to join). 
> I'd like to propose to introduce a couple of new Ignite events: 
> EVT_LOCAL_NODE_JOINED and EVT_LOCAL_NODE_LEFT that will be generated by the 
> Discovery Manager when it has successfully started and when it has 
> disconnected correspondingly. Importantly, the events must be generated by 
> the discovery worker thread (and only this thread!) so that the total 
> ordering of all discovery events is preserved. Clearly, the 
> EVT_LOCAL_NODE_LEFT event should be generated and delivered on the 
> best-effort basis. 
> EVT_LOCAL_NODE_FAILED may also be considered: it could be generated when the 
> cluster coordinator has refused the node's attempt to join the cluster (for 
> whatever reason).
> The introduction of local node-specific discovery events rather than reusing 
> the existing ones would help keep the existing code backward compatible, and 
> in general makes sense.
> It is possible to approximate this feature using just the existing API, but 
> the code is complex, prone to race conditions and may require use of Ignite 
> internal APIs.



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

[jira] [Reopened] (IGNITE-1401) Introduce special local node discovery events

[Andrey Kornev (JIRA)]

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

Andrey Kornev reopened IGNITE-1401:
---

> Introduce special local node discovery events
> -
>
> Key: IGNITE-1401
> URL: https://issues.apache.org/jira/browse/IGNITE-1401
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Andrey Kornev
>Priority: Minor
>  Labels: easyfix
>
> Currently, Ignite doesn't record the EVT_NODE_JOINED event for the local 
> node. In general, it might be useful to know when the local node has joined 
> the cluster as well as when the local node has left the cluster (or has 
> failed to join). 
> I'd like to propose to introduce a couple of new Ignite events: 
> EVT_LOCAL_NODE_JOINED and EVT_LOCAL_NODE_LEFT that will be generated by the 
> Discovery Manager when it has successfully started and when it has 
> disconnected correspondingly. Importantly, the events must be generated by 
> the discovery worker thread (and only this thread!) so that the total 
> ordering of all discovery events is preserved. Clearly, the 
> EVT_LOCAL_NODE_LEFT event should be generated and delivered on the 
> best-effort basis. 
> EVT_LOCAL_NODE_FAILED may also be considered: it could be generated when the 
> cluster coordinator has refused the node's attempt to join the cluster (for 
> whatever reason).
> The introduction of local node-specific discovery events rather than reusing 
> the existing ones would help keep the existing code backward compatible, and 
> in general makes sense.
> It is possible to approximate this feature using just the existing API, but 
> the code is complex, prone to race conditions and may require use of Ignite 
> internal APIs.



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

[jira] [Commented] (IGNITE-7456) Fix wrong batch logic in distributed MLP training.

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7456:


As of now it looks good to go to master and to 2.4 branch: code changes are OK, 
unit tests pass and examples run correctly. One thing worth doing prior to 
merge is to get rid of double-whitespace in the text of the message in 
MLPGroupTrainerExample: {{">>> Distributed  multilayer perceptron example 
started."}} (it's between words Distributed and multilayer).

 

Another interesting thing I noticed when I tried MLP group example with number 
of steps larger that set in code (100 instead of 20): there were confusing 
exceptions in example log. Note I only managed to get it on my machine; when 
Artem tried it on his machine example run without exceptions. Because of that I 
attached my execution log here: 
[^IGNITE-7456.NPE.MLPGroupTrainerExample.tweaked.log]. This issue is out of 
scope of this ticket since it was with settings that aren't there but after 
this change is merged to masted we better open a separate ticket to investigate 
what could go wrong in my trial change.

> Fix wrong batch logic in distributed MLP training.
> --
>
> Key: IGNITE-7456
> URL: https://issues.apache.org/jira/browse/IGNITE-7456
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.4
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>Priority: Major
> Fix For: 2.4
>
> Attachments: IGNITE-7456.NPE.MLPGroupTrainerExample.tweaked.log
>
>
> Batch for training is created outside of training loop, therefore in each 
> local step we work with the same batch.



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

[jira] [Updated] (IGNITE-7456) Fix wrong batch logic in distributed MLP training.

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7456:
---
Attachment: IGNITE-7456.NPE.MLPGroupTrainerExample.tweaked.log

> Fix wrong batch logic in distributed MLP training.
> --
>
> Key: IGNITE-7456
> URL: https://issues.apache.org/jira/browse/IGNITE-7456
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.4
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>Priority: Major
> Fix For: 2.4
>
> Attachments: IGNITE-7456.NPE.MLPGroupTrainerExample.tweaked.log
>
>
> Batch for training is created outside of training loop, therefore in each 
> local step we work with the same batch.



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

[jira] [Commented] (IGNITE-7403) Improve content on What's Ignite page

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-7403:
---

[~vabramova], thanks, but I don't like the amount of real estate we spend on 
links. I would like the links to be very compact and then move on to Ignite 
Facts. On top of that, I want us to see how we can show Ignite Facts in a more 
compact fashion. 

> Improve content on What's Ignite page
> -
>
> Key: IGNITE-7403
> URL: https://issues.apache.org/jira/browse/IGNITE-7403
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Vica Abramova
>Priority: Major
> Attachments: What.png, What_v2.png
>
>
> A proposed of a new draft for the What's Ignite page:
> https://ignite.apache.org/whatisignite-2.html
> The goal is to make the page more informative and tell about the main things 
> of Ignite or provide references to them. Overall, the structure should be as 
> follows:
> - Product name and definition.
> - Diagram.
> - Features and Benefits
> - Ignite facts



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

[jira] [Commented] (IGNITE-7403) Improve content on What's Ignite page

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7403:
-

[~vabramova] , thanks for the sketches. Let me think over a bit which one to 
use.

> Improve content on What's Ignite page
> -
>
> Key: IGNITE-7403
> URL: https://issues.apache.org/jira/browse/IGNITE-7403
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Vica Abramova
>Priority: Major
> Attachments: What.png, What_v2.png
>
>
> A proposed of a new draft for the What's Ignite page:
> https://ignite.apache.org/whatisignite-2.html
> The goal is to make the page more informative and tell about the main things 
> of Ignite or provide references to them. Overall, the structure should be as 
> follows:
> - Product name and definition.
> - Diagram.
> - Features and Benefits
> - Ignite facts



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

[jira] [Commented] (IGNITE-7378) WAL converter: add records statistic to WAL reader dev-util

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7378:


Github user dspavlov closed the pull request at:

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


> WAL converter: add records statistic to WAL reader dev-util
> ---
>
> Key: IGNITE-7378
> URL: https://issues.apache.org/jira/browse/IGNITE-7378
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.4
>
>
> In Standalone WAL iterator implemented under 
> https://issues.apache.org/jira/browse/IGNITE-5558 and in 
> https://issues.apache.org/jira/browse/IGNITE-6277
> but this tool just prints record into log.
> It is usefull to see at least machine readable statistics of record types, 
> caches involved into this log to find out most popular record types.
> It is suggested to add statistic to this tool and print this at end of 
> execution.
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73638827



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

[jira] [Commented] (IGNITE-7380) Avoid updating PagePartitionCounters in case all counters were not modified

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7380:


Github user dspavlov closed the pull request at:

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


> Avoid updating PagePartitionCounters in case all counters were not modified
> ---
>
> Key: IGNITE-7380
> URL: https://issues.apache.org/jira/browse/IGNITE-7380
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.4
>
>
> PagePartitionCountersIO ignores actual values of counters and marks pages 
> dirty even if partition has no counters update.
> This leads to  PAGE_RECORD creation for pages from PagePartitionCountersIO
> and as result with pages from TrackingPageIO.
> These modificaiton may be skipped if counters are checked for equality before 
> storing data.



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

[jira] [Commented] (IGNITE-7456) Fix wrong batch logic in distributed MLP training.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7456:


GitHub user artemmalykh opened a pull request:

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

IGNITE-7456: Fix wrong batch logic in distributed MLP training.



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

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

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

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


commit 995d781b58b57c4721b3fd92d3867975d652272a
Author: Artem Malykh 
Date:   2018-01-12T13:22:21Z

IGNITE-7397: Fix cache configuration and reduced trainings count in MLP 
group training test.

commit 123f14ccc8b8c0e27104061b4644876b45a8a123
Author: Artem Malykh 
Date:   2018-01-12T13:23:02Z

Merge branch 'master-apache' into ignite-7397

commit b2cfa9017b69b8ebfd2bca4143c91315c1fd3a06
Author: Artem Malykh 
Date:   2018-01-12T15:15:01Z

IGNITE-7350: Moved update calculators from nn package to optimization.

commit 32de402cd6939aba24cec572e42ddc8d90dc3251
Author: Artem Malykh 
Date:   2018-01-12T15:24:33Z

IGNITE-7350: Moved LossFunctions, fixed some comments.

commit eb1ceb580c418ec91c3e5b42585132b15073aa97
Author: Artem Malykh 
Date:   2018-01-12T16:03:26Z

IGNITE-7350: Removed in-place changing of update and model in Nesterov 
update calculator.

commit e5d3299c6b344fb2b9c54b6f578cdda2739c7ffa
Author: Artem Malykh 
Date:   2018-01-12T16:07:31Z

IGNITE-7350: Default implementation for 'withParameters'.

commit b0dc57dcf8e717def820806dab62d50715de02f6
Author: Artem Malykh 
Date:   2018-01-12T16:11:26Z

IGNITE-7350: Moved some files to appropriate packages.

commit 3badb8aaf899448cf5fb222048a1e5e7fdd247b1
Author: Artem Malykh 
Date:   2018-01-12T16:40:23Z

IGNITE-7350: Added javadoc.

commit ef6724af220a7a1bdb9523f497787b185621104d
Author: Artem Malykh 
Date:   2018-01-12T20:42:02Z

IGNITE-7350: Changed todos.

commit 3dc51d7da99512aac5f734d0b8ddde3f33871d48
Author: Artem Malykh 
Date:   2018-01-12T20:53:18Z

IGNITE-7350: Added javadocs.

commit 20f3d34aaf6f072be60ac8744112f91308540aba
Author: Artem Malykh 
Date:   2018-01-12T21:14:30Z

IGNITE-7350: Added javadocs.

commit a243d7875b4d33e1d1abab710a8442affeb38119
Author: Artem Malykh 
Date:   2018-01-12T21:16:08Z

IGNITE-7350: Added javadocs.

commit 0da733145252fe92f8a894d2364da3695923e40e
Author: Artem Malykh 
Date:   2018-01-17T16:08:06Z

IGNITE-7456: Fixed wrong batches logic.

commit fe3ea2d6a7ec9fc97c255c3bbd04bb91bf92ad69
Author: Artem Malykh 
Date:   2018-01-17T16:09:39Z

ignite-7456: Some changes to tests.

commit 53aef283e94f61a0ee96549c2bcae9f1fe2bdb4d
Author: Artem Malykh 
Date:   2018-01-17T16:29:58Z

Merge branch 'master-apache' into ignite-7456

# Conflicts:
#   
modules/ml/src/main/java/org/apache/ignite/ml/nn/MLPGroupUpdateTrainerCacheInput.java
#   
modules/ml/src/main/java/org/apache/ignite/ml/nn/trainers/distributed/MLPGroupUpdateTrainingData.java
#   
modules/ml/src/main/java/org/apache/ignite/ml/nn/trainers/distributed/MLPGroupUpdateTrainingLoopData.java
#   
modules/ml/src/main/java/org/apache/ignite/ml/optimization/updatecalculators/SimpleGDParameter.java
#   
modules/ml/src/main/java/org/apache/ignite/ml/trainers/local/package-info.java
#   modules/ml/src/main/java/org/apache/ignite/ml/util/Utils.java
#   
modules/ml/src/test/java/org/apache/ignite/ml/nn/MLPGroupTrainerTest.java

commit d34e2c7185c2f9a309fd7e8d9fdb6ef6aea1ea6a
Author: Artem Malykh 
Date:   2018-01-17T16:33:06Z

IGNITE-7456: Rolled back paths to mnist.

commit 2d98abfe94a7a80ed58ad0a00944ee95a4c749f2
Author: Artem Malykh 
Date:   2018-01-17T16:33:45Z

IGNITE-7456: Reformatted javadoc.




> Fix wrong batch logic in distributed MLP training.
> --
>
> Key: IGNITE-7456
> URL: https://issues.apache.org/jira/browse/IGNITE-7456
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.4
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>Priority: Major
> Fix For: 2.4
>
>
> Batch for training is created outside of training loop, therefore in each 
> local step we work with the same batch.



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

[jira] [Updated] (IGNITE-7456) Fix wrong batch logic in distributed MLP training.

[Artem Malykh (JIRA)]

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

Artem Malykh updated IGNITE-7456:
-
Summary: Fix wrong batch logic in distributed MLP training.  (was: Wrong 
batch logic in distributed MLP training.)

> Fix wrong batch logic in distributed MLP training.
> --
>
> Key: IGNITE-7456
> URL: https://issues.apache.org/jira/browse/IGNITE-7456
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.4
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>Priority: Major
> Fix For: 2.4
>
>
> Batch for training is created outside of training loop, therefore in each 
> local step we work with the same batch.



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

[jira] [Commented] (IGNITE-7077) Spark Data Frame Support. Strategy to convert complete query to Ignite SQL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7077:


GitHub user nizhikov opened a pull request:

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

IGNITE-7077: Implementation of Spark query optimization.



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

$ git pull https://github.com/nizhikov/ignite IGNITE-7077

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

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






> Spark Data Frame Support. Strategy to convert complete query to Ignite SQL
> --
>
> Key: IGNITE-7077
> URL: https://issues.apache.org/jira/browse/IGNITE-7077
> Project: Ignite
>  Issue Type: New Feature
>  Components: spark
>Affects Versions: 2.3
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: bigdata
> Fix For: 2.4
>
>
> Basic support of Spark Data Frame for Ignite implemented in IGNITE-3084.
> We need to implement custom spark strategy that can convert whole Spark SQL 
> query to Ignite SQL Query if query consists of only Ignite tables.
> The strategy does nothing if spark query includes not only Ignite tables.
> Memsql implementation can be taken as an example - 
> https://github.com/memsql/memsql-spark-connector



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

[jira] [Commented] (IGNITE-7107) Apache Ignite RPM packages

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7107:


GitHub user vveider opened a pull request:

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

IGNITE-7107 Apache Ignite RPM packages

 * added changelog to package specification

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

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

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

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


commit 5edaabd6cf64f134d121a07695f0b50e2dcf05d7
Author: Ivanov Petr 
Date:   2018-01-17T16:07:23Z

IGNITE-7107 Apache Ignite RPM packages
 * added changelog to package specification




> Apache Ignite RPM packages
> --
>
> Key: IGNITE-7107
> URL: https://issues.apache.org/jira/browse/IGNITE-7107
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
>  Labels: important
> Fix For: 2.4
>
>
> Pack apache-ignite into RPM package for distribution through RPM-based Linux 
> distros (Fedora / CentOS / RHEL, etc.)
> Iteration (I): bundle (all-in-one) RPM



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

[jira] [Updated] (IGNITE-7454) Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7454:
---
Description: 
Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203: 
\{{org.apache.ignite.ml.testsuites}}. Also, it is not added to the list in 
{{IgniteExamplesSelfTestSuite{{ which is supposed to run all examples 
self-tests.

Change to correct package: \{{org.apache.ignite.testsuites}} and add to main 
testsuite.

For the sake of completeness, a bunch of newer ml benchmarks (done per 
IGNITE-7214 and IGNITE-7097) were forgotten to be moved in yardstick module 
when merging to master. These should be fixed (moved to proper folder).

  was:
Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203: 
\{{org.apache.ignite.ml.testsuites}}. Also, it is not added to the list in 
{{IgniteExamplesSelfTestSuite{{ which is supposed to run all examples 
self-tests.

Change to correct package: \{{org.apache.ignite.testsuites}} and add to main 
testsuite.

For the sake of completeness, a bunch of newer ml benchmarks were forgotten to 
be moved in yardstick module when merging to master. These should be fixed 
(moved to proper folder).


> Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203
> -
>
> Key: IGNITE-7454
> URL: https://issues.apache.org/jira/browse/IGNITE-7454
> Project: Ignite
>  Issue Type: Bug
>  Components: examples, ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>
> Wrong package in IgniteExamplesMLTestSuite after it was moved per 
> IGNITE-7203: \{{org.apache.ignite.ml.testsuites}}. Also, it is not added to 
> the list in {{IgniteExamplesSelfTestSuite{{ which is supposed to run all 
> examples self-tests.
> Change to correct package: \{{org.apache.ignite.testsuites}} and add to main 
> testsuite.
> For the sake of completeness, a bunch of newer ml benchmarks (done per 
> IGNITE-7214 and IGNITE-7097) were forgotten to be moved in yardstick module 
> when merging to master. These should be fixed (moved to proper folder).



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

[jira] [Commented] (IGNITE-7450) Always use RandomAccessFileIO for FileWriteAheadLogManager

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7450:
-

Merged to master and ignite-2.4 branches.

> Always use RandomAccessFileIO for FileWriteAheadLogManager
> --
>
> Key: IGNITE-7450
> URL: https://issues.apache.org/jira/browse/IGNITE-7450
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.4
>
>
> Always use {{RandomAccessFileIO}} for {{FileWriteAheadLogManager}}. Other 
> implementations don't make sense after IGNITE-6339.



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

[jira] [Commented] (IGNITE-5565) Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.

[Sergey Kosarev (JIRA)]

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

Sergey Kosarev commented on IGNITE-5565:


PR

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

> Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.
> --
>
> Key: IGNITE-5565
> URL: https://issues.apache.org/jira/browse/IGNITE-5565
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Sergey Kosarev
>Priority: Major
>
> 1) Cron4J is very old:
>   Latest Cron4j 2.2.5 released: 28-Dec-2011 
>   Latest Quarz 2.3.0 released: 20-Apr-2017
> 2) Not very friendly license:
>   CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
>   Quartz is freely usable, licensed under the Apache 2.0 license.
> So, if we replace Cron4J  with Quartz we can move ignite-schedule module
>  from lgpl profile to main distribution.
> Also spring's scheduler could be considered as Cron4J alternative.



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

[jira] [Commented] (IGNITE-5565) Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5565:


GitHub user macrergate opened a pull request:

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

IGNITE-5565 replace Cron4J with Quartz



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

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

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

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


commit 6760c40230dece2f439ffadd5341e0c505bf2a89
Author: Sergey Kosarev 
Date:   2018-01-17T14:31:49Z

IGNITE-5565 replace Cron4J with Quartz




> Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.
> --
>
> Key: IGNITE-5565
> URL: https://issues.apache.org/jira/browse/IGNITE-5565
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Sergey Kosarev
>Priority: Major
>
> 1) Cron4J is very old:
>   Latest Cron4j 2.2.5 released: 28-Dec-2011 
>   Latest Quarz 2.3.0 released: 20-Apr-2017
> 2) Not very friendly license:
>   CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE
>   Quartz is freely usable, licensed under the Apache 2.0 license.
> So, if we replace Cron4J  with Quartz we can move ignite-schedule module
>  from lgpl profile to main distribution.
> Also spring's scheduler could be considered as Cron4J alternative.



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

[jira] [Commented] (IGNITE-7450) Always use RandomAccessFileIO for FileWriteAheadLogManager

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-7450:
-

Fixed. TC looks good.

> Always use RandomAccessFileIO for FileWriteAheadLogManager
> --
>
> Key: IGNITE-7450
> URL: https://issues.apache.org/jira/browse/IGNITE-7450
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.4
>
>
> Always use {{RandomAccessFileIO}} for {{FileWriteAheadLogManager}}. Other 
> implementations don't make sense after IGNITE-6339.



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

[jira] [Updated] (IGNITE-7454) Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7454:
---
Description: 
Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203: 
\{{org.apache.ignite.ml.testsuites}}. Also, it is not added to the list in 
{{IgniteExamplesSelfTestSuite{{ which is supposed to run all examples 
self-tests.

Change to correct package: \{{org.apache.ignite.testsuites}} and add to main 
testsuite.

For the sake of completeness, a bunch of newer ml benchmarks were forgotten to 
be moved in yardstick module when merging to master. These should be fixed 
(moved to proper folder).

  was:
Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203: 
\{{org.apache.ignite.ml.testsuites}}. Also, it is not added to the list in 
{{IgniteExamplesSelfTestSuite{{ which is supposed to run all examples 
self-tests.

Change to correct package: \{{org.apache.ignite.testsuites}} and add to main 
testsuite.


> Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203
> -
>
> Key: IGNITE-7454
> URL: https://issues.apache.org/jira/browse/IGNITE-7454
> Project: Ignite
>  Issue Type: Bug
>  Components: examples, ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>
> Wrong package in IgniteExamplesMLTestSuite after it was moved per 
> IGNITE-7203: \{{org.apache.ignite.ml.testsuites}}. Also, it is not added to 
> the list in {{IgniteExamplesSelfTestSuite{{ which is supposed to run all 
> examples self-tests.
> Change to correct package: \{{org.apache.ignite.testsuites}} and add to main 
> testsuite.
> For the sake of completeness, a bunch of newer ml benchmarks were forgotten 
> to be moved in yardstick module when merging to master. These should be fixed 
> (moved to proper folder).



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

[jira] [Updated] (IGNITE-7454) Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7454:
---
Component/s: yardstick

> Wrong package in IgniteExamplesMLTestSuite after it was moved per IGNITE-7203
> -
>
> Key: IGNITE-7454
> URL: https://issues.apache.org/jira/browse/IGNITE-7454
> Project: Ignite
>  Issue Type: Bug
>  Components: examples, ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>
> Wrong package in IgniteExamplesMLTestSuite after it was moved per 
> IGNITE-7203: \{{org.apache.ignite.ml.testsuites}}. Also, it is not added to 
> the list in {{IgniteExamplesSelfTestSuite{{ which is supposed to run all 
> examples self-tests.
> Change to correct package: \{{org.apache.ignite.testsuites}} and add to main 
> testsuite.
> For the sake of completeness, a bunch of newer ml benchmarks were forgotten 
> to be moved in yardstick module when merging to master. These should be fixed 
> (moved to proper folder).



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

[jira] [Comment Edited] (IGNITE-7449) Rebalancing metrics doesn't display actual information about current rebalance state

[Dmitry Sherstobitov (JIRA)]

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

Dmitry Sherstobitov edited comment on IGNITE-7449 at 1/17/18 3:18 PM:
--

I've investigated this problem and found that observable cache have small 
amount of data on the node.
 So rebalance metrics have long type - observable values are less that 1 and 
displayed as 0.

On the other hand case with massive caches displays correct information for 
this metrics


was (Author: qvad):
I've investigated this problem and found that observable cache have small 
amount of data on the node.
 So rebalance metrics have long type - observable values are less that 1 and 
displayed as 0.

On the other hand massive caches displays correct information for this metrics

> Rebalancing metrics doesn't display actual information about current 
> rebalance state
> 
>
> Key: IGNITE-7449
> URL: https://issues.apache.org/jira/browse/IGNITE-7449
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitry Sherstobitov
>Priority: Major
>
> In case of shutdown node with clear LFS following metrics doesn't display 
> correct information about rebalance:
> RebalancingKeysRate
> RebalancingBytesRate
> KeysToRebalanceLeft
>  
> Otherwise RebalancingPartitionsCount metric displays information correctly
> Steps to reproduce:
>  1. Cluster with enabled statistics
>  2. Shutdown node and clear LFS
>  3. Run node
>  4. Start node and ask node for current rebalance state through JMX:
> Current result:
> 1 tick
> RebalancingKeysRate 0
> RebalancingBytesRate 0
> KeysToRebalanceLeft 0
> RebalancingPartitionsCount 342
> 2 tick
> RebalancingKeysRate 0
> RebalancingBytesRate 0
> KeysToRebalanceLeft 0
> RebalancingPartitionsCount 80
> Expected:
> 2 tick
> RebalancingKeysRate SOME_NON_ZERO_VALUE
> RebalancingBytesRate SOME_NON_ZERO_VALUE
> KeysToRebalanceLeft SOME_NON_ZERO_VALUE
> RebalancingPartitionsCount 80
>  
> UPD: -DIGNITE_REBALANCE_STATISTICS_TIME_INTERVAL=1000 doesn't affect results



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