[jira] [Reopened] (IGNITE-12438) Extend communication protocol to establish client-server connection
[ https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda reopened IGNITE-12438: - Assignee: (was: Ivan Bessonov) Documentation of the feature is needed. Moving back to the open state. [~abudnikov], could you please facilitate with this? > Extend communication protocol to establish client-server connection > --- > > Key: IGNITE-12438 > URL: https://issues.apache.org/jira/browse/IGNITE-12438 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Alexey Goncharuk >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Recently there was quite a lot of questions related to thick clients > connectivity issues when the clients are deployed in a k8s pod [1]. The > general issue here is clients reporting network address which are not > reachable from server nodes. At the same time, the clients can connect to > server nodes. > An idea of how to fix this is as follows: > * Make sure that think clients discovery SPI always maintains a connection > to a server node (this should be already implemented) > * (Optionally) detect when a client has only one-way connectivity with the > server nodes. This part should be investigated. We need this to avoid server > nodes attempt to connect to a client and send communication request to the > client node faster > * When a server attempts to establish a connection with a client, check if > client is unreachable or the previous connection attempt failed. If so, send > a discovery message to the client to force a client-server connection. In > this case, server will be able to send the original message via the newly > established connection. > [1] > https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12438) Extend communication protocol to establish client-server connection
[ https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-12438: Component/s: documentation > Extend communication protocol to establish client-server connection > --- > > Key: IGNITE-12438 > URL: https://issues.apache.org/jira/browse/IGNITE-12438 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Alexey Goncharuk >Assignee: Ivan Bessonov >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Recently there was quite a lot of questions related to thick clients > connectivity issues when the clients are deployed in a k8s pod [1]. The > general issue here is clients reporting network address which are not > reachable from server nodes. At the same time, the clients can connect to > server nodes. > An idea of how to fix this is as follows: > * Make sure that think clients discovery SPI always maintains a connection > to a server node (this should be already implemented) > * (Optionally) detect when a client has only one-way connectivity with the > server nodes. This part should be investigated. We need this to avoid server > nodes attempt to connect to a client and send communication request to the > client node faster > * When a server attempts to establish a connection with a client, check if > client is unreachable or the previous connection attempt failed. If so, send > a discovery message to the client to force a client-server connection. In > this case, server will be able to send the original message via the newly > established connection. > [1] > https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization
[ https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-5038: - Assignee: Mirza Aliev > BinaryMarshaller might need to use context class loader for deserialization > --- > > Key: IGNITE-5038 > URL: https://issues.apache.org/jira/browse/IGNITE-5038 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 2.0 >Reporter: Dmitry Karachentsev >Assignee: Mirza Aliev >Priority: Major > Labels: features > Attachments: results-compound-20170802.zip, > results-compound-20170808.zip > > Time Spent: 50m > Remaining Estimate: 0h > > There is a special use case discussed on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224 > According to the use case, BinaryMarshaller might need to try to deserialize > an object using a context class loader if it failed to do so with a custom > classloader (`IgniteConfiguration.getClassLoader()`) or the system one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization
[ https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172560#comment-17172560 ] Vladislav Pyatkov commented on IGNITE-5038: --- [~maliev] I left several comments in PR. > BinaryMarshaller might need to use context class loader for deserialization > --- > > Key: IGNITE-5038 > URL: https://issues.apache.org/jira/browse/IGNITE-5038 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 2.0 >Reporter: Dmitry Karachentsev >Assignee: Mirza Aliev >Priority: Major > Labels: features > Attachments: results-compound-20170802.zip, > results-compound-20170808.zip > > Time Spent: 50m > Remaining Estimate: 0h > > There is a special use case discussed on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224 > According to the use case, BinaryMarshaller might need to try to deserialize > an object using a context class loader if it failed to do so with a custom > classloader (`IgniteConfiguration.getClassLoader()`) or the system one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization
[ https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-5038: - Assignee: (was: Vladislav Pyatkov) > BinaryMarshaller might need to use context class loader for deserialization > --- > > Key: IGNITE-5038 > URL: https://issues.apache.org/jira/browse/IGNITE-5038 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 2.0 >Reporter: Dmitry Karachentsev >Priority: Major > Labels: features > Attachments: results-compound-20170802.zip, > results-compound-20170808.zip > > Time Spent: 50m > Remaining Estimate: 0h > > There is a special use case discussed on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224 > According to the use case, BinaryMarshaller might need to try to deserialize > an object using a context class loader if it failed to do so with a custom > classloader (`IgniteConfiguration.getClassLoader()`) or the system one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-5038) BinaryMarshaller might need to use context class loader for deserialization
[ https://issues.apache.org/jira/browse/IGNITE-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladislav Pyatkov reassigned IGNITE-5038: - Assignee: Vladislav Pyatkov > BinaryMarshaller might need to use context class loader for deserialization > --- > > Key: IGNITE-5038 > URL: https://issues.apache.org/jira/browse/IGNITE-5038 > Project: Ignite > Issue Type: Improvement > Components: binary >Affects Versions: 2.0 >Reporter: Dmitry Karachentsev >Assignee: Vladislav Pyatkov >Priority: Major > Labels: features > Attachments: results-compound-20170802.zip, > results-compound-20170808.zip > > Time Spent: 50m > Remaining Estimate: 0h > > There is a special use case discussed on the dev list: > http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-td17126.html#a17224 > According to the use case, BinaryMarshaller might need to try to deserialize > an object using a context class loader if it failed to do so with a custom > classloader (`IgniteConfiguration.getClassLoader()`) or the system one. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13338) Ability to Query for the Names of All Distributed Data Structures
Brandon Szeliga created IGNITE-13338: Summary: Ability to Query for the Names of All Distributed Data Structures Key: IGNITE-13338 URL: https://issues.apache.org/jira/browse/IGNITE-13338 Project: Ignite Issue Type: New Feature Reporter: Brandon Szeliga Currently it is possible to use Ignite::cacheNames api to request a collection of all the different cache names available in the system. However, there is no equivalent method for all the other distribute data structures available (sets/queues/locks/sequences/stamps/references/latches/etc). It would be highly beneficial to provide an API that allows access to all distributed data structures names and types in order to provide a dynamic way of looking into whats being created/used inside Ignite. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13204) Java Thin client Kubernetes discovery
[ https://issues.apache.org/jira/browse/IGNITE-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172468#comment-17172468 ] Maksim Timonin commented on IGNITE-13204: - Hi [~Vladimir Pligin] ! I started implement this feature as we have a relative case. Currently I found that there could be possibility to avoid directly access k8s api and rely on k8s service address. To check that I'll prepare demo for 2 cases (statefull / stateless) on next week. After that I'll send a proposal to devlist. > Java Thin client Kubernetes discovery > - > > Key: IGNITE-13204 > URL: https://issues.apache.org/jira/browse/IGNITE-13204 > Project: Ignite > Issue Type: New Feature > Components: platforms >Reporter: Alexandr >Assignee: Maksim Timonin >Priority: Major > Labels: java > > Thin clients should be able to discover servers from within Kubernetes pod > through k8s API, without specifying any IP addresses. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13292) Remove unneeded ZkPinger from ZookeeperDiscovery
[
https://issues.apache.org/jira/browse/IGNITE-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172408#comment-17172408
]
Sergey Chugunov commented on IGNITE-13292:
--
[~ivandasch], patch looks good to me, I merged it to master branch in commit
*ee7d1369e4008c346c06bad46cb4c2261dc976df*.
Thank you for contribution!
> Remove unneeded ZkPinger from ZookeeperDiscovery
>
>
> Key: IGNITE-13292
> URL: https://issues.apache.org/jira/browse/IGNITE-13292
> Project: Ignite
> Issue Type: Improvement
> Components: zookeeper
>Affects Versions: 2.9
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Trivial
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We need remove uneeded {{ZkPinger}} from our codebase, introduced in
> [IGNITE-9683|https://issues.apache.org/jira/browse/IGNITE-9683].
> This pinger was introduced to solve issues with server nodes segmentation
> when cluster is deactivated. The main reason of that is the strange all
> thread freeze when huge amount of memory is deallocated with
> {{Unsafe.freeMemory}}, such freeze can last for a minute and more. So this
> pinger doesn't solve problem at all and this is proved. The working solution
> to this problem is introduced in
> [IGNITE-9658|https://issues.apache.org/jira/browse/IGNITE-9658]
> So we should remove this code from our codebase.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13320) TDE - Phase-3. CLI management
[ https://issues.apache.org/jira/browse/IGNITE-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13320: -- Labels: IEP-18 tde-phase-3 (was: iep-19 tde-phase-3) > TDE - Phase-3. CLI management > - > > Key: IGNITE-13320 > URL: https://issues.apache.org/jira/browse/IGNITE-13320 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: IEP-18, tde-phase-3 > > Provide the ability to manage the process of key rotation (and cache > re-encryption) through the command line. > - Launch key rotation (distributed) > Local > - Launch re-encryption > - Stop re-encryption > - View keys (id, hash) for cache group -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13320) TDE - Phase-3. CLI management
[ https://issues.apache.org/jira/browse/IGNITE-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13320: -- Labels: iep-19 tde-phase-3 (was: tde-phase-3) > TDE - Phase-3. CLI management > - > > Key: IGNITE-13320 > URL: https://issues.apache.org/jira/browse/IGNITE-13320 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-19, tde-phase-3 > > Provide the ability to manage the process of key rotation (and cache > re-encryption) through the command line. > - Launch key rotation (distributed) > Local > - Launch re-encryption > - Stop re-encryption > - View keys (id, hash) for cache group -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13320) TDE - Phase-3. CLI management
[ https://issues.apache.org/jira/browse/IGNITE-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13320: -- Labels: tde-phase-3 (was: ) > TDE - Phase-3. CLI management > - > > Key: IGNITE-13320 > URL: https://issues.apache.org/jira/browse/IGNITE-13320 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: tde-phase-3 > > Provide the ability to manage the process of key rotation (and cache > re-encryption) through the command line. > - Launch key rotation (distributed) > Local > - Launch re-encryption > - Stop re-encryption > - View keys (id, hash) for cache group -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12843) TDE - Phase-3. Cache key rotation.
[ https://issues.apache.org/jira/browse/IGNITE-12843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-12843: -- Labels: IEP-18 tde-phase-3 (was: IEP-18 tde-phase-3 еву) > TDE - Phase-3. Cache key rotation. > -- > > Key: IGNITE-12843 > URL: https://issues.apache.org/jira/browse/IGNITE-12843 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: IEP-18, tde-phase-3 > Fix For: 2.10 > > Time Spent: 1h > Remaining Estimate: 0h > > Add the ability to rotate (change) the cache group encryption key. > The design is described here: > [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384#TDE.Phase3.Cachekeyrotation.-Description] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12843) TDE - Phase-3. Cache key rotation.
[ https://issues.apache.org/jira/browse/IGNITE-12843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-12843: -- Labels: IEP-18 tde-phase-3 еву (was: IEP-18) > TDE - Phase-3. Cache key rotation. > -- > > Key: IGNITE-12843 > URL: https://issues.apache.org/jira/browse/IGNITE-12843 > Project: Ignite > Issue Type: Sub-task >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: IEP-18, tde-phase-3, еву > Fix For: 2.10 > > Time Spent: 1h > Remaining Estimate: 0h > > Add the ability to rotate (change) the cache group encryption key. > The design is described here: > [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384#TDE.Phase3.Cachekeyrotation.-Description] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13133) Add integration with QuerydslPredicateExecutor for spring-data integrations
[
https://issues.apache.org/jira/browse/IGNITE-13133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172365#comment-17172365
]
Ilya Kasnacheev commented on IGNITE-13133:
--
The patch will not apply due to conflicts. Can you please rebase it to master?
[~smoldachev]
> Add integration with QuerydslPredicateExecutor for spring-data integrations
> ---
>
> Key: IGNITE-13133
> URL: https://issues.apache.org/jira/browse/IGNITE-13133
> Project: Ignite
> Issue Type: New Feature
> Components: springdata
>Reporter: Moldachev Sergey
>Assignee: Moldachev Sergey
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We have a pretty ignite-spring-data integration but we don't have a support
> of *QuerydslPredicateExecutor* which provide ability to filter cache entities
> by dynamic criterias.
> Example of usage:
> {code:java}
> /**
> * Simple entity.
> */
> @QueryEntity
> public class Person {
> /** First name. */
> @QuerySqlField(index = true)
> private String firstName;
> /** Second name. */
> @QuerySqlField(index = true)
> private String secondName;
> /** Age. **/
> @QuerySqlField(index = true)
> private int age;
> }
> /**
> * Implement QuerydslPredicateExecutor interface.
> */
> public interface PersonRepository extends IgniteRepository,
> QuerydslPredicateExecutor {
> }
> /**
> * Now we can filter our entites by firstName prdicate.
> */
> List persons = (List) repo.findAll(
> QPerson.person.firstName.eq(firstName_1)
> .or(QPerson.person.firstName.eq(firstName_2))
> );
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13313) IndexOutOfBoundsException from GridDhtAtomicUpdateRequest on server node startup
[ https://issues.apache.org/jira/browse/IGNITE-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172353#comment-17172353 ] Grigory Domozhirov edited comment on IGNITE-13313 at 8/6/20, 1:30 PM: -- [~ivan.glukos] load pattern: Launching 1 server + 1 client node sequentially on each of 6 hosts. So, 2 nodes on each virtial machine, 12 nodes total: 6 server + 6 clients. Server nodes performs nothing. Each client node creates and massively populates number of caches. Mostly with putAllAsync (wating for previous call future to complete), but also with some invokeAllAsync and sometimes performs clear. Size of batch - up to 100k records. First of laucnhed clients creates and populates about 200 caches, others - from 1 to 10. This results, in particular, that server nodes could be added to topology while caches is activlely creating and loading. was (Author: gdomo): [~ivan.glukos] load pattern: Launching 1 server + 1 client node sequentially on each of 6 hosts. So, 2 nodes on each virtial machine, 12 nodes total: 6 server + 6 clients. Server nodes performs nothing. Each client node creates and massively populates number of caches. Mostly with putAllAsync (wating for previous call future to complete), but also with some invokeAllAsync and sometimes performs clear. Size of batch - up to 100k records. First of laucnhed clients creates and populates about 200 caches, others - from 1 to 10. > IndexOutOfBoundsException from GridDhtAtomicUpdateRequest on server node > startup > > > Key: IGNITE-13313 > URL: https://issues.apache.org/jira/browse/IGNITE-13313 > Project: Ignite > Issue Type: Bug >Reporter: Grigory Domozhirov >Priority: Major > > Sometimes server node fails on startup with following exception. > GGCE 8.7.21, no persistance, atomic caches > > 2020-07-30 13:39:02,962 [sys-stripe-0-#1|#1] ERROR > o.a.i.i.p.c.GridCacheIoManager - Failed processing message > [senderId=98dc3c18-ea57-4805-9603-b92eb7e62be2, msg=GridD > htAtomicUpdateRequest [keys=ArrayList > [com.moex.esb.blackhole.model.fx.trade.Securities$Key [idHash=4701836, > hash=890931906, secboard=AETS, seccode=GLDRUB_TOD], > *__* > ... and 111883 skipped ...=0,_**_ > prevVals=ArrayList [null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, > null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, n > ull, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, nul > l, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null... and 19 more], > ttls=null, conflict > ExpireTimes=null, nearTtls=null, nearExpireTimes=null, nearKeys=null, > nearVals=null, obsoleteIndexes=null, forceTransformBackups=false, > updateCntrs=GridLongList [id > x=174, > arr=[1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1, > > 1,2,1,1,1,1,1,1,3,1,1,1,1,1,1,1,1,1,2,2,1,1,1,1,2,1,1,3,1,1,1,1,1,2,1,2,1,1,1,1,2,1,1,1,2,1,2,1,2,1,1,1,2,1,2,2,1,4,1,3,3,1,2,2,2,2,1,3,1,1,1,1,1,2,3,4,1,1,2,1,1,1, > 1,4,1,1,1,2,1,2,1,1,1,1,3,1,1,1]], super=GridDhtAtomicAbstractUpdateRequest > [onRes=false, nearNodeId=ae4abad0-d501-4703-98bf-b5eabd10f159, > nearFutId=147459, flags=k > eepBinary|hasRes]]] > java.lang.IndexOutOfBoundsException: Index 119 out of bounds for length 119 > at > java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) > ~[na:na] > at > java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) > ~[na:na] > at > java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) > ~[na:na] > at java.base/java.util.Objects.checkIndex(Objects.java:373) ~[na:na] > at java.base/java.util.ArrayList.get(ArrayList.java:425) ~[na:na] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest.previousValue(GridDhtAtomicUpdateRequest.java:391) > ~[ignite > -core-8.7.21.jar:8.7.21] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3363) > ~[ignit > e-core-8.7.21.jar:8.7.21] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:141) >
[jira] [Comment Edited] (IGNITE-13313) IndexOutOfBoundsException from GridDhtAtomicUpdateRequest on server node startup
[ https://issues.apache.org/jira/browse/IGNITE-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172353#comment-17172353 ] Grigory Domozhirov edited comment on IGNITE-13313 at 8/6/20, 1:26 PM: -- [~ivan.glukos] load pattern: Launching 1 server + 1 client node sequentially on each of 6 hosts. So, 2 nodes on each virtial machine, 12 nodes total: 6 server + 6 clients. Server nodes performs nothing. Each client node creates and massively populates number of caches. Mostly with putAllAsync (wating for previous call future to complete), but also with some invokeAllAsync and sometimes performs clear. Size of batch - up to 100k records. First of laucnhed clients creates and populates about 200 caches, others - from 1 to 10. was (Author: gdomo): load pattern: Launching 1 server + 1 client node sequentially on each of 6 hosts. So, 2 nodes on each virtial machine, 12 nodes total: 6 server + 6 clients. Server nodes performs nothing. Each client node creates and massively populates number of caches. Mostly with putAllAsync (wating for previous call future to complete), but also with some invokeAllAsync and sometimes performs clear. Size of batch - up to 100k records. First of laucnhed clients creates and populates about 200 caches, others - from 1 to 10. > IndexOutOfBoundsException from GridDhtAtomicUpdateRequest on server node > startup > > > Key: IGNITE-13313 > URL: https://issues.apache.org/jira/browse/IGNITE-13313 > Project: Ignite > Issue Type: Bug >Reporter: Grigory Domozhirov >Priority: Major > > Sometimes server node fails on startup with following exception. > GGCE 8.7.21, no persistance, atomic caches > > 2020-07-30 13:39:02,962 [sys-stripe-0-#1|#1] ERROR > o.a.i.i.p.c.GridCacheIoManager - Failed processing message > [senderId=98dc3c18-ea57-4805-9603-b92eb7e62be2, msg=GridD > htAtomicUpdateRequest [keys=ArrayList > [com.moex.esb.blackhole.model.fx.trade.Securities$Key [idHash=4701836, > hash=890931906, secboard=AETS, seccode=GLDRUB_TOD], > *__* > ... and 111883 skipped ...=0,_**_ > prevVals=ArrayList [null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, > null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, n > ull, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, nul > l, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null... and 19 more], > ttls=null, conflict > ExpireTimes=null, nearTtls=null, nearExpireTimes=null, nearKeys=null, > nearVals=null, obsoleteIndexes=null, forceTransformBackups=false, > updateCntrs=GridLongList [id > x=174, > arr=[1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1, > > 1,2,1,1,1,1,1,1,3,1,1,1,1,1,1,1,1,1,2,2,1,1,1,1,2,1,1,3,1,1,1,1,1,2,1,2,1,1,1,1,2,1,1,1,2,1,2,1,2,1,1,1,2,1,2,2,1,4,1,3,3,1,2,2,2,2,1,3,1,1,1,1,1,2,3,4,1,1,2,1,1,1, > 1,4,1,1,1,2,1,2,1,1,1,1,3,1,1,1]], super=GridDhtAtomicAbstractUpdateRequest > [onRes=false, nearNodeId=ae4abad0-d501-4703-98bf-b5eabd10f159, > nearFutId=147459, flags=k > eepBinary|hasRes]]] > java.lang.IndexOutOfBoundsException: Index 119 out of bounds for length 119 > at > java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) > ~[na:na] > at > java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) > ~[na:na] > at > java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) > ~[na:na] > at java.base/java.util.Objects.checkIndex(Objects.java:373) ~[na:na] > at java.base/java.util.ArrayList.get(ArrayList.java:425) ~[na:na] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest.previousValue(GridDhtAtomicUpdateRequest.java:391) > ~[ignite > -core-8.7.21.jar:8.7.21] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3363) > ~[ignit > e-core-8.7.21.jar:8.7.21] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:141) > ~[ignite-core-8.7.21.jar:8. > 7.21] > at >
[jira] [Commented] (IGNITE-13313) IndexOutOfBoundsException from GridDhtAtomicUpdateRequest on server node startup
[ https://issues.apache.org/jira/browse/IGNITE-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172353#comment-17172353 ] Grigory Domozhirov commented on IGNITE-13313: - load pattern: Launching 1 server + 1 client node sequentially on each of 6 hosts. So, 2 nodes on each virtial machine, 12 nodes total: 6 server + 6 clients. Server nodes performs nothing. Each client node creates and massively populates number of caches. Mostly with putAllAsync (wating for previous call future to complete), but also with some invokeAllAsync and sometimes performs clear. Size of batch - up to 100k records. First of laucnhed clients creates and populates about 200 caches, others - from 1 to 10. > IndexOutOfBoundsException from GridDhtAtomicUpdateRequest on server node > startup > > > Key: IGNITE-13313 > URL: https://issues.apache.org/jira/browse/IGNITE-13313 > Project: Ignite > Issue Type: Bug >Reporter: Grigory Domozhirov >Priority: Major > > Sometimes server node fails on startup with following exception. > GGCE 8.7.21, no persistance, atomic caches > > 2020-07-30 13:39:02,962 [sys-stripe-0-#1|#1] ERROR > o.a.i.i.p.c.GridCacheIoManager - Failed processing message > [senderId=98dc3c18-ea57-4805-9603-b92eb7e62be2, msg=GridD > htAtomicUpdateRequest [keys=ArrayList > [com.moex.esb.blackhole.model.fx.trade.Securities$Key [idHash=4701836, > hash=890931906, secboard=AETS, seccode=GLDRUB_TOD], > *__* > ... and 111883 skipped ...=0,_**_ > prevVals=ArrayList [null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, > null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, n > ull, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null, null, null, null, null, > null, nul > l, null, null, null, null, null, null, null, null, null, null, null, null, > null, null, null, null, null, null, null, null, null... and 19 more], > ttls=null, conflict > ExpireTimes=null, nearTtls=null, nearExpireTimes=null, nearKeys=null, > nearVals=null, obsoleteIndexes=null, forceTransformBackups=false, > updateCntrs=GridLongList [id > x=174, > arr=[1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,1,2,1,1,1,1,1,1,1,2,1,1, > > 1,2,1,1,1,1,1,1,3,1,1,1,1,1,1,1,1,1,2,2,1,1,1,1,2,1,1,3,1,1,1,1,1,2,1,2,1,1,1,1,2,1,1,1,2,1,2,1,2,1,1,1,2,1,2,2,1,4,1,3,3,1,2,2,2,2,1,3,1,1,1,1,1,2,3,4,1,1,2,1,1,1, > 1,4,1,1,1,2,1,2,1,1,1,1,3,1,1,1]], super=GridDhtAtomicAbstractUpdateRequest > [onRes=false, nearNodeId=ae4abad0-d501-4703-98bf-b5eabd10f159, > nearFutId=147459, flags=k > eepBinary|hasRes]]] > java.lang.IndexOutOfBoundsException: Index 119 out of bounds for length 119 > at > java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) > ~[na:na] > at > java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) > ~[na:na] > at > java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) > ~[na:na] > at java.base/java.util.Objects.checkIndex(Objects.java:373) ~[na:na] > at java.base/java.util.ArrayList.get(ArrayList.java:425) ~[na:na] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicUpdateRequest.previousValue(GridDhtAtomicUpdateRequest.java:391) > ~[ignite > -core-8.7.21.jar:8.7.21] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3363) > ~[ignit > e-core-8.7.21.jar:8.7.21] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$600(GridDhtAtomicCache.java:141) > ~[ignite-core-8.7.21.jar:8. > 7.21] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:311) > ~[ignite-core-8.7.21.jar:8.7.2 > 1] > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$7.apply(GridDhtAtomicCache.java:306) > ~[ignite-core-8.7.21.jar:8.7.2 > 1] > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142) > ~[ignite-core-8.7.21.jar:8.7.21] > at > org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591) > ~[ignite-core-8.7.21.jar:8.7.21] > at >
[jira] [Commented] (IGNITE-13191) Public-facing API for "waiting for backups on shutdown"
[
https://issues.apache.org/jira/browse/IGNITE-13191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172306#comment-17172306
]
Maxim Muzafarov commented on IGNITE-13191:
--
[~ivan.glukos], [~v.pyatkov]
Folks, does anyone investigated the execution timeout error on the `MVCC Cache
7`? It hangs on the newly added test {{GracefulShutdownTest}} in most of the
50% runs.
[https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E=builds]
> Public-facing API for "waiting for backups on shutdown"
> ---
>
> Key: IGNITE-13191
> URL: https://issues.apache.org/jira/browse/IGNITE-13191
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> We should introduce "should wait for backups on shutdown" flag in Ignition
> and/or IgniteConfiguration.
> Maybe we should do the same to "cancel compute tasks" flag.
> Also make sure that we can shut down node explicitly, overriding this flag
> but without JVM termination.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13337) Performance drop in ignite-2.9 vs Ignite 2.8.1
[
https://issues.apache.org/jira/browse/IGNITE-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172303#comment-17172303
]
Ivan Artukhov commented on IGNITE-13337:
Attached Spring XML configs for server and client nodes.
> Performance drop in ignite-2.9 vs Ignite 2.8.1
> --
>
> Key: IGNITE-13337
> URL: https://issues.apache.org/jira/browse/IGNITE-13337
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Affects Versions: 2.9
> Environment: 9 equal physical hosts (2x Xeon E5-2609 v4, 96Gb RAM,
> 3x800Gb SSD RAID0, 10Gb/s ethernet)
> 3 server nodes, one node per physical host
> 6 client nodes, one node per physical host, 64 load threads
>Reporter: Ivan Artukhov
>Priority: Critical
> Attachments: caches.xml, driver.xml, in-mem-FULL_SYNC.png,
> in-mem-PRIMARY_SYNC.png, pds-LOG_ONLY-FULL_SYNC.png,
> pds-LOG_ONLY-PRIMARY_SYNC.png, server.xml
>
>
> Yardstick benchmarks show up to 7% performance drop in branch {{ignite-2.9}}
> (rev. 6592dfa5) vs Ignite 2.8.1. Please see the attached screenshots.
> The benchmarks in use:
> {noformat}
> IgnitePutBenchmark
> IgniteGetBenchmark
> IgnitePutTxImplicitBenchmark
> IgnitePutGetTxBenchmark -optimistic
> IgnitePutGetTxBenchmark -pessimistic
> IgnitePutGetTxBenchmark -optimistic -serializable
> IgniteSqlQueryBenchmark
> IgnitePutAllTxBenchmark
> IgnitePutAllBenchmark
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13337) Performance drop in ignite-2.9 vs Ignite 2.8.1
[
https://issues.apache.org/jira/browse/IGNITE-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Artukhov updated IGNITE-13337:
---
Attachment: caches.xml
driver.xml
server.xml
> Performance drop in ignite-2.9 vs Ignite 2.8.1
> --
>
> Key: IGNITE-13337
> URL: https://issues.apache.org/jira/browse/IGNITE-13337
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Affects Versions: 2.9
> Environment: 9 equal physical hosts (2x Xeon E5-2609 v4, 96Gb RAM,
> 3x800Gb SSD RAID0, 10Gb/s ethernet)
> 3 server nodes, one node per physical host
> 6 client nodes, one node per physical host, 64 load threads
>Reporter: Ivan Artukhov
>Priority: Critical
> Attachments: caches.xml, driver.xml, in-mem-FULL_SYNC.png,
> in-mem-PRIMARY_SYNC.png, pds-LOG_ONLY-FULL_SYNC.png,
> pds-LOG_ONLY-PRIMARY_SYNC.png, server.xml
>
>
> Yardstick benchmarks show up to 7% performance drop in branch {{ignite-2.9}}
> (rev. 6592dfa5) vs Ignite 2.8.1. Please see the attached screenshots.
> The benchmarks in use:
> {noformat}
> IgnitePutBenchmark
> IgniteGetBenchmark
> IgnitePutTxImplicitBenchmark
> IgnitePutGetTxBenchmark -optimistic
> IgnitePutGetTxBenchmark -pessimistic
> IgnitePutGetTxBenchmark -optimistic -serializable
> IgniteSqlQueryBenchmark
> IgnitePutAllTxBenchmark
> IgnitePutAllBenchmark
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13309) Extend c++ build documentation.
[ https://issues.apache.org/jira/browse/IGNITE-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-13309: - Fix Version/s: 2.10 > Extend c++ build documentation. > --- > > Key: IGNITE-13309 > URL: https://issues.apache.org/jira/browse/IGNITE-13309 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Minor > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > Need to append additional boost dependencies: > *boost-regex* > And additional steps for QTCreator running. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13337) Performance drop in ignite-2.9 vs Ignite 2.8.1
Ivan Artukhov created IGNITE-13337:
--
Summary: Performance drop in ignite-2.9 vs Ignite 2.8.1
Key: IGNITE-13337
URL: https://issues.apache.org/jira/browse/IGNITE-13337
Project: Ignite
Issue Type: Bug
Components: cache, sql
Affects Versions: 2.9
Environment: 9 equal physical hosts (2x Xeon E5-2609 v4, 96Gb RAM,
3x800Gb SSD RAID0, 10Gb/s ethernet)
3 server nodes, one node per physical host
6 client nodes, one node per physical host, 64 load threads
Reporter: Ivan Artukhov
Attachments: in-mem-FULL_SYNC.png, in-mem-PRIMARY_SYNC.png,
pds-LOG_ONLY-FULL_SYNC.png, pds-LOG_ONLY-PRIMARY_SYNC.png
Yardstick benchmarks show up to 7% performance drop in branch {{ignite-2.9}}
(rev. 6592dfa5) vs Ignite 2.8.1. Please see the attached screenshots.
The benchmarks in use:
{noformat}
IgnitePutBenchmark
IgniteGetBenchmark
IgnitePutTxImplicitBenchmark
IgnitePutGetTxBenchmark -optimistic
IgnitePutGetTxBenchmark -pessimistic
IgnitePutGetTxBenchmark -optimistic -serializable
IgniteSqlQueryBenchmark
IgnitePutAllTxBenchmark
IgnitePutAllBenchmark
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13336) .NET: Misleading LINQ exception when expression can't be translated
Pavel Tupitsyn created IGNITE-13336:
---
Summary: .NET: Misleading LINQ exception when expression can't be
translated
Key: IGNITE-13336
URL: https://issues.apache.org/jira/browse/IGNITE-13336
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.8.1
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.10
The following program results in a cryptic exception, when the problem is
simply lack of Expression<> wrapper around the query filter:
{code}
class Program
{
private static readonly IIgnite Ignite = Ignition.Start();
static void Main(string[] args)
{
var cache = GetCache();
cache["1"] = new Foo();
var res = Where2(e => e.Value.X == 0);
Console.WriteLine(res);
}
public static ICache GetCache()
{
var cacheName = typeof(T).Name;
var cfg = new CacheConfiguration(cacheName, new
QueryEntity(typeof(T)));
return Ignite.GetOrCreateCache(cfg);
}
public static List Where2(Expression,
bool>> query)
{
var queryResult = GetCache().AsCacheQueryable().Where(query);
return queryResult.Select(x => x.Value).ToList();
}
}
public class Foo
{
[QuerySqlField] public int X { get; set; }
}
{code}
We should throw a better exception that says "LINQ expression can't be
translated to SQL because of ..."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13204) Java Thin client Kubernetes discovery
[ https://issues.apache.org/jira/browse/IGNITE-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172265#comment-17172265 ] Vladimir Pligin commented on IGNITE-13204: -- Hi [~timonin.maksim], thanks for the initiative to implement this useful feature. It'll be very valuable when it arrives. How is it going? Do we have any ETA about the matter? > Java Thin client Kubernetes discovery > - > > Key: IGNITE-13204 > URL: https://issues.apache.org/jira/browse/IGNITE-13204 > Project: Ignite > Issue Type: New Feature > Components: platforms >Reporter: Alexandr >Assignee: Maksim Timonin >Priority: Major > Labels: java > > Thin clients should be able to discover servers from within Kubernetes pod > through k8s API, without specifying any IP addresses. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13013) Thick client must not open server sockets when used by serverless functions
[ https://issues.apache.org/jira/browse/IGNITE-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172149#comment-17172149 ] Anton Kalashnikov commented on IGNITE-13013: [~ibessonov] LGTM. [~agoncharuk] can you help with the merge, please? > Thick client must not open server sockets when used by serverless functions > --- > > Key: IGNITE-13013 > URL: https://issues.apache.org/jira/browse/IGNITE-13013 > Project: Ignite > Issue Type: Improvement > Components: networking >Affects Versions: 2.8 >Reporter: Denis A. Magda >Assignee: Ivan Bessonov >Priority: Critical > Fix For: 2.10 > > Attachments: image-2020-07-30-18-42-01-266.png > > Time Spent: 10m > Remaining Estimate: 0h > > A thick client fails to start if being used inside of a serverless function > such as AWS Lamda or Azure Functions. Cloud providers prohibit opening > network ports to accept connections on the function's end. In short, the > function can only connect to a remote address. > To reproduce, you can follow this tutorial and swap the thin client (used in > the tutorial) with the thick one: > https://www.gridgain.com/docs/tutorials/serverless/azure_functions_tutorial > The thick client needs to support a mode when the communication SPI doesn't > create a server socket if the client is used for serverless computing. This > improvement looks like an extra task of this initiative: > https://issues.apache.org/jira/browse/IGNITE-12438 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13335) Document changes to thin client binary protocol
Aleksey Plekhanov created IGNITE-13335: -- Summary: Document changes to thin client binary protocol Key: IGNITE-13335 URL: https://issues.apache.org/jira/browse/IGNITE-13335 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Plekhanov Currently, only the initial version of binary protocol is documented. There were a lot of changes and a lot of features implemented after initial implementation. These protocol changes should be documented to help to implement features by existing clients and to simplify new clients implementations. Some of protocol changes already described on corresponding IEP pages: * https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients * https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support * https://cwiki.apache.org/confluence/display/IGNITE/IEP-42+Thin+client%3A+compute+support * https://cwiki.apache.org/confluence/display/IGNITE/IEP-46%3A+Thin+Client+Service+Invocation * https://cwiki.apache.org/confluence/display/IGNITE/IEP-50%3A+Thin+Client+Continuous+Queries * https://cwiki.apache.org/confluence/display/IGNITE/IEP-44%3A+Thin+client+cluster+discovery Some features were implemented without an IEP: * Expiration policies * Cluster API * Cluster group API * User attributes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13102) IgniteCache#isClosed() returns false on server node even if the cache had been closed before.
[
https://issues.apache.org/jira/browse/IGNITE-13102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172129#comment-17172129
]
Ignite TC Bot commented on IGNITE-13102:
{panel:title=Branch: [pull/8087/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8087/head] Base: [master] : New Tests
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5520570]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=eab4d9fb371-b6148e56-2a2f-4c91-a31f-64baef8ff549, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=912e5360-197b-4768-b951-112d2e7fe17e, topVer=0, msgTemplate=null,
span=null, nodeId8=912e5360, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596647623594]], val2=AffinityTopologyVersion
[topVer=4816031799281483861, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=eab4d9fb371-b6148e56-2a2f-4c91-a31f-64baef8ff549, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=912e5360-197b-4768-b951-112d2e7fe17e, topVer=0, msgTemplate=null,
span=null, nodeId8=912e5360, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596647623594]], val2=AffinityTopologyVersion
[topVer=4816031799281483861, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=c117e05f-3f87-4a3c-9ebd-e2e971c02ac6, topVer=0,
msgTemplate=null, span=null, nodeId8=4c6fbd90, msg=, type=NODE_JOINED,
tstamp=1596647623594], val2=AffinityTopologyVersion
[topVer=1606378985067874872, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=c117e05f-3f87-4a3c-9ebd-e2e971c02ac6, topVer=0,
msgTemplate=null, span=null, nodeId8=4c6fbd90, msg=, type=NODE_JOINED,
tstamp=1596647623594], val2=AffinityTopologyVersion
[topVer=1606378985067874872, minorTopVer=0]]] - PASSED{color}
{color:#8b}Service Grid (legacy mode){color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5520571]]
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=c4c3a935-8d07-46e0-9dec-a7ba142847d8, topVer=0,
msgTemplate=null, span=null, nodeId8=e150186c, msg=, type=NODE_JOINED,
tstamp=1596647739690], val2=AffinityTopologyVersion
[topVer=7926716467868785299, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryEvent [evtNode=c4c3a935-8d07-46e0-9dec-a7ba142847d8, topVer=0,
msgTemplate=null, span=null, nodeId8=e150186c, msg=, type=NODE_JOINED,
tstamp=1596647739690], val2=AffinityTopologyVersion
[topVer=7926716467868785299, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=03209afb371-0fc70b96-9cc1-4214-a7ea-f78fe0ba86eb, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=b948cfa8-aab0-44c2-8ae7-a9a30f167ea6, topVer=0, msgTemplate=null,
span=null, nodeId8=b948cfa8, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596647739690]], val2=AffinityTopologyVersion
[topVer=-609859720708393679, minorTopVer=0]]] - PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite:
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest
[id=03209afb371-0fc70b96-9cc1-4214-a7ea-f78fe0ba86eb, reqs=SingletonList
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent
[evtNode=b948cfa8-aab0-44c2-8ae7-a9a30f167ea6, topVer=0, msgTemplate=null,
span=null, nodeId8=b948cfa8, msg=null, type=DISCOVERY_CUSTOM_EVT,
tstamp=1596647739690]], val2=AffinityTopologyVersion
[topVer=-609859720708393679, minorTopVer=0]]] - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5520593buildTypeId=IgniteTests24Java8_RunAll]
> IgniteCache#isClosed() returns false on server node even if the cache had
> been closed before.
> -
>
>
[jira] [Updated] (IGNITE-12492) TDE - Phase-2. Documentation.
[ https://issues.apache.org/jira/browse/IGNITE-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12492: --- Component/s: documentation > TDE - Phase-2. Documentation. > - > > Key: IGNITE-12492 > URL: https://issues.apache.org/jira/browse/IGNITE-12492 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.9 > > > Add documentation for the master key change process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12492) TDE - Phase-2. Documentation.
[ https://issues.apache.org/jira/browse/IGNITE-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12492: --- Fix Version/s: 2.9 > TDE - Phase-2. Documentation. > - > > Key: IGNITE-12492 > URL: https://issues.apache.org/jira/browse/IGNITE-12492 > Project: Ignite > Issue Type: Sub-task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.9 > > > Add documentation for the master key change process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13333) Document TDE master key rotation
[ https://issues.apache.org/jira/browse/IGNITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-1: --- Labels: (was: important) > Document TDE master key rotation > > > Key: IGNITE-1 > URL: https://issues.apache.org/jira/browse/IGNITE-1 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Priority: Major > Fix For: 2.9 > > > Document TDE master key rotation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12492) TDE - Phase-2. Documentation.
[ https://issues.apache.org/jira/browse/IGNITE-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12492: --- Labels: important (was: ) > TDE - Phase-2. Documentation. > - > > Key: IGNITE-12492 > URL: https://issues.apache.org/jira/browse/IGNITE-12492 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: important > Fix For: 2.9 > > > Add documentation for the master key change process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-13333) Document TDE master key rotation
[ https://issues.apache.org/jira/browse/IGNITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov resolved IGNITE-1. Resolution: Duplicate > Document TDE master key rotation > > > Key: IGNITE-1 > URL: https://issues.apache.org/jira/browse/IGNITE-1 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Priority: Major > Labels: important > Fix For: 2.9 > > > Document TDE master key rotation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12492) TDE - Phase-2. Documentation.
[ https://issues.apache.org/jira/browse/IGNITE-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12492: --- Ignite Flags: (was: Docs Required,Release Notes Required) > TDE - Phase-2. Documentation. > - > > Key: IGNITE-12492 > URL: https://issues.apache.org/jira/browse/IGNITE-12492 > Project: Ignite > Issue Type: Sub-task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > > Add documentation for the master key change process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13309) Extend c++ build documentation.
[ https://issues.apache.org/jira/browse/IGNITE-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172102#comment-17172102 ] Stanilovsky Evgeny commented on IGNITE-13309: - [~isapego] can you merge it, or i need to find some one else ? > Extend c++ build documentation. > --- > > Key: IGNITE-13309 > URL: https://issues.apache.org/jira/browse/IGNITE-13309 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.8.1 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Need to append additional boost dependencies: > *boost-regex* > And additional steps for QTCreator running. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13334) Document initial tracing implementation
Aleksey Plekhanov created IGNITE-13334: -- Summary: Document initial tracing implementation Key: IGNITE-13334 URL: https://issues.apache.org/jira/browse/IGNITE-13334 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Plekhanov Fix For: 2.9 Document initial tracing implementation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13330) Document java thin client features implemented in 2.8 and 2.9 release
[ https://issues.apache.org/jira/browse/IGNITE-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13330: --- Summary: Document java thin client features implemented in 2.8 and 2.9 release (was: Document java thin client 2.8 and 2.9 release features) > Document java thin client features implemented in 2.8 and 2.9 release > - > > Key: IGNITE-13330 > URL: https://issues.apache.org/jira/browse/IGNITE-13330 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Priority: Major > Labels: important > Fix For: 2.9 > > > Document implemented in 2.8 and 2.9 release features for java thin client: > * Partition awareness > * Expiration policy > * Cluster API > * Cluster group API > * Compute > * Services -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13333) Document TDE master key rotation
Aleksey Plekhanov created IGNITE-1: -- Summary: Document TDE master key rotation Key: IGNITE-1 URL: https://issues.apache.org/jira/browse/IGNITE-1 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Plekhanov Fix For: 2.9 Document TDE master key rotation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13332) Document .NET Native Near Cache
Aleksey Plekhanov created IGNITE-13332: -- Summary: Document .NET Native Near Cache Key: IGNITE-13332 URL: https://issues.apache.org/jira/browse/IGNITE-13332 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Plekhanov Fix For: 2.9 Document .NET Native Near Cache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12883) .NET: Rename PlatformNearCache to PlatformCache, mark as Experimental
[ https://issues.apache.org/jira/browse/IGNITE-12883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12883: --- Flags: (was: Important) > .NET: Rename PlatformNearCache to PlatformCache, mark as Experimental > - > > Key: IGNITE-12883 > URL: https://issues.apache.org/jira/browse/IGNITE-12883 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.9 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > PlatformNearCache is not actually "Near" - it just mirrors cache entries that > are present on current node in CLR heap for faster access. Those entries can > be primary, backup, or near. > PlatformCache seems to be a better name. > Rename: > * `PlatformNearCacheConfiguration` -> `PlatformCacheConfiguration` > * `CachePeekMode.PlatformNear` -> `CachePeekMode.Platform` > * `CacheConfiguration.PlatformNearConfiguration` -> > `CacheConfiguration.PlatformCacheConfiguration` > Mark all new platform (near) cache APIs with `[IgniteExperimental]` -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13330) Document java thin client 2.8 and 2.9 release features
[ https://issues.apache.org/jira/browse/IGNITE-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13330: --- Description: Document implemented in 2.8 and 2.9 release features for java thin client: * Partition awareness * Expiration policy * Cluster API * Cluster group API * Compute * Services was: Document implemented in 2.8 and 2.9 release features for java thin client: * Partition awareness * Cluster API * Cluster group API * Compute * Services > Document java thin client 2.8 and 2.9 release features > -- > > Key: IGNITE-13330 > URL: https://issues.apache.org/jira/browse/IGNITE-13330 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Aleksey Plekhanov >Priority: Major > Labels: important > Fix For: 2.9 > > > Document implemented in 2.8 and 2.9 release features for java thin client: > * Partition awareness > * Expiration policy > * Cluster API > * Cluster group API > * Compute > * Services -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13331) Document .NET thin client features implemented in 2.9 release
Aleksey Plekhanov created IGNITE-13331: -- Summary: Document .NET thin client features implemented in 2.9 release Key: IGNITE-13331 URL: https://issues.apache.org/jira/browse/IGNITE-13331 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Plekhanov Fix For: 2.9 Document .NET thin client features: * Cluster API * Cluster group API * Compute API * Server discovery * Continues queries -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13040) Remove unused parameter from TcpDiscoverySpi.writeToSocket()
[
https://issues.apache.org/jira/browse/IGNITE-13040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172093#comment-17172093
]
Aleksey Kurinov commented on IGNITE-13040:
--
[~vladsz83] I've updated source code according you your recommendations.
{color:#24292e}TcpDiscoveryConnectionCheckMessage
{color:#003000}m{color}{color}essage stub is used according to your comment
{color:#24292e}// Replace logic routine message with a stub to update
last-sent-time to avoid segmentation on{color}
{color:#24292e} // connRecoveryTimeout.{color}
{color:#24292e}please review PR changes to check if I updated it
correctly{color}
[~slava.koptilin] , [~vladsz83] test still fail in TeamCity and i'm not sure why
here is the link to report in teamcity Bot:
[https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/7977/head=Latest]
to double check I submitted another Pull Request with a minor change against
master branch. I just added a comment line. TemCity test also failed for this
fake PR:
[https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/8121/head=Latest]
Please clarify how to get TeamCity test passed ?
> Remove unused parameter from TcpDiscoverySpi.writeToSocket()
>
>
> Key: IGNITE-13040
> URL: https://issues.apache.org/jira/browse/IGNITE-13040
> Project: Ignite
> Issue Type: Improvement
> Environment:
>Reporter: Vladimir Steshin
>Assignee: Aleksey Kurinov
>Priority: Trivial
> Labels: newbie
>
> Unused parameter
> {code:java}
> TcpDiscoveryAbstractMessage msg{code}
> should be removed from
> {code:java}
> TcpDiscoverySpi.writeToSocket(Socket sock, TcpDiscoveryAbstractMessage msg,
> byte[] data, long timeout){code}
> This method seems to send raw data, not a message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12791) [IEP-39] Management API to cancel user provided tasks and queries - documentation
[ https://issues.apache.org/jira/browse/IGNITE-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12791: --- Labels: IEP-39 important (was: IEP-39) > [IEP-39] Management API to cancel user provided tasks and queries - > documentation > - > > Key: IGNITE-12791 > URL: https://issues.apache.org/jira/browse/IGNITE-12791 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-39, important > > New featured from IGNITE-12632 should be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12791) [IEP-39] Management API to cancel user provided tasks and queries - documentation
[ https://issues.apache.org/jira/browse/IGNITE-12791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12791: --- Fix Version/s: 2.9 > [IEP-39] Management API to cancel user provided tasks and queries - > documentation > - > > Key: IGNITE-12791 > URL: https://issues.apache.org/jira/browse/IGNITE-12791 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-39, important > Fix For: 2.9 > > > New featured from IGNITE-12632 should be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12968) Create cluster snapshot documentation pages
[ https://issues.apache.org/jira/browse/IGNITE-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12968: --- Labels: iep-43 important (was: iep-43) > Create cluster snapshot documentation pages > --- > > Key: IGNITE-12968 > URL: https://issues.apache.org/jira/browse/IGNITE-12968 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Major > Labels: iep-43, important > Fix For: 2.9 > > > Add the following to the Apache Ignite documentation: > 1. How to create a cluster snapshot (describe API, limitations) > 2. How to configure a destination directory > 3. Manual steps for a snapshot restore > 4. Examples -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13239) Document APIs to view and change Cluster ID and Tag
[ https://issues.apache.org/jira/browse/IGNITE-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13239: --- Fix Version/s: 2.9 > Document APIs to view and change Cluster ID and Tag > --- > > Key: IGNITE-13239 > URL: https://issues.apache.org/jira/browse/IGNITE-13239 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Chugunov >Priority: Major > Labels: important > Fix For: 2.9 > > > In IGNITE-13185 new APIs and changes were introduced to view Cluster ID and > Tag and change Tag. > These APIs and use cases need to be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13239) Document APIs to view and change Cluster ID and Tag
[ https://issues.apache.org/jira/browse/IGNITE-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13239: --- Labels: important (was: ) > Document APIs to view and change Cluster ID and Tag > --- > > Key: IGNITE-13239 > URL: https://issues.apache.org/jira/browse/IGNITE-13239 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Sergey Chugunov >Priority: Major > Labels: important > > In IGNITE-13185 new APIs and changes were introduced to view Cluster ID and > Tag and change Tag. > These APIs and use cases need to be documented. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12443) Document the Ignite Sandbox
[ https://issues.apache.org/jira/browse/IGNITE-12443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12443: --- Labels: iep-38 important (was: iep-38) > Document the Ignite Sandbox > --- > > Key: IGNITE-12443 > URL: https://issues.apache.org/jira/browse/IGNITE-12443 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-38, important > Fix For: 2.9 > > > Document how to configure and use the Ignite Sandbox. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12443) Document the Ignite Sandbox
[ https://issues.apache.org/jira/browse/IGNITE-12443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12443: --- Fix Version/s: 2.9 > Document the Ignite Sandbox > --- > > Key: IGNITE-12443 > URL: https://issues.apache.org/jira/browse/IGNITE-12443 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Garus >Assignee: Denis Garus >Priority: Major > Labels: iep-38 > Fix For: 2.9 > > > Document how to configure and use the Ignite Sandbox. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13330) Document java thin client 2.8 and 2.9 release features
Aleksey Plekhanov created IGNITE-13330: -- Summary: Document java thin client 2.8 and 2.9 release features Key: IGNITE-13330 URL: https://issues.apache.org/jira/browse/IGNITE-13330 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Plekhanov Fix For: 2.9 Document implemented in 2.8 and 2.9 release features for java thin client: * Partition awareness * Cluster API * Cluster group API * Compute * Services -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13328) Control.sh bash script swallow return code of CommandHandler and always return 0
[
https://issues.apache.org/jira/browse/IGNITE-13328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinskiy reassigned IGNITE-13328:
-
Assignee: Ivan Daschinskiy
> Control.sh bash script swallow return code of CommandHandler and always
> return 0
>
>
> Key: IGNITE-13328
> URL: https://issues.apache.org/jira/browse/IGNITE-13328
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1, 2.8
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Blocker
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After merging
> [IGNITE-12367|https://issues.apache.org/jira/browse/IGNITE-12367],
> control.sh always return 0, despite the fact that CommandHandler returns
> correct code.
> For example:
> Ignite 2.8.1
> {code}
> Failed to execute baseline command='collect'
> Latest topology update failed.
> Connection to cluster failed. Latest topology update failed.
> Command [BASELINE] finished with code: 2
> Control utility has completed execution at: 2020-08-05T15:01:34.123
> Execution time: 26627 ms
> >>> echo $?
> 0
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11719) Document cluster read-only mode
[ https://issues.apache.org/jira/browse/IGNITE-11719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-11719: --- Labels: important (was: ) > Document cluster read-only mode > --- > > Key: IGNITE-11719 > URL: https://issues.apache.org/jira/browse/IGNITE-11719 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Sergey Antonov >Assignee: Artem Budnikov >Priority: Critical > Labels: important > Fix For: 2.9 > > > We should document cluster wide read-only mode. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13060) Tracing: initial implementation
[ https://issues.apache.org/jira/browse/IGNITE-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-13060: --- Labels: important (was: ) > Tracing: initial implementation > --- > > Key: IGNITE-13060 > URL: https://issues.apache.org/jira/browse/IGNITE-13060 > Project: Ignite > Issue Type: Improvement >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Initial tracing implementation. See > [IEP-48|https://cwiki.apache.org/confluence/display/IGNITE/IEP-48%3A+Tracing] > for details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12438) Extend communication protocol to establish client-server connection
[ https://issues.apache.org/jira/browse/IGNITE-12438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-12438: --- Labels: important (was: ) > Extend communication protocol to establish client-server connection > --- > > Key: IGNITE-12438 > URL: https://issues.apache.org/jira/browse/IGNITE-12438 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Ivan Bessonov >Priority: Major > Labels: important > Fix For: 2.9 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Recently there was quite a lot of questions related to thick clients > connectivity issues when the clients are deployed in a k8s pod [1]. The > general issue here is clients reporting network address which are not > reachable from server nodes. At the same time, the clients can connect to > server nodes. > An idea of how to fix this is as follows: > * Make sure that think clients discovery SPI always maintains a connection > to a server node (this should be already implemented) > * (Optionally) detect when a client has only one-way connectivity with the > server nodes. This part should be investigated. We need this to avoid server > nodes attempt to connect to a client and send communication request to the > client node faster > * When a server attempts to establish a connection with a client, check if > client is unreachable or the previous connection attempt failed. If so, send > a discovery message to the client to force a client-server connection. In > this case, server will be able to send the original message via the newly > established connection. > [1] > https://stackoverflow.com/questions/59192075/ignite-communicationspi-questions-in-paas-environment/59232504 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172072#comment-17172072
]
Aleksey Plekhanov commented on IGNITE-12911:
Discussed with [~akalashnikov] privately. There is no chance to resolve this
issue in 2.9. Moved to the next release.
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Assignee: Anton Kalashnikov
>Priority: Blocker
> Fix For: 2.10
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-16-46-381.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
> !image-2020-04-21-17-16-29-107.png!
>
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
>
[jira] [Updated] (IGNITE-12911) B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled.
[
https://issues.apache.org/jira/browse/IGNITE-12911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-12911:
---
Fix Version/s: (was: 2.9)
2.10
> B+Tree Corrupted exception when using a key extracted from a BinaryObject
> value object --- and SQL enabled.
> ---
>
> Key: IGNITE-12911
> URL: https://issues.apache.org/jira/browse/IGNITE-12911
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
>Reporter: Alexander Korenshteyn
>Assignee: Anton Kalashnikov
>Priority: Blocker
> Fix For: 2.10
>
> Attachments: Employee.java, EmployeeId.java, ServerNode.java,
> image-2020-04-21-17-10-55-797.png, image-2020-04-21-17-11-31-242.png,
> image-2020-04-21-17-16-10-703.png, image-2020-04-21-17-16-29-107.png,
> image-2020-04-21-17-16-46-381.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a key is part of the value like so:
> class key \{ ... }
> class value
> { private Key key getKey() }
> cache = ignite.cache()*.withKeepBinary()*
> the following scenario yields a B+ Tree exception:
> 1. *Enable SQL via annotations or QueryEntities.*
> key1= new Key()
> value1 = new Value(key1)
> cache.put(key1, value1)
> BinaryObject val2 = cache.get(key1)
> BinaryObject key2 = val2.field("key")
>
> *cache2.put(key2.toBuilder().build(), emp1); // OK!*
>
> *cache.put(key2, emp1); // CRASH!!! CorruptedTreeException: B+Tree
> iscorrupted ...*
> user list:
>
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-crashes-with-CorruptedTreeException-quot-B-Tree-is-corrupted-quot-on-a-composite-BinaryObjecto-tc32032.html]
> *Reproducer – attached*
>
> his happens because:
> CacheRowAdapter.readFullRow() reads the length
> *int len = PageUtils.getInt(addr,off)*
> *it returns 0 when val2.field("key") is used*
>
> *the data is written correctly in DataPageIO.writeDataPageIO():*
> !image-2020-04-21-17-16-46-381.png!
>
> *but read incorrectly in CacheRowAdapter.readFullRow()*
> !image-2020-04-21-17-16-29-107.png!
>
>
> Exception:
> [2020-04-17 11:24:33,475][ERROR][main][root] Critical system error detected.
> Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
> o.a.i.i.processors.cache.persistence.tree.CorruptedTreeException: B+Tree is
> corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith
> class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> B+Tree is corrupted [pages(groupId, pageId)=[IgniteBiTuple [val1=1258113742,
> val2=844420635164673]], cacheId=1976096430, cacheName=EMPLOYEE,
> indexName=_key_PK, msg=Runtime failure on row: Row@2233cac0[ key:
> model.EmployeeId [idHash=1744523301, hash=674030145, employeeNumber=65348765,
> departmentNumber=123], val: model.Employee [idHash=382762227,
> hash=1627745429, firstName=John, lastName=Smith, id=model.EmployeeId
> [idHash=2021540695, hash=674030145, employeeNumber=65348765,
> departmentNumber=123]] ][ John, Smith ]]
> at
> org.apache.ignite.internal.processors.query.h2.database.H2Tree.corruptedTreeException(H2Tree.java:836)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2447)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2394)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:437)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:756)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:363)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:2016)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:401)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2555)
> at
>
