[jira] [Commented] (IGNITE-14398) Document thin client support for spring-data integration.
[ https://issues.apache.org/jira/browse/IGNITE-14398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311132#comment-17311132 ] Mikhail Petrov commented on IGNITE-14398: - [~nsafonov] , Could you please take a look? > Document thin client support for spring-data integration. > - > > Key: IGNITE-14398 > URL: https://issues.apache.org/jira/browse/IGNITE-14398 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > It's needed to document thin client support for spring-data integration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14198) Define interface for meta storage client
[ https://issues.apache.org/jira/browse/IGNITE-14198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311034#comment-17311034 ] Andrey N. Gura commented on IGNITE-14198: - [~Berkov] 2 and 3 question are out of scope. I don't understand 1st question. So could you please start discussion on dev-list instead of JIRA issue? > Define interface for meta storage client > > > Key: IGNITE-14198 > URL: https://issues.apache.org/jira/browse/IGNITE-14198 > Project: Ignite > Issue Type: New Feature >Reporter: Andrey N. Gura >Assignee: Andrey N. Gura >Priority: Major > Labels: iep-61, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 9h 10m > Remaining Estimate: 0h > > Interface for meta storage client should be defined in order to unblock > development and unit-testing. > Interface implementation is not needed on this stage. > We need to crystallize the metastorage interface prototype from the IEP to > understand how it will be integrated with other system components. > Need to cover: > * Asynchrony aspects > * Possible error codes (connection failure -> unknown result vs Raft failure > -> known result, etc) > * Complex multi-updates (aka transactions) > * Watchers. Each node can watch all updates and filter locally or adjust the > watched ranges dynamically (consistency is important here) > These interfaces are considered "client" interfaces as they will be available > on all nodes in the cluster -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14198) Define interface for meta storage client
[
https://issues.apache.org/jira/browse/IGNITE-14198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311035#comment-17311035
]
Andrey N. Gura commented on IGNITE-14198:
-
Merged to {{main}} branch.
> Define interface for meta storage client
>
>
> Key: IGNITE-14198
> URL: https://issues.apache.org/jira/browse/IGNITE-14198
> Project: Ignite
> Issue Type: New Feature
>Reporter: Andrey N. Gura
>Assignee: Andrey N. Gura
>Priority: Major
> Labels: iep-61, ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 9h 10m
> Remaining Estimate: 0h
>
> Interface for meta storage client should be defined in order to unblock
> development and unit-testing.
> Interface implementation is not needed on this stage.
> We need to crystallize the metastorage interface prototype from the IEP to
> understand how it will be integrated with other system components.
> Need to cover:
> * Asynchrony aspects
> * Possible error codes (connection failure -> unknown result vs Raft failure
> -> known result, etc)
> * Complex multi-updates (aka transactions)
> * Watchers. Each node can watch all updates and filter locally or adjust the
> watched ranges dynamically (consistency is important here)
> These interfaces are considered "client" interfaces as they will be available
> on all nodes in the cluster
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13769) Add examples of using thin client with Ignite Spring Data integration.
[ https://issues.apache.org/jira/browse/IGNITE-13769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311023#comment-17311023 ] Amelchev Nikita commented on IGNITE-13769: -- [~PetrovMikhail], thanks for the contribution. Merged to the master. > Add examples of using thin client with Ignite Spring Data integration. > --- > > Key: IGNITE-13769 > URL: https://issues.apache.org/jira/browse/IGNITE-13769 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > > It's needed to add examples of using thin client with the Ignite Spring Data > integration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13769) Add examples of using thin client with Ignite Spring Data integration.
[ https://issues.apache.org/jira/browse/IGNITE-13769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-13769: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Add examples of using thin client with Ignite Spring Data integration. > --- > > Key: IGNITE-13769 > URL: https://issues.apache.org/jira/browse/IGNITE-13769 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > > It's needed to add examples of using thin client with the Ignite Spring Data > integration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14434) Add examples of using thin client with spring-tx-ext
[ https://issues.apache.org/jira/browse/IGNITE-14434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-14434: - Ignite Flags: Release Notes Required (was: Docs Required,Release Notes Required) > Add examples of using thin client with spring-tx-ext > > > Key: IGNITE-14434 > URL: https://issues.apache.org/jira/browse/IGNITE-14434 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Minor > > It's needed to add examples of thin client using with spring-tx-ext > integration. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13405) [Pyignite] Invalid cache configuration parameters
[ https://issues.apache.org/jira/browse/IGNITE-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy reassigned IGNITE-13405: - Assignee: Ivan Daschinskiy > [Pyignite] Invalid cache configuration parameters > - > > Key: IGNITE-13405 > URL: https://issues.apache.org/jira/browse/IGNITE-13405 > Project: Ignite > Issue Type: Bug > Components: python >Reporter: Ivan Smirnov >Assignee: Ivan Daschinskiy >Priority: Blocker > Labels: python > Original Estimate: 1h > Time Spent: 10m > Remaining Estimate: 50m > > Invalid argument for prop_partition_loss_policy in python thin client that > affects the cache creation > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14431) Assertion error in GridDhtAtomicCache.unlockEntries
[
https://issues.apache.org/jira/browse/IGNITE-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310855#comment-17310855
]
Vyacheslav Koptilin commented on IGNITE-14431:
--
Hello [~ascherbakov],
The proposed patch looks good to me.
> Assertion error in GridDhtAtomicCache.unlockEntries
> ---
>
> Key: IGNITE-14431
> URL: https://issues.apache.org/jira/browse/IGNITE-14431
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Fix For: 2.11
>
> Attachments: reproducer.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.onMarkedObsolete(GridDhtCacheEntry.java:169)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(GridCacheMapEntry.java:4671)
> at
> org.apache.ignite.internal.processors.cache.CacheOffheapEvictionManager.touch(CacheOffheapEvictionManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.touch(GridCacheMapEntry.java:5104)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(GridDhtAtomicCache.java:3166)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1990)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.lambda$updateAllAsyncInternal0$4cef81e4$1(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1724)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3295)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:146)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:287)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:282)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1143)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:110)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:309)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:242)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
> at
> org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14076) Quadratic putAll performance degradation in transactional cache
[
https://issues.apache.org/jira/browse/IGNITE-14076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310842#comment-17310842
]
Vyacheslav Koptilin commented on IGNITE-14076:
--
Hello [~zstan]
Well, the proposed patch looks good to me. However, we need to think about a
proper fix for the case of using near caches.
Merged into the master branch. Thank you for your contribution!
> Quadratic putAll performance degradation in transactional cache
> ---
>
> Key: IGNITE-14076
> URL: https://issues.apache.org/jira/browse/IGNITE-14076
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Affects Versions: 2.10
>Reporter: Pavel Tupitsyn
>Assignee: Stanilovsky Evgeny
>Priority: Critical
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{putAll}} execution time grows almost exponentially while the number of keys
> grows linearly in the following test:
> {code:java}
> public class PutAllTxTest extends GridCommonAbstractTest {
> @Test
> public void testPutAll() throws Exception {
> Ignition.start(getConfiguration("server1"));
> Ignition.start(getConfiguration("server2"));
> Ignite ignite =
> Ignition.start(getConfiguration("client").setClientMode(true));
> IgniteCache cache = ignite.createCache(
> new CacheConfiguration("c")
> .setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL));
> int count = 5;
> Map data = new TreeMap<>();
> for (int i = 0; i < count; i++)
> data.put(i, i);
> long begin = System.nanoTime();
> cache.putAll(data);
> long dur = System.nanoTime() - begin;
> System.out.println("> " + dur / 100);
> }
> }
> {code}
> ||Entries||Seconds||
> |1000|0.4|
> |5000|1.9|
> |1|3.8|
> |2|10.7|
> |3|23.5|
> |4|41|
> |5|64|
> |6|90|
> |10|254|
> This does not reproduce with 1 server node, and does not reproduce on
> {{ATOMIC}} caches with any number of nodes.
> *Observations:*
> - Not a GC issue (it barely runs)
> - Not a memory issue (heap is under 1GB)
> - GridDhtTxPrepareFuture#localDhtPendingVersions ->
> GridCacheMapEntry.localCandidates is the bottleneck. For 1K keys,
> localCandidates gets called 123K times, 2K keys - 484K times, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14440) Run external tests in ducktape
[ https://issues.apache.org/jira/browse/IGNITE-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-14440: Sprint: Ducktape Sprint 6 > Run external tests in ducktape > -- > > Key: IGNITE-14440 > URL: https://issues.apache.org/jira/browse/IGNITE-14440 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56 > > Docker with ducktape should have following volumes: > # ignite-dev -> Ignite current branch > # ignite-lib -> python lib + java deps in modules/ducktests/tests/ignitetest > # ignite-tests -> python tests, default - modules/ducktests/ignitetest/tests > # ignite-specs -> specs for tests, structure of directories contain specs > (incl. jinja2 templates) should be redefined. Set default value for new > directory within ignitetest. > # /opt/ignite-* - all distributives. > Mount with python libs (lib, tests, specs) must be installed in docker as > develop lib (see, python setup.py develop). Notes: > # Ordering of installing matters - lib, specs, tests > # ignitetest - Manifest.in should skip directories: ./tests, with specs. > There should be an util that responsible for uploading ignite dists. Note: > # Provide a migration mode for the util. Try copy distributives from > existing docker image to local fs to skip downloading them from Internet. > # Download new versions by running .sh command. > > *Nice to have:* replace runtests.sh and ducker-ignite with: > # docker-compose.yml describes num of containers, mounts, ports, etc. > # entrypoint for docker is a ducktape command. > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14440) Run external tests in ducktape
[ https://issues.apache.org/jira/browse/IGNITE-14440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-14440: Labels: IEP-56 (was: ) > Run external tests in ducktape > -- > > Key: IGNITE-14440 > URL: https://issues.apache.org/jira/browse/IGNITE-14440 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Major > Labels: IEP-56 > > Docker with ducktape should have following volumes: > # ignite-dev -> Ignite current branch > # ignite-lib -> python lib + java deps in modules/ducktests/tests/ignitetest > # ignite-tests -> python tests, default - modules/ducktests/ignitetest/tests > # ignite-specs -> specs for tests, structure of directories contain specs > (incl. jinja2 templates) should be redefined. Set default value for new > directory within ignitetest. > # /opt/ignite-* - all distributives. > Mount with python libs (lib, tests, specs) must be installed in docker as > develop lib (see, python setup.py develop). Notes: > # Ordering of installing matters - lib, specs, tests > # ignitetest - Manifest.in should skip directories: ./tests, with specs. > There should be an util that responsible for uploading ignite dists. Note: > # Provide a migration mode for the util. Try copy distributives from > existing docker image to local fs to skip downloading them from Internet. > # Download new versions by running .sh command. > > *Nice to have:* replace runtests.sh and ducker-ignite with: > # docker-compose.yml describes num of containers, mounts, ports, etc. > # entrypoint for docker is a ducktape command. > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14440) Run external tests in ducktape
Maksim Timonin created IGNITE-14440: --- Summary: Run external tests in ducktape Key: IGNITE-14440 URL: https://issues.apache.org/jira/browse/IGNITE-14440 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin Docker with ducktape should have following volumes: # ignite-dev -> Ignite current branch # ignite-lib -> python lib + java deps in modules/ducktests/tests/ignitetest # ignite-tests -> python tests, default - modules/ducktests/ignitetest/tests # ignite-specs -> specs for tests, structure of directories contain specs (incl. jinja2 templates) should be redefined. Set default value for new directory within ignitetest. # /opt/ignite-* - all distributives. Mount with python libs (lib, tests, specs) must be installed in docker as develop lib (see, python setup.py develop). Notes: # Ordering of installing matters - lib, specs, tests # ignitetest - Manifest.in should skip directories: ./tests, with specs. There should be an util that responsible for uploading ignite dists. Note: # Provide a migration mode for the util. Try copy distributives from existing docker image to local fs to skip downloading them from Internet. # Download new versions by running .sh command. *Nice to have:* replace runtests.sh and ducker-ignite with: # docker-compose.yml describes num of containers, mounts, ports, etc. # entrypoint for docker is a ducktape command. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14431) Assertion error in GridDhtAtomicCache.unlockEntries
[
https://issues.apache.org/jira/browse/IGNITE-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310767#comment-17310767
]
Alexey Scherbakov edited comment on IGNITE-14431 at 3/29/21, 4:26 PM:
--
List of changes:
* Removed useless validation on DHT primary node.
* Fixed NPE in exchange future.
* Reverted the change causing performance drop for SQL.
* Fixed a bug when lost partitions are not detected on client cache start.
[~sk0x50] Can you take a look ?
was (Author: ascherbakov):
List of changes:
* Removed useless validation on DHT primary node.
* Fixed NPE in exchange future.
* Reverted the change causing performance drop for SQL.
* Fixed a bug when lost partition are not detected on client cache start.
[~sk0x50] Can you take a look ?
> Assertion error in GridDhtAtomicCache.unlockEntries
> ---
>
> Key: IGNITE-14431
> URL: https://issues.apache.org/jira/browse/IGNITE-14431
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Fix For: 2.11
>
> Attachments: reproducer.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.onMarkedObsolete(GridDhtCacheEntry.java:169)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(GridCacheMapEntry.java:4671)
> at
> org.apache.ignite.internal.processors.cache.CacheOffheapEvictionManager.touch(CacheOffheapEvictionManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.touch(GridCacheMapEntry.java:5104)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(GridDhtAtomicCache.java:3166)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1990)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.lambda$updateAllAsyncInternal0$4cef81e4$1(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1724)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3295)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:146)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:287)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:282)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1143)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:110)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:309)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:242)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
> at
> org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
> at
>
[jira] [Commented] (IGNITE-14431) Assertion error in GridDhtAtomicCache.unlockEntries
[
https://issues.apache.org/jira/browse/IGNITE-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310767#comment-17310767
]
Alexey Scherbakov commented on IGNITE-14431:
List of changes:
* Removed useless validation on DHT primary node.
* Fixed NPE in exchange future.
* Reverted the change causing performance drop for SQL.
* Fixed a bug when lost partition are not detected on client cache start.
[~sk0x50] Can you take a look ?
> Assertion error in GridDhtAtomicCache.unlockEntries
> ---
>
> Key: IGNITE-14431
> URL: https://issues.apache.org/jira/browse/IGNITE-14431
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Fix For: 2.11
>
> Attachments: reproducer.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.onMarkedObsolete(GridDhtCacheEntry.java:169)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(GridCacheMapEntry.java:4671)
> at
> org.apache.ignite.internal.processors.cache.CacheOffheapEvictionManager.touch(CacheOffheapEvictionManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.touch(GridCacheMapEntry.java:5104)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(GridDhtAtomicCache.java:3166)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1990)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.lambda$updateAllAsyncInternal0$4cef81e4$1(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1724)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3295)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:146)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:287)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:282)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1143)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:110)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:309)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:242)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
> at
> org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14431) Assertion error in GridDhtAtomicCache.unlockEntries
[
https://issues.apache.org/jira/browse/IGNITE-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310759#comment-17310759
]
Ignite TC Bot commented on IGNITE-14431:
{panel:title=Branch: [pull/8939/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8939/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5936522buildTypeId=IgniteTests24Java8_RunAll]
> Assertion error in GridDhtAtomicCache.unlockEntries
> ---
>
> Key: IGNITE-14431
> URL: https://issues.apache.org/jira/browse/IGNITE-14431
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Alexey Scherbakov
>Assignee: Alexey Scherbakov
>Priority: Major
> Fix For: 2.11
>
> Attachments: reproducer.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.onMarkedObsolete(GridDhtCacheEntry.java:169)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.evictInternal(GridCacheMapEntry.java:4671)
> at
> org.apache.ignite.internal.processors.cache.CacheOffheapEvictionManager.touch(CacheOffheapEvictionManager.java:45)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.touch(GridCacheMapEntry.java:5104)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.unlockEntries(GridDhtAtomicCache.java:3166)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1990)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.lambda$updateAllAsyncInternal0$4cef81e4$1(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:354)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1906)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1724)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processNearAtomicUpdateRequest(GridDhtAtomicCache.java:3295)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$400(GridDhtAtomicCache.java:146)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:287)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$5.apply(GridDhtAtomicCache.java:282)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1143)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:592)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:110)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:309)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1908)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:242)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1422)
> at
> org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:569)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14439) NPE when accessing clustername before first exchange finished
Pavel Vinokurov created IGNITE-14439: Summary: NPE when accessing clustername before first exchange finished Key: IGNITE-14439 URL: https://issues.apache.org/jira/browse/IGNITE-14439 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.9 Reporter: Pavel Vinokurov [IGNITE-11406|https://issues.apache.org/jira/browse/IGNITE-11406] has not been fixed properly for two reasons. The first is one is that _GridCacheProcessor.utilityCache_ could be accessed before the first exchange finished. The second is that it doesn't resolve the original issue, because _GridServiceProcessor.onKernelStop_ is followed by _GridCacheProcessor.onKernelStop_, so caches should be already initialized. Thus that fix should be reverted. Revering this fix induces the issue related to accessing the utility cache by getting cluster name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14379) Fix vulnerability of commons-codec <1.13
[ https://issues.apache.org/jira/browse/IGNITE-14379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310725#comment-17310725 ] Anton Kurbanov commented on IGNITE-14379: - LGTM, proceed with merge. > Fix vulnerability of commons-codec <1.13 > > > Key: IGNITE-14379 > URL: https://issues.apache.org/jira/browse/IGNITE-14379 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > https://www.whitesourcesoftware.com/vulnerability-database/WS-2019-0379 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310694#comment-17310694 ] Ilya Kasnacheev commented on IGNITE-14346: -- It is also possible that IP finder is waiting silently after this happens. Either way, I don't see how to go forward from here. > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Labels: ReviewNeeded > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[
https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310691#comment-17310691
]
Ilya Kasnacheev commented on IGNITE-14346:
--
Azure also seems to interfere with slf4j settings in some way that I can no
longer see anything printed to logs after azure discovery starts
The last that I see is
{code}
[14:19:06,989][INFO][main][GridTcpRestProtocol] Command protocol successfully
started [name=TCP binary, host=0.0.0.0/0.0.0.0, port=11211]
[14:19:07,250][INFO][main][GridJettyRestProtocol] Command protocol successfully
started [name=Jetty REST, host=/0.0.0.0, port=8080]
[14:19:07,314][INFO][main][IgniteKernal] Non-loopback local IPs: 10.1.1.4,
fe80:0:0:0:222:48ff:fe1f:b80f%eth0
[14:19:07,314][INFO][main][IgniteKernal] Enabled local MACs: 0022481FB80F
[14:19:07,322][INFO][main][ClusterProcessor] Cluster ID and tag has been read
from metastorage: null
[14:19:07,327][INFO][main][IgniteClusterImpl] Shutdown policy was updated
[oldVal=null, newVal=null]
log4j:WARN No appenders could be found for logger
(io.netty.util.internal.logging.InternalLoggerFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{code}
> Implement Azure Blob Storage Based IP Finder
>
>
> Key: IGNITE-14346
> URL: https://issues.apache.org/jira/browse/IGNITE-14346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Atri Sharma
>Assignee: Atri Sharma
>Priority: Major
> Labels: ReviewNeeded
> Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot
> 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png,
> Screenshot 2021-03-23 at 8.45.05 PM.png
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14347) Fix Node failure on Receiving Data of Unknown class via Distributed Metastorage
[
https://issues.apache.org/jira/browse/IGNITE-14347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semyon Danilov updated IGNITE-14347:
Description:
When a node sees an object of a class that is missing on this node's classpath,
it fails with the following exception:
{noformat}
[16:46:47,134][SEVERE][disco-notifier-worker-#41][] 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.IgniteCheckedException: Failed to find class with given class loader for
unmarshalling (make sure same versions of all classes are available on all
nodes or enable peer-class-loading)
[clsLdr=sun.misc.Launcher$AppClassLoader@764c12b6,
cls=example.ClientNode$BamboozleClass]]]
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading)
[clsLdr=sun.misc.Launcher$AppClassLoader@764c12b6,
cls=example.ClientNode$BamboozleClass]
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:128)
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:138)
at
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:80)
at
org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageUtil.unmarshal(DistributedMetaStorageUtil.java:61)
at
org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl.completeWrite(DistributedMetaStorageImpl.java:1161)
at
org.apache.ignite.internal.processors.metastorage.persistence.DistributedMetaStorageImpl.onUpdateMessage(DistributedMetaStorageImpl.java:1089)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:650)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:521)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2718)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2756)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: example.ClientNode$BamboozleClass
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9061)
at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:58)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1925)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1808)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2099)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1625)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:465)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:423)
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:123)
... 11 more{noformat}
The result is that one node can write an object of some custom class to the
metastorage and make all other nodes fail.
The following reproducer can be used:
{code:java}
public class ClientNode {
public static void main(String[] args) throws IgniteCheckedException {
IgniteConfiguration igniteCfg = nodeConfiguration().setClientMode(true);
IgniteKernal ignite = (IgniteKernal) Ignition.start(igniteCfg);
DistributedMetaStorage metaStorage =
ignite.context().distributedMetastorage();
metaStorage.write("hey", new BamboozleClass());
}
private static IgniteConfiguration nodeConfiguration() {
IgniteConfiguration igniteCfg = new IgniteConfiguration();
TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();
discoverySpi.setIpFinder(new TcpDiscoveryVmIpFinder()
.setAddresses(Collections.singleton("127.0.0.1:47500..47600")));
[jira] [Commented] (IGNITE-14347) Fix Node failure on Receiving Data of Unknown class via Distributed Metastorage
[ https://issues.apache.org/jira/browse/IGNITE-14347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310685#comment-17310685 ] Semyon Danilov commented on IGNITE-14347: - LGTM > Fix Node failure on Receiving Data of Unknown class via Distributed > Metastorage > --- > > Key: IGNITE-14347 > URL: https://issues.apache.org/jira/browse/IGNITE-14347 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14436) Scala documentation
[ https://issues.apache.org/jira/browse/IGNITE-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl resolved IGNITE-14436. - Resolution: Fixed > Scala documentation > --- > > Key: IGNITE-14436 > URL: https://issues.apache.org/jira/browse/IGNITE-14436 > Project: Ignite > Issue Type: Bug > Components: website >Affects Versions: 2.9.1 > Environment: Browser used : Brave (Chromium) >Reporter: Thibaud Faurie >Assignee: Mauricio Stekl >Priority: Major > > Scala documentation on website is broken. > When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a > ERR_TOO_MANY_REDIRECTS error. > Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14436) Scala documentation
[ https://issues.apache.org/jira/browse/IGNITE-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310680#comment-17310680 ] Mauricio Stekl commented on IGNITE-14436: - Hi, I renamed the dir scaladocs/ to scaladoc/ since that's the name we had used in the past and we also have lots of incoming links to that dir. > Scala documentation > --- > > Key: IGNITE-14436 > URL: https://issues.apache.org/jira/browse/IGNITE-14436 > Project: Ignite > Issue Type: Bug > Components: website >Affects Versions: 2.9.1 > Environment: Browser used : Brave (Chromium) >Reporter: Thibaud Faurie >Assignee: Mauricio Stekl >Priority: Major > > Scala documentation on website is broken. > When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a > ERR_TOO_MANY_REDIRECTS error. > Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[
https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310678#comment-17310678
]
Ilya Kasnacheev commented on IGNITE-14346:
--
[~atri] I have added some more comments.
I can also see this problem:
{code}
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name
'org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryAzureBlobStoreIpFinder#70be0a2b'
defined in URL
[file:/home/gg_rw_user/apache-ignite-2.11.0-SNAPSHOT-bin/config/default-config.xml]:
Instantiation of bean failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryAzureBlobStoreIpFinder]:
No default constructor found; nested exception is
java.lang.NoClassDefFoundError: com/azure/core/exception/HttpResponseException
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1158)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1102)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481)
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:299)
... 28 more
Caused by: org.springframework.beans.BeanInstantiationException: Failed to
instantiate
[org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryAzureBlobStoreIpFinder]:
No default constructor found; nested exception is
java.lang.NoClassDefFoundError: com/azure/core/exception/HttpResponseException
at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:85)
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1150)
... 32 more
Caused by: java.lang.NoClassDefFoundError:
com/azure/core/exception/HttpResponseException
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:800)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:698)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:621)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:579)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at
java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3137)
at java.base/java.lang.Class.getConstructor0(Class.java:3342)
at java.base/java.lang.Class.getDeclaredConstructor(Class.java:2553)
at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:80)
... 33 more
Caused by: java.lang.ClassNotFoundException:
com.azure.core.exception.HttpResponseException
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
... 47 more
{code}
When Apache Ignite releases are built, dependencies are not resolved in
transient manner. All dependencies need to be listed explicitly in module's
pom.xml. Please collect and add them.
> Implement Azure Blob Storage Based IP Finder
>
>
> Key: IGNITE-14346
> URL: https://issues.apache.org/jira/browse/IGNITE-14346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Atri Sharma
>Assignee: Atri Sharma
>Priority: Major
> Labels: ReviewNeeded
> Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot
> 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png,
> Screenshot 2021-03-23 at 8.45.05 PM.png
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
--
This message was sent by
[jira] [Assigned] (IGNITE-14436) Scala documentation
[ https://issues.apache.org/jira/browse/IGNITE-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauricio Stekl reassigned IGNITE-14436: --- Assignee: Mauricio Stekl > Scala documentation > --- > > Key: IGNITE-14436 > URL: https://issues.apache.org/jira/browse/IGNITE-14436 > Project: Ignite > Issue Type: Bug > Components: website >Affects Versions: 2.9.1 > Environment: Browser used : Brave (Chromium) >Reporter: Thibaud Faurie >Assignee: Mauricio Stekl >Priority: Major > > Scala documentation on website is broken. > When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a > ERR_TOO_MANY_REDIRECTS error. > Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14347) Fix Node failure on Receiving Data of Unknown class via Distributed Metastorage
[
https://issues.apache.org/jira/browse/IGNITE-14347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310674#comment-17310674
]
Ignite TC Bot commented on IGNITE-14347:
{panel:title=Branch: [pull/8898/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache (Expiry Policy){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5922642]]
* IgniteCacheExpiryPolicyTestSuite:
GridCacheTtlManagerNotificationTest.testThatNotificationWorkAsExpectedInMultithreadedMode
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
{panel:title=Branch: [pull/8898/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5930711]]
* {color:#013220}IgniteBasicTestSuite:
DistributedMetaStorageClassloadingTest.testFailListeningForDataOfUnknownClass -
PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
DistributedMetaStorageClassloadingTest.testWontFailReceivingDataOfUnknownClass
- PASSED{color}
* {color:#013220}IgniteBasicTestSuite:
DistributedMetaStorageClassloadingTest.testWontFailReadingDataOfUnknownClass -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5922698buildTypeId=IgniteTests24Java8_RunAll]
> Fix Node failure on Receiving Data of Unknown class via Distributed
> Metastorage
> ---
>
> Key: IGNITE-14347
> URL: https://issues.apache.org/jira/browse/IGNITE-14347
> Project: Ignite
> Issue Type: Improvement
>Reporter: Atri Sharma
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14425) Hang transactions in FINISH [COMMIT] phase when сommunication spi is blocked
[
https://issues.apache.org/jira/browse/IGNITE-14425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310659#comment-17310659
]
Denis Chudov edited comment on IGNITE-14425 at 3/29/21, 1:43 PM:
-
[~slava.koptilin] could you pls review this fix?
was (Author: denis chudov):
[~sk0x50] could you pls review this fix?
> Hang transactions in FINISH [COMMIT] phase when сommunication spi is blocked
>
>
> Key: IGNITE-14425
> URL: https://issues.apache.org/jira/browse/IGNITE-14425
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> scenario:
> From a client for two concurrent transactions on a single key.
> At the same time, the GridNearTxFinishRequest message is blocked from the
> client, a partial network failure is emulated, as a result, one of the
> transactions is not completed even if the node is no longer working
> Reproducer:
> (insert this test into *TxRollbackOnTimeoutTest*)
> {code:java}
> /**
> *
> */
> @Test
> public void testRollbackOnNearNodeLeft() throws Exception {
> Ignite client = startClient();
> Integer pk = primaryKey(grid(0).cache(CACHE_NAME));
> CountDownLatch locked = new CountDownLatch(1);
> CountDownLatch blocked = new CountDownLatch(1);
> IgniteInternalFuture fut = runAsync(new Callable() {
> @Override public Void call() throws Exception {
> try (Transaction tx0 = client.transactions().txStart()) {
> client.cache(CACHE_NAME).put(pk, 0);
> locked.countDown();
> U.awaitQuiet(blocked);
> tx0.commit();
> }
> catch (Exception e) {
> // Ignored.
> }
> return null;
> }
> });
> IgniteInternalFuture fut2 = runAsync(new Runnable() {
> @Override public void run() {
> try (Transaction tx1 =
> client.transactions().txStart(PESSIMISTIC, REPEATABLE_READ, 1000, 0)) {
> U.awaitQuiet(locked);
>
> TestRecordingCommunicationSpi.spi(client).blockMessages(new
> IgniteBiPredicate() {
> @Override public boolean apply(ClusterNode
> clusterNode, Message msg) {
> return msg instanceof GridNearTxFinishRequest;
> }
> });
>
> TestRecordingCommunicationSpi.spi(grid(0)).blockMessages(new
> IgniteBiPredicate() {
> @Override public boolean apply(ClusterNode
> clusterNode, Message msg) {
> return msg instanceof GridNearLockResponse;
> }
> });
> client.cache(CACHE_NAME).put(pk, 1);
> fail();
> }
> catch (Exception e) {
> assertTrue(X.hasCause(e,
> TransactionTimeoutException.class));
> }
> }
> });
> TestRecordingCommunicationSpi.spi(client).waitForBlocked();
> TestRecordingCommunicationSpi.spi(grid(0)).waitForBlocked();
> fut2.get();
> client.close();
> TestRecordingCommunicationSpi.spi(grid(0)).stopBlock();
> blocked.countDown();
> fut.get();
>
> assertTrue(grid(0).context().cache().context().tm().activeTransactions().isEmpty());
> }
> {code}
> As the result, transaction hangs on server node in MARKED_ROLLBACK state
> forever.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310660#comment-17310660
]
Denis Chudov edited comment on IGNITE-14423 at 3/29/21, 1:43 PM:
-
[~slava.koptilin] could you pls review my fix?
was (Author: denis chudov):
[~sk0x50] could you pls review my fix?
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
>
[jira] [Updated] (IGNITE-14425) Hang transactions in FINISH [COMMIT] phase when сommunication spi is blocked
[
https://issues.apache.org/jira/browse/IGNITE-14425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-14425:
--
Reviewer: Vyacheslav Koptilin (was: Slava Koptilin)
> Hang transactions in FINISH [COMMIT] phase when сommunication spi is blocked
>
>
> Key: IGNITE-14425
> URL: https://issues.apache.org/jira/browse/IGNITE-14425
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> scenario:
> From a client for two concurrent transactions on a single key.
> At the same time, the GridNearTxFinishRequest message is blocked from the
> client, a partial network failure is emulated, as a result, one of the
> transactions is not completed even if the node is no longer working
> Reproducer:
> (insert this test into *TxRollbackOnTimeoutTest*)
> {code:java}
> /**
> *
> */
> @Test
> public void testRollbackOnNearNodeLeft() throws Exception {
> Ignite client = startClient();
> Integer pk = primaryKey(grid(0).cache(CACHE_NAME));
> CountDownLatch locked = new CountDownLatch(1);
> CountDownLatch blocked = new CountDownLatch(1);
> IgniteInternalFuture fut = runAsync(new Callable() {
> @Override public Void call() throws Exception {
> try (Transaction tx0 = client.transactions().txStart()) {
> client.cache(CACHE_NAME).put(pk, 0);
> locked.countDown();
> U.awaitQuiet(blocked);
> tx0.commit();
> }
> catch (Exception e) {
> // Ignored.
> }
> return null;
> }
> });
> IgniteInternalFuture fut2 = runAsync(new Runnable() {
> @Override public void run() {
> try (Transaction tx1 =
> client.transactions().txStart(PESSIMISTIC, REPEATABLE_READ, 1000, 0)) {
> U.awaitQuiet(locked);
>
> TestRecordingCommunicationSpi.spi(client).blockMessages(new
> IgniteBiPredicate() {
> @Override public boolean apply(ClusterNode
> clusterNode, Message msg) {
> return msg instanceof GridNearTxFinishRequest;
> }
> });
>
> TestRecordingCommunicationSpi.spi(grid(0)).blockMessages(new
> IgniteBiPredicate() {
> @Override public boolean apply(ClusterNode
> clusterNode, Message msg) {
> return msg instanceof GridNearLockResponse;
> }
> });
> client.cache(CACHE_NAME).put(pk, 1);
> fail();
> }
> catch (Exception e) {
> assertTrue(X.hasCause(e,
> TransactionTimeoutException.class));
> }
> }
> });
> TestRecordingCommunicationSpi.spi(client).waitForBlocked();
> TestRecordingCommunicationSpi.spi(grid(0)).waitForBlocked();
> fut2.get();
> client.close();
> TestRecordingCommunicationSpi.spi(grid(0)).stopBlock();
> blocked.countDown();
> fut.get();
>
> assertTrue(grid(0).context().cache().context().tm().activeTransactions().isEmpty());
> }
> {code}
> As the result, transaction hangs on server node in MARKED_ROLLBACK state
> forever.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Chudov updated IGNITE-14423:
--
Reviewer: Vyacheslav Koptilin (was: Slava Koptilin)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Updated] (IGNITE-14375) Pending discovery messages can be erroneously send.
[ https://issues.apache.org/jira/browse/IGNITE-14375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-14375: Summary: Pending discovery messages can be erroneously send. (was: Pending cache destroy messages can be erroneously send.) > Pending discovery messages can be erroneously send. > --- > > Key: IGNITE-14375 > URL: https://issues.apache.org/jira/browse/IGNITE-14375 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.10 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Due to pending messages logic implementation its possible to process already > outdated _DynamicCacheChangeBatch_ message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14425) Hang transactions in FINISH [COMMIT] phase when сommunication spi is blocked
[
https://issues.apache.org/jira/browse/IGNITE-14425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310648#comment-17310648
]
Ignite TC Bot commented on IGNITE-14425:
{panel:title=Branch: [pull/8936/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8936/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 6{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5936189]]
* {color:#013220}IgniteCacheTestSuite6:
TxRollbackOnTimeoutNoDeadlockDetectionTest.testRollbackOnNearNodeLeft -
PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
TxRollbackOnTimeoutNearCacheTest.testRollbackOnNearNodeLeft - PASSED{color}
* {color:#013220}IgniteCacheTestSuite6:
TxRollbackOnTimeoutTest.testRollbackOnNearNodeLeft - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5936230buildTypeId=IgniteTests24Java8_RunAll]
> Hang transactions in FINISH [COMMIT] phase when сommunication spi is blocked
>
>
> Key: IGNITE-14425
> URL: https://issues.apache.org/jira/browse/IGNITE-14425
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> scenario:
> From a client for two concurrent transactions on a single key.
> At the same time, the GridNearTxFinishRequest message is blocked from the
> client, a partial network failure is emulated, as a result, one of the
> transactions is not completed even if the node is no longer working
> Reproducer:
> (insert this test into *TxRollbackOnTimeoutTest*)
> {code:java}
> /**
> *
> */
> @Test
> public void testRollbackOnNearNodeLeft() throws Exception {
> Ignite client = startClient();
> Integer pk = primaryKey(grid(0).cache(CACHE_NAME));
> CountDownLatch locked = new CountDownLatch(1);
> CountDownLatch blocked = new CountDownLatch(1);
> IgniteInternalFuture fut = runAsync(new Callable() {
> @Override public Void call() throws Exception {
> try (Transaction tx0 = client.transactions().txStart()) {
> client.cache(CACHE_NAME).put(pk, 0);
> locked.countDown();
> U.awaitQuiet(blocked);
> tx0.commit();
> }
> catch (Exception e) {
> // Ignored.
> }
> return null;
> }
> });
> IgniteInternalFuture fut2 = runAsync(new Runnable() {
> @Override public void run() {
> try (Transaction tx1 =
> client.transactions().txStart(PESSIMISTIC, REPEATABLE_READ, 1000, 0)) {
> U.awaitQuiet(locked);
>
> TestRecordingCommunicationSpi.spi(client).blockMessages(new
> IgniteBiPredicate() {
> @Override public boolean apply(ClusterNode
> clusterNode, Message msg) {
> return msg instanceof GridNearTxFinishRequest;
> }
> });
>
> TestRecordingCommunicationSpi.spi(grid(0)).blockMessages(new
> IgniteBiPredicate() {
> @Override public boolean apply(ClusterNode
> clusterNode, Message msg) {
> return msg instanceof GridNearLockResponse;
> }
> });
> client.cache(CACHE_NAME).put(pk, 1);
> fail();
> }
> catch (Exception e) {
> assertTrue(X.hasCause(e,
> TransactionTimeoutException.class));
> }
> }
> });
> TestRecordingCommunicationSpi.spi(client).waitForBlocked();
> TestRecordingCommunicationSpi.spi(grid(0)).waitForBlocked();
> fut2.get();
> client.close();
> TestRecordingCommunicationSpi.spi(grid(0)).stopBlock();
> blocked.countDown();
> fut.get();
>
> assertTrue(grid(0).context().cache().context().tm().activeTransactions().isEmpty());
> }
> {code}
> As the result, transaction hangs on server node in MARKED_ROLLBACK state
> forever.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14438) Add README.md files to cli and cli-common modules
Kirill Gusakov created IGNITE-14438: --- Summary: Add README.md files to cli and cli-common modules Key: IGNITE-14438 URL: https://issues.apache.org/jira/browse/IGNITE-14438 Project: Ignite Issue Type: Task Reporter: Kirill Gusakov Assignee: Kirill Gusakov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14333) Services should be stopped only once
[
https://issues.apache.org/jira/browse/IGNITE-14333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310627#comment-17310627
]
Anton Vinogradov commented on IGNITE-14333:
---
Merged into ignite-ducktape.
> Services should be stopped only once
>
>
> Key: IGNITE-14333
> URL: https://issues.apache.org/jira/browse/IGNITE-14333
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, Zookeeper service may hang because {{kill -9}} may follow {{kill
> -15}} on the tear down.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14436) Scala documentation
[ https://issues.apache.org/jira/browse/IGNITE-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310620#comment-17310620 ] Vyacheslav Koptilin commented on IGNITE-14436: -- Hello [~TurboGofre], Could you please check the following link https://ignite.apache.org/releases/latest/scaladocs ? > Scala documentation > --- > > Key: IGNITE-14436 > URL: https://issues.apache.org/jira/browse/IGNITE-14436 > Project: Ignite > Issue Type: Bug > Components: website >Affects Versions: 2.9.1 > Environment: Browser used : Brave (Chromium) >Reporter: Thibaud Faurie >Priority: Major > > Scala documentation on website is broken. > When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a > ERR_TOO_MANY_REDIRECTS error. > Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14437) Adjust test params: exclude input net failures with disabled connRecovery
[ https://issues.apache.org/jira/browse/IGNITE-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-14437: -- Description: INPUT network failures are incosistent with disabled connection recovery in the ducktests. Alive node can be thrown out the ring. > Adjust test params: exclude input net failures with disabled connRecovery > - > > Key: IGNITE-14437 > URL: https://issues.apache.org/jira/browse/IGNITE-14437 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > INPUT network failures are incosistent with disabled connection recovery in > the ducktests. Alive node can be thrown out the ring. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-14437) Adjust test params: exclude input net failures with disabled connRecovery
[ https://issues.apache.org/jira/browse/IGNITE-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-14437: -- Comment: was deleted (was: INPUT network failures are incosistent with disabled connection recovery in the ducktests. Alive node can be thrown out the ring.) > Adjust test params: exclude input net failures with disabled connRecovery > - > > Key: IGNITE-14437 > URL: https://issues.apache.org/jira/browse/IGNITE-14437 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > > INPUT network failures are incosistent with disabled connection recovery in > the ducktests. Alive node can be thrown out the ring. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14437) Adjust test params: exclude input net failures with disabled connRecovery
[ https://issues.apache.org/jira/browse/IGNITE-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310607#comment-17310607 ] Vladimir Steshin commented on IGNITE-14437: --- INPUT network failures are incosistent with disabled connection recovery in the ducktests. Alive node can be thrown out the ring. > Adjust test params: exclude input net failures with disabled connRecovery > - > > Key: IGNITE-14437 > URL: https://issues.apache.org/jira/browse/IGNITE-14437 > Project: Ignite > Issue Type: Sub-task >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14437) Adjust test params: exclude input net failures with disabled connRecovery
Vladimir Steshin created IGNITE-14437: - Summary: Adjust test params: exclude input net failures with disabled connRecovery Key: IGNITE-14437 URL: https://issues.apache.org/jira/browse/IGNITE-14437 Project: Ignite Issue Type: Sub-task Reporter: Vladimir Steshin Assignee: Vladimir Steshin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310601#comment-17310601
]
Ignite TC Bot commented on IGNITE-14423:
{panel:title=Branch: [pull/8935/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8935/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5935984]]
* {color:#013220}IgniteCacheTestSuite7:
TxRecoveryWithConcurrentRollbackTest.testTxDoesntBecomePreparedAfterError -
PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5936024buildTypeId=IgniteTests24Java8_RunAll]
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction
[jira] [Comment Edited] (IGNITE-14422) Version management for ducktape.
[
https://issues.apache.org/jira/browse/IGNITE-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310569#comment-17310569
]
Anton Vinogradov edited comment on IGNITE-14422 at 3/29/21, 11:07 AM:
--
Merged into ignite-ducktape.
Thanks for your contribution!
was (Author: av):
Merged into ducktape.
Thanks for your contribution!
> Version management for ducktape.
>
>
> Key: IGNITE-14422
> URL: https://issues.apache.org/jira/browse/IGNITE-14422
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Daschinskiy
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: IEP-56
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I propose following:
> 1. Add to {{update-versions}} task a sub-task, that bumps versions in
> {{ignitetests.__init__.py}} (i.e. {{2.11-SNAPSHOT}} to {{2.11-dev}})
> 2. Change {{ignitetests.versions.DEV}} to
> {{IgniteVersion(ignitetests.__version__)}}
> This automatically set {{DEV}} as latest version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14422) Version management for ducktape.
[
https://issues.apache.org/jira/browse/IGNITE-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310569#comment-17310569
]
Anton Vinogradov commented on IGNITE-14422:
---
Merged into ducktape.
Thanks for your contribution!
> Version management for ducktape.
>
>
> Key: IGNITE-14422
> URL: https://issues.apache.org/jira/browse/IGNITE-14422
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Daschinskiy
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: IEP-56
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I propose following:
> 1. Add to {{update-versions}} task a sub-task, that bumps versions in
> {{ignitetests.__init__.py}} (i.e. {{2.11-SNAPSHOT}} to {{2.11-dev}})
> 2. Change {{ignitetests.versions.DEV}} to
> {{IgniteVersion(ignitetests.__version__)}}
> This automatically set {{DEV}} as latest version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14429) Python thin client cache.get_size works not as expected and PeekModes are incorrect.
[ https://issues.apache.org/jira/browse/IGNITE-14429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310561#comment-17310561 ] Ivan Daschinskiy commented on IGNITE-14429: --- [~isapego] Hi, patch is ready for review > Python thin client cache.get_size works not as expected and PeekModes are > incorrect. > > > Key: IGNITE-14429 > URL: https://issues.apache.org/jira/browse/IGNITE-14429 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: python-0.4.0 > > > 1. PeekModes is now ByteArray, so class variables should be changed. > Currently these values are incorrect, seems like masks. They should be > changed to ordinal values in order to resemble java enum. > 2. By default, peek_modes in get_size should be None, not 0 > * If pass 0, behaviour is not if we use PeekModes.ALL, but PeekModes.PRIMARY -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14429) Python thin client cache.get_size works not as expected and PeekModes are incorrect.
[ https://issues.apache.org/jira/browse/IGNITE-14429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy updated IGNITE-14429: -- Fix Version/s: python-0.4.0 > Python thin client cache.get_size works not as expected and PeekModes are > incorrect. > > > Key: IGNITE-14429 > URL: https://issues.apache.org/jira/browse/IGNITE-14429 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: python-0.4.0 > > > 1. PeekModes is now ByteArray, so class variables should be changed. > Currently these values are incorrect, seems like masks. They should be > changed to ordinal values in order to resemble java enum. > 2. By default, peek_modes in get_size should be None, not 0 > * If pass 0, behaviour is not if we use PeekModes.ALL, but PeekModes.PRIMARY -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14436) Scala documentation
Thibaud Faurie created IGNITE-14436: --- Summary: Scala documentation Key: IGNITE-14436 URL: https://issues.apache.org/jira/browse/IGNITE-14436 Project: Ignite Issue Type: Bug Components: website Affects Versions: 2.9.1 Environment: Browser used : Brave (Chromium) Reporter: Thibaud Faurie Scala documentation on website is broken. When I go to [https://ignite.apache.org/releases/latest/scaladoc/] I get a ERR_TOO_MANY_REDIRECTS error. Thus can't access the doc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14429) Python thin client cache.get_size works not as expected and PeekModes are incorrect.
[ https://issues.apache.org/jira/browse/IGNITE-14429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy reassigned IGNITE-14429: - Assignee: Ivan Daschinskiy > Python thin client cache.get_size works not as expected and PeekModes are > incorrect. > > > Key: IGNITE-14429 > URL: https://issues.apache.org/jira/browse/IGNITE-14429 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > > 1. PeekModes is now ByteArray, so class variables should be changed. > Currently these values are incorrect, seems like masks. They should be > changed to ordinal values in order to resemble java enum. > 2. By default, peek_modes in get_size should be None, not 0 > * If pass 0, behaviour is not if we use PeekModes.ALL, but PeekModes.PRIMARY -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14301) Authentication processor can hang all user management operation after server node reconnect
[ https://issues.apache.org/jira/browse/IGNITE-14301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-14301: Description: First for all look at the test - AuthenticationProcessorNodeRestartTest#testConcurrentAddUpdateRemoveNodeRestartServer which is flaky - [TC history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8873434544416175780=testDetails] The first problem with this test is that user management operations(add/update/remove) create too many discovery messages. So discovery custom message history size is not enough to properly skip duplicated custom messages that can be sent across the ring during server node reconnect. It leads to mentioned test failures due to duplication of user management operations (see GridDiscoveryManager#discoCacheHist, IGNITE_DISCOVERY_HISTORY_SIZE system property, and ServerImpl.RingMessageWorker#sendMessageAcrossRing). If the discovery history size will be increased significantly, the test stops failing and starts hanging. The steps that lead to this: 1. Client node sent UserProposedMessage across the ring while one node is offline due to reconnect. 2. Alive server nodes update their local user lists and finish the operation. 3. Reconnected node joins the ring and receives an updated user list from the coordinator. 4. Reconnected node receives duplicated UserProposedMessage that has been already handled by all nodes, handles it, and sents UserManagementOperationFinishedMessage to the coordinator and start to wait for the UserAcceptedMessage from it. But the coordinator has already finished this operation. So the thread that responsible for user management operation on the reconnected node becomes blocked (see IgniteAuthenticationProcessor.UserOperationWorker#body). 5. Client node starts the next operation that needs all alive nodes to respond with UserManagementOperationFinishedMessage. But reconnected node authentication thread is blocked. So this operation can't be completed at all. This issue causes all tests in the AuthenticationProcessorNodeRestartTest test class to be flaky. was: First for all look at the test - AuthenticationProcessorNodeRestartTest#testConcurrentAddUpdateRemoveNodeRestartServer which is flaky - [TC history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8873434544416175780=testDetails] The first problem with this test is that user management operations(add/update/remove) create too many discovery messages. So discovery custom message history size is not enough to properly skip duplicated custom messages that can be sent across the ring during server node reconnect. It leads to mentioned test failures due to duplication of user management operations (see GridDiscoveryManager#discoCacheHist, IGNITE_DISCOVERY_HISTORY_SIZE system property, and ServerImpl.RingMessageWorker#sendMessageAcrossRing). If the discovery history size will be increased significantly, the test stops failing and starts hanging. The steps that lead to this: 1. Client node sent UserProposedMessage across the ring while one node is offline due to reconnect. 2. Alive server nodes update their local user lists and finish the operation. 3. Reconnected node joins the ring and receives an updated user list from the coordinator. 4. Reconnected node receives duplicated UserProposedMessage that has been already handled by all nodes, handles it, and sents UserManagementOperationFinishedMessage to the coordinator and start to wait for the UserAcceptedMessage from it. But the coordinator has already finished this operation. So the thread that responsible for user management operation on the reconnected node becomes blocked (see IgniteAuthenticationProcessor.UserOperationWorker#body). 5. Client node starts the next operation that needs all alive nodes to respond with UserManagementOperationFinishedMessage. But reconnected node authentication thread is blocked. So this operation can't be completed at all. > Authentication processor can hang all user management operation after server > node reconnect > --- > > Key: IGNITE-14301 > URL: https://issues.apache.org/jira/browse/IGNITE-14301 > Project: Ignite > Issue Type: Bug >Reporter: Mikhail Petrov >Priority: Major > > First for all look at the test - > AuthenticationProcessorNodeRestartTest#testConcurrentAddUpdateRemoveNodeRestartServer > which is flaky - [TC > history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8873434544416175780=testDetails] > The first problem with this test is that user management > operations(add/update/remove) create too many discovery messages. So > discovery custom message history size is not enough to properly
[jira] [Commented] (IGNITE-14422) Version management for ducktape.
[
https://issues.apache.org/jira/browse/IGNITE-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310486#comment-17310486
]
Ignite TC Bot commented on IGNITE-14422:
{panel:title=Branch: [pull/8938/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8938/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5936377buildTypeId=IgniteTests24Java8_RunAll]
> Version management for ducktape.
>
>
> Key: IGNITE-14422
> URL: https://issues.apache.org/jira/browse/IGNITE-14422
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Daschinskiy
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: IEP-56
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I propose following:
> 1. Add to {{update-versions}} task a sub-task, that bumps versions in
> {{ignitetests.__init__.py}} (i.e. {{2.11-SNAPSHOT}} to {{2.11-dev}})
> 2. Change {{ignitetests.versions.DEV}} to
> {{IgniteVersion(ignitetests.__version__)}}
> This automatically set {{DEV}} as latest version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14435) Refactor PdsConsistentIdProcessor for reusage
[
https://issues.apache.org/jira/browse/IGNITE-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-14435:
-
Labels: IEP-59 (was: )
> Refactor PdsConsistentIdProcessor for reusage
> -
>
> Key: IGNITE-14435
> URL: https://issues.apache.org/jira/browse/IGNITE-14435
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Major
> Labels: IEP-59
>
> Logic to resolve PDS folders should be reused inside {{IgniteCDC}} to lock
> specific Ignite node CDC folder.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14435) Refactor PdsConsistentIdProcessor for reusage
Nikolay Izhikov created IGNITE-14435:
Summary: Refactor PdsConsistentIdProcessor for reusage
Key: IGNITE-14435
URL: https://issues.apache.org/jira/browse/IGNITE-14435
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Logic to resolve PDS folders should be reused inside {{IgniteCDC}} to lock
specific Ignite node CDC folder.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14432) Python thin: Support "with" statement for connection method
[
https://issues.apache.org/jira/browse/IGNITE-14432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310457#comment-17310457
]
Ivan Daschinskiy commented on IGNITE-14432:
---
[~isapego] Hi, patch is ready for review.
> Python thin: Support "with" statement for connection method
> ---
>
> Key: IGNITE-14432
> URL: https://issues.apache.org/jira/browse/IGNITE-14432
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Reporter: Igor Sapego
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: python-0.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [pep-0343|https://www.python.org/dev/peps/pep-0343/]
> instead of this:
> {code:python}client.connect(environ['DB_HOST'], int(environ['DB_PORT']))
> try:
> return client.sql(q, query_args=q_args, include_field_names=True)
> finally:
> client.close(){code}
> The user will be able to use this:
> {code:python}with client.connect(environ['DB_HOST'], int(environ['DB_PORT'])):
> return client.sql(q, query_args=q_args, include_field_names=True){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12191) Add support of system view and metric to Visor
[
https://issues.apache.org/jira/browse/IGNITE-12191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov resolved IGNITE-12191.
--
Resolution: Fixed
> Add support of system view and metric to Visor
> --
>
> Key: IGNITE-12191
> URL: https://issues.apache.org/jira/browse/IGNITE-12191
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Priority: Minor
> Labels: IEP-35
>
> After Ignite obtain new {{SystemView}} and {{Metric}} API we should add
> support of it to the Visor.
> User should be able to query and view any system view content or Metric
> Registry values.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
