[jira] [Updated] (IGNITE-13449) Ducktape selftest checks use java from JAVA_HOME
[ https://issues.apache.org/jira/browse/IGNITE-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13449: -- Priority: Critical (was: Major) > Ducktape selftest checks use java from JAVA_HOME > - > > Key: IGNITE-13449 > URL: https://issues.apache.org/jira/browse/IGNITE-13449 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Critical > > Selftests are tests that check ducktests environment is correct and test are > reliable, and we can rely on their timings and results. > > Check that ignite.sh uses java set with JAVA_HOME -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13430) Create minimal documentation for ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-13430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-13430:
--
Priority: Critical (was: Major)
> Create minimal documentation for ducktape tests
> ---
>
> Key: IGNITE-13430
> URL: https://issues.apache.org/jira/browse/IGNITE-13430
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Ivan Daschinskiy
>Assignee: Sergei Ryzhov
>Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Create minimal quickstart documentation in {{README.md}}
> Documentation should contain following:
> # Requirements for development
> # Requirements for running tests locally
> # Exact algorithm how to run tests locally (full suite, particular suite,
> particular test)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13448) Ducktests selftest: time is synchronized on nodes
[ https://issues.apache.org/jira/browse/IGNITE-13448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13448: -- Priority: Critical (was: Major) > Ducktests selftest: time is synchronized on nodes > - > > Key: IGNITE-13448 > URL: https://issues.apache.org/jira/browse/IGNITE-13448 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Critical > Time Spent: 1h 50m > Remaining Estimate: 0h > > Selftests are tests that check ducktests environment is correct and test are > reliable, and we can rely on their timings and results. > It's required to add test that check that time on all nodes is synchronized > (the same). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13446) Configs inside Ducktests logs should be pretty printed
[
https://issues.apache.org/jira/browse/IGNITE-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-13446:
--
Priority: Critical (was: Major)
> Configs inside Ducktests logs should be pretty printed
> --
>
> Key: IGNITE-13446
> URL: https://issues.apache.org/jira/browse/IGNITE-13446
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov (Obsolete, actual is "av")
>Assignee: Sergei Ryzhov
>Priority: Critical
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, I see the following inside the logs
> {code}
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>
> http://www.springframework.org/schema/beans/spring-beans.xsd;>
>
>
>
>
> value="/mnt/service/ignite-log4j.xml"/>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>
>
>
> ducker02
>
> ducker03
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction">
>
> class="org.apache.ignite.internal.ducktest.tests.cellular_affinity_test.CellularAffinityBackupFilter">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-13969) Thin client test [umbrella]
[ https://issues.apache.org/jira/browse/IGNITE-13969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov reassigned IGNITE-13969: - Assignee: Evgeniya Vdovets > Thin client test [umbrella] > --- > > Key: IGNITE-13969 > URL: https://issues.apache.org/jira/browse/IGNITE-13969 > Project: Ignite > Issue Type: Wish >Reporter: Anton Vinogradov >Assignee: Evgeniya Vdovets >Priority: Major > > Ensure Thin client works. > Check the whole TC API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14015) Tracing SQL: tracing of SELECT queries causes incorrect span inheritance
Mikhail Petrov created IGNITE-14015: --- Summary: Tracing SQL: tracing of SELECT queries causes incorrect span inheritance Key: IGNITE-14015 URL: https://issues.apache.org/jira/browse/IGNITE-14015 Project: Ignite Issue Type: Bug Reporter: Mikhail Petrov Assignee: Mikhail Petrov Execution of SELECT queries with tracing enabled leaves span related to this query in MTC#span variable for user thread. So the trace of next operation from the user thread will be inherited from span related to previous query execution. We must clear MTC#span thread local variable after query execution ends. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14013: - Priority: Critical (was: Major) > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Critical > Labels: important > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14013: - Fix Version/s: 2.10 > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14013: - Ignite Flags: (was: Docs Required,Release Notes Required) > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14013: - Labels: important (was: ) > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14013: - Component/s: documentation > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267413#comment-17267413 ] Nikita Safonov commented on IGNITE-14013: - [~PetrovMikhail] I've approved your PR. > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267407#comment-17267407 ] Nikita Safonov commented on IGNITE-14013: - [~PetrovMikhail] Sure! > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-14013: Description: It's needed to add documentation for the node validation failure event. (was: It's needed to add documentation for the node validation failed event.) > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failure event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267395#comment-17267395 ] Mikhail Petrov commented on IGNITE-14013: - [~nsafonov], could you please take a look? > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failed event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14013) Add documentation for node validation failure event
[ https://issues.apache.org/jira/browse/IGNITE-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-14013: Summary: Add documentation for node validation failure event (was: Add documentation for node validation failed event) > Add documentation for node validation failure event > --- > > Key: IGNITE-14013 > URL: https://issues.apache.org/jira/browse/IGNITE-14013 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to add documentation for the node validation failed event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13986) Proof of concept - SWIM group membership protocol for discovery
[ https://issues.apache.org/jira/browse/IGNITE-13986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267364#comment-17267364 ] Ivan Bessonov commented on IGNITE-13986: Ok, now the same thing but with a new context. Following thought might go into IEP in the future. New component will conceptually include group membership and p2p messaging subsystem. It's going to be a general network component. Required API consists of the following: * start / stop; * retrieving information about current group members; * listening to membership events: ** node appeared; ** node left; ** node failed; * listening for incoming messages; * sending messages: ** there's a requirements of being able to send idempotent messages with very weak guarantees: *** no delivery guarantees required; *** multiple copies of the same message might be sent; *** no need to have any kind of acknowledgement; ** there's another requirement for the common use: *** message must be sent exactly once with an acknowledgement that it has actually been received (not processed); *** messages must be received in the same order they were sent. These types of messages might utilize current recovery protocol with acks every 32 (or so) messages. This setting must be flexible enough so that we won't get OOM in big topologies. Possibility of SSL connections should be considered. Given that SWIM membership events appear in no particular order, it's possible to receive a message from node before knowing that it exists or after it's already gone. This is one of the reasons why we should basically merge "discovery" and "communication" into one thing. Another reason is that it's more convenient to use a single port per node instead of two (i.e. use multiplexing). There might be a requirement to stream data from one node to another (in SQL engine, for example). The implementation is not obvious for me, maybe such thing will be implemented on top of the current component. Anyway, implementation will be tightly coupled with netty integration, currently investigated by [~sergeychugunov]. Everything related to actual "Discovery" and messages like "NodeJoined" is not discussed here. Since we're moving to RAFT-based distributed metadata storage as a mean to send ordered messages, discussing them is just out of scope. Current "Discovery" with its join protocol and strict ordering of events will cease to exist. There's a bunch of settings that should be extracted from scalecube configuration and joined with some specific netty settings. The whole set of settings will be determined during implementation. New configuration framework will be used. For the first time, probably. > Proof of concept - SWIM group membership protocol for discovery > --- > > Key: IGNITE-13986 > URL: https://issues.apache.org/jira/browse/IGNITE-13986 > Project: Ignite > Issue Type: New Feature >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: iep-61, ignite-3 > > In IEP-61 it is mentioned that discovery protocol will be updated. We need to > play with mentioned options for a little bit to conclude if they match our > needs: > [http://www.cs.cornell.edu/Info/Projects/Spinglass/public_pdfs/SWIM.pdf] > [https://github.com/scalecube/scalecube-cluster] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14003) OOM on creating rebalance iterator while rebalancing cache with large values.
[ https://issues.apache.org/jira/browse/IGNITE-14003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-14003: - Fix Version/s: 2.11 > OOM on creating rebalance iterator while rebalancing cache with large values. > - > > Key: IGNITE-14003 > URL: https://issues.apache.org/jira/browse/IGNITE-14003 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9, 2.8.1, 2.9.1 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Critical > Fix For: 2.11 > > Attachments: ReplicatedCacheRebalanceTest.java > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario > 1. Start replicated cache on ignite node, memory region approx 6 Gb, heap 1Gb > 2. Load significant amount of data to cache with values approx 200Kb (~20K kv > pairs) > 3. Start another node > First node (supplier) will crash while initializing rebalance iterator with > OOM > Main reason -- all values, to whon pointed from leaf of BTree, are all loaded > to buffer in BPlusTree#ForwardCursor. For replicated cache, 512 iterators for > each partition are created at once. > Reproducer is attached, run it with *-Xmx1G* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13761) Implement Segmented-LRU and CLOCK page replacement algorithms
[ https://issues.apache.org/jira/browse/IGNITE-13761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267341#comment-17267341 ] Aleksey Plekhanov commented on IGNITE-13761: [~zstan], here is a summary of average throughput from the attached reports: || ||Random-LRU||Segmented-LRU||CLOCK|| |putAll without page replacement|3,221.42|3,095.70|3,187.12| |putAll with page replacement|913.84|979.63|966.68| |putAll with page replacement and BG queries|829.18|886.95|884.00| |getAll without page replacement|5,195.35|4,859.03|5,287.69| |getAll with page replacement|2,231.77|2,437.03|2,567.85| |getAll with page replacement and BG queries|1,145.97|1,288.32|1,331.15| > Implement Segmented-LRU and CLOCK page replacement algorithms > - > > Key: IGNITE-13761 > URL: https://issues.apache.org/jira/browse/IGNITE-13761 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-62 > Attachments: GetBenchmark.zip, PutBenchmark.zip > > Time Spent: 2h 40m > Remaining Estimate: 0h > > See IEP-62 for more details. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14003) OOM on creating rebalance iterator while rebalancing cache with large values.
[ https://issues.apache.org/jira/browse/IGNITE-14003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267339#comment-17267339 ] Anton Vinogradov commented on IGNITE-14003: --- GLTM (except explicit nulling to help the GC, but this makes fix smaller (safer :) ) and appliable to older versions asap). Merged to master. Thanks for your contribution! > OOM on creating rebalance iterator while rebalancing cache with large values. > - > > Key: IGNITE-14003 > URL: https://issues.apache.org/jira/browse/IGNITE-14003 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9, 2.8.1, 2.9.1 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Critical > Attachments: ReplicatedCacheRebalanceTest.java > > Time Spent: 20m > Remaining Estimate: 0h > > Scenario > 1. Start replicated cache on ignite node, memory region approx 6 Gb, heap 1Gb > 2. Load significant amount of data to cache with values approx 200Kb (~20K kv > pairs) > 3. Start another node > First node (supplier) will crash while initializing rebalance iterator with > OOM > Main reason -- all values, to whon pointed from leaf of BTree, are all loaded > to buffer in BPlusTree#ForwardCursor. For replicated cache, 512 iterators for > each partition are created at once. > Reproducer is attached, run it with *-Xmx1G* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-14001:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14014) Insufficient documentation and examples for ignite-spring-boot-autoconfigure-ext
Sergey Kadaner created IGNITE-14014: --- Summary: Insufficient documentation and examples for ignite-spring-boot-autoconfigure-ext Key: IGNITE-14014 URL: https://issues.apache.org/jira/browse/IGNITE-14014 Project: Ignite Issue Type: Bug Components: spring Affects Versions: 2.9.1 Reporter: Sergey Kadaner I tried following the example on the documentation page linked below but it covers only a small subset of Ignite configuration options. I tried guessing how to configure an IP finder and a near cache with an eviction policy, but without any success. To make matters worse incorrect configuration is usually silently ignored. https://ignite.apache.org/docs/latest/extensions-and-integrations/spring/spring-boot#set-ignite-up-via-spring-boot-configuration -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-14001:
-
Fix Version/s: 3.0.0-alpha2
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha1
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12955) Document a new command control.sh --cache check_index_inline_sizes
[ https://issues.apache.org/jira/browse/IGNITE-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-12955: Assignee: Maxim Muzafarov > Document a new command control.sh --cache check_index_inline_sizes > -- > > Key: IGNITE-12955 > URL: https://issues.apache.org/jira/browse/IGNITE-12955 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Assignee: Maxim Muzafarov >Priority: Major > Labels: important > Fix For: 2.10 > > > Please look at IGNITE-12942 and devlist discussion linked to IGNITE-12942 for > all information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14011) Add RAT check, PMD, Idea Inspections, and code style suites for Ignite 3 project
[ https://issues.apache.org/jira/browse/IGNITE-14011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267276#comment-17267276 ] Peter Ivanov edited comment on IGNITE-14011 at 1/18/21, 3:04 PM: - Prepared builds: * [Licenses Headers|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_LicensesHeaders] * [Inspections|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_Inspections] * [Code Style|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_CodeStyle?mode=builds] was (Author: vveider): Prepared builds: * [Licenses Headers|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_LicensesHeaders] * [Inspections|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_Inspections] > Add RAT check, PMD, Idea Inspections, and code style suites for > Ignite 3 project > > > Key: IGNITE-14011 > URL: https://issues.apache.org/jira/browse/IGNITE-14011 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We need to copy the following suites to Ignite 3 (public TC). Please create a > corresponding ticket in Ignite JIRA if pom.xml modifications are > required.https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_LicensesHeaders?mode=builds#all-projectshttps://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_InspectionsCore?mode=builds#all-projects > (assuming TC will be able to run inspections check on the new > repository)https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle?mode=builds#all-projectshttps://ggtc.gridgain.com/buildConfiguration/Tests_GridGainCeEeUe_Latest_SanityCheck_Pmd?mode=builds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11747) Document --tx control script commands
[
https://issues.apache.org/jira/browse/IGNITE-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11747:
-
Fix Version/s: (was: 2.10)
> Document --tx control script commands
> -
>
> Key: IGNITE-11747
> URL: https://issues.apache.org/jira/browse/IGNITE-11747
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Ivan Rakov
>Priority: Critical
> Labels: important
>
> Along with consistency check utilities, ./control.sh script has --tx command
> which allows to display info about active transactions and even kill hanging
> transactions directly.
> ./control.sh provides just brief description of options:
> {code:java}
> List or kill transactions:
> control.sh --tx [--xid XID] [--min-duration SECONDS] [--min-size SIZE]
> [--label PATTERN_REGEX] [--servers|--clients] [--nodes
> consistentId1[,consistentId2,,consistentIdN]] [--limit NUMBER] [--order
> DURATION|SIZE|START_TIME] [--kill] [--info] [--yes]
> {code}
> We should document possible use cases and options of the command, possibly
> somewhere close to [https://apacheignite-tools.readme.io/docs/control-script]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11747) Document --tx control script commands
[
https://issues.apache.org/jira/browse/IGNITE-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267331#comment-17267331
]
Nikita Safonov commented on IGNITE-11747:
-
Hello [~mmuzaf], I have no objections.
> Document --tx control script commands
> -
>
> Key: IGNITE-11747
> URL: https://issues.apache.org/jira/browse/IGNITE-11747
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Ivan Rakov
>Priority: Critical
> Labels: important
> Fix For: 2.10
>
>
> Along with consistency check utilities, ./control.sh script has --tx command
> which allows to display info about active transactions and even kill hanging
> transactions directly.
> ./control.sh provides just brief description of options:
> {code:java}
> List or kill transactions:
> control.sh --tx [--xid XID] [--min-duration SECONDS] [--min-size SIZE]
> [--label PATTERN_REGEX] [--servers|--clients] [--nodes
> consistentId1[,consistentId2,,consistentIdN]] [--limit NUMBER] [--order
> DURATION|SIZE|START_TIME] [--kill] [--info] [--yes]
> {code}
> We should document possible use cases and options of the command, possibly
> somewhere close to [https://apacheignite-tools.readme.io/docs/control-script]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11747) Document --tx control script commands
[
https://issues.apache.org/jira/browse/IGNITE-11747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267324#comment-17267324
]
Maxim Muzafarov commented on IGNITE-11747:
--
[~nsafonov]
Hello, it seems this issue related to the 2.8 release feature. What if we
complete this issue outside of the 2.10 release scope?
> Document --tx control script commands
> -
>
> Key: IGNITE-11747
> URL: https://issues.apache.org/jira/browse/IGNITE-11747
> Project: Ignite
> Issue Type: Task
> Components: control.sh, documentation
>Reporter: Ivan Rakov
>Priority: Critical
> Labels: important
> Fix For: 2.10
>
>
> Along with consistency check utilities, ./control.sh script has --tx command
> which allows to display info about active transactions and even kill hanging
> transactions directly.
> ./control.sh provides just brief description of options:
> {code:java}
> List or kill transactions:
> control.sh --tx [--xid XID] [--min-duration SECONDS] [--min-size SIZE]
> [--label PATTERN_REGEX] [--servers|--clients] [--nodes
> consistentId1[,consistentId2,,consistentIdN]] [--limit NUMBER] [--order
> DURATION|SIZE|START_TIME] [--kill] [--info] [--yes]
> {code}
> We should document possible use cases and options of the command, possibly
> somewhere close to [https://apacheignite-tools.readme.io/docs/control-script]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12955) Document a new command control.sh --cache check_index_inline_sizes
[ https://issues.apache.org/jira/browse/IGNITE-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12955: - Ignite Flags: (was: Docs Required) > Document a new command control.sh --cache check_index_inline_sizes > -- > > Key: IGNITE-12955 > URL: https://issues.apache.org/jira/browse/IGNITE-12955 > Project: Ignite > Issue Type: New Feature > Components: control.sh, documentation >Reporter: Sergey Antonov >Priority: Major > Labels: important > Fix For: 2.10 > > > Please look at IGNITE-12942 and devlist discussion linked to IGNITE-12942 for > all information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14011) Add RAT check, PMD, Idea Inspections, and code style suites for Ignite 3 project
[ https://issues.apache.org/jira/browse/IGNITE-14011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267276#comment-17267276 ] Peter Ivanov edited comment on IGNITE-14011 at 1/18/21, 2:09 PM: - Prepared builds: * [Licenses Headers|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_LicensesHeaders] * [Inspections|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_Inspections] was (Author: vveider): Prepared builds: * [Licenses Headers|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_LicensesHeaders?mode=builds] > Add RAT check, PMD, Idea Inspections, and code style suites for > Ignite 3 project > > > Key: IGNITE-14011 > URL: https://issues.apache.org/jira/browse/IGNITE-14011 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We need to copy the following suites to Ignite 3 (public TC). Please create a > corresponding ticket in Ignite JIRA if pom.xml modifications are > required.https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_LicensesHeaders?mode=builds#all-projectshttps://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_InspectionsCore?mode=builds#all-projects > (assuming TC will be able to run inspections check on the new > repository)https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle?mode=builds#all-projectshttps://ggtc.gridgain.com/buildConfiguration/Tests_GridGainCeEeUe_Latest_SanityCheck_Pmd?mode=builds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13883) .NET: Performance: Refactor BinarySystemHandlers.TryReadSystemType to switch-case
[
https://issues.apache.org/jira/browse/IGNITE-13883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267292#comment-17267292
]
Maxim Muzafarov commented on IGNITE-13883:
--
Cherry-picked to 2.10
> .NET: Performance: Refactor BinarySystemHandlers.TryReadSystemType to
> switch-case
> -
>
> Key: IGNITE-13883
> URL: https://issues.apache.org/jira/browse/IGNITE-13883
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
> Labels: .NET
> Fix For: 2.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{BinarySystemHandlers.TryReadSystemType}} is too clever with interfaces and
> generics:
> * Hard to understand and maintain
> * Possibly causes overhead due to virtual method calls
> Refactor to switch-case and check if performance improves.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13931) .NET: Service can't assign correct type to passed array parameters (.Net -> .Net call)
[
https://issues.apache.org/jira/browse/IGNITE-13931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267290#comment-17267290
]
Maxim Muzafarov commented on IGNITE-13931:
--
Cherry-picked to 2.10
> .NET: Service can't assign correct type to passed array parameters (.Net ->
> .Net call)
> --
>
> Key: IGNITE-13931
> URL: https://issues.apache.org/jira/browse/IGNITE-13931
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Yaroslav Molochkov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: .NET
> Fix For: 2.10
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This issue relates to IGNITE-12823.
> Ignite client calls deployed service and fails with the following exception:
> {code:java}
> Apache.Ignite.Core.Common.JavaException: class
> org.apache.ignite.IgniteException: Failed to invoke proxy: there is no method
> 'processSomething' in type 'SomeService' with (Int32, Object[]) arguments
> at
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.inLongOutLong(Native
> Method)
> at
> org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.serviceInvokeMethod(PlatformCallbackGateway.java:942)
> at
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.invokeMethod(PlatformAbstractService.java:214)
> at
> org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.invokeMethod(PlatformAbstractService.java:185)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.callService(GridServiceProxy.java:491)
> at
> org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:469)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1847)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:598)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7077)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:592)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:521)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1368)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:2130)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1907)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1528)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:241)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1421)
> at
> org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Service interface itself looks like this:
> {code:java}
> public interface SomeService : IService
> {
> int processSomething(int foo, Parameter[] parameters);
> int processSomething(int foo, int bar);
> }
> public class Parameter
{
> private int id;
> private ParamValue[] _values;
> public Parameter(int id, ParamValue[] _values)
{
>this.id = id;
>this._values = _values;
> }
>
}
>
public class ParamValue
{
> private int id;
> private double val;
> public ParamValue(int id, double val)
{
>this.id = id;
>this.val = val;
> }
>
}
> {code}
> And the call to the service:
> {code:java}
> var svc = igniteServices.GetServiceProxy(name, false);
> var result = svc.processSomething(id, parameters);
> {code}
> Please note, that if there's no overloaded methods, at least in our
>
[jira] [Updated] (IGNITE-14012) Ducktape jmx_utils should consider the possibility of intermediate MBeans
[ https://issues.apache.org/jira/browse/IGNITE-14012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14012: -- Labels: (was: IEP-56) > Ducktape jmx_utils should consider the possibility of intermediate MBeans > - > > Key: IGNITE-14012 > URL: https://issues.apache.org/jira/browse/IGNITE-14012 > Project: Ignite > Issue Type: Task >Reporter: Mikhail Filatov >Assignee: Mikhail Filatov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Sometimes MBeans structure looks like: > org.apache:clsLdr=764c12b6,group=Kernal,igniteInstanceName=Server_Example_Xml_-676757500,name=IgniteKernal > but jmx_utils works only if it looks like: > .*group=Kernal,name=IgniteKernal > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13704) Discovery ducktest: Reduce FDT. Fix netfilter logs. Make cluster scalable.
[ https://issues.apache.org/jira/browse/IGNITE-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13704: -- Labels: iep-45 (was: IEP-56 iep-45) > Discovery ducktest: Reduce FDT. Fix netfilter logs. Make cluster scalable. > -- > > Key: IGNITE-13704 > URL: https://issues.apache.org/jira/browse/IGNITE-13704 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Labels: iep-45 > Time Spent: 20m > Remaining Estimate: 0h > > Discovery ducktest: Reduce FDT. Fix netfilter logs. Make cluster scalable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11110) UnsupportedOperationException: null when stopping grid
[
https://issues.apache.org/jira/browse/IGNITE-0?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267281#comment-17267281
]
Maxim Muzafarov commented on IGNITE-0:
--
Cherry-picked to 2.10
> UnsupportedOperationException: null when stopping grid
> --
>
> Key: IGNITE-0
> URL: https://issues.apache.org/jira/browse/IGNITE-0
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Jens Borgland
>Assignee: Anton Kurbanov
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> After upgrading to 2.7 we've started getting these errors when stopping grids:
> {noformat}
> java.lang.UnsupportedOperationException: null
> at
> org.jsr166.ConcurrentLinkedHashMap.clear(ConcurrentLinkedHashMap.java:1551)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.stop(GridJobProcessor.java:264)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2356)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2228)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2612)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2575)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:379)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at org.apache.ignite.Ignition.stop(Ignition.java:225)
> ~[ignite-core-2.7.0.jar:2.7.0]
> at
> org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3568)
> ~[ignite-core-2.7.0.jar:2.7.0]
> {noformat}
> At first glance it looks likely that it was introduced with commit
> [d04d764|https://github.com/apache/ignite/commit/d04d76440ce86873de7aebc8c03d39484cd1e3e5]
> (the {{GridJobProcessor}} still calls {{clear()}} on maps).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-9109) CPP Thin: Implement SQL API
[ https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267280#comment-17267280 ] Maxim Muzafarov commented on IGNITE-9109: - Cherry-picked to 2.10 > CPP Thin: Implement SQL API > --- > > Key: IGNITE-9109 > URL: https://issues.apache.org/jira/browse/IGNITE-9109 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.6 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > Need to implement SQL API for C++ thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13928) Index defragmentation: only one index defragmented
[
https://issues.apache.org/jira/browse/IGNITE-13928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267279#comment-17267279
]
Maxim Muzafarov commented on IGNITE-13928:
--
Cherry-picked to 2.10
> Index defragmentation: only one index defragmented
> --
>
> Key: IGNITE-13928
> URL: https://issues.apache.org/jira/browse/IGNITE-13928
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Semyon Danilov
>Assignee: Semyon Danilov
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In IndexingDefragmentation.java:
> {code:java}
> // code placeholder
> H2TreeIndex oldH2Idx = (H2TreeIndex)indexes.get(2);
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14011) Add RAT check, PMD, Idea Inspections, and code style suites for Ignite 3 project
[ https://issues.apache.org/jira/browse/IGNITE-14011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267276#comment-17267276 ] Peter Ivanov commented on IGNITE-14011: --- Prepared builds: * [Licenses Headers|https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_SanityChecks_LicensesHeaders?mode=builds] > Add RAT check, PMD, Idea Inspections, and code style suites for > Ignite 3 project > > > Key: IGNITE-14011 > URL: https://issues.apache.org/jira/browse/IGNITE-14011 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We need to copy the following suites to Ignite 3 (public TC). Please create a > corresponding ticket in Ignite JIRA if pom.xml modifications are > required.https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_LicensesHeaders?mode=builds#all-projectshttps://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_InspectionsCore?mode=builds#all-projects > (assuming TC will be able to run inspections check on the new > repository)https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle?mode=builds#all-projectshttps://ggtc.gridgain.com/buildConfiguration/Tests_GridGainCeEeUe_Latest_SanityCheck_Pmd?mode=builds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14013) Add documentation for node validation failed event
Mikhail Petrov created IGNITE-14013: --- Summary: Add documentation for node validation failed event Key: IGNITE-14013 URL: https://issues.apache.org/jira/browse/IGNITE-14013 Project: Ignite Issue Type: Improvement Reporter: Mikhail Petrov Assignee: Mikhail Petrov It's needed to add documentation for the node validation failed event. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9109) CPP Thin: Implement SQL API
[ https://issues.apache.org/jira/browse/IGNITE-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-9109: Labels: important (was: ) > CPP Thin: Implement SQL API > --- > > Key: IGNITE-9109 > URL: https://issues.apache.org/jira/browse/IGNITE-9109 > Project: Ignite > Issue Type: New Feature > Components: platforms >Affects Versions: 2.6 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > Need to implement SQL API for C++ thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8732) SQL: REPLICATED cache cannot be left-joined to PARTITIONED
[
https://issues.apache.org/jira/browse/IGNITE-8732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-8732:
Issue Type: Bug (was: Improvement)
> SQL: REPLICATED cache cannot be left-joined to PARTITIONED
> --
>
> Key: IGNITE-8732
> URL: https://issues.apache.org/jira/browse/IGNITE-8732
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.5
>Reporter: Vladimir Ozerov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Labels: sql-engine
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *Steps to reproduce*
> # Run
> {{org.apache.ignite.sqltests.ReplicatedSqlTest#testLeftJoinReplicatedPartitioned}}
> # Observe that we have 2x results on 2-node cluster
> *Root Cause*
> {{left LEFT JOIN right ON cond}} operation assumes full scan of of a left
> expression. Currently we perform this scan on every node and then simply
> merge results on reducer. Two nodes, two scans of {{REPLICATED}} cache, 2x
> results.
> *Potential Solutions*
> We may consider several solutions. Deeper analysis is required to understand
> which is the right one.
> # Perform deduplication on reducer - this most prospective and general
> technique, described in more details below
> # Treat {{REPLICATED}} cache as {{PARTITIONED}}. Essentially, we just need
> to pass proper backup filter. But what if {{REPLICATED}} cache spans more
> nodes than {{PARTITIONED}}? We cannot rely on primary/backup in this case
> # Implement additional execution phase as follows:
> {code:java}
> SELECT left.cols, right.cols FROM left INNER JOIN right ON cond;
> // Get "inner join" part
> UNION
> UNICAST SELECT left.cols, [NULL].cols FROM left WHERE left.id NOT IN ([ids
> from the first phase]) // Get "outer join" part
> {code}
> *Reducer Deduplication*
> The idea is to get all data locally and then perform final deduplication.
> This may incur high network overhead, because of lot of duplicated left parts
> would be transferred. However, this could be optimized greatly with the
> following techniques applied one after another
> # Semi-jions: {{left}} is {{joined}} on mapper node, but instead of sending
> {{(left, right)}} relation, we send {{(left) + (right)}}
> # In case {{left}} part is known to be idempotent (i.e. it produces the same
> result set on all nodes), only one node will send {{(left) + (right)}}, other
> nodes will send {{(right)}} only
> # Merge {{left}} results with if needed (i.e. if idempotence-related opto
> was not applicable)
> # Join {{left}} and {{right}} parts on reducer
> *UPDATE*
> After a few attempts at the implementation, the solution of treating
> REPLICATED cache as PARTITIONED looks the most practical. The solution works
> in a limited case:
> * REPLICATED and PARTITIONED both have the same affinity function, number of
> partitions, node filter
> ** Note that REPLICATED has a different number of partitions by default
> * The JOIN is done on an affinity column of both caches
> ** Note that users often don’t create affinity keys for REPLICATED caches
> today
> * distributedJoins=false (distributed joins aren’t supported for now)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13659) TDE - Phase 3. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267247#comment-17267247 ] Maxim Muzafarov commented on IGNITE-13659: -- Merged to the master branch cherry-picked to 2.10 Thank you all for the review and contribution. > TDE - Phase 3. Documentation > > > Key: IGNITE-13659 > URL: https://issues.apache.org/jira/browse/IGNITE-13659 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: IEP-18, important, tde-phase-3 > Fix For: 2.10 > > Attachments: html-ver.zip > > Time Spent: 5h > Remaining Estimate: 0h > > Write documentation on the cache encryption key rotation function. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13854) Add documentation for the cluster performance profiling tool
[ https://issues.apache.org/jira/browse/IGNITE-13854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267216#comment-17267216 ] Maxim Muzafarov commented on IGNITE-13854: -- Merged to the master branch and cherry-picked to 2.10 Thank you for the review and contribution. > Add documentation for the cluster performance profiling tool > > > Key: IGNITE-13854 > URL: https://issues.apache.org/jira/browse/IGNITE-13854 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Labels: IEP-35, important > Fix For: 2.10 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > Add documentation for the cluster performance profiling tool. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14012) Ducktape jmx_utils should consider the possibility of intermediate MBeans
Mikhail Filatov created IGNITE-14012: Summary: Ducktape jmx_utils should consider the possibility of intermediate MBeans Key: IGNITE-14012 URL: https://issues.apache.org/jira/browse/IGNITE-14012 Project: Ignite Issue Type: Task Reporter: Mikhail Filatov Assignee: Mikhail Filatov Sometimes MBeans structure looks like: org.apache:clsLdr=764c12b6,group=Kernal,igniteInstanceName=Server_Example_Xml_-676757500,name=IgniteKernal but jmx_utils works only if it looks like: .*group=Kernal,name=IgniteKernal -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13994) Rebalance huge cache in the case of in-memory cluster
[ https://issues.apache.org/jira/browse/IGNITE-13994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267215#comment-17267215 ] Anton Vinogradov commented on IGNITE-13994: --- We should test both cases, a huge cache, and a huge entry. > Rebalance huge cache in the case of in-memory cluster > - > > Key: IGNITE-13994 > URL: https://issues.apache.org/jira/browse/IGNITE-13994 > Project: Ignite > Issue Type: Test >Reporter: Ivan Daschinskiy >Priority: Major > Labels: IEP-56 > > There are some evidence, that rebalancing huge cache without rebalance > throttling can cause OOM on supplier. We need to cover this scenario. > Scenario: > 1. Start two nodes and 1 replicated cache with data region much more than > heap. > 2. Stop one of the node. > 3. Load data to cache almost equal to size of data region. > 4. Start node. > Goal is to run experiments with parameters > 1. Heap size > 2. Cache size > 3. Rebalance batch size. > 4. Rebalance throttle -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13982) Add documentation for new checkpoint, cluster and cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267210#comment-17267210 ] Maxim Muzafarov commented on IGNITE-13982: -- Merged to the master branch and cherry-picked to 2.10. Thank you all. > Add documentation for new checkpoint, cluster and cache metrics > --- > > Key: IGNITE-13982 > URL: https://issues.apache.org/jira/browse/IGNITE-13982 > Project: Ignite > Issue Type: Task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.10 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Add documentation for new metrics: > * LastCheckpointbeforeLockDuration > * LastCheckpointListenersExecuteDuration > * LastCheckpointLockHoldDuration > * LastCheckpointWalCpRecordFsyncDuration > * LastCheckpointWriteCheckpointEntryDuration > * LastCheckpointSplitAndSortPagesDuration > * LastCheckpointStart > * CheckpointBeforeLockHistogram > * CheckpointLockWaitHistogram > * CheckpointListenersExecuteHistogram > * CheckpointMarkHistogram > * CheckpointLockHoldHistogram > * CheckpointPagesWriteHistogram > * CheckpointFsyncHistogram > * CheckpointWalRecordFsyncHistogram > * CheckpointWriteEntryHistogram > * CheckpointSplitAndSortPagesHistogram > * CheckpointHistogram > * TotalBaselineNodes > * TotalServerNodes > * TotalClientNodes > * ActiveBaselineNodes > * Rebalanced > * OffHeapEntriesCount > * OffHeapBackupEntriesCount > * OffHeapPrimaryEntriesCount > * HeapEntriesCount > * CacheSize > * IndexRebuildKeyProcessed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13982) Add documentation for new checkpoint, cluster and cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13982: - Component/s: documentation > Add documentation for new checkpoint, cluster and cache metrics > --- > > Key: IGNITE-13982 > URL: https://issues.apache.org/jira/browse/IGNITE-13982 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.10 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Add documentation for new metrics: > * LastCheckpointbeforeLockDuration > * LastCheckpointListenersExecuteDuration > * LastCheckpointLockHoldDuration > * LastCheckpointWalCpRecordFsyncDuration > * LastCheckpointWriteCheckpointEntryDuration > * LastCheckpointSplitAndSortPagesDuration > * LastCheckpointStart > * CheckpointBeforeLockHistogram > * CheckpointLockWaitHistogram > * CheckpointListenersExecuteHistogram > * CheckpointMarkHistogram > * CheckpointLockHoldHistogram > * CheckpointPagesWriteHistogram > * CheckpointFsyncHistogram > * CheckpointWalRecordFsyncHistogram > * CheckpointWriteEntryHistogram > * CheckpointSplitAndSortPagesHistogram > * CheckpointHistogram > * TotalBaselineNodes > * TotalServerNodes > * TotalClientNodes > * ActiveBaselineNodes > * Rebalanced > * OffHeapEntriesCount > * OffHeapBackupEntriesCount > * OffHeapPrimaryEntriesCount > * HeapEntriesCount > * CacheSize > * IndexRebuildKeyProcessed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13982) Add documentation for new checkpoint, cluster and cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-13982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-13982: - Ignite Flags: (was: Docs Required) > Add documentation for new checkpoint, cluster and cache metrics > --- > > Key: IGNITE-13982 > URL: https://issues.apache.org/jira/browse/IGNITE-13982 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.10 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Add documentation for new metrics: > * LastCheckpointbeforeLockDuration > * LastCheckpointListenersExecuteDuration > * LastCheckpointLockHoldDuration > * LastCheckpointWalCpRecordFsyncDuration > * LastCheckpointWriteCheckpointEntryDuration > * LastCheckpointSplitAndSortPagesDuration > * LastCheckpointStart > * CheckpointBeforeLockHistogram > * CheckpointLockWaitHistogram > * CheckpointListenersExecuteHistogram > * CheckpointMarkHistogram > * CheckpointLockHoldHistogram > * CheckpointPagesWriteHistogram > * CheckpointFsyncHistogram > * CheckpointWalRecordFsyncHistogram > * CheckpointWriteEntryHistogram > * CheckpointSplitAndSortPagesHistogram > * CheckpointHistogram > * TotalBaselineNodes > * TotalServerNodes > * TotalClientNodes > * ActiveBaselineNodes > * Rebalanced > * OffHeapEntriesCount > * OffHeapBackupEntriesCount > * OffHeapPrimaryEntriesCount > * HeapEntriesCount > * CacheSize > * IndexRebuildKeyProcessed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13958) .NET: Avoid binary configuration for Compute API invocation
[ https://issues.apache.org/jira/browse/IGNITE-13958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-13958: - Summary: .NET: Avoid binary configuration for Compute API invocation (was: .NET: Avoid binary configuration on Compute and Cache API invocation) > .NET: Avoid binary configuration for Compute API invocation > > > Key: IGNITE-13958 > URL: https://issues.apache.org/jira/browse/IGNITE-13958 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.9.1 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET > Fix For: 2.10 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently, it's required to explicitly register any custom user type as a > binary type to be able to invoke some compute API method with this type as a > parameter or return value. > We should use the same technique as in IGNITE-10075 to avoid explicit binary > type registration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13835) Improve discovery ducktape test to research small timeouts and behavior on large cluster.
[ https://issues.apache.org/jira/browse/IGNITE-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13835: -- Sprint: Ducktape Sprint 1 > Improve discovery ducktape test to research small timeouts and behavior on > large cluster. > - > > Key: IGNITE-13835 > URL: https://issues.apache.org/jira/browse/IGNITE-13835 > Project: Ignite > Issue Type: Improvement >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > Improve discovery ducktape test to research the cluster behavior with bigger > node number and smaller timeouts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14003) OOM on creating rebalance iterator while rebalancing cache with large values.
[
https://issues.apache.org/jira/browse/IGNITE-14003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267199#comment-17267199
]
Ignite TC Bot commented on IGNITE-14003:
{panel:title=Branch: [pull/8671/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8671/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5832146]]
* {color:#013220}IgniteCacheTestSuite2:
RebalanceIteratorLargeEntriesOOMTest.testRebalance - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5832189buildTypeId=IgniteTests24Java8_RunAll]
> OOM on creating rebalance iterator while rebalancing cache with large values.
> -
>
> Key: IGNITE-14003
> URL: https://issues.apache.org/jira/browse/IGNITE-14003
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9, 2.8.1, 2.9.1
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Critical
> Attachments: ReplicatedCacheRebalanceTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario
> 1. Start replicated cache on ignite node, memory region approx 6 Gb, heap 1Gb
> 2. Load significant amount of data to cache with values approx 200Kb (~20K kv
> pairs)
> 3. Start another node
> First node (supplier) will crash while initializing rebalance iterator with
> OOM
> Main reason -- all values, to whon pointed from leaf of BTree, are all loaded
> to buffer in BPlusTree#ForwardCursor. For replicated cache, 512 iterators for
> each partition are created at once.
> Reproducer is attached, run it with *-Xmx1G*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13845) Add checkpoint metrics
[ https://issues.apache.org/jira/browse/IGNITE-13845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267202#comment-17267202 ] Maxim Muzafarov commented on IGNITE-13845: -- Cherry-picked to 2.10 > Add checkpoint metrics > -- > > Key: IGNITE-13845 > URL: https://issues.apache.org/jira/browse/IGNITE-13845 > Project: Ignite > Issue Type: New Feature >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.10 > > Time Spent: 40m > Remaining Estimate: 0h > > Add last checkpoint duration metrics: > * beforeLockDuration > * listenersExecuteDuration > * lockHoldDuration > * walCpRecordFsyncDuration > * writeCheckpointEntryDuration > * splitAndSortCpPagesDuration > Add durations histograms: > * CheckpointBeforeLockHistogram > * CheckpointLockWaitHistogram > * CheckpointListenersExecuteHistogram > * CheckpointMarkHistogram > * CheckpointLockHoldHistogram > * CheckpointPagesWriteHistogram > * CheckpointFsyncHistogram > * CheckpointWalRecordFsyncHistogram > * CheckpointWriteEntryHistogram > * CheckpointSplitAndSortPagesHistogram > * CheckpointHistogram -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13977) Code enhancement after review of encryption persistent storage
[ https://issues.apache.org/jira/browse/IGNITE-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-13977: - Ignite Flags: (was: Docs Required,Release Notes Required) > Code enhancement after review of encryption persistent storage > -- > > Key: IGNITE-13977 > URL: https://issues.apache.org/jira/browse/IGNITE-13977 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > # There are a lot of difficult code snipped in `GridCacheOffheapManager` > where the type of page choosing. > # CacheGroupReencryptionTest.testPhysicalRecoveryWithUpdates test is flaky, > when checkpoint is triggered before expected. > # Encryption SPI doesn't allow working with several master keys, only that > key which be set as default. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13877) Error restarting the node with switching from disabled WAL archiving to enabled
[
https://issues.apache.org/jira/browse/IGNITE-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-13877:
-
Fix Version/s: 2.11
> Error restarting the node with switching from disabled WAL archiving to
> enabled
> ---
>
> Key: IGNITE-13877
> URL: https://issues.apache.org/jira/browse/IGNITE-13877
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Attachments: Ignite13877Test.java
>
>
> If a user starts a node with WAL archiving disabled, and then poured data
> there and there were more than *DataStorageConfiguration#walSegments* and
> then wants to restart a node with WAL archiving enabled, they will fail due
> to the following error:
> {noformat}
> SEVERE: 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.StorageException: Failed to read
> checkpoint record from WAL, persistence consistency cannot be guaranteed.
> Make sure configuration points to correct WAL folders and WAL folder is
> properly mounted [ptr=FileWALPointer [idx=11, fileOff=15864934, len=21409],
> walPath=db/wal, walArchive=db/wal/archive]]]
> class
> org.apache.ignite.internal.processors.cache.persistence.StorageException:
> Failed to read checkpoint record from WAL, persistence consistency cannot be
> guaranteed. Make sure configuration points to correct WAL folders and WAL
> folder is properly mounted [ptr=FileWALPointer [idx=11, fileOff=15864934,
> len=21409], walPath=db/wal, walArchive=db/wal/archive]
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.performBinaryMemoryRestore(GridCacheDatabaseSharedManager.java:2324)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:799)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:3523)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1206)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2089)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1147)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1065)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:951)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:850)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:720)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:689)
> at org.apache.ignite.Ignition.start(Ignition.java:344)
> {noformat}
> At this point, the user can be offered the following workaround:
> Move all segments to WAL archive directory (include consistentId directory)
> as they are except the last one. Last one rename as index %
> *DataStorageConfiguration#walSegments*.
> Described workaround should be done automatically without user intervention.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14011) Add RAT check, PMD, Idea Inspections, and code style suites for Ignite 3 project
Peter Ivanov created IGNITE-14011: - Summary: Add RAT check, PMD, Idea Inspections, and code style suites for Ignite 3 project Key: IGNITE-14011 URL: https://issues.apache.org/jira/browse/IGNITE-14011 Project: Ignite Issue Type: Task Reporter: Peter Ivanov Assignee: Peter Ivanov We need to copy the following suites to Ignite 3 (public TC). Please create a corresponding ticket in Ignite JIRA if pom.xml modifications are required.https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_LicensesHeaders?mode=builds#all-projectshttps://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_InspectionsCore?mode=builds#all-projects (assuming TC will be able to run inspections check on the new repository)https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle?mode=builds#all-projectshttps://ggtc.gridgain.com/buildConfiguration/Tests_GridGainCeEeUe_Latest_SanityCheck_Pmd?mode=builds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13560) Add cluster node attribute colocated BackupFilter
[
https://issues.apache.org/jira/browse/IGNITE-13560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267149#comment-17267149
]
Ignite TC Bot commented on IGNITE-13560:
{panel:title=Branch: [pull/8668/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8668/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 2{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=5832080]]
* {color:#013220}IgniteCacheTestSuite2:
ClusterNodeAttributeColocatedBackupFilterSelfTest.testBackupFilterWithBaseline
- PASSED{color}
* {color:#013220}IgniteCacheTestSuite2:
ClusterNodeAttributeColocatedBackupFilterSelfTest.testPartitionDistribution -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite2:
ClusterNodeAttributeColocatedBackupFilterSelfTest.testBackupFilterWithNullAttribute
- PASSED{color}
* {color:#013220}IgniteCacheTestSuite2:
ClusterNodeAttributeColocatedBackupFilterSelfTest.testPartitionDistributionWithAffinityBackupFilter
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5828768buildTypeId=IgniteTests24Java8_RunAll]
> Add cluster node attribute colocated BackupFilter
> -
>
> Key: IGNITE-13560
> URL: https://issues.apache.org/jira/browse/IGNITE-13560
> Project: Ignite
> Issue Type: New Feature
>Reporter: Maksim Timonin
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13995) Update EncryptedCacheExample and remove deprecated methods usages
[
https://issues.apache.org/jira/browse/IGNITE-13995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267115#comment-17267115
]
Vyacheslav Koptilin commented on IGNITE-13995:
--
Hello [~maliev],
The patch looks good to me. Merged to the master branch. Thank you for your
efforts!
> Update EncryptedCacheExample and remove deprecated methods usages
> --
>
> Key: IGNITE-13995
> URL: https://issues.apache.org/jira/browse/IGNITE-13995
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Change deprecated {{ignite.cluster().active(true)}} to
> {{ignite.cluster().state(ClusterState.ACTIVE)}} and some refactroing is
> needed for {{EncryptedCacheExample}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13428) Ignite Distributed Environment Tests (IEP-56)
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13428: -- Summary: Ignite Distributed Environment Tests (IEP-56) (was: Ignite Distributed Environment Tests) > Ignite Distributed Environment Tests (IEP-56) > - > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: Epic >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56 > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13428) Ignite Distributed Environment Tests (IEP-56)
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13428: -- Epic Name: IEP-56 > Ignite Distributed Environment Tests (IEP-56) > - > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: Epic >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56 > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13428) Ignite Distributed Environment Tests
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13428: -- Labels: IEP-56 (was: ) > Ignite Distributed Environment Tests > > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: Epic >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56 > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13888) Provide the utility to output performance statistics operations to the console
[ https://issues.apache.org/jira/browse/IGNITE-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita reassigned IGNITE-13888: Assignee: Amelchev Nikita > Provide the utility to output performance statistics operations to the console > -- > > Key: IGNITE-13888 > URL: https://issues.apache.org/jira/browse/IGNITE-13888 > Project: Ignite > Issue Type: Sub-task >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > > Provide the utility to output performance statistics operations to the > console (to integrate with the other cmd tools) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13428) Ignite Distributed Environment Tests
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13428: -- Labels: (was: IEP-56 ducktape) > Ignite Distributed Environment Tests > > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: Epic >Reporter: Maksim Timonin >Priority: Major > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13428) Ignite Distributed Environment Tests
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13428: -- Summary: Ignite Distributed Environment Tests (was: Ignite Distributed Environment Tests [Umbrella]) > Ignite Distributed Environment Tests > > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: Epic >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56, ducktape > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14010) Ignite-extensions: KafkaIgniteSteamerSelfTest is flaky
Mikhail Petrov created IGNITE-14010:
---
Summary: Ignite-extensions: KafkaIgniteSteamerSelfTest is flaky
Key: IGNITE-14010
URL: https://issues.apache.org/jira/browse/IGNITE-14010
Project: Ignite
Issue Type: Bug
Reporter: Mikhail Petrov
Assignee: Mikhail Petrov
KafkaIgniteSteamerSelfTest test is flaky - [TC
build|https://ci.ignite.apache.org/test/4285346063968224069?currentProjectId=IgniteExtensions_Tests=IgniteExtensions_Tests_Build=].
It fails with the following error:
{code:java}
java.lang.AssertionError: Failed to wait latch completion, still wait 100
events at
org.apache.ignite.stream.kafka.KafkaIgniteStreamerSelfTest.consumerStream(KafkaIgniteStreamerSelfTest.java:242)
at
org.apache.ignite.stream.kafka.KafkaIgniteStreamerSelfTest.testKafkaStreamer(KafkaIgniteStreamerSelfTest.java:113)
{code}
This needs to be fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13428) Ignite Distributed Environment Tests [Umbrella]
[ https://issues.apache.org/jira/browse/IGNITE-13428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13428: -- Issue Type: Epic (was: New Feature) > Ignite Distributed Environment Tests [Umbrella] > --- > > Key: IGNITE-13428 > URL: https://issues.apache.org/jira/browse/IGNITE-13428 > Project: Ignite > Issue Type: Epic >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56, ducktape > > Currently Ignite doesn’t have a solution for automated testing in real-world > distributed environment. > This ticket aims to provide such solution. The proposed test framework is > based on [ducktape|https://github.com/confluentinc/ducktape]. Requirements to > integration tests includes: easy start of fair distributed environment > locally, run compatibility tests, provide comparison benchmarks between > different Ignite versions, integration tests with 3rd party services, > parametrize tests and provide clear reports. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14009) Ignite-extensions: PubSubStreamerSelfTest is flaky
[
https://issues.apache.org/jira/browse/IGNITE-14009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-14009:
Description:
PubSubStreamerSelfTest is flaky - [TC
build|https://ci.ignite.apache.org/test/-1227012852016489408?currentProjectId=IgniteExtensions_Tests=IgniteExtensions_Tests_Build=pull%2F34%2F].
It fails with the following error:
{code:java}
java.lang.AssertionError: Failed to wait latch completion, still wait 100 events
at
org.apache.ignite.stream.pubsub.PubSubStreamerSelfTest.consumerStream(PubSubStreamerSelfTest.java:214)
at
org.apache.ignite.stream.pubsub.PubSubStreamerSelfTest.testPubSubStreamer(PubSubStreamerSelfTest.java:138)
{code}
This needs to be fixed.
was:PubSubStreamerSelfTest is flaky - [TC
build|https://ci.ignite.apache.org/test/-1227012852016489408?currentProjectId=IgniteExtensions_Tests=IgniteExtensions_Tests_Build=pull%2F34%2F].
This needs to be fixed.
> Ignite-extensions: PubSubStreamerSelfTest is flaky
> --
>
> Key: IGNITE-14009
> URL: https://issues.apache.org/jira/browse/IGNITE-14009
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
>
> PubSubStreamerSelfTest is flaky - [TC
> build|https://ci.ignite.apache.org/test/-1227012852016489408?currentProjectId=IgniteExtensions_Tests=IgniteExtensions_Tests_Build=pull%2F34%2F].
> It fails with the following error:
> {code:java}
> java.lang.AssertionError: Failed to wait latch completion, still wait 100
> events
> at
> org.apache.ignite.stream.pubsub.PubSubStreamerSelfTest.consumerStream(PubSubStreamerSelfTest.java:214)
> at
> org.apache.ignite.stream.pubsub.PubSubStreamerSelfTest.testPubSubStreamer(PubSubStreamerSelfTest.java:138)
> {code}
>
>
> This needs to be fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14001) Minor code style fixes for configuration and runner modules
[
https://issues.apache.org/jira/browse/IGNITE-14001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semyon Danilov reassigned IGNITE-14001:
---
Assignee: Semyon Danilov
> Minor code style fixes for configuration and runner modules
> ---
>
> Key: IGNITE-14001
> URL: https://issues.apache.org/jira/browse/IGNITE-14001
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Semyon Danilov
>Priority: Major
>
> * Some of the configuration files contain TODOs or FIXMEs without tickets -
> either tickets should be created, or TODOs fixed/removed.
> * {{Selector}}, {{DynamicProperty}}, {{ConfigurationStorage}},
> {{ConfigurationValidationException}}, {{FieldValidator}} contain extra
> spacing before the end of class/at the beginning of the class.
> * Some of the overridden methods do not contain {{@Override}} annotation
> ({{ConfigurationProperty#value}}, anonymous {{PropertyListener}} in
> {{Configurator#onAttached}})
> We will try to figure out automated checks for this in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
