[jira] [Updated] (IGNITE-6565) Use long type for size and keySize in cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6565: --- Fix Version/s: (was: 2.6) 2.7 > Use long type for size and keySize in cache metrics > --- > > Key: IGNITE-6565 > URL: https://issues.apache.org/jira/browse/IGNITE-6565 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Ilya Kasnacheev >Assignee: Alexander Menshikov >Priority: Major > Labels: easyfix > Fix For: 2.7 > > > Currently it's int so for large caches there's no way to convey correct value. > Should introduce getSizeLong() and getKeySizeLong() > Also introduce the same in .Net and make sure that compatibility not broken > when passing OP_LOCAL_METRICS and OP_GLOBAL_METRICS. > BTW do we need keySize at all? What's it for? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7280) SQL TX: improve JDBC test coverage
[ https://issues.apache.org/jira/browse/IGNITE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7280: --- Fix Version/s: (was: 2.6) 2.7 > SQL TX: improve JDBC test coverage > -- > > Key: IGNITE-7280 > URL: https://issues.apache.org/jira/browse/IGNITE-7280 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko >Priority: Major > Fix For: 2.7 > > > The following cases must be handled: > 1) Single update stmt in TX > 2) Multiple update stmts in TX > 3) Changes to multiple caches in TX > 4) Mix of both selects and updates (e.g. get data from select and then build > updates based on it) > 5) Different operation types - INSERT, UPDATE, MERGE (take in count various > DML optimizations to ensure that as much code paths are covered as possible) > 6) Batch updates > 7) Joins (both co-located and distributed) > 8) Different cache modes - PARTITIONED, REPLICATED > 9) Different backup counts > 10) Communication with client node vs communication with server node > 11) Both implicit and explicit transactions -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8469) Non-heap memory leak for calling cluster activation multi times
[
https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8469:
---
Fix Version/s: (was: 2.6)
2.7
> Non-heap memory leak for calling cluster activation multi times
> ---
>
> Key: IGNITE-8469
> URL: https://issues.apache.org/jira/browse/IGNITE-8469
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.7
>
>
> Calling multiple time cluster (with enabled persistence and started client
> nodes) activation {{ig3CB.cluster().active(true);}} leads to non-heap memory
> leak.
> Line
> {{org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java:234}}
> looks suspicious because of in case method
> {{org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl#start}}
> callled multi times (e.g. activate(true) called multi times) we lost info
> about allocated regions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8050) Throw a meaningful exception when user issues TX SQL keyword with MVCC turned off
[ https://issues.apache.org/jira/browse/IGNITE-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8050: --- Fix Version/s: (was: 2.6) 2.7 > Throw a meaningful exception when user issues TX SQL keyword with MVCC turned > off > - > > Key: IGNITE-8050 > URL: https://issues.apache.org/jira/browse/IGNITE-8050 > Project: Ignite > Issue Type: Task > Components: jdbc, sql >Reporter: Alexander Paschenko >Assignee: Alexander Paschenko >Priority: Major > Fix For: 2.7 > > > An exception must be thrown when the user issues TX SQL command (BEGIN, > COMMIT, ROLLBACK) in absence of MVCC - ingoring these may be confusing and > can lead to SQL engine behavior to behaving quite differently from what the > user expects, esp. in terms of data consistency. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8544) WAL disabling during rebalance mechanism uses wrong topology version in case of exchanges merge
[ https://issues.apache.org/jira/browse/IGNITE-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8544: --- Fix Version/s: (was: 2.6) 2.7 > WAL disabling during rebalance mechanism uses wrong topology version in case > of exchanges merge > --- > > Key: IGNITE-8544 > URL: https://issues.apache.org/jira/browse/IGNITE-8544 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Critical > Fix For: 2.7 > > > After exchange is done, we're using initial exchange version to determine > topology version on what rebalance should be finished and save it. After > rebalance finishing we check current topology version and saved version and > if they are equal, we enable WAL, own partitions and do checkpoint. In other > case we do nothing, because of topology change. > In case of exchanges merge we're saving old topology version (before merge) > and it leads to ignoring logic of enabling WAL and etc, because check on > topology version will be always false-negative. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8235) Implement execution of selected part of SQL query
[ https://issues.apache.org/jira/browse/IGNITE-8235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8235: --- Fix Version/s: (was: 2.6) 2.7 > Implement execution of selected part of SQL query > - > > Key: IGNITE-8235 > URL: https://issues.apache.org/jira/browse/IGNITE-8235 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > > If we had 3 SQL rows in the notebook, and selected one and clicked execute. > We should only execute the highlighted row. If no row is highlighted, then > all rows should be executed. That's a standard feature of graphical SQL tools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8422) Zookeeper discovery split brain detection shouldn't consider client nodes
[ https://issues.apache.org/jira/browse/IGNITE-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8422: --- Fix Version/s: (was: 2.6) 2.7 > Zookeeper discovery split brain detection shouldn't consider client nodes > - > > Key: IGNITE-8422 > URL: https://issues.apache.org/jira/browse/IGNITE-8422 > Project: Ignite > Issue Type: Bug > Components: zookeeper >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.7 > > > Currently Zookeeper discovery checks each splitted cluster on full > connectivity taking into account client nodes. This is not correct, because > server and client nodes may use different networks to connect to each other. > It means that there can be client which sees both parts of splitted cluster > and breaks split brain recovery - full connected part of server nodes will be > never find. > We should exclude client nodes from split brain analysis and improve split > brain tests to make them truly fair. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5965) Ignite Basic: Flaky failure of GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology
[
https://issues.apache.org/jira/browse/IGNITE-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5965:
---
Fix Version/s: (was: 2.6)
2.7
> Ignite Basic: Flaky failure of
> GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology
> --
>
> Key: IGNITE-5965
> URL: https://issues.apache.org/jira/browse/IGNITE-5965
> Project: Ignite
> Issue Type: Test
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Andrew Medvedev
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
> Attachments: log.txt
>
>
> Test has 85% success rate in master:
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-2642357454043293898=testDetails_Ignite20Tests=%3Cdefault%3E
> Flaky failure is reproduced locally with similar success rate (24/30, Win 10).
> {noformat}
> junit.framework.AssertionFailedError:
> Expected :4
> Actual :5
>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessorAbstractSelfTest.checkCount(GridServiceProcessorAbstractSelfTest.java:765)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.checkDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:287)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:144)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8334) Web console: add ability to show/hide password field value
[ https://issues.apache.org/jira/browse/IGNITE-8334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8334: --- Fix Version/s: (was: 2.6) 2.7 > Web console: add ability to show/hide password field value > -- > > Key: IGNITE-8334 > URL: https://issues.apache.org/jira/browse/IGNITE-8334 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: eye-icon-close.svg, eye-icon-open.svg > > > The ability to toggle password inputs value visibility will improve the UX of > several forms. Since most of password inputs are located on sign-in and > profile pages, for now it'll be enough to update inputs used on these pages > only. > The button should: > 1. Has opened eye icon when password value is visible. > 2. Has closed eye icon when password value is hidden (i.e. default dots). > 3. Be placed at the right side of the input and to the right of validation > error message. That means that error message will be place a bit more to the > left compared to text inputs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8795) Add ability to start and maintain TensorFlow cluster on top of Apache Ignite
[ https://issues.apache.org/jira/browse/IGNITE-8795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8795: --- Fix Version/s: (was: 2.6) 2.7 > Add ability to start and maintain TensorFlow cluster on top of Apache Ignite > > > Key: IGNITE-8795 > URL: https://issues.apache.org/jira/browse/IGNITE-8795 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.7 > > > As described in the [design > document|https://docs.google.com/document/d/1jROIahK1rc7bSgOvhJhfpMqIGvht_IE8zn5NAt6x8ks/edit?usp=sharing], > Distributed TensorFlow is based on TensorFlow cluster concept. It's a set of > TensorFlow processes started among the cluster and available througth the > gRPC interfaces. It's assumed that these processes contain heavy operations > that requires data to be stored locally on the nodes where the processes > running. Apache Ignite admits the data to be moved from one node to another > as result of node failure of rebalancing. As result the TensorFlow cluster > should be changed dynamically as well as TensorFlow Cache (follow-the-data > strategy). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed
[ https://issues.apache.org/jira/browse/IGNITE-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6252: --- Fix Version/s: (was: 2.6) 2.7 > Cassandra Cache Store Session does not retry if prepare statement failed > > > Key: IGNITE-6252 > URL: https://issues.apache.org/jira/browse/IGNITE-6252 > Project: Ignite > Issue Type: Bug > Components: cassandra >Affects Versions: 2.0, 2.1 >Reporter: Sunny Chan >Assignee: Igor Rudyak >Priority: Major > Fix For: 2.7 > > > During our testing, we have found that certain warning about prepared > statement: > 2017-08-31 11:27:19.479 > org.apache.ignite.cache.store.cassandra.CassandraCacheStore > flusher-0-#265%% WARN CassandraCacheStore - Prepared statement cluster > error detected, refreshing Cassandra session > com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute > unknown prepared query : 0xc7647611fd755386ef63478ee7de577b. You may have > used a PreparedStatement that was created with another Cluster instance. > We notice that after this warning occurs some of the data didn't persist > properly in cassandra cache. After further examining the Ignite's > CassandraSessionImpl code in method > execute(BatchExecutionAssistance,Iterable), we found that at around [line > 283|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L283], > if the prepare statement fails in the asnyc call, it will not retry the > operation as the error is stored in [line > 269|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L269] > and cleared in [line > 277|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L277] > but it was not checked again after going through the [ResultSetFuture > |https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L307]. > I believe in line 307 you should check for error != null such that any > failure will be retry. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8013) CPP: Check pending snapshots in BinaryTypeManager::GetHandler
[
https://issues.apache.org/jira/browse/IGNITE-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8013:
---
Fix Version/s: (was: 2.6)
2.7
> CPP: Check pending snapshots in BinaryTypeManager::GetHandler
> -
>
> Key: IGNITE-8013
> URL: https://issues.apache.org/jira/browse/IGNITE-8013
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.7
>
>
> This will improve performance a lot, when using operations like {{PutAll()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8257) GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely)
[
https://issues.apache.org/jira/browse/IGNITE-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8257:
---
Fix Version/s: (was: 2.6)
2.7
> GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely)
> -
>
> Key: IGNITE-8257
> URL: https://issues.apache.org/jira/browse/IGNITE-8257
> Project: Ignite
> Issue Type: Test
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> {code:java}
> class org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout
> was reached before computation completed.
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:242)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:151)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.checkChaining(GridFutureAdapterSelfTest.java:283)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.testChaining(GridFutureAdapterSelfTest.java:237)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7807) SQL TX: Store lock info inside tuples
[
https://issues.apache.org/jira/browse/IGNITE-7807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7807:
---
Fix Version/s: (was: 2.6)
2.7
> SQL TX: Store lock info inside tuples
> -
>
> Key: IGNITE-7807
> URL: https://issues.apache.org/jira/browse/IGNITE-7807
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> We need to store lock info inside tuples. Otherwise, touching a lot of
> entries would lead to OOME. Also we should rework our locking logic - instead
> of trying to enlist ourselves in every entry, we should stop on the very
> first locked entry and wait for it's release.
> Suggested fix:
> 1) Check for {{lock_id}} field of an entry
> 2) If it is empty, CAS own XID
> 3) If it is not empty, check fo TX LOG to see if transaction is still active;
> if not - CAS itself
> 4) If failed to install own version - stop locking and wait for release
> 5) When transaction commits, no locks are released explicilty. Instead, it is
> responsibility of the next locker to check TX LOG and undesrantnad whether
> entry could be locked or not
> 6) When lock is acquired, create new version of an entry with lock info
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8602) Add support filter label=null for control.sh tx utility
[ https://issues.apache.org/jira/browse/IGNITE-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8602: --- Fix Version/s: (was: 2.6) 2.7 > Add support filter label=null for control.sh tx utility > --- > > Key: IGNITE-8602 > URL: https://issues.apache.org/jira/browse/IGNITE-8602 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Dmitry Sherstobitov >Assignee: Alexand Polyakov >Priority: Major > Fix For: 2.7 > > Attachments: TC 01 recheck.png, TC 02 recheck.png, TC 03 recheck.png, > TC 04 recheck.png, TC.png > > > For now this transactions cannot be separated from other by using filter > "label null" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6439) IgnitePersistentStoreSchemaLoadTest is broken
[ https://issues.apache.org/jira/browse/IGNITE-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6439: --- Fix Version/s: (was: 2.6) 2.7 > IgnitePersistentStoreSchemaLoadTest is broken > - > > Key: IGNITE-6439 > URL: https://issues.apache.org/jira/browse/IGNITE-6439 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Denis Garus >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > After start nodes, cluster must be activated explicit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4193) SQL TX: ODBC driver support
[ https://issues.apache.org/jira/browse/IGNITE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-4193: --- Fix Version/s: (was: 2.6) 2.7 > SQL TX: ODBC driver support > --- > > Key: IGNITE-4193 > URL: https://issues.apache.org/jira/browse/IGNITE-4193 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Denis Magda >Assignee: Igor Sapego >Priority: Major > Labels: iep-3 > Fix For: 2.7 > > > To support execution of DML and SELECT statements inside of a transaction > started from ODBC driver side. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence
[ https://issues.apache.org/jira/browse/IGNITE-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5977: --- Fix Version/s: (was: 2.6) 2.7 > [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence > --- > > Key: IGNITE-5977 > URL: https://issues.apache.org/jira/browse/IGNITE-5977 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Aleksey Plekhanov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Fails locally. > Example of failing > http://ci.ignite.apache.org/viewLog.html?buildId=760759=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId2829619862655631000 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8594) Make error messages in validate_indexes command report more informative
[
https://issues.apache.org/jira/browse/IGNITE-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8594:
---
Fix Version/s: (was: 2.6)
2.7
> Make error messages in validate_indexes command report more informative
> ---
>
> Key: IGNITE-8594
> URL: https://issues.apache.org/jira/browse/IGNITE-8594
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.7
>
>
> In case index is broken and contains links to missing items in data pages,
> validate_indexes command will show "Item not found" messages in report:
> {noformat}
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=_key_PK], class java.lang.IllegalStateException: Item not found: 65
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=_key_PK], class java.lang.IllegalStateException: Item not found: 15
> SQL Index [cache=cache_group_1_028, idx=LONG__VAL_IDX]
> ValidateIndexesPartitionResult [consistentId=node2, sqlIdxName=LONG__VAL_IDX]
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 60
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 65
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 65
> IndexValidationIssue [key=null, cacheName=cache_group_1_028,
> idxName=LONG__VAL_IDX], class java.lang.IllegalStateException: Item not
> found: 15
> {noformat}
> It would be better to explain what is happening: key is present in SQL index,
> but is missing in corresponding data page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8694) SQL JOIN between PARTITIONED and REPLICATED cache fails
[ https://issues.apache.org/jira/browse/IGNITE-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8694: --- Fix Version/s: (was: 2.6) 2.7 > SQL JOIN between PARTITIONED and REPLICATED cache fails > --- > > Key: IGNITE-8694 > URL: https://issues.apache.org/jira/browse/IGNITE-8694 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Rakov >Assignee: Ivan Rakov >Priority: Major > Fix For: 2.7 > > > We already have IGNITE-7766 where TC test fails due to the same problem. > Particular case with PARTITIONED and REPLICATED caches will be fixed under > this ticket, while rest of the work will be completed under IGNITE-7766. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8587) High Contention in GridToStringBuilder.toStringImpl
[ https://issues.apache.org/jira/browse/IGNITE-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8587: --- Fix Version/s: (was: 2.6) 2.7 > High Contention in GridToStringBuilder.toStringImpl > - > > Key: IGNITE-8587 > URL: https://issues.apache.org/jira/browse/IGNITE-8587 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Sergey Kosarev >Assignee: Sergey Kosarev >Priority: Major > Fix For: 2.7 > > > org.apache.ignite.internal.util.tostring.GridToStringBuilder#classCache > implemented as > ordinal HashMap with all operations syncronised by one ReadWriteLock. > this can trigger high contention as this class widely used in toString() > methods. > For instance it shoots when DEBUG or TRACE logs are enabled as count of > toString() invocations increases in this case extremely. > We need to use ConcurrentHashMap instead and avoid global locks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8533) Timeout collision in Client Nodes test suite
[ https://issues.apache.org/jira/browse/IGNITE-8533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8533: --- Fix Version/s: (was: 2.6) 2.7 > Timeout collision in Client Nodes test suite > > > Key: IGNITE-8533 > URL: https://issues.apache.org/jira/browse/IGNITE-8533 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Medvedev >Assignee: Andrew Medvedev >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > IGNITE-8085 increased NODE_START_CHECK_LIMIT so "remote" node log is parsed > for longer (set now to 25 * 2000ms) > https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L85 > > This exceeds total timeout set up for remote node startup in > [https://github.com/apache/ignite/blob/282b334f76479460613f28347d8cea97ba23f795/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L1054] > (40 * 1000ms) > > This leads to debug message with ref to remote log file being never shown > because 5 timeout will never be reached > [https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L285] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7302) SQL TX: Failed to query INFORMATIONAL_SCHEMA
[
https://issues.apache.org/jira/browse/IGNITE-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7302:
---
Fix Version/s: (was: 2.6)
2.7
> SQL TX: Failed to query INFORMATIONAL_SCHEMA
>
>
> Key: IGNITE-7302
> URL: https://issues.apache.org/jira/browse/IGNITE-7302
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Major
> Fix For: 2.7
>
>
> {code}
> javax.cache.CacheException: class org.apache.ignite.IgniteException:
> Unsupported query: Unexpected Table implementation [cls=MetaTable]
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.assert0(GridSqlQueryParser.java:1876)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parseTable(GridSqlQueryParser.java:612)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parseTableFilter(GridSqlQueryParser.java:565)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parseSelect(GridSqlQueryParser.java:665)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parseQuery(GridSqlQueryParser.java:1539)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQueryParser.parse(GridSqlQueryParser.java:1490)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.mvccTracker(IgniteH2Indexing.java:1294)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryLocalSqlFields(IgniteH2Indexing.java:926)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryLocalSqlFields(IgniteH2Indexing.java:870)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryLocalSqlFields(IgniteH2Indexing.java:1163)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:1951)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:1936)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2521)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1968)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:585)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:560)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:382)
> at
> org.apache.ignite.internal.processors.cache.local.IgniteCacheLocalFieldsQuerySelfTest.testInformationSchema(IgniteCacheLocalFieldsQuerySelfTest.java:49)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8160) GridCacheAbstractDataStructuresFailoverSelfTest#testAtomicInitialization flaky-fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8160: --- Fix Version/s: (was: 2.6) 2.7 > GridCacheAbstractDataStructuresFailoverSelfTest#testAtomicInitialization > flaky-fails on TC > -- > > Key: IGNITE-8160 > URL: https://issues.apache.org/jira/browse/IGNITE-8160 > Project: Ignite > Issue Type: Test >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > The test fails because sequence initialization compute is sent to nodes being > stopped. The test should be changed to test: > 1) If the closure may be sent to a stopping node, then NodeStoppingException > should be ignored > 2) Another test should send closures only to stable nodes and should not > tolerate any failures -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7592) Dynamic cache with rebalanceDelay == -1 doesn't trigger late affinity assignment even after explicit rebalance is called on every node
[
https://issues.apache.org/jira/browse/IGNITE-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7592:
---
Fix Version/s: (was: 2.6)
2.7
> Dynamic cache with rebalanceDelay == -1 doesn't trigger late affinity
> assignment even after explicit rebalance is called on every node
> --
>
> Key: IGNITE-7592
> URL: https://issues.apache.org/jira/browse/IGNITE-7592
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Ilya Lantukh
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.7
>
>
> Reproducer:
> {noformat}
> startGrids(NODE_COUNT);
> IgniteEx ig = grid(0);
> ig.cluster().active(true);
> awaitPartitionMapExchange();
> IgniteCache cache =
> ig.createCache(
> new CacheConfiguration()
> .setName(CACHE_NAME)
> .setCacheMode(PARTITIONED)
> .setBackups(1)
> .setPartitionLossPolicy(READ_ONLY_SAFE)
> .setReadFromBackup(true)
> .setWriteSynchronizationMode(FULL_SYNC)
> .setRebalanceDelay(-1)
> );
> for (int i = 0; i < NODE_COUNT; i++)
> grid(i).cache(CACHE_NAME).rebalance().get();
> awaitPartitionMapExchange();
> {noformat}
> Sometimes this code will hang on the last awaitPartitionMapExchange(), though
> probability that it will happen is rather low (<10%).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8079) Service config variations test has flaky failures in Basic 2 suite: Not serializable
[
https://issues.apache.org/jira/browse/IGNITE-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8079:
---
Fix Version/s: (was: 2.6)
2.7
> Service config variations test has flaky failures in Basic 2 suite: Not
> serializable
>
>
> Key: IGNITE-8079
> URL: https://issues.apache.org/jira/browse/IGNITE-8079
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
>
> IgniteServiceConfigVariationsFullApiTest.testClusterSingletonDeploy 5
> failures in one build
> IgniteServiceConfigVariationsFullApiTest.testDeploy 5 failures in one build
> IgniteServiceConfigVariationsFullApiTest.testKeyAffinityDeploy 5
> failures in one build
> IgniteServiceConfigVariationsFullApiTest.testMultipleDeploy 5 failures in
> one build
> IgniteServiceConfigVariationsFullApiTest.testNodeSingletonDeploy
> {noformat}
> [2018-03-25
> 09:11:24,764][ERROR][test-runner-#15278%service.IgniteServiceConfigVariationsFullApiTest%][GridServiceProcessor]
> Failed to marshal service with configured marshaller [name=testService,
> srvc=o.a.i.i.processors.service.IgniteServiceConfigVariationsFullApiTest$TestServiceImpl@587a67fa,
> marsh=JdkMarshaller [clsFilter=null]]
> class org.apache.ignite.IgniteCheckedException: Failed to serialize object:
> org.apache.ignite.internal.processors.service.IgniteServiceConfigVariationsFullApiTest$TestServiceImpl@587a67fa
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal0(JdkMarshaller.java:103)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:70)
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.marshal0(JdkMarshaller.java:117)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10051)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor.prepareServiceConfigurations(GridServiceProcessor.java:560)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor.deployAll(GridServiceProcessor.java:612)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor.deployAll(GridServiceProcessor.java:600)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor.deployMultiple(GridServiceProcessor.java:488)
> at
> org.apache.ignite.internal.processors.service.GridServiceProcessor.deployClusterSingleton(GridServiceProcessor.java:469)
> at
> org.apache.ignite.internal.IgniteServicesImpl.deployClusterSingleton(IgniteServicesImpl.java:120)
> at
> org.apache.ignite.internal.processors.service.IgniteServiceConfigVariationsFullApiTest$2.run(IgniteServiceConfigVariationsFullApiTest.java:99)
> at
> org.apache.ignite.internal.processors.service.IgniteServiceConfigVariationsFullApiTest.testService(IgniteServiceConfigVariationsFullApiTest.java:225)
> at
> org.apache.ignite.internal.processors.service.IgniteServiceConfigVariationsFullApiTest$ServiceTestRunnable.run(IgniteServiceConfigVariationsFullApiTest.java:189)
> at
> org.apache.ignite.testframework.junits.IgniteConfigVariationsAbstractTest.runInAllDataModes(IgniteConfigVariationsAbstractTest.java:248)
> at
> org.apache.ignite.internal.processors.service.IgniteServiceConfigVariationsFullApiTest.testClusterSingletonDeploy(IgniteServiceConfigVariationsFullApiTest.java:97)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.NotSerializableException:
> org.apache.ignite.testframework.junits.IgniteConfigVariationsAbstractTest$PlaneObject
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
>
[jira] [Updated] (IGNITE-8086) Flaky test timeouts in Activate/Deactivate Cluster suite
[ https://issues.apache.org/jira/browse/IGNITE-8086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8086: --- Fix Version/s: (was: 2.6) 2.7 > Flaky test timeouts in Activate/Deactivate Cluster suite > > > Key: IGNITE-8086 > URL: https://issues.apache.org/jira/browse/IGNITE-8086 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Pavlov >Assignee: Maxim Muzafarov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > # Activate | Deactivate Cluster > IgniteStandByClusterSuite: > CacheBaselineTopologyTest.testPrimaryLeftAndClusterRestart (master fail rate > 37,1%) > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6798733272445954906=%3Cdefault%3E=testDetails] > # IgniteStandByClusterSuite: > CacheBaselineTopologyTest.testBaselineTopologyChangesFromClient (master fail > rate 24,9%) > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9217764610687235146=%3Cdefault%3E=testDetails] > # IgniteStandByClusterSuite: > CacheBaselineTopologyTest.testBaselineTopologyChangesFromServer (master fail > rate 19,8%) > > [https://ci.ignite.apache.org/viewLog.html?buildId=1199624=buildResultsDiv=IgniteTests24Java8_ActivateDeactivateCluster#testNameId-4432469336264773506] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7271) UPDATE and DELETE statements do not work through thin JDBC work in MVCC mode
[ https://issues.apache.org/jira/browse/IGNITE-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7271: --- Fix Version/s: (was: 2.6) 2.7 > UPDATE and DELETE statements do not work through thin JDBC work in MVCC mode > > > Key: IGNITE-7271 > URL: https://issues.apache.org/jira/browse/IGNITE-7271 > Project: Ignite > Issue Type: Bug > Components: jdbc, sql >Reporter: Vladimir Ozerov >Assignee: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > > See relevant failures JDBC suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8666) Add ability of filtering data during datasets creation
[ https://issues.apache.org/jira/browse/IGNITE-8666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8666: --- Fix Version/s: (was: 2.6) 2.7 > Add ability of filtering data during datasets creation > -- > > Key: IGNITE-8666 > URL: https://issues.apache.org/jira/browse/IGNITE-8666 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.7 > > > So far we use straightforward strategy to feed data into partition based > dataset. We retrieve all entries from an upstream cache partition, transform > it somehow and write into correspondent dataset partition (data and context). > As result we can't choose the data to be fed into dataset and data to be not > fed. To implement IGNITE-8667 (Splitting of dataset to test and training > sets) and IGNITE-8668 (K-fold cross validation of models) we need to have > such ability. > The goal of this task is to add an ability to filter data that fed from cache > to dataset. It will allow us to create different dataset (training, testing, > k-fold, etc...) based on a single cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8491) Add JMX flag: Is the node in baseline or not?
[
https://issues.apache.org/jira/browse/IGNITE-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8491:
---
Fix Version/s: (was: 2.6)
2.7
> Add JMX flag: Is the node in baseline or not?
> -
>
> Key: IGNITE-8491
> URL: https://issues.apache.org/jira/browse/IGNITE-8491
> Project: Ignite
> Issue Type: Improvement
>Reporter: Vladislav Pyatkov
>Assignee: Vladislav Pyatkov
>Priority: Major
> Fix For: 2.7
>
>
> Need to add a baseline flag on JMX.
> {code}
> public interface IgniteMXBean {
> /**
> * Gets a flag is node in baseline.
> *
> * @return Return a baseline flag.
> */
> @MXBeanDescription("Baseline node flag.")
> public boolean isNodeInBaseline();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8413) CacheGroupMetricsMBeanTest.testCacheGroupMetrics fails on master.
[
https://issues.apache.org/jira/browse/IGNITE-8413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8413:
---
Fix Version/s: (was: 2.6)
2.7
> CacheGroupMetricsMBeanTest.testCacheGroupMetrics fails on master.
> -
>
> Key: IGNITE-8413
> URL: https://issues.apache.org/jira/browse/IGNITE-8413
> Project: Ignite
> Issue Type: Test
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> CacheGroupMetricsMBeanTest.testCacheGroupMetrics fails due to a race.
> Seems, we should pause rebalance to see expected instant metrics.
> {code:java}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupMetricsMBeanTest.testCacheGroupMetrics(CacheGroupMetricsMBeanTest.java:262)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
> at java.lang.Thread.run(Thread.java:748){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6612) Wrap ack methods in their own class
[ https://issues.apache.org/jira/browse/IGNITE-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6612: --- Fix Version/s: (was: 2.6) 2.7 > Wrap ack methods in their own class > --- > > Key: IGNITE-6612 > URL: https://issues.apache.org/jira/browse/IGNITE-6612 > Project: Ignite > Issue Type: Improvement >Affects Versions: None >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Trivial > Labels: refactor > Fix For: 2.7 > > > Several methods in IgniteKernal implement similar functions: “ackAsciiLogo”, > “ackConfigUrl”, “ackDaemon”, “ackOsInfo”, “ackLanguageRuntime”, > “ackRemoteManagement”, “ackVmArguments”, “ackClassPaths”, > “ackSystemProperties”, “ackEnviromentVariables”, “ackMemoryConfiguration”, > “ackCacheConfiguration”, “ackP2PConfiguration”, “ackRebalanceConfiguration”. > These methods should be placed in separate class “AckVariousInformation” and > called from the class instance in IgniteKernal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8437) Control utility fails to connect to cluster if zookeeper discovery used
[
https://issues.apache.org/jira/browse/IGNITE-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8437:
---
Fix Version/s: (was: 2.6)
2.7
> Control utility fails to connect to cluster if zookeeper discovery used
> ---
>
> Key: IGNITE-8437
> URL: https://issues.apache.org/jira/browse/IGNITE-8437
> Project: Ignite
> Issue Type: Improvement
> Components: zookeeper
>Affects Versions: 2.5
>Reporter: Dmitry Sherstobitov
>Assignee: Alexei Scherbakov
>Priority: Blocker
> Fix For: 2.7
>
>
> Start cluster with zookeeper discovery and try to run control.sh --tx utility
>
> {code:java}
> 2018-05-03 16:56:36.225
> [ERROR][mgmt-#115268%DPL_GRID%DplGridNodeName%][o.a.i.i.p.r.p.t.GridTcpRestProtocol]
> Failed to process client request [ses=GridSelectorNioSessionImpl
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=395
> lim=395 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0,
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker
> [name=grid-nio-worker-tcp-rest-0,
> igniteInstanceName=DPL_GRID%DplGridNodeName, finished=false,
> hashCode=1766410348, interrupted=false,
> runner=grid-nio-worker-tcp-rest-0-#48%DPL_GRID%DplGridNodeName%]]],
> writeBuf=null, readBuf=null, inRecovery=null, outRecovery=null,
> super=GridNioSessionImpl [locAddr=/10.116.158.48:11211,
> rmtAddr=/10.78.10.31:55847, createTime=1525355795984,
> closeTime=1525355796217, bytesSent=521553, bytesRcvd=461, bytesSent0=521553,
> bytesRcvd0=461, sndSchedTime=1525355796217, lastSndTime=1525355796075,
> lastRcvTime=1525355796175, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser
> [marsh=JdkMarshaller [clsFilter=o.a.i.i.IgniteKernal$5@3e3d1d0d],
> routerClient=false], directMode=false]], accepted=true]],
> msg=GridClientTaskRequest [taskName=o.a.i.i.v.tx.VisorTxTask,
> arg=VisorTaskArgument [debug=false]]]
> org.apache.ignite.internal.util.nio.GridNioException: class
> org.apache.ignite.IgniteCheckedException: Failed to serialize object:
> GridClientResponse [clientId=587ea745-dd1e-4631-aa85-feb5d49acc36, reqId=2,
> destId=null, status=0, errMsg=null, result=GridClientTaskResultBean
> [res={ZookeeperClusterNode [id=c4cc818d-b29f-427b-86b5-9a625287feb6,
> addrs=[10.116.159.100], order=30, loc=false, client=true]=VisorTxTaskResult
> []}, error=null, finished=true, id=~a7245b33-a37a-4084-a954-460c31834442]]
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onSessionWrite(GridNioCodecFilter.java:100)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionWrite(GridNioFilterAdapter.java:121)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onSessionWrite(GridNioFilterChain.java:269)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onSessionWrite(GridNioFilterChain.java:192)
> at
> org.apache.ignite.internal.util.nio.GridNioSessionImpl.send(GridNioSessionImpl.java:110)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestNioListener$1.apply(GridTcpRestNioListener.java:261)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestNioListener$1.apply(GridTcpRestNioListener.java:232)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2$1.apply(GridRestProcessor.java:165)
> at
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2$1.apply(GridRestProcessor.java:162)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
>
[jira] [Updated] (IGNITE-8423) Control utility may block when joining node is watiting for partition map exchange
[
https://issues.apache.org/jira/browse/IGNITE-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8423:
---
Fix Version/s: (was: 2.6)
2.7
> Control utility may block when joining node is watiting for partition map
> exchange
> --
>
> Key: IGNITE-8423
> URL: https://issues.apache.org/jira/browse/IGNITE-8423
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Alexey Goncharuk
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.7
>
>
> The utility hang because {{GridTcpRestNioListener}} is blocked on the
> following piece of code:
> {code}
> if (marshMapLatch.getCount() > 0)
> U.awaitQuiet(marshMapLatch);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8525) Support for IgniteZeroMqStreamer non-multi-part pub-sub
[ https://issues.apache.org/jira/browse/IGNITE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8525: --- Fix Version/s: (was: 2.6) 2.7 > Support for IgniteZeroMqStreamer non-multi-part pub-sub > --- > > Key: IGNITE-8525 > URL: https://issues.apache.org/jira/browse/IGNITE-8525 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > Currently only multi-part pub-sub is supported. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5934) Integrate mvcc support in sql query protocol
[ https://issues.apache.org/jira/browse/IGNITE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5934: --- Fix Version/s: (was: 2.6) 2.7 > Integrate mvcc support in sql query protocol > > > Key: IGNITE-5934 > URL: https://issues.apache.org/jira/browse/IGNITE-5934 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Semen Boikov >Assignee: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > > Need integrate mvcc support in sql query protocol: > - request current ID and list of active txs from coordinator > - pass this info in sql requests and in sql queries > - notify coordinator after query completed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8511) [ML] Add support for Multi-Class Logistic Regression
[ https://issues.apache.org/jira/browse/IGNITE-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8511: --- Fix Version/s: (was: 2.6) 2.7 > [ML] Add support for Multi-Class Logistic Regression > > > Key: IGNITE-8511 > URL: https://issues.apache.org/jira/browse/IGNITE-8511 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8624) Add test coverage for NPE in TTL Manager [IGNITE-7972]
[ https://issues.apache.org/jira/browse/IGNITE-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8624: --- Fix Version/s: (was: 2.6) 2.7 > Add test coverage for NPE in TTL Manager [IGNITE-7972] > -- > > Key: IGNITE-8624 > URL: https://issues.apache.org/jira/browse/IGNITE-8624 > Project: Ignite > Issue Type: Test >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Minor > Fix For: 2.7 > > > Add test coverage (reproducer) to the [IGNITE-7972] case. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8763) java.nio.file.AccessDeniedException is not handled with default failure handler
[
https://issues.apache.org/jira/browse/IGNITE-8763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8763:
---
Fix Version/s: (was: 2.6)
2.7
> java.nio.file.AccessDeniedException is not handled with default failure
> handler
> ---
>
> Key: IGNITE-8763
> URL: https://issues.apache.org/jira/browse/IGNITE-8763
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Andrey Gura
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.7
>
>
> java.nio.file.AccessDeniedException is not handled with default failure
> handler
> 1. Start cluster(4 nodes).
> 2. Upload some data.
> 3. Make files in metastore read only.
> 4. Deactivate grid.
> 5. Activate grid.
> On this step I see java.nio.file.AccessDeniedException:
> {noformat}
> [17:55:40,035][INFO][exchange-worker-#62][GridCacheDatabaseSharedManager]
> Read checkpoint status
> [startMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-START.bin,
>
> endMarker=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/cp/1526568907638-46128a87-562a-45fc-8d73-75ccb1490d63-END.bin]
> [17:55:40,037][SEVERE][exchange-worker-#62][GridDhtPartitionsExchangeFuture]
> Failed to activate node components
> [nodeId=bd7115d5-1f95-4673-9f40-47056b0b1a58, client=false,
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=5]]
> class org.apache.ignite.IgniteCheckedException: Error while creating file
> page store
> [file=/storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin]:
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:98)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initDir(FilePageStoreManager.java:463)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.initializeForMetastorage(FilePageStoreManager.java:234)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readCheckpointAndRestoreMemory(GridCacheDatabaseSharedManager.java:743)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClusterStateChangeRequest(GridDhtPartitionsExchangeFuture.java:896)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:643)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.file.AccessDeniedException:
> /storage/ssd/avolkov/tiden/iep_14-180517-175425/test_iep_14/ignite.server.1/work/db/node1/metastorage/part-0.bin
> at
> sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at
> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at
> sun.nio.fs.UnixFileSystemProvider.newAsynchronousFileChannel(UnixFileSystemProvider.java:196)
> at
> java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:248)
> at
> java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:301)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.(AsyncFileIO.java:57)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:53)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileVersionCheckingFactory.createPageStore(FileVersionCheckingFactory.java:78)
> ... 9 more
> {noformat}
> Situation led to NPE exception after AccessDeniedException looks like this:
> 1. AccessDeniedException was thrown in ExchangeFuture right before affinity
> initialization so affinity was never initialized.
> 2. After that node receives PartitionSingleMessage and tries to access
> affinity information. Null is returned
[jira] [Updated] (IGNITE-8675) Fix flacky test PdsWithTtlCompatibilityTest.testNodeStartByOldVersionPersistenceData_2_1
[ https://issues.apache.org/jira/browse/IGNITE-8675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8675: --- Fix Version/s: (was: 2.6) 2.7 > Fix flacky test > PdsWithTtlCompatibilityTest.testNodeStartByOldVersionPersistenceData_2_1 > - > > Key: IGNITE-8675 > URL: https://issues.apache.org/jira/browse/IGNITE-8675 > Project: Ignite > Issue Type: Test >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Looks like 2.1 node that is started in separate JVM, fails with OOM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6430) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically.
[
https://issues.apache.org/jira/browse/IGNITE-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-6430:
---
Fix Version/s: (was: 2.6)
2.7
> CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails
> periodically.
>
>
> Key: IGNITE-6430
> URL: https://issues.apache.org/jira/browse/IGNITE-6430
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Alexander Menshikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> {{CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime}} test
> fails periodically.
> {noformat}
> [2017-09-18 15:18:20,073][ERROR][main][root] Test failed.
> junit.framework.AssertionFailedError: Expected less 5000, Actual:-100969
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.internal.processors.cache.CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime(CacheGroupsMetricsRebalanceTest.java:261)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> After fix test should be unmuted on TC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8108) .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup
[ https://issues.apache.org/jira/browse/IGNITE-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8108: --- Fix Version/s: (was: 2.6) 2.7 > .NET: Fix flaky > EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup > -- > > Key: IGNITE-8108 > URL: https://issues.apache.org/jira/browse/IGNITE-8108 > Project: Ignite > Issue Type: Bug > Components: platforms >Affects Versions: 2.5 >Reporter: Alexey Popov >Assignee: Alexey Popov >Priority: Minor > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > https://ci.ignite.apache.org/viewLog.html?buildId=1171195=IgniteTests24Java8_IgnitePlatformNetIntegrations=buildLog&_focus=6035 > Test uses multicast ipFinder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7342) SQL TX: Fix checking whether currently updating row was updated after it pass query filter
[ https://issues.apache.org/jira/browse/IGNITE-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7342: --- Fix Version/s: (was: 2.6) 2.7 > SQL TX: Fix checking whether currently updating row was updated after it pass > query filter > -- > > Key: IGNITE-7342 > URL: https://issues.apache.org/jira/browse/IGNITE-7342 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Igor Seliverstov >Assignee: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8134) Services can't be deployed on servers outside of baseline topology
[
https://issues.apache.org/jira/browse/IGNITE-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8134:
---
Fix Version/s: (was: 2.6)
2.7
> Services can't be deployed on servers outside of baseline topology
> --
>
> Key: IGNITE-8134
> URL: https://issues.apache.org/jira/browse/IGNITE-8134
> Project: Ignite
> Issue Type: Bug
> Components: managed services, persistence
>Affects Versions: 2.4
>Reporter: Stanislav Lukyanov
>Assignee: Denis Mekhanikov
>Priority: Major
> Fix For: 2.7
>
>
> If a node is not a part of the baseline topology, the services will never be
> deployed on it. In particular, if that node calls a synchronous deploy*
> method, the method will hang.
> After the node is added to the baseline, all previously initiated
> deployments succeed (and deploy* methods return).
> It seems that the issue is with the continuous query started by the
> GridServiceProcessor on the ignite-sys-cache.
> Example:
> =
> {code}
> public class BltServicesBug {
> public static void main(String[] args) {
> // start one node
> IgniteConfiguration cfg1 = new IgniteConfiguration()
> .setIgniteInstanceName("node1")
> .setDataStorageConfiguration(
> new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(
> new DataRegionConfiguration()
> .setPersistenceEnabled(true)
> )
> );
> try (Ignite ignite1 = Ignition.start(cfg1)) {
> // activate and set baseline topology
> ignite1.cluster().active(true);
> // start another node
> IgniteConfiguration cfg2 = new IgniteConfiguration(cfg1)
> .setIgniteInstanceName("node2");
> try (Ignite ignite2 = Ignition.start(cfg2)) {
> // try to deploy a service;
> // this call hangs until the second node is added to the BLT
> (e.g. externally via control.sh)
> ignite2.services().deployNodeSingleton("myService", new
> MyServiceImpl()); System.out.println("> Deployed"); }
> }
> }
> private static class MyServiceImpl implements Service {
> @Override public void cancel(ServiceContext ctx) { }
> @Override public void init(ServiceContext ctx) { }
> @Override public void execute(ServiceContext ctx) { }
> }
> }
> }
> {code}
> =
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8162) Handle ClassNotFoundException during deserialization of persisted cache configuration
[ https://issues.apache.org/jira/browse/IGNITE-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8162: --- Fix Version/s: (was: 2.6) 2.7 > Handle ClassNotFoundException during deserialization of persisted cache > configuration > -- > > Key: IGNITE-8162 > URL: https://issues.apache.org/jira/browse/IGNITE-8162 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.4 >Reporter: Ivan Rakov >Assignee: Denis Garus >Priority: Major > Labels: newbie > Fix For: 2.7 > > > Ticket is created according to dev list discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-Data-Loss-while-upgrading-custom-jar-from-old-jar-in-server-and-client-nodes-td28808.html > Cache configuration is serialized by JDK marshaller and persisted in > cache_data.dat file. It may contain instances of classes that disappeared > from runtime classpath (e.g. if implementation of CacheStore has been > renamed). In such case, node will fail on start. > We should handle this and show meaningful message with instruction how to > overcome this issue - delete cache_data.dat and restart cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8111) Add extra validation for WAL segment size
[ https://issues.apache.org/jira/browse/IGNITE-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8111: --- Fix Version/s: (was: 2.6) 2.7 > Add extra validation for WAL segment size > - > > Key: IGNITE-8111 > URL: https://issues.apache.org/jira/browse/IGNITE-8111 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Ivan Rakov >Assignee: Denis Garus >Priority: Major > Labels: newbie > Fix For: 2.7 > > > Currently we can set extra small DataStorageConfiguration#walSegmentSize (10 > pages or even less than one page), which will trigger multiple assertion > errors in code. > We have to implement validation on node start that WAL segment size has > reasonable value (512KB or more). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8447) .NET: DataStreamer.perThreadBufferSize
[ https://issues.apache.org/jira/browse/IGNITE-8447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8447: --- Fix Version/s: (was: 2.6) 2.7 > .NET: DataStreamer.perThreadBufferSize > --- > > Key: IGNITE-8447 > URL: https://issues.apache.org/jira/browse/IGNITE-8447 > Project: Ignite > Issue Type: Bug > Components: platforms >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: .NET, MakeTeamcityGreenAgain > Fix For: 2.7 > > > Need to add support of DataStreamer#perThreadBuffer property. > It was added in IGNITE-6699. > Related failed test - DataStreamerTest.TestBufferSize > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-7699185391938208048=%3Cdefault%3E=testDetails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8282) Direct IO: support fdatasync, which does not flush modified metadata
[ https://issues.apache.org/jira/browse/IGNITE-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8282: --- Fix Version/s: (was: 2.6) 2.7 > Direct IO: support fdatasync, which does not flush modified metadata > > > Key: IGNITE-8282 > URL: https://issues.apache.org/jira/browse/IGNITE-8282 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Major > Fix For: 2.7 > > > fsync(2) - Linux man page > fdatasync() is similar to fsync(), but does not flush modified metadata > unless that metadata is needed in order to allow a subsequent data retrieval > to be correctly handled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8499) validate_indexes command doesn't detect absent rows in cache data tree
[ https://issues.apache.org/jira/browse/IGNITE-8499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8499: --- Fix Version/s: (was: 2.6) 2.7 > validate_indexes command doesn't detect absent rows in cache data tree > -- > > Key: IGNITE-8499 > URL: https://issues.apache.org/jira/browse/IGNITE-8499 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Rakov >Assignee: Ivan Rakov >Priority: Major > Fix For: 2.7 > > > validate_indexes command performs lookup only in one direction: > *if* something is present in cache data tree *then* it should be present in > SQL indexes. > We should perform lookup in reverse direction as well to ensure that indexes > are correct. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8787) Striped Executor thread failure is not processed by IgniteFailureProcessor
[ https://issues.apache.org/jira/browse/IGNITE-8787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8787: --- Fix Version/s: (was: 2.6) 2.7 > Striped Executor thread failure is not processed by IgniteFailureProcessor > -- > > Key: IGNITE-8787 > URL: https://issues.apache.org/jira/browse/IGNITE-8787 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Andrew Medvedev >Priority: Major > Fix For: 2.7 > > Attachments: after.jstack, before.jstack > > > org.apache.ignite.internal.util.StripedExecutor.Stripe#run currently does not > invoke IgniteFailureProcessor upon thread death. This can lead to dying all > striped threads on a running node. see jstacks attached taken before and > after killing all striped threads (via JMX). > > If striped executor threads are considered critical, they should be processed > by IgniteFailureProcessor as well -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8838) Query cursor is open after INSERT call
[
https://issues.apache.org/jira/browse/IGNITE-8838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8838:
---
Fix Version/s: (was: 2.6)
2.7
> Query cursor is open after INSERT call
> ---
>
> Key: IGNITE-8838
> URL: https://issues.apache.org/jira/browse/IGNITE-8838
> Project: Ignite
> Issue Type: Bug
> Components: odbc, platforms, sql
>Affects Versions: 2.4
>Reporter: Pavel Vinokurov
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.7
>
>
> Ignite ODBC driver returns open cursor for an insert command.
> {code}
> AddStatusRecord: Adding new record: Query cursor is in open state already.,
> rowNum: 0, columnNum: 0
> SQLGetDiagField: SQLGetDiagField called: 1
> PutString: value: HY010
> SQLGetDiagField: SQLGetDiagField called: 2
> SQLGetDiagRec: SQLGetDiagRec called
> SQLGetDiagRec: SQLGetDiagRec called
> SQLGetDiagRec: SQLGetDiagRec called
> SQLParamOptions: SQLParamOptions called
> SQLBindParameter: SQLBindParameter called: 1, 1, 12
> SQLBindParameter: SQLBindParameter called: 2, 1, 12
> SQLBindParameter: SQLBindParameter called: 3, 1, 12
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8651) VisorTxTask fails then printing transactions having implicit single type.
[ https://issues.apache.org/jira/browse/IGNITE-8651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8651: --- Fix Version/s: (was: 2.6) 2.7 > VisorTxTask fails then printing transactions having implicit single type. > - > > Key: IGNITE-8651 > URL: https://issues.apache.org/jira/browse/IGNITE-8651 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.7 > > > org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal#mappings > returns null for IgniteTxMappingsSingleImpl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5789) After client reconnects to server if server was restarted, client doesn't create caches defined in client's configuration
[ https://issues.apache.org/jira/browse/IGNITE-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5789: --- Fix Version/s: (was: 2.6) 2.7 > After client reconnects to server if server was restarted, client doesn't > create caches defined in client's configuration > - > > Key: IGNITE-5789 > URL: https://issues.apache.org/jira/browse/IGNITE-5789 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Evgenii Zhuravlev >Assignee: vk >Priority: Major > Fix For: 2.7 > > Attachments: ClientReconnectAfterClusterRestartTest.java > > > User with this problem on SO: > https://stackoverflow.com/questions/46053089/ignite-cache-reconnection-issue-cache-is-stopped -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6709) Support mvcc filter for H2TreeIndex.findFirstOrLast
[ https://issues.apache.org/jira/browse/IGNITE-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6709: --- Fix Version/s: (was: 2.6) 2.7 > Support mvcc filter for H2TreeIndex.findFirstOrLast > --- > > Key: IGNITE-6709 > URL: https://issues.apache.org/jira/browse/IGNITE-6709 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Semen Boikov >Assignee: Igor Seliverstov >Priority: Major > Fix For: 2.7 > > > Need implement possibility to pass filter in findFirst/findLast (test already > exists CacheMvccSqlQueriesTest.testMaxMinTransactional). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7844) Transaction incorrect state after client reconnected
[ https://issues.apache.org/jira/browse/IGNITE-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7844: --- Fix Version/s: (was: 2.6) 2.7 > Transaction incorrect state after client reconnected > > > Key: IGNITE-7844 > URL: https://issues.apache.org/jira/browse/IGNITE-7844 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > > Transaction is started on client node. > Client reconnects, transaction rollbacks, but its state is left ACTIVE, > which is incorrect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6140) JDBC thin: implement DataSource interface
[
https://issues.apache.org/jira/browse/IGNITE-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-6140:
---
Fix Version/s: (was: 2.6)
2.7
> JDBC thin: implement DataSource interface
> -
>
> Key: IGNITE-6140
> URL: https://issues.apache.org/jira/browse/IGNITE-6140
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.7
>
>
> Implemented {{DataSource}} interface is required for JDBC compliance.
> Also it us useful for external connection pool implementation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8400) Flaky failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup (Grid is in invalid state)
[
https://issues.apache.org/jira/browse/IGNITE-8400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8400:
---
Fix Version/s: (was: 2.6)
2.7
> Flaky failure of
> IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup
> (Grid is in invalid state)
> -
>
> Key: IGNITE-8400
> URL: https://issues.apache.org/jira/browse/IGNITE-8400
> Project: Ignite
> Issue Type: Bug
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Test fails sometimes on TeamCity with exception:
> {noformat}
> java.lang.IllegalStateException: Grid is in invalid state to perform this
> operation. It either not started yet or has already being or have stopped
> [igniteInstanceName=cache.IgniteTopologyValidatorGridSplitCacheTest6,
> state=STOPPED]
> {noformat}
> Before this exception node is dropped out of topology by coordinator:
> {noformat}
> [tcp-disco-msg-worker-#7831%cache.IgniteTopologyValidatorGridSplitCacheTest6%][IgniteCacheTopologySplitAbstractTest$SplitTcpDiscoverySpi]
> Node is out of topology (probably, due to short-time network problems).
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8474) WalStateNodeLeaveExchangeTask prevents merge exchanges on leaving many nodes
[ https://issues.apache.org/jira/browse/IGNITE-8474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8474: --- Fix Version/s: (was: 2.6) 2.7 > WalStateNodeLeaveExchangeTask prevents merge exchanges on leaving many nodes > > > Key: IGNITE-8474 > URL: https://issues.apache.org/jira/browse/IGNITE-8474 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.7 > > > Exchange merge mechanism provides huge optimization when a lot of nodes join > or leave cluster simultaneously. > In IGNITE-7003 WalStateNodeLeaveExchangeTask custom exchange task was added > which is generated for each NODE_LEFT/NODE_FAILED event. > Because of property skipForExchangeMerge set to false on this task it > prohibits exchange merge optimization. > The property needs to be reconsidered and changed if it is not crucial for > this functionality. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8755) NegativeArraySizeException when trying to serialize in GridClientOptimizedMarshaller humongous object
[
https://issues.apache.org/jira/browse/IGNITE-8755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8755:
---
Fix Version/s: (was: 2.6)
2.7
> NegativeArraySizeException when trying to serialize in
> GridClientOptimizedMarshaller humongous object
> -
>
> Key: IGNITE-8755
> URL: https://issues.apache.org/jira/browse/IGNITE-8755
> Project: Ignite
> Issue Type: Bug
> Components: binary
>Affects Versions: 2.5
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.7
>
>
> When trying to serialize humongous object in GridClientOptimizedMarshaller,
> NegativeArraySizeException thrown. See below
> {code:java}
> java.io.IOException: class org.apache.ignite.IgniteCheckedException: Failed
> to serialize object: GridClientResponse [clientId=null, reqId=0, destId=null,
> status=0, errMsg=null,
> result=org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest$HugeObject@60a582c1]
> at
> org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller.marshal(GridClientOptimizedMarshaller.java:101)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest.testHugeObject(TcpRestParserSelfTest.java:103)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2086)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2001)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> serialize object: GridClientResponse [clientId=null, reqId=0, destId=null,
> status=0, errMsg=null,
> result=org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest$HugeObject@60a582c1]
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedMarshaller.marshal0(OptimizedMarshaller.java:206)
> at
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.marshal(AbstractNodeNameAwareMarshaller.java:58)
> at
> org.apache.ignite.internal.util.IgniteUtils.marshal(IgniteUtils.java:10059)
> at
> org.apache.ignite.internal.client.marshaller.optimized.GridClientOptimizedMarshaller.marshal(GridClientOptimizedMarshaller.java:88)
> ... 10 more
> Caused by: java.lang.NegativeArraySizeException
> at
> org.apache.ignite.internal.util.io.GridUnsafeDataOutput.requestFreeSize(GridUnsafeDataOutput.java:131)
> at
> org.apache.ignite.internal.util.io.GridUnsafeDataOutput.write(GridUnsafeDataOutput.java:166)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.write(OptimizedObjectOutputStream.java:142)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.TcpRestParserSelfTest$HugeObject.writeExternal(TcpRestParserSelfTest.java:122)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeExternalizable(OptimizedObjectOutputStream.java:319)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:814)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:242)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObjectOverride(OptimizedObjectOutputStream.java:159)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
> at
> org.apache.ignite.internal.processors.rest.client.message.GridClientResponse.writeExternal(GridClientResponse.java:103)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeExternalizable(OptimizedObjectOutputStream.java:319)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedClassDescriptor.write(OptimizedClassDescriptor.java:814)
> at
> org.apache.ignite.internal.marshaller.optimized.OptimizedObjectOutputStream.writeObject0(OptimizedObjectOutputStream.java:242)
> at
>
[jira] [Updated] (IGNITE-3464) Possible race between partition exchange and prepare/finish requests
[ https://issues.apache.org/jira/browse/IGNITE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-3464: --- Fix Version/s: (was: 2.6) 2.7 > Possible race between partition exchange and prepare/finish requests > > > Key: IGNITE-3464 > URL: https://issues.apache.org/jira/browse/IGNITE-3464 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: ignite-1.4 >Reporter: Alexey Goncharuk >Assignee: Vitaliy Biryukov >Priority: Major > Fix For: 2.7 > > > Consider the following scenario: > Two nodes A (coordinator), B. Node C is joining the grid. Current topology > version is 2. > - Node A starts a transaction on version 2 and sends a prepare request to > node B > - Discovery event happens on node A. Exchange future is created, captures > the transaction and waits for this transaction to finish. > - Discovery event happens on node B. Exchange future is created, but since > there is no transaction on this node (the request has not been processed > yet), partition release future is completed and exchange waits for an ACK > from coordinator. > - Prepare request is processed on node B > - Node A commits the transaction locally, partition release future is > completed. Both finish request and exchange message are sent to the node B. > - Node B processes the exchange message first and completes exchange. > - Node C starts rebalancing from node B and acquires stale value of the key > which was supposed to be updated in the transaction. > - Node B processes finish request and commits the transaction. > As a result, node B and C have different values stored in the cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8403) [ML] Add Binary Logistic Regression based on partitioned datasets and MLP
[ https://issues.apache.org/jira/browse/IGNITE-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8403: --- Fix Version/s: (was: 2.6) 2.7 > [ML] Add Binary Logistic Regression based on partitioned datasets and MLP > - > > Key: IGNITE-8403 > URL: https://issues.apache.org/jira/browse/IGNITE-8403 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > Fix For: 2.7 > > > Add binary logistic regression implementation based on partitioned dataset > and MLP(Multi-layered perceptron) architecture with SGD (Stochastic Gradient > Descent). > Provide test, example, model and trainer -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc
[
https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8406:
---
Fix Version/s: (was: 2.6)
2.7
> Update IgniteDataStreamer.flush() javadoc
> -
>
> Key: IGNITE-8406
> URL: https://issues.apache.org/jira/browse/IGNITE-8406
> Project: Ignite
> Issue Type: Task
> Components: streaming
>Affects Versions: 2.4
>Reporter: Andrey Kuznetsov
>Assignee: Ivan Fedotov
>Priority: Minor
> Fix For: 2.7
>
>
> Current {{flush()}} implementation can throw {{CacheException}} if one or
> more futures previously returned by {{addData()}} have been completed
> exceptionally. This behavior should be described in {{IgniteDataStreamer}}
> javadoc. Also it's worth noting explicitly that all futures completion upon
> return from {{flush}} does not imply all those future listeners have been
> completed by this moment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
[
https://issues.apache.org/jira/browse/IGNITE-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7791:
---
Fix Version/s: (was: 2.6)
2.7
> Ignite Client Nodes: failed test
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
> Attachments: IgniteClientReconnectCacheDelayExchangeTest.java
>
>
> Test is flaky, success rate: 32.4%, test history is
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9174769196124217030=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertTrue(Assert.java:31)
> at junit.framework.TestCase.assertTrue(TestCase.java:201)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
> at
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36,
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null,
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1,
> lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:,
> isClient=false], topVer=6, nodeId8=658aeb36, msg=null,
> type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330,
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: 236160867
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAffinityChangeRequest(GridDhtPartitionsExchangeFuture.java:992)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:648)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
> at
>
[jira] [Updated] (IGNITE-7347) Warning about page eviction, when persistence for different data region is enabled
[
https://issues.apache.org/jira/browse/IGNITE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7347:
---
Fix Version/s: (was: 2.6)
2.7
> Warning about page eviction, when persistence for different data region is
> enabled
> --
>
> Key: IGNITE-7347
> URL: https://issues.apache.org/jira/browse/IGNITE-7347
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Mekhanikov
>Assignee: Denis Mekhanikov
>Priority: Trivial
> Fix For: 2.7
>
>
> Consider the following configuration:
> {noformat}
>
>
>
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
> It leads to the following warning on start: *Page eviction mode for
> \[B_Region\] memory region is ignored because Ignite Native Persistence is
> enabled*.
> But page eviction is actually applied and work as expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8706) IgnitePdsDataRegionMetricsTest#testMemoryUsageMultipleNodes fails in master
[ https://issues.apache.org/jira/browse/IGNITE-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8706: --- Fix Version/s: (was: 2.6) 2.7 > IgnitePdsDataRegionMetricsTest#testMemoryUsageMultipleNodes fails in master > --- > > Key: IGNITE-8706 > URL: https://issues.apache.org/jira/browse/IGNITE-8706 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > The test fails because FilePageStore decrements the pages metric after > allocated pages count is set to 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8141) Improve OS config suggestions: SWAPPINESS
[ https://issues.apache.org/jira/browse/IGNITE-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8141: --- Fix Version/s: (was: 2.6) 2.7 > Improve OS config suggestions: SWAPPINESS > - > > Key: IGNITE-8141 > URL: https://issues.apache.org/jira/browse/IGNITE-8141 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.4 >Reporter: Reed Sandberg >Assignee: Reed Sandberg >Priority: Minor > Labels: pull-request-available > Fix For: 2.7 > > > Acknowledge suggested SWAPPINESS OS param adjustment using a range (<= 10). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7973) TX SQL: plain INSERT should not be broadcasted to all data nodes
[
https://issues.apache.org/jira/browse/IGNITE-7973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7973:
---
Fix Version/s: (was: 2.6)
2.7
> TX SQL: plain INSERT should not be broadcasted to all data nodes
>
>
> Key: IGNITE-7973
> URL: https://issues.apache.org/jira/browse/IGNITE-7973
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.7
>
>
> At the moment all {{INSERT}} statements are broadcasted. This could be OK for
> {{INSERT ... SELECT}}, but is definitely not needed for {{INSERT ...
> VALUES}}. Instead we should construct final key-value pairs locally, and then
> send them to affected data nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-5954) Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails
[ https://issues.apache.org/jira/browse/IGNITE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5954: --- Fix Version/s: (was: 2.6) 2.7 > Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove > fails > -- > > Key: IGNITE-5954 > URL: https://issues.apache.org/jira/browse/IGNITE-5954 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Eduard Shangareev >Assignee: Alexey Kuznetsov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.7 > > > Probably, it's broken after IGNITE-5272. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8508) Zookeeper discovery SPI may notify custom message ACK with out-of-order topology version
[
https://issues.apache.org/jira/browse/IGNITE-8508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8508:
---
Fix Version/s: (was: 2.6)
2.7
> Zookeeper discovery SPI may notify custom message ACK with out-of-order
> topology version
>
>
> Key: IGNITE-8508
> URL: https://issues.apache.org/jira/browse/IGNITE-8508
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7
>
>
> I observed the following assertion in one of my tests.
> {code}
> java.lang.AssertionError: Topology version out of order [this.topVer=Snapshot
> [topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0]], topVer=4,
> node=ZookeeperClusterNode [id=2933aa95-0161-4a0d-aad8-274a7b887fae,
> addrs=[172.25.1.30, 172.17.0.1, 0:0:0:0:0:0:0:1%lo, 127.0.0.1], order=1,
> loc=true, client=false], nextTopVer=AffinityTopologyVersion [topVer=4,
> minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:746)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:589)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.notifyCustomEvent(ZookeeperDiscoveryImpl.java:3428)
> {code}
> The assertion happens because a custom event ACK is generated after another
> discovery message processing, which may lead to the following sequence of
> events:
> {code}
> Custom event (5, 1)
> Node Failed (6, 0)
> Custom event ACK (5, 1)
> {code}
> The root cause is ZK discovery using the original message topology version
> for notification. TCP discovery uses current ring topology version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6879) Support Spring Data 2.0
[ https://issues.apache.org/jira/browse/IGNITE-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6879: --- Fix Version/s: (was: 2.6) 2.7 > Support Spring Data 2.0 > --- > > Key: IGNITE-6879 > URL: https://issues.apache.org/jira/browse/IGNITE-6879 > Project: Ignite > Issue Type: Improvement > Components: spring >Affects Versions: 2.3 >Reporter: Alexey Kukushkin >Assignee: Roman Meerson >Priority: Major > Fix For: 2.7 > > > Ignite-spring and ignite-spring-data now use Spring 1.1 and cannot be rebuilt > with Spring 2.0. Trying to change the Spring dependency version to > 2.0.0.release results in compile errors like below and requires regression in > general. > This improvement was created to either migrate from Spring 1.1 to 2.0 or > create another set of modules ignite-spring-xxx-2 to have backward > compatibility with Spring 1.1. > [ERROR] > /Users/kukushal/Dev/incubator-ignite/modules/spring-data/src/main/java/org/apache/ignite/springdata/repository/IgniteRepository.java:[57,10] > name clash: deleteAll(java.lang.Iterable) in > org.apache.ignite.springdata.repository.IgniteRepository and > deleteAll(java.lang.Iterable) in > org.springframework.data.repository.CrudRepository have the same erasure, yet > neither overrides the other -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8577) Add MIGRATION_GUIDE file
[ https://issues.apache.org/jira/browse/IGNITE-8577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8577: --- Fix Version/s: (was: 2.6) 2.7 > Add MIGRATION_GUIDE file > > > Key: IGNITE-8577 > URL: https://issues.apache.org/jira/browse/IGNITE-8577 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > We are going to log all important changes in public API (deprecations, better > APIs, changes to default behavior) in separate document, called > "MIGRATION_GUIDE". > Need to create it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8610) Searching checkpoint / WAL history for rebalancing is not properly working in case of local/global WAL disabling
[ https://issues.apache.org/jira/browse/IGNITE-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8610: --- Fix Version/s: (was: 2.6) 2.7 > Searching checkpoint / WAL history for rebalancing is not properly working in > case of local/global WAL disabling > > > Key: IGNITE-8610 > URL: https://issues.apache.org/jira/browse/IGNITE-8610 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.7 > > > After implementation IGNITE-6411 and IGNITE-8087 we can face with situation > when after some checkpoint, WAL was temporarily disabled and enabled again. > In this case we can't treat that checkpoint as start point to rebalance, > because WAL history after such checkpoint may contain gaps. > We should rework our checkpoint / wal history searching mechanism and ignore > such checkpoints. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8800) Binary: add type name to an error when schema cannot be resolved
[ https://issues.apache.org/jira/browse/IGNITE-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8800: --- Fix Version/s: (was: 2.6) 2.7 > Binary: add type name to an error when schema cannot be resolved > > > Key: IGNITE-8800 > URL: https://issues.apache.org/jira/browse/IGNITE-8800 > Project: Ignite > Issue Type: Task > Components: binary >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > Currently we print only type ID and schema ID. Let's add type name and > existing schema IDs to error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8456) Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but persistence enabled
[ https://issues.apache.org/jira/browse/IGNITE-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8456: --- Fix Version/s: (was: 2.6) 2.7 > Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but > persistence enabled > -- > > Key: IGNITE-8456 > URL: https://issues.apache.org/jira/browse/IGNITE-8456 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Dmitriy Pavlov >Assignee: Ryabov Dmitrii >Priority: Critical > Labels: easyfix, newbie > Fix For: 2.7 > > > In method org.apache.ignite.internal.util.IgniteUtils#workDirectory > Ignite determine Work dir to be set, same value may be used in case > persistence Store Folder is not set and IGNITE_HOME is not specified. > In case work dir is not specified, temp directory is used for Ignite Work. > But for persistence enabled case this means user DB goes to temp folder and > may be removed later. > User may be confused by this behaviour. See: > [https://stackoverflow.com/questions/48434929/apache-ignite-persistent-storage] > and related Dev.List discussion > [http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-HOME-for-persistence-td26470.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8563) WAL file archiver does not propagate file archiving error to error handler
[
https://issues.apache.org/jira/browse/IGNITE-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8563:
---
Fix Version/s: (was: 2.6)
2.7
> WAL file archiver does not propagate file archiving error to error handler
> --
>
> Key: IGNITE-8563
> URL: https://issues.apache.org/jira/browse/IGNITE-8563
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.5
>Reporter: Alexey Goncharuk
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.7
>
>
> I observed this error when a disk with WAL archive left out of space:
> {code}
> ...
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:464)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:517)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:940)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:819)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:775)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:97)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:189)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:187)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1054)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:579)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:511)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.ignite.IgniteException: Runtime failure on row:
> Row@1ec13b23[ key: 4458000681143704309, val:
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2119)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2066)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:247)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:548)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:480)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:659)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1866)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:403)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:1393)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1257)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1511)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:352)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3602)
> at
>
[jira] [Updated] (IGNITE-6596) A safer way for user re-login in kerberized cluster
[ https://issues.apache.org/jira/browse/IGNITE-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6596: --- Fix Version/s: (was: 2.6) 2.7 > A safer way for user re-login in kerberized cluster > --- > > Key: IGNITE-6596 > URL: https://issues.apache.org/jira/browse/IGNITE-6596 > Project: Ignite > Issue Type: Bug > Components: hadoop >Affects Versions: 2.2 >Reporter: Reid Chan >Priority: Major > Fix For: 2.7 > > Attachments: IGNITE-6596.master.001.patch > > > I'm running kerberos related tests before putting ignite into productions. > And accidentally found that the re-login user (login through keytab), > somehow, was replaced by system-wide user (login through kinit). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8584) Provide ability to terminate any thread with enabled test features
[
https://issues.apache.org/jira/browse/IGNITE-8584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8584:
---
Fix Version/s: (was: 2.6)
2.7
> Provide ability to terminate any thread with enabled test features
> --
>
> Key: IGNITE-8584
> URL: https://issues.apache.org/jira/browse/IGNITE-8584
> Project: Ignite
> Issue Type: New Feature
>Reporter: Andrey Gura
>Assignee: Dmitriy Sorokin
>Priority: Major
> Fix For: 2.7
>
>
> eWe already have {{WorkersControlMXBean}} that provides possibility to
> interrupt thread registered in system workers registry. We also want stop any
> thread in the system for testing purposes.
> Method {{stop(long id)}} should be added that have to find thread by id and
> stop it.
> Example of thread information form thread dump where thread id is bold:
> "tcp-disco-msg-worker-#2" #*62* prio=10 os_prio=0 tid=0x7f2519714800
> nid=0x32b4 runnable [0x7f24a425]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7708) Ignite Compute has flaky failures
[
https://issues.apache.org/jira/browse/IGNITE-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7708:
---
Fix Version/s: (was: 2.6)
2.7
> Ignite Compute has flaky failures
> --
>
> Key: IGNITE-7708
> URL: https://issues.apache.org/jira/browse/IGNITE-7708
> Project: Ignite
> Issue Type: Bug
> Components: compute
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1093187=IgniteTests24Java8_IgniteComputeGrid
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1092214=IgniteTests24Java8_IgniteComputeGrid
> IgniteBinaryObjectsComputeGridTestSuite
> IgniteComputeBasicConfigVariationsFullApiTestSuite
> it is required to fix flaky failure or remove tests from suite because of
> default notifications were enabled recently.
> Flaky failures generates a lot of unecessary spam.
> {noformat}
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollection
> (fail rate 9%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollectionAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollection
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApply
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCall
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testExecuteTask
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyForCollectionWithReducerAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testAffinityCall
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastCallableAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastCallable
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollectionAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallCollectionWithReducer
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testExecuteTaskClassAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testBroadcastClosure
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testApplyAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testCallAsync
> (fail rate 8%)
>
> org.apache.ignite.testsuites.IgniteComputeBasicConfigVariationsFullApiTestSuite:
>
> org.apache.ignite.internal.processors.compute.IgniteComputeConfigVariationsFullApiTest.testDeployExecuteByName
>
[jira] [Updated] (IGNITE-6502) Need to output warning if -Djava.net.preferIPv4Stack=true is not set
[
https://issues.apache.org/jira/browse/IGNITE-6502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-6502:
---
Fix Version/s: (was: 2.6)
2.7
> Need to output warning if -Djava.net.preferIPv4Stack=true is not set
>
>
> Key: IGNITE-6502
> URL: https://issues.apache.org/jira/browse/IGNITE-6502
> Project: Ignite
> Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: vk
>Priority: Major
> Labels: usability
> Fix For: 2.7
>
>
> Some issues were reported on dev/user list that may be caused by ipv6 usage.
> I am not sure if Ignite can properly work with ipv6 networks. This needs to
> be tested and another issue has been filed -
> https://issues.apache.org/jira/browse/IGNITE-6503.
> For now it seems to be pretty handy just to have warning on node start:
> {noformat}
> Please set system property '-Djava.net.preferIPv4Stack=true' to avoid
> possible problems in mixed environments.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7585) GridDhtLockFuture related memory leak
[ https://issues.apache.org/jira/browse/IGNITE-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7585: --- Fix Version/s: (was: 2.6) 2.7 > GridDhtLockFuture related memory leak > - > > Key: IGNITE-7585 > URL: https://issues.apache.org/jira/browse/IGNITE-7585 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.7 > > Attachments: memleak.jpg > > > GridDhtLockFuture related LockTimeoutObject is not removed on commit, > resulting in tx reference until timeout handler is triggered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8709) CacheMBStatisticsBeanTest.testPutIfAbsent failed
[ https://issues.apache.org/jira/browse/IGNITE-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8709: --- Fix Version/s: (was: 2.6) 2.7 > CacheMBStatisticsBeanTest.testPutIfAbsent failed > > > Key: IGNITE-8709 > URL: https://issues.apache.org/jira/browse/IGNITE-8709 > Project: Ignite > Issue Type: Sub-task >Reporter: Alexander Menshikov >Assignee: Alexander Menshikov >Priority: Major > Labels: iep-21 > Fix For: 2.7 > > > Now Cache#putIfAbsent should change hit/miss statistic. > But test in TCK 1.0.1 was incorrect. > *So we can't make this test pass in both versions of TCK.* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7272) SQL TX: incorrect row MVCC version override during CREATE INDEX
[
https://issues.apache.org/jira/browse/IGNITE-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-7272:
---
Fix Version/s: (was: 2.6)
2.7
> SQL TX: incorrect row MVCC version override during CREATE INDEX
> ---
>
> Key: IGNITE-7272
> URL: https://issues.apache.org/jira/browse/IGNITE-7272
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.7
>
>
> Affected tests: {{DynamicIndexServerNodeFIlterBasicSelfTest}} and all
> siblings.
> Root cause: see {{IgniteH2Indexing#dynamicIndexCreate}}
> {code}
> if (rowDesc.context().mvccEnabled())
> row.mvccVersion(1, MVCC_START_CNTR);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8186) SQL: Create test base to cover sql by features with flexible configuration
[ https://issues.apache.org/jira/browse/IGNITE-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8186: --- Fix Version/s: (was: 2.6) 2.7 > SQL: Create test base to cover sql by features with flexible configuration > -- > > Key: IGNITE-8186 > URL: https://issues.apache.org/jira/browse/IGNITE-8186 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Pavel Kuznetsov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.7 > > > We need to cover sql feature by feature. > We need to be able to run the same test cases with different configurations. > At the moment configurations in scope: > 1) Inmemory/persistence > 2) Distributed joins: on/off > 3) Cache mode: PARTITIONED/REPLICATED > Features in scope: > 1) Simple SELECT > 2) JOIN (distributed and local) > 3) GROUP BY > Data model: > Employee (1000) > Department (50-100) > Status of distributed joins affects affinity key of data model. > Test cluster should contain 1 client and 2 server nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8252) NullPointerException is thrown during parallel massive start of nodes
[
https://issues.apache.org/jira/browse/IGNITE-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8252:
---
Fix Version/s: (was: 2.6)
2.7
> NullPointerException is thrown during parallel massive start of nodes
> -
>
> Key: IGNITE-8252
> URL: https://issues.apache.org/jira/browse/IGNITE-8252
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.7
>
>
> When many nodes are started in parallel and IGNITE_DISCOVERY_HISTORY_SIZE is
> set to too small value (smaller than size of batch of nodes joining the
> cluster simultaneously) NPE is thrown from the exchange thread:
> {noformat}
> [ERROR][exchange-worker-#62][GridDhtPartitionsExchangeFuture] Failed to
> reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=5,
> minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=ZookeeperClusterNode
> [id=2f412f7f-d326-4303-86f9-91004c82aa7b, addrs=[172.25.1.18], order=5,
> loc=true, client=false], topVer=5, nodeId8=2f412f7f, msg=null,
> type=NODE_JOINED, tstamp=1523571878505], nodeId=2f412f7f, evt=NODE_JOINED]
> java.lang.NullPointerException: null
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.getLatchCoordinator(ExchangeLatchManager.java:249)
> ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.getOrCreate(ExchangeLatchManager.java:207)
> ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.waitPartitionRelease(GridDhtPartitionsExchangeFuture.java:1227)
> ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1112)
> ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:713)
> [ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2414)
> [ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2294)
> [ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> [ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7968) IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed to acquire lock for keys
[ https://issues.apache.org/jira/browse/IGNITE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7968: --- Fix Version/s: (was: 2.6) 2.7 > IgniteAtomicSequence.incrementAndGet throws ClusterTopologyException: Failed > to acquire lock for keys > - > > Key: IGNITE-7968 > URL: https://issues.apache.org/jira/browse/IGNITE-7968 > Project: Ignite > Issue Type: Bug > Components: data structures >Affects Versions: 2.3, 2.4 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > Fix For: 2.7 > > Attachments: AtomicSeqAndClusterTopologyReproducer.java > > > When a primary node for a atomic sequnce has left cluster, > IgniteAtomicSequence.incrementAndGet could throw ClusterTopologyException. > The reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6679) Clean up some deprecated cache metrics
[ https://issues.apache.org/jira/browse/IGNITE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6679: --- Fix Version/s: (was: 2.6) 2.7 > Clean up some deprecated cache metrics > --- > > Key: IGNITE-6679 > URL: https://issues.apache.org/jira/browse/IGNITE-6679 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Sergey Puchnin >Assignee: Amelchev Nikita >Priority: Trivial > Labels: Newbie > Fix For: 2.7 > > > An old optimistic serializable mode implementation was removed in 2.0 but > some cache metrics still present in CacheMetrics interface. > Need to clean up and remove these metrics: > *TxCommitQueueSize* > *TxPrepareQueueSize* > *TxStartVersionCountsSize* > *TxDhtCommitQueueSize* > *TxDhtPrepareQueueSize* > *TxDhtStartVersionCountsSize* > An algorithm for page eviction was changed and metric > *DhtEvictQueueCurrentSize* should be removed also. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8826) Add missed licence to pom file
[ https://issues.apache.org/jira/browse/IGNITE-8826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8826: --- Fix Version/s: (was: 2.6) 2.7 > Add missed licence to pom file > -- > > Key: IGNITE-8826 > URL: https://issues.apache.org/jira/browse/IGNITE-8826 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Yury Babak >Assignee: Yury Babak >Priority: Major > Fix For: 2.7 > > > Add missed licence to modules\tensorflow\pom.xml -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-5945) Flaky failure in IgniteCache 5: IgniteCacheAtomicProtocolTest.testPutReaderUpdate2
[
https://issues.apache.org/jira/browse/IGNITE-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-5945:
---
Fix Version/s: (was: 2.6)
2.7
> Flaky failure in IgniteCache 5:
> IgniteCacheAtomicProtocolTest.testPutReaderUpdate2
> --
>
> Key: IGNITE-5945
> URL: https://issues.apache.org/jira/browse/IGNITE-5945
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Alexander Menshikov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest#testPutReaderUpdate2
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.Assert.assertFalse(Assert.java:47)
> at junit.framework.TestCase.assertFalse(TestCase.java:219)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest.readerUpdateDhtFails(IgniteCacheAtomicProtocolTest.java:865)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.IgniteCacheAtomicProtocolTest.testPutReaderUpdate2(IgniteCacheAtomicProtocolTest.java:765)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Fail is reproducable locally 2 times per 20 runs
> On TeamCity test success rate is 88,2%
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8659) Wrong FreeList usage in PendingTree may lead to page corruption.
[ https://issues.apache.org/jira/browse/IGNITE-8659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8659: --- Fix Version/s: (was: 2.6) 2.7 > Wrong FreeList usage in PendingTree may lead to page corruption. > > > Key: IGNITE-8659 > URL: https://issues.apache.org/jira/browse/IGNITE-8659 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > Fix For: 2.7 > > > Per-partition pending trees uses common index freelist. > This make possible partition data pages will be used by indices and lead to > errors as pages have different structures. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8668) K-fold cross validation of models
[ https://issues.apache.org/jira/browse/IGNITE-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8668: --- Fix Version/s: (was: 2.6) 2.7 > K-fold cross validation of models > - > > Key: IGNITE-8668 > URL: https://issues.apache.org/jira/browse/IGNITE-8668 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.7 > > > Cross validation is a well knows approach that allows to avoid overfitting > and therefore improve model quality. K-fold cross validation is based on > splitting dataset on _k_ disjoint subsets and using _k-1_ of them as train > subset and the remaining subset for test (with all possible combinations). > The goal of this task is to implement K-fold cross validation based on an > ability to filter dataset added recently in IGNITE-8666. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8836) NullPointerException during Ignition.start prevents JVM shutdown
[ https://issues.apache.org/jira/browse/IGNITE-8836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8836: --- Fix Version/s: (was: 2.6) 2.7 > NullPointerException during Ignition.start prevents JVM shutdown > > > Key: IGNITE-8836 > URL: https://issues.apache.org/jira/browse/IGNITE-8836 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.9, 2.4, 2.5 >Reporter: Anton Kurbanov >Assignee: Anton Kurbanov >Priority: Major > Fix For: 2.7 > > > The exception like below leaves node in stopping state forever: > java.lang.NullPointerException: null > at > java.util.concurrent.ConcurrentLinkedQueue.checkNotNull(ConcurrentLinkedQueue.java:914) > at > java.util.concurrent.ConcurrentLinkedQueue.offer(ConcurrentLinkedQueue.java:327) > at > java.util.concurrent.ConcurrentLinkedQueue.add(ConcurrentLinkedQueue.java:297) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKey(GridNearAtomicUpdateResponse.java:347) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicSingleUpdateFuture.addFailedKeys(GridDhtAtomicSingleUpdateFuture.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:446) > at > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.onDone(GridDhtAtomicAbstractUpdateFuture.java:56) > at > org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:345) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.cancelClientFutures(GridCacheMvccManager.java:388) > at > org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onStop(GridCacheMvccManager.java:370) > at > org.apache.ignite.internal.processors.cache.GridCacheProcessor.onKernalStop(GridCacheProcessor.java:956) > at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2095) > at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2041) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2397) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2360) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.run(IgnitionEx.java:1871) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8439) IGNITE_JETTY_HOST doesn't work (probably never has)
[ https://issues.apache.org/jira/browse/IGNITE-8439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8439: --- Fix Version/s: (was: 2.6) 2.7 > IGNITE_JETTY_HOST doesn't work (probably never has) > --- > > Key: IGNITE-8439 > URL: https://issues.apache.org/jira/browse/IGNITE-8439 > Project: Ignite > Issue Type: Bug > Components: rest >Affects Versions: 2.4 >Reporter: Paul Anderson >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > GridJettyRestProtocol.java > > public void start(GridRestProtocolHandler hnd) > ... > System.setProperty(IGNITE_JETTY_HOST, locHost.getHostAddress()) > ... > should be > if(System.getProperty(IGNITE_JETTY_HOST)==null) > System.setProperty(IGNITE_JETTY_HOST, locHost.getHostAddress()); -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8084) Unlock write lock in DataStreamerImpl
[ https://issues.apache.org/jira/browse/IGNITE-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8084: --- Fix Version/s: (was: 2.6) 2.7 > Unlock write lock in DataStreamerImpl > - > > Key: IGNITE-8084 > URL: https://issues.apache.org/jira/browse/IGNITE-8084 > Project: Ignite > Issue Type: Improvement > Components: streaming >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: usability > Fix For: 2.7 > > > In method DataStreamerImpl.CloseEx there is wrire lock without unlock [1]. I > think this behavior is based on impossibility to call after closing other > public method of DataStreamer, that use read lock. > It's not correctly that after closing streamer we don't unlock writeLock: I > think that we can use *closed* flag to throw exception if streamer will be > used after closing. > [1]https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastreamer/DataStreamerImpl.java#L1217 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8156) Ignite Compatibility: common improvements
[
https://issues.apache.org/jira/browse/IGNITE-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8156:
---
Fix Version/s: (was: 2.6)
2.7
> Ignite Compatibility: common improvements
> -
>
> Key: IGNITE-8156
> URL: https://issues.apache.org/jira/browse/IGNITE-8156
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.4
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Minor
> Labels: tests
> Fix For: 2.7
>
>
> Found issues in the 'compatibility' module:
> * classpath building process should be simplified
> * {{DummyPersistenceCompatibilityTest}} should be renamed or split
> * needs resolve code style issues
> * {{IgniteUuidCompatibilityTest}} should be removed. {{UUID type}} should be
> checked in common test
> * PDS's directory cleaning logic should be moved to
> {{IgniteCompatibilityAbstractTest}}
> * etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6936) SQL TX: Implement commit protocol
[ https://issues.apache.org/jira/browse/IGNITE-6936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-6936: --- Fix Version/s: (was: 2.6) 2.7 > SQL TX: Implement commit protocol > - > > Key: IGNITE-6936 > URL: https://issues.apache.org/jira/browse/IGNITE-6936 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov >Priority: Major > Labels: iep-3 > Fix For: 2.7 > > > Once we are able to lock entries [1], next step is to implement 2PC commit > protocol. Cache protocol could be used as a template. The main difference is > that near (client) node will not store entries. > [1] IGNITE-6935 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8701) If Thin Client authentication is disabled on cluster, JDBC Thin Driver disallows supplying of login/password
[
https://issues.apache.org/jira/browse/IGNITE-8701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8701:
---
Fix Version/s: (was: 2.6)
2.7
> If Thin Client authentication is disabled on cluster, JDBC Thin Driver
> disallows supplying of login/password
>
>
> Key: IGNITE-8701
> URL: https://issues.apache.org/jira/browse/IGNITE-8701
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Affects Versions: 2.5
>Reporter: Ilya Kasnacheev
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 2.7
>
>
> Previously, Ignite JDBC clients would just ignore supplied login and password.
> In 2.5, Ignite Thin JDBC driver will instead fail with following error:
> {code}
> The requested operation could not be performed due to the following error :
> Handshake failed [driverProtocolVer=ClientListenerProtocolVersion [major=2,
> minor=5, maintenance=0], remoteNodeProtocolVer=ClientListenerProtocolVersion
> [major=2, minor=5, maintenance=0], err=Handshake error: Can not perform the
> operation because the authentication is not enabled for the cluster.]
> {code}
> when connecting to the cluster where authentication is disabled.
> This represents a *breaking change* in Apache Ignite API.
> Note that many tools (such as Informatica) insist on providing non-blank
> username and-or password for JDBC connections. This will mean they *no longer
> work* with Apache Ignite with no apparent workaround.
> My suggestion is to ignore login/password for JDBC Thin connections when
> authentication is not enabled for cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8480) Broken Ignite Examples test Support Spring Data 2.0
[ https://issues.apache.org/jira/browse/IGNITE-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8480: --- Fix Version/s: (was: 2.6) 2.7 > Broken Ignite Examples test Support Spring Data 2.0 > --- > > Key: IGNITE-8480 > URL: https://issues.apache.org/jira/browse/IGNITE-8480 > Project: Ignite > Issue Type: Test > Components: spring >Affects Versions: 2.6 >Reporter: Dmitriy Pavlov >Assignee: Roman Meerson >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test > Fix For: 2.7 > > > https://issues.apache.org/jira/browse/IGNITE-6879 implementation was > introduced support of spring data of version 2.0+ > > But example test is broken on TC after this change > [Examples > |https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples=%3Cdefault%3E=buildTypeStatusDiv] > IgniteExamplesSelfTestSuite: > SpringDataExampleSelfTest.testSpringDataExample > > Test history: > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9052304574499269123=%3Cdefault%3E=testDetails] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8808) Improve control.sh --tx command to show local and remote transactions.
[ https://issues.apache.org/jira/browse/IGNITE-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8808: --- Fix Version/s: (was: 2.6) 2.7 > Improve control.sh --tx command to show local and remote transactions. > -- > > Key: IGNITE-8808 > URL: https://issues.apache.org/jira/browse/IGNITE-8808 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.7 > > > Currently --tx option for control.sh shows only transactions found on > near(initiating) nodes. > Due to various issues it's possible to have corresponding dht local and > remote transaction without near part. > Such transactions must be visible to utility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8690) Missed package-info for some packages
[
https://issues.apache.org/jira/browse/IGNITE-8690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8690:
---
Fix Version/s: (was: 2.6)
2.7
> Missed package-info for some packages
> -
>
> Key: IGNITE-8690
> URL: https://issues.apache.org/jira/browse/IGNITE-8690
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Pavel Kovalenko
>Priority: Major
> Fix For: 2.7
>
>
> List of affected packages:
> {noformat}
> org.apache.ignite.spi.communication.tcp.internal
> org.apache.ignite.spi.discovery.zk
> org.apache.ignite.spi.discovery.zk.internal
> org.apache.ignite.ml.structures.partition
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-5136) GridLogThrottle memory leak
[ https://issues.apache.org/jira/browse/IGNITE-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-5136: --- Fix Version/s: (was: 2.6) 2.7 > GridLogThrottle memory leak > --- > > Key: IGNITE-5136 > URL: https://issues.apache.org/jira/browse/IGNITE-5136 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Stanilovsky Evgeny >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.7 > > > class GridLogThrottle stores throttle info into map and noone clears it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
