[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594558#comment-16594558 ] Saikat Maitra commented on IGNITE-3303: --- [~amashenkov] Thank you for reviewing the changes. I have incorporated the changes. Please review and let me know if any changes required. Regards, Saikat > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Priority: Major > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log, win7.PNG > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9382) Node.js fails to process large payloads
[ https://issues.apache.org/jira/browse/IGNITE-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594355#comment-16594355 ] Toru Yabuki commented on IGNITE-9382: - [~alexey.kosenchuk] yes, I fixed! > Node.js fails to process large payloads > --- > > Key: IGNITE-9382 > URL: https://issues.apache.org/jira/browse/IGNITE-9382 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Roman Shtykh >Assignee: Toru Yabuki >Priority: Major > > Looks like finalizing response is done too early. > This can be easily checked with an SQL _limit_ 1 and _limit 100_. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9382) Node.js fails to process large payloads
[ https://issues.apache.org/jira/browse/IGNITE-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594356#comment-16594356 ] Toru Yabuki commented on IGNITE-9382: - Event 'data' of Net.Socket is called multiple times when data comes in more than one chunk. It occurs when handling a large data (eg. 2896+ bytes in my test) But now, it works only at first chunk. I think we should collect all the data, and then process it. This is my patch. https://github.com/apache/ignite/pull/4629 > Node.js fails to process large payloads > --- > > Key: IGNITE-9382 > URL: https://issues.apache.org/jira/browse/IGNITE-9382 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Roman Shtykh >Assignee: Toru Yabuki >Priority: Major > > Looks like finalizing response is done too early. > This can be easily checked with an SQL _limit_ 1 and _limit 100_. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9382) Node.js fails to process large payloads
[ https://issues.apache.org/jira/browse/IGNITE-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594352#comment-16594352 ] ASF GitHub Bot commented on IGNITE-9382: GitHub user tyabuki opened a pull request: https://github.com/apache/ignite/pull/4629 IGNITE-9382 Fixed data handling for multiple chunks of data You can merge this pull request into a Git repository by running: $ git pull https://github.com/tyabuki/ignite ignite-9382 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4629.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4629 commit 92ef9dfcb779c2a8b171a2dc691bd6d64c5b78ee Author: Toru Yabuki Date: 2018-08-23T10:28:41Z IGNITE-9382 Fixed data handling for multiple chunks of data > Node.js fails to process large payloads > --- > > Key: IGNITE-9382 > URL: https://issues.apache.org/jira/browse/IGNITE-9382 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Roman Shtykh >Assignee: Toru Yabuki >Priority: Major > > Looks like finalizing response is done too early. > This can be easily checked with an SQL _limit_ 1 and _limit 100_. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9305) Wrong off-heap size is reported for a node
[
https://issues.apache.org/jira/browse/IGNITE-9305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594258#comment-16594258
]
Pavel Pereslegin commented on IGNITE-9305:
--
[~dmagda], is this format ok?
> Wrong off-heap size is reported for a node
> --
>
> Key: IGNITE-9305
> URL: https://issues.apache.org/jira/browse/IGNITE-9305
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.6
>Reporter: Denis Magda
>Assignee: Pavel Pereslegin
>Priority: Blocker
> Fix For: 2.7
>
>
> Was troubleshooting an Ignite deployment today and couldn't find out from the
> logs what was the actual off-heap space used.
> Those were the given memory resoures (Ignite 2.6):
> {code}
> [2018-08-16 15:07:49,961][INFO ][main][GridDiscoveryManager] Topology
> snapshot [ver=1, servers=1, clients=0, CPUs=64, offheap=30.0GB, heap=24.0GB]
> {code}
> And that weird stuff was reported by the node (pay attention to the last
> line):
> {code}
> [2018-08-16 15:45:50,211][INFO
> ][grid-timeout-worker-#135%cluster_31-Dec-2017%][IgniteKernal%cluster_31-Dec-2017]
>
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=c033026e, name=cluster_31-Dec-2017, uptime=00:38:00.257]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=64]
> ^-- CPU [cur=0.03%, avg=5.54%, GC=0%]
> ^-- PageMemory [pages=6997377]
> ^-- Heap [used=9706MB, free=61.18%, comm=22384MB]
> ^-- Non heap [used=144MB, free=-1%, comm=148MB] - this line is always the
> same!
> {code}
> Had to change the code by using
> {code}dataRegion.getPhysicalMemoryPages(){code} to find out that actual
> off-heap usage size was
> {code}
> >>> Physical Memory Size: 28651614208 => 27324 MB, 26 GB
> {code}
> The logs have to report the following instead:
> {code}
> ^-- Off-heap {Data Region 1} [used={dataRegion1.getPhysicalMemorySize()},
> free=X%, comm=dataRegion1.maxSize()]
> ^-- Off-heap {Data Region 2} [used={dataRegion2.getPhysicalMemorySize()},
> free=X%, comm=dataRegion2.maxSize()]
> {code}
> If Ignite persistence is enabled then the following extra lines have to be
> added to see the disk used space:
> {code}
> ^-- Ignite persistence {Data Region 1}:
> used={dataRegion1.getTotalAllocatedSize() -
> dataRegion1.getPhysicalMemorySize()}
> ^-- Ignite persistence {Data Region 2}
> [used={dataRegion2.getTotalAllocatedSize() -
> dataRegion2.getPhysicalMemorySize()}]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9393) [ML] KMeans fails on complex data in cache
[ https://issues.apache.org/jira/browse/IGNITE-9393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594028#comment-16594028 ] ASF GitHub Bot commented on IGNITE-9393: GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/4628 IGNITE-9393: Fixed bug in reduce function in dataset.compute You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9393 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4628.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4628 commit 96fffa56cd0b334a1dd3b678b68bc9224f5b4c02 Author: Zinoviev Alexey Date: 2018-08-27T17:44:07Z IGNITE-8924: Result of merge > [ML] KMeans fails on complex data in cache > -- > > Key: IGNITE-9393 > URL: https://issues.apache.org/jira/browse/IGNITE-9393 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Aleksey Zinoviev >Assignee: Aleksey Zinoviev >Priority: Major > > Described here > http://apache-ignite-users.70518.x6.nabble.com/NPE-exception-in-KMeansTrainer-td23504.html#a23512 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7259) GridIndexRebuildSelfTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593933#comment-16593933 ] ASF GitHub Bot commented on IGNITE-7259: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/4627 IGNITE-7259: tests fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-7259 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4627.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4627 commit 04f94948bbd89136d4555a2e3fccd9367169 Author: Igor Seliverstov Date: 2017-12-27T14:04:58Z IGNITE-7321 DML operation hangs in case exception is thrown from DHT enlist future commit 3818bc9d74b2bba594ef89cc2d1ac975da816b54 Author: Igor Seliverstov Date: 2017-12-27T14:33:18Z fix tests. commit eb7a615c9d32e648eceeafb09893b226fe276467 Author: Igor Seliverstov Date: 2017-12-27T14:47:39Z fix exception types. commit f4ce065ce863a741e0d14901e087ff69856b7d9f Author: Alexander Paschenko Date: 2017-12-27T16:23:23Z Merge branch 'master' into ignite-5571 commit 73bedeb4979d5474be654c6f8f80c168c9a0606f Author: Alexander Paschenko Date: 2017-12-27T19:00:36Z IGNITE-5571 More tests commit ccf16fcc4d819e33b71a3322ae99d48755ee6b76 Author: Alexander Paschenko Date: 2017-12-28T07:49:25Z IGNITE-7259: Fixed GridIndexRebuildSelfTest. This closes #3304. commit 53466fc059d027edb24b3d7f5da05b6be2e997fc Author: Igor Seliverstov Date: 2017-12-28T11:24:16Z fix partition checking. commit b9aa9ebca0dca79fec278415beb5753ef49a4c60 Author: Igor Seliverstov Date: 2017-12-29T12:18:30Z fix mvcc version checking on lock acquire commit a86af95ea1ee08c2f66751a8e2fc440e4671d686 Author: Igor Seliverstov Date: 2018-01-11T12:45:02Z TODOs, right tickets numbers, minors commit 59ba16afcab00326a60f53b3a7592d2978f19313 Author: Igor Seliverstov Date: 2018-01-11T14:45:53Z Merge branch 'master' into ignite-4191-master commit 79d876bce306802bf097a69030e1fcca61cec859 Author: Igor Seliverstov Date: 2018-01-11T14:49:22Z Merge branch 'master' into ignite-4191-master commit 9bd874c8d132f23842ae4bf8caa2c633b42b0789 Author: Igor Seliverstov Date: 2018-01-11T14:52:15Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java commit cbae5040399f433c0689df76e697df5a637ca1bc Author: Igor Seliverstov Date: 2018-01-11T15:29:13Z Disable DROP COLUMN with enabled mvcc commit c5bb6c68a3faf9f236ae8a1639bfaf495c825eb7 Author: Igor Seliverstov Date: 2018-01-12T09:09:52Z Merge branch 'master' into ignite-4191-master commit 02f4ffa82a6ebaaaeaf96c31f15c4e8191c188d0 Author: Igor Seliverstov Date: 2018-01-12T09:23:00Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/JdbcThinTcpIo.java # modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcConnectionContext.java # modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite.java commit 21f9acdee409265f98893a2910e04effa63bcc2d Author: Igor Seliverstov Date: 2018-01-12T10:34:45Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheOffheapManager.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/H2Tree.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/H2TreeIndex.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2ExtrasInnerIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2ExtrasLeafIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2InnerIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2LeafIO.java commit 5684b7224d077e285af35c5741d50332dec31eae Author: Igor Seliverstov Date: 2018-01-12T10:36:04Z Merge branch 'master' into ignite-4191-master commit 284c4335897fc82388baa99c960693b59a460e61 Author: Alexander Paschenko Date: 2018-01-17T09:20:35Z Merge remote-tracking branch 'apache/master' into ignite-5571 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcRequestHandler.java #
[jira] [Updated] (IGNITE-8318) MVCC TX: Scan query call throws an exception when it is mixed with Key-Value API in the same transaction.
[
https://issues.apache.org/jira/browse/IGNITE-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-8318:
-
Description:
Scan queries should not throw Exceptions in key-value API transactions.
Reproducer: {{CacheMvccTransactionsTest#testPutAllGetAll_SingleNode_Scan}}
This should fix
org.apache.ignite.internal.processors.cache.mvcc.CacheMvccTransactionsTest.testCleanupWaitsForGet1()
as well.
was:
Scan queries should not throw Exceptions in key-value API transactions.
Reproducer: {{CacheMvccTransactionsTest#testPutAllGetAll_SingleNode_Scan}}
> MVCC TX: Scan query call throws an exception when it is mixed with Key-Value
> API in the same transaction.
> --
>
> Key: IGNITE-8318
> URL: https://issues.apache.org/jira/browse/IGNITE-8318
> Project: Ignite
> Issue Type: Bug
> Components: cache, mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
>
> Scan queries should not throw Exceptions in key-value API transactions.
> Reproducer: {{CacheMvccTransactionsTest#testPutAllGetAll_SingleNode_Scan}}
>
> This should fix
> org.apache.ignite.internal.processors.cache.mvcc.CacheMvccTransactionsTest.testCleanupWaitsForGet1()
> as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7259) GridIndexRebuildSelfTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593894#comment-16593894 ] Andrew Mashenkov commented on IGNITE-7259: -- PFA Thread dumps attached. > GridIndexRebuildSelfTest hangs > -- > > Key: IGNITE-7259 > URL: https://issues.apache.org/jira/browse/IGNITE-7259 > Project: Ignite > Issue Type: Task > Components: mvcc, sql >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.7 > > Attachments: deadlock-thread-dumps.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9389) Concurrent Cache#close and put/get operations lead to a deadlock
[ https://issues.apache.org/jira/browse/IGNITE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593893#comment-16593893 ] ASF GitHub Bot commented on IGNITE-9389: GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/4626 IGNITE-9389 Avoid deadlocks on cache#close() You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9389 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4626.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4626 commit 18bf109f386ea87470f9371faeafd7e2104e09b4 Author: Denis Mekhanikov Date: 2018-08-27T16:13:57Z IGNITE-9389 Add test. commit 3321f77bd7242ec0a26002bee152bf6522943586 Author: Denis Mekhanikov Date: 2018-08-27T16:16:16Z IGNITE-9389 Avoid deadlock on cache#close(). > Concurrent Cache#close and put/get operations lead to a deadlock > > > Key: IGNITE-9389 > URL: https://issues.apache.org/jira/browse/IGNITE-9389 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.6 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Attachments: CacheConcurrentUseAndCloseTest.java > > > When cache is closed on a client node, while it is being used concurrently in > other threads, deadlock may occur. > Test case, reproducing the problem is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7259) GridIndexRebuildSelfTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-7259: - Attachment: deadlock-thread-dumps.txt > GridIndexRebuildSelfTest hangs > -- > > Key: IGNITE-7259 > URL: https://issues.apache.org/jira/browse/IGNITE-7259 > Project: Ignite > Issue Type: Task > Components: mvcc, sql >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.7 > > Attachments: deadlock-thread-dumps.txt > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[ https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593872#comment-16593872 ] ASF GitHub Bot commented on IGNITE-9183: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4483 > Proper handling UUID columns, that are added by DDL. > > > Key: IGNITE-9183 > URL: https://issues.apache.org/jira/browse/IGNITE-9183 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5, 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.7 > > > Currently, if we added new UUID columnt thru DDL, it is saved to schema as > byte[]. So it's impossible to use it with DML without placeholders and put > values thru cache api without converting UUID to byte[]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[ https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-9183. - Resolution: Fixed > Proper handling UUID columns, that are added by DDL. > > > Key: IGNITE-9183 > URL: https://issues.apache.org/jira/browse/IGNITE-9183 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5, 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.7 > > > Currently, if we added new UUID columnt thru DDL, it is saved to schema as > byte[]. So it's impossible to use it with DML without placeholders and put > values thru cache api without converting UUID to byte[]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[ https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reopened IGNITE-9183: - > Proper handling UUID columns, that are added by DDL. > > > Key: IGNITE-9183 > URL: https://issues.apache.org/jira/browse/IGNITE-9183 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5, 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.7 > > > Currently, if we added new UUID columnt thru DDL, it is saved to schema as > byte[]. So it's impossible to use it with DML without placeholders and put > values thru cache api without converting UUID to byte[]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9389) Concurrent Cache#close and put/get operations lead to a deadlock
[ https://issues.apache.org/jira/browse/IGNITE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Mekhanikov reassigned IGNITE-9389: Assignee: Denis Mekhanikov > Concurrent Cache#close and put/get operations lead to a deadlock > > > Key: IGNITE-9389 > URL: https://issues.apache.org/jira/browse/IGNITE-9389 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.6 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Attachments: CacheConcurrentUseAndCloseTest.java > > > When cache is closed on a client node, while it is being used concurrently in > other threads, deadlock may occur. > Test case, reproducing the problem is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7259) GridIndexRebuildSelfTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593832#comment-16593832 ] Andrew Mashenkov commented on IGNITE-7259: -- Wrong lock order is the issue here. GridIndexRebuildSelfTest.putData() acquires semaphore permit and then update an entry under lock, while SchemaIndexCacheVisitorImpl calls TestRebuildClosure under entry lock and waits for permits become available inside the closure. Seems, we should either force visitor to revisit a row or rethink if semaphore is really needed here. > GridIndexRebuildSelfTest hangs > -- > > Key: IGNITE-7259 > URL: https://issues.apache.org/jira/browse/IGNITE-7259 > Project: Ignite > Issue Type: Task > Components: mvcc, sql >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9256) SQL: make sure that fetched results are cleared from iterator when last element is fetched
[
https://issues.apache.org/jira/browse/IGNITE-9256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593829#comment-16593829
]
Sergey Grimstad commented on IGNITE-9256:
-
Fixed, tests added, TC tested
https://ci.ignite.apache.org/viewLog.html?buildId=1724673;
> SQL: make sure that fetched results are cleared from iterator when last
> element is fetched
> --
>
> Key: IGNITE-9256
> URL: https://issues.apache.org/jira/browse/IGNITE-9256
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Vladimir Ozerov
>Assignee: Sergey Grimstad
>Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
> Attachments: IGNITE-9256__Implemented.patch
>
>
> In practice it is possible for user to forget to nullify Ignite's result set
> after iteration is finished. Or he may delay cleanup for some reason.
> The problem is that we hold the whole H2's result set inside our iterator
> even after all results are delivered to the user.
> We should forcibly close and then nullify all H2 objects once all results are
> returned.
> Key code pieces:
> {{IgniteH2Indexing.executeSqlQueryWithTimer}} - how we get result from H2
> {{H2ResultSetIterator}} - base iterator with H2 objects inside
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8337) Java ThinClient benchmark for yardstick
[ https://issues.apache.org/jira/browse/IGNITE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593796#comment-16593796 ] Andrey Gura commented on IGNITE-8337: - [~oleg-ostanin] LGTM. Merged to master branch. Thanks for contribution! > Java ThinClient benchmark for yardstick > --- > > Key: IGNITE-8337 > URL: https://issues.apache.org/jira/browse/IGNITE-8337 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Sergey Kozlov >Assignee: Oleg Ostanin >Priority: Major > Fix For: 2.7 > > > Version 2.4 introduced new binary protocol thus we need to add put, put-get, > put-all benchmarks for Yardstick for both atomic, tx caches. > Take the data models, the load profiles from regular benchmarks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8337) Java ThinClient benchmark for yardstick
[ https://issues.apache.org/jira/browse/IGNITE-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-8337. - Resolution: Fixed > Java ThinClient benchmark for yardstick > --- > > Key: IGNITE-8337 > URL: https://issues.apache.org/jira/browse/IGNITE-8337 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.4 >Reporter: Sergey Kozlov >Assignee: Oleg Ostanin >Priority: Major > Fix For: 2.7 > > > Version 2.4 introduced new binary protocol thus we need to add put, put-get, > put-all benchmarks for Yardstick for both atomic, tx caches. > Take the data models, the load profiles from regular benchmarks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9382) Node.js fails to process large payloads
[ https://issues.apache.org/jira/browse/IGNITE-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593771#comment-16593771 ] Alexey Kosenchuk commented on IGNITE-9382: -- [~tyabuki] do you already have a fix for the nodejs thin client? If not, we will fix it today-tomorrow, if you don't mind. > Node.js fails to process large payloads > --- > > Key: IGNITE-9382 > URL: https://issues.apache.org/jira/browse/IGNITE-9382 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Roman Shtykh >Assignee: Toru Yabuki >Priority: Major > > Looks like finalizing response is done too early. > This can be easily checked with an SQL _limit_ 1 and _limit 100_. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9393) [ML] KMeans fails on complex data in cache
Aleksey Zinoviev created IGNITE-9393: Summary: [ML] KMeans fails on complex data in cache Key: IGNITE-9393 URL: https://issues.apache.org/jira/browse/IGNITE-9393 Project: Ignite Issue Type: Bug Components: ml Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Described here http://apache-ignite-users.70518.x6.nabble.com/NPE-exception-in-KMeansTrainer-td23504.html#a23512 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC
[ https://issues.apache.org/jira/browse/IGNITE-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593753#comment-16593753 ] ASF GitHub Bot commented on IGNITE-9392: GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/4625 IGNITE-9392 : Specified TX timeout in test configuration. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9392 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4625.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4625 commit 3ffc1065787ea67f4f07f9882fc9401062cc0f8e Author: Ilya Lantukh Date: 2018-08-27T14:31:37Z IGNITE-9392 : Specified TX timeout in test configuration. > CacheAsyncOperationsFailoverTxTest hangs on TC > -- > > Key: IGNITE-9392 > URL: https://issues.apache.org/jira/browse/IGNITE-9392 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Lantukh >Assignee: Ilya Lantukh >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9392) CacheAsyncOperationsFailoverTxTest hangs on TC
Ilya Lantukh created IGNITE-9392: Summary: CacheAsyncOperationsFailoverTxTest hangs on TC Key: IGNITE-9392 URL: https://issues.apache.org/jira/browse/IGNITE-9392 Project: Ignite Issue Type: Bug Reporter: Ilya Lantukh Assignee: Ilya Lantukh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9233) MVCC SQL: False write conflicts on fast updates
[ https://issues.apache.org/jira/browse/IGNITE-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16588496#comment-16588496 ] Ivan Pavlukhin edited comment on IGNITE-9233 at 8/27/18 2:20 PM: - MERGE behavior was broken in such way that it acts like UPDATE. was (Author: pavlukhin): MERGE behavior was broken it such way that it acts like UPDATE. > MVCC SQL: False write conflicts on fast updates > --- > > Key: IGNITE-9233 > URL: https://issues.apache.org/jira/browse/IGNITE-9233 > Project: Ignite > Issue Type: Bug > Components: mvcc, sql >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Attachments: MvccInsertDeleteConcurrent.java > > > Currently is possible to encounter query failure e.g. in case when DELETE > with directly specified key encounters write conflict for row which is > created by concurrent INSERT. From SNAPSHOT isolation point of view DELETE > either should not see a row and do nothing or should remove a row gracefully. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9391) Incorrect calculated esitmated rebalancing finish time
[ https://issues.apache.org/jira/browse/IGNITE-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593717#comment-16593717 ] ASF GitHub Bot commented on IGNITE-9391: GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/4624 IGNITE-9391 added checking result on waitForCondition in testRebalanc… …eEstimateFinishTime You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9391 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4624.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4624 commit d7fa9496f5976107d4ba96b721170a430f9e1d35 Author: Anton Kalashnikov Date: 2018-08-27T14:14:00Z IGNITE-9391 added checking result on waitForCondition in testRebalanceEstimateFinishTime > Incorrect calculated esitmated rebalancing finish time > -- > > Key: IGNITE-9391 > URL: https://issues.apache.org/jira/browse/IGNITE-9391 > Project: Ignite > Issue Type: Test >Reporter: Anton Kalashnikov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Actually looks like test > CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime is incorrect > or we have bug in esitmated rebalancing finish time calculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9391) Incorrect calculated esitmated rebalancing finish time
[ https://issues.apache.org/jira/browse/IGNITE-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kalashnikov updated IGNITE-9391: -- Summary: Incorrect calculated esitmated rebalancing finish time (was: Incorrect calculated esitmated rabalancing finish time) > Incorrect calculated esitmated rebalancing finish time > -- > > Key: IGNITE-9391 > URL: https://issues.apache.org/jira/browse/IGNITE-9391 > Project: Ignite > Issue Type: Test >Reporter: Anton Kalashnikov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Actually looks like test > CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime is incorrect > or we have bug in esitmated rebalancing finish time calculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9391) Incorrect calculated esitmated rabalancing finish time
[ https://issues.apache.org/jira/browse/IGNITE-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kalashnikov updated IGNITE-9391: -- Description: Actually looks like test CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime is incorrect or we have bug in esitmated rebalancing finish time calculation. (was: Actually looks like test CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime is incorrect or we have bug in esitmated rabalancing finish time calculation.) > Incorrect calculated esitmated rabalancing finish time > -- > > Key: IGNITE-9391 > URL: https://issues.apache.org/jira/browse/IGNITE-9391 > Project: Ignite > Issue Type: Test >Reporter: Anton Kalashnikov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Actually looks like test > CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime is incorrect > or we have bug in esitmated rebalancing finish time calculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9391) Incorrect calculated esitmated rabalancing finish time
Anton Kalashnikov created IGNITE-9391: - Summary: Incorrect calculated esitmated rabalancing finish time Key: IGNITE-9391 URL: https://issues.apache.org/jira/browse/IGNITE-9391 Project: Ignite Issue Type: Test Reporter: Anton Kalashnikov Actually looks like test CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime is incorrect or we have bug in esitmated rabalancing finish time calculation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9333) Adding page with simple statistic for last 50 runs.
[ https://issues.apache.org/jira/browse/IGNITE-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593706#comment-16593706 ] ASF GitHub Bot commented on IGNITE-9333: zzzadruga opened a new pull request #3: IGNITE-9333 Add statistics page URL: https://github.com/apache/ignite-teamcity-bot/pull/3 This is a draft version This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Adding page with simple statistic for last 50 runs. > --- > > Key: IGNITE-9333 > URL: https://issues.apache.org/jira/browse/IGNITE-9333 > Project: Ignite > Issue Type: Sub-task >Reporter: Eduard Shangareev >Assignee: Nikolai Kulagin >Priority: Major > > Ok, I am proposing to add a new page which would be named "Statistic". > It should show last 50 "Run All" for master, the columns: > ||Id||Total tests||Failed tests||Ignored tests|| Muted tests||Total issues > (count and the list of TC configurations with links) || Total run time || > Also, we need to calculate the statistic. > Totals (all unique tests with issues), average issues/fails per run, median, > max, min. > Total issues = Exit codes + JVM Crashes + OOMs + other issues which caused TC > configuration fail -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4150) B-Tree index cannot be used efficiently with IN clause.
[
https://issues.apache.org/jira/browse/IGNITE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-4150:
Labels: performance (was: performance sql-stability)
> B-Tree index cannot be used efficiently with IN clause.
> ---
>
> Key: IGNITE-4150
> URL: https://issues.apache.org/jira/browse/IGNITE-4150
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: performance
> Fix For: 2.7
>
>
> Consider the following query:
> {code}
> SELECT * FROM table
> WHERE a = ? AND b IN (?, ?)
> {code}
> If there is an index {{(a, b)}}, it will not be used properly: only column
> {{a}} will be used. This will leads to multiple unnecessary comparisons.
> Most obvious way to fix that - use temporary table and {{JOIN}}. However,
> this approach doesn't work well when there are multiple {{IN}}'s.
> Proper solution would be to hack deeper into H2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9390) MVCC: add MVCC support to .NET configuration.
Andrew Mashenkov created IGNITE-9390: Summary: MVCC: add MVCC support to .NET configuration. Key: IGNITE-9390 URL: https://issues.apache.org/jira/browse/IGNITE-9390 Project: Ignite Issue Type: Improvement Components: mvcc, platforms Reporter: Andrew Mashenkov Fix For: 2.7 We should make MVCC configurable from .NET client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9389) Concurrent Cache#close and put/get operations lead to a deadlock
Denis Mekhanikov created IGNITE-9389: Summary: Concurrent Cache#close and put/get operations lead to a deadlock Key: IGNITE-9389 URL: https://issues.apache.org/jira/browse/IGNITE-9389 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.6 Reporter: Denis Mekhanikov Attachments: CacheConcurrentUseAndCloseTest.java When cache is closed on a client node, while it is being used concurrently in other threads, deadlock may occur. Test case, reproducing the problem is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9267) Deadlock between unsuccessful client reconnecting and stopping.
[
https://issues.apache.org/jira/browse/IGNITE-9267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593611#comment-16593611
]
ASF GitHub Bot commented on IGNITE-9267:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4552
> Deadlock between unsuccessful client reconnecting and stopping.
> ---
>
> Key: IGNITE-9267
> URL: https://issues.apache.org/jira/browse/IGNITE-9267
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Fix For: 2.7
>
>
> *T1* start reconnecting and acquire *stateMux*
> (ZookeeperDiscoveryImpl#processLocalJoin) -> *T2* start stopping and acquire
> *IgnitionEx.this* (IgnitionEx#stop0) -> *T2* stopping ZookeeperDiscoveryImpl
> and wait for *stateMux* -> *T1* fails on reconnecting and start to stopping
> node and wait for *IgnitionEx.this*.
> Reconnecting thread:
> {noformat}
> "zk-internal.IgniteClientReconnectCacheTest3-EventThread" #593633 daemon
> prio=5 os_prio=0 tid=0x7ff8e4063800 nid=0x478e waiting for monitor entry
> [0x7ff90f2f]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2565)
> - waiting to lock <0xe9429280> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2557)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
> at org.apache.ignite.Ignition.stop(Ignition.java:229)
> at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3417)
> at
> org.apache.ignite.internal.IgniteKernal.onReconnected(IgniteKernal.java:3904)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:831)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:590)
> - locked <0xe9429468> (a java.lang.Object)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processLocalJoin(ZookeeperDiscoveryImpl.java:2960)
> - locked <0xe9429478> (a java.lang.Object)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2760)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2623)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2598)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.access$2000(ZookeeperDiscoveryImpl.java:108)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl$ZkWatcher.processResult(ZookeeperDiscoveryImpl.java:4108)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperClient$DataCallbackWrapper.processResult(ZookeeperClient.java:1219)
> at
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561)
> at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498)
> {noformat}
> Stopping thread:
> {noformat}
> "main" #1 prio=5 os_prio=0 tid=0x7ffba000e000 nid=0x6aa3 waiting for
> monitor entry [0x7ffba8c83000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.stop0(ZookeeperDiscoveryImpl.java:3838)
> - waiting to lock <0xe9429478> (a java.lang.Object)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.stop(ZookeeperDiscoveryImpl.java:3813)
> at
> org.apache.ignite.spi.discovery.zk.ZookeeperDiscoverySpi.spiStop(ZookeeperDiscoverySpi.java:501)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.stopSpi(GridManagerAdapter.java:330)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.stop(GridDiscoveryManager.java:1683)
> at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2206)
> at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2081)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2594)
> - locked <0xe9429280> (a
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2557)
> at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:374)
> at org.apache.ignite.Ignition.stop(Ignition.java:229)
> at
>
[jira] [Commented] (IGNITE-9373) MVCC tests fail
[ https://issues.apache.org/jira/browse/IGNITE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593603#comment-16593603 ] ASF GitHub Bot commented on IGNITE-9373: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/4623 IGNITE-9373: Fix mvcc tests. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite IGNITE-9373 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4623.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4623 commit 6150d94c51b748fff361df32391131f1e68095e5 Author: Igor Seliverstov Date: 2017-12-27T11:32:58Z Fix no query in update plan. commit 2c212c18159848e413927dd05cf330e2be1cd97d Author: Alexander Paschenko Date: 2017-12-27T11:49:11Z IGNITE-7280: JDBC tests. commit e50c81e9ec3597414d8dbe775626654e0dc86eb0 Author: Alexander Paschenko Date: 2017-12-27T13:06:00Z IGNITE-7302: Fixed INFORMATIONAL_SCHEMA processing. This closes #3294. commit 04f94948bbd89136d4555a2e3fccd9367169 Author: Igor Seliverstov Date: 2017-12-27T14:04:58Z IGNITE-7321 DML operation hangs in case exception is thrown from DHT enlist future commit 3818bc9d74b2bba594ef89cc2d1ac975da816b54 Author: Igor Seliverstov Date: 2017-12-27T14:33:18Z fix tests. commit eb7a615c9d32e648eceeafb09893b226fe276467 Author: Igor Seliverstov Date: 2017-12-27T14:47:39Z fix exception types. commit f4ce065ce863a741e0d14901e087ff69856b7d9f Author: Alexander Paschenko Date: 2017-12-27T16:23:23Z Merge branch 'master' into ignite-5571 commit 73bedeb4979d5474be654c6f8f80c168c9a0606f Author: Alexander Paschenko Date: 2017-12-27T19:00:36Z IGNITE-5571 More tests commit ccf16fcc4d819e33b71a3322ae99d48755ee6b76 Author: Alexander Paschenko Date: 2017-12-28T07:49:25Z IGNITE-7259: Fixed GridIndexRebuildSelfTest. This closes #3304. commit 53466fc059d027edb24b3d7f5da05b6be2e997fc Author: Igor Seliverstov Date: 2017-12-28T11:24:16Z fix partition checking. commit b9aa9ebca0dca79fec278415beb5753ef49a4c60 Author: Igor Seliverstov Date: 2017-12-29T12:18:30Z fix mvcc version checking on lock acquire commit a86af95ea1ee08c2f66751a8e2fc440e4671d686 Author: Igor Seliverstov Date: 2018-01-11T12:45:02Z TODOs, right tickets numbers, minors commit 59ba16afcab00326a60f53b3a7592d2978f19313 Author: Igor Seliverstov Date: 2018-01-11T14:45:53Z Merge branch 'master' into ignite-4191-master commit 79d876bce306802bf097a69030e1fcca61cec859 Author: Igor Seliverstov Date: 2018-01-11T14:49:22Z Merge branch 'master' into ignite-4191-master commit 9bd874c8d132f23842ae4bf8caa2c633b42b0789 Author: Igor Seliverstov Date: 2018-01-11T14:52:15Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java commit cbae5040399f433c0689df76e697df5a637ca1bc Author: Igor Seliverstov Date: 2018-01-11T15:29:13Z Disable DROP COLUMN with enabled mvcc commit c5bb6c68a3faf9f236ae8a1639bfaf495c825eb7 Author: Igor Seliverstov Date: 2018-01-12T09:09:52Z Merge branch 'master' into ignite-4191-master commit 02f4ffa82a6ebaaaeaf96c31f15c4e8191c188d0 Author: Igor Seliverstov Date: 2018-01-12T09:23:00Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/JdbcThinTcpIo.java # modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcConnectionContext.java # modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite.java commit 21f9acdee409265f98893a2910e04effa63bcc2d Author: Igor Seliverstov Date: 2018-01-12T10:34:45Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheOffheapManager.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/H2Tree.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/H2TreeIndex.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2ExtrasInnerIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2ExtrasLeafIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2InnerIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2LeafIO.java commit
[jira] [Commented] (IGNITE-9246) Transactions can wait for topology future on remap for a long time even if timeout is set.
[ https://issues.apache.org/jira/browse/IGNITE-9246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593600#comment-16593600 ] ASF GitHub Bot commented on IGNITE-9246: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4572 > Transactions can wait for topology future on remap for a long time even if > timeout is set. > -- > > Key: IGNITE-9246 > URL: https://issues.apache.org/jira/browse/IGNITE-9246 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.7 > > > This is possible if long PME is occured during tx remap phase. > Fix: wait for new topology on remap with timeout if set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9147) Race between tx async rollback and lock mapping on near node can produce hanging primary tx
[ https://issues.apache.org/jira/browse/IGNITE-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593591#comment-16593591 ] ASF GitHub Bot commented on IGNITE-9147: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4574 > Race between tx async rollback and lock mapping on near node can produce > hanging primary tx > --- > > Key: IGNITE-9147 > URL: https://issues.apache.org/jira/browse/IGNITE-9147 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.5 >Reporter: ARomantsov >Assignee: Alexei Scherbakov >Priority: Critical > Fix For: 2.7 > > > I ran a simple test > 1) Start 15 servers node > 2) Start client with long transaction > 3) Additional start 5 client with loading in many caches (near 2 thousand) > 4) Stop 1 server node, wait 1 minute and start it back > Cluster freenze on more than hour -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9246) Transactions can wait for topology future on remap for a long time even if timeout is set.
[ https://issues.apache.org/jira/browse/IGNITE-9246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9246: - Ignite Flags: (was: Docs Required) > Transactions can wait for topology future on remap for a long time even if > timeout is set. > -- > > Key: IGNITE-9246 > URL: https://issues.apache.org/jira/browse/IGNITE-9246 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.7 > > > This is possible if long PME is occured during tx remap phase. > Fix: wait for new topology on remap with timeout if set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6044) SQL insert waits for transaction commit, but it must be executed right away
[ https://issues.apache.org/jira/browse/IGNITE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593568#comment-16593568 ] Yury Gerzhedovich commented on IGNITE-6044: --- [Latest test results|https://ci.ignite.apache.org/viewLog.html?buildId=1744216=IgniteTests24Java8_BuildApacheIgnite=buildResultsDiv] > SQL insert waits for transaction commit, but it must be executed right away > --- > > Key: IGNITE-6044 > URL: https://issues.apache.org/jira/browse/IGNITE-6044 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1 >Reporter: Mikhail Cherkasov >Assignee: Yury Gerzhedovich >Priority: Critical > Labels: sql-stability, usability > > Doc says: > ""Presently, DML supports the atomic mode only meaning that if there is a DML > query that is executed as a part of an Ignite transaction then it will not be > enlisted in the transaction's writing queue and will be executed right away."" > https://apacheignite.readme.io/docs/dml#section-transactional-support > However the data will be added to cache only after transaction commit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593544#comment-16593544
]
Ilya Kasnacheev commented on IGNITE-9367:
-
LGTM.
[~isapego] can you please chime in?
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9388) IgniteProvider tries to access obolete ignite.run or download from slow archive
Roman Shtykh created IGNITE-9388: Summary: IgniteProvider tries to access obolete ignite.run or download from slow archive Key: IGNITE-9388 URL: https://issues.apache.org/jira/browse/IGNITE-9388 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Roman Shtykh Assignee: Roman Shtykh Although it downloads from the archive, for Japan, for instance, it takes 2-3 hours. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[ https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593531#comment-16593531 ] Ivan Daschinskiy commented on IGNITE-9183: -- [~vozerov] Actually, if cache is created with CacheConfiguration, everything works as it should. Passed tests confirms that my change doesn't break this case. > Proper handling UUID columns, that are added by DDL. > > > Key: IGNITE-9183 > URL: https://issues.apache.org/jira/browse/IGNITE-9183 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5, 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.7 > > > Currently, if we added new UUID columnt thru DDL, it is saved to schema as > byte[]. So it's impossible to use it with DML without placeholders and put > values thru cache api without converting UUID to byte[]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-4434) Web Console: Grow input to all available space for form field.
[ https://issues.apache.org/jira/browse/IGNITE-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-4434. -- Resolution: Fixed Obsoleted, all inputs were refactored > Web Console: Grow input to all available space for form field. > -- > > Key: IGNITE-4434 > URL: https://issues.apache.org/jira/browse/IGNITE-4434 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Dmitriy Shabalin >Assignee: Dmitriy Shabalin >Priority: Minor > Labels: web-console-configuration > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[ https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593526#comment-16593526 ] Ivan Daschinskiy commented on IGNITE-9183: -- [~vozerov] Thank you for your review. 1) Got it, i'm adding new tests. 2) This case is already covered in many plases, i.e IgniteCacheObjectKeyIndexingSelfTest (specifically testObjectKeyHandling) and IgniteSqlParameterizedQueryTest#testSupportedTypes (see Bookmark#serialNumber field). 3).Got it. > Proper handling UUID columns, that are added by DDL. > > > Key: IGNITE-9183 > URL: https://issues.apache.org/jira/browse/IGNITE-9183 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5, 2.6 >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.7 > > > Currently, if we added new UUID columnt thru DDL, it is saved to schema as > byte[]. So it's impossible to use it with DML without placeholders and put > values thru cache api without converting UUID to byte[]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8234) Web console: refactor inputs
[ https://issues.apache.org/jira/browse/IGNITE-8234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-8234. -- Resolution: Fixed > Web console: refactor inputs > > > Key: IGNITE-8234 > URL: https://issues.apache.org/jira/browse/IGNITE-8234 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Dmitriy Shabalin >Priority: Minor > > Inputs are getting out of hand, we need to do some housekeeping: > 1. Converge and simplify SCSS for inputs with both styles of error message > (text vs icon). > 2. Converge and remove duplicate input mixins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-3820) Web console: 'undo' apper in wrong section
[ https://issues.apache.org/jira/browse/IGNITE-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-3820. -- Resolution: Won't Fix Obsoleted > Web console: 'undo' apper in wrong section > -- > > Key: IGNITE-3820 > URL: https://issues.apache.org/jira/browse/IGNITE-3820 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin >Priority: Minor > Labels: web-console-configuration > > Create a new cache - Save. > Open Memory section and open Mode drop down list but do not select any item. > Observing - 'undo' appear in the General section. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8996) Web console: Dropdown pupup menu is scrolled with page body on modal dialog.
[ https://issues.apache.org/jira/browse/IGNITE-8996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-8996. -- Resolution: Cannot Reproduce > Web console: Dropdown pupup menu is scrolled with page body on modal dialog. > > > Key: IGNITE-8996 > URL: https://issues.apache.org/jira/browse/IGNITE-8996 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.6 >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin >Priority: Major > > # Open *Cluster* configuration of *Advanced* tab of *Configure* page. > # Open *Import from database* dialog > # On *Tables* step expand any dropdown > # Try to scroll mouse on area instead of import dialog. > On scroll the dropdown popup is scrolled together with background content. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8199) Web console: Make the Confirmation dialog a more clear
[ https://issues.apache.org/jira/browse/IGNITE-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-8199: Assignee: Alexey Kuznetsov (was: Dmitriy Shabalin) > Web console: Make the Confirmation dialog a more clear > -- > > Key: IGNITE-8199 > URL: https://issues.apache.org/jira/browse/IGNITE-8199 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.7 > > Attachments: image-2018-04-11-13-54-07-997.png, > image-2018-04-11-13-54-23-306.png, screenshot-1.png > > > In case of unsaved changes, we show the following confirmation > !screenshot-1.png! > It is unclear what I have to do to see the changes. > I suggest to change the text 'Click here to see changes' somehow to make it > more obvious. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8029) Web console: wrong behaviour of cluster activation component
[ https://issues.apache.org/jira/browse/IGNITE-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-8029. -- Resolution: Fixed > Web console: wrong behaviour of cluster activation component > > > Key: IGNITE-8029 > URL: https://issues.apache.org/jira/browse/IGNITE-8029 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin >Priority: Minor > Fix For: 2.7 > > > I've noticed that during activation the text 'Deactivation' is printed for > ~0.5 second > and else - during deactivation, the text 'Activation' is printed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4943) Web Console: Improve design of tables with grouping on Admin Panel screen
[ https://issues.apache.org/jira/browse/IGNITE-4943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-4943: Assignee: Alexey Kuznetsov (was: Dmitriy Shabalin) > Web Console: Improve design of tables with grouping on Admin Panel screen > - > > Key: IGNITE-4943 > URL: https://issues.apache.org/jira/browse/IGNITE-4943 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Affects Versions: 1.9 >Reporter: Andrey Novikov >Assignee: Alexey Kuznetsov >Priority: Major > Attachments: Advanced Table.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7237) Web console: Wrong switcher behaviour on grid deactivation
[ https://issues.apache.org/jira/browse/IGNITE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-7237. -- Resolution: Fixed > Web console: Wrong switcher behaviour on grid deactivation > -- > > Key: IGNITE-7237 > URL: https://issues.apache.org/jira/browse/IGNITE-7237 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin >Priority: Major > > # Run node and agent. > # Open notebook page. > # Activate grid. > # Deactivate grid. > In process of deactivation switcher transit to off state. In that transition > *Deactivation...* message is changed to "Activation...". Progress animation > is showed in some time after switcher state was changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8306) Web console: grid UI regression
[ https://issues.apache.org/jira/browse/IGNITE-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-8306. -- Resolution: Cannot Reproduce > Web console: grid UI regression > --- > > Key: IGNITE-8306 > URL: https://issues.apache.org/jira/browse/IGNITE-8306 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Ilya Borisov >Assignee: Dmitriy Shabalin >Priority: Minor > Attachments: image-2018-04-18-12-23-44-129.png, > image-2018-04-18-12-24-20-991.png > > > *How to reproduce:* > 1. Go to admin panel. > 2. Click on "all" in columns dropdown twice to hide all columns. > 3. Enable "Last login" column. > *What happens:* > Column headers of "User" and "Last login" have different height, the rows are > misaligned. > !image-2018-04-18-12-23-44-129.png! > *What should happen:* > Column headers should have the same height, rows should not become offset > relative to other columns. Here's a screenshot from an older version: > !image-2018-04-18-12-24-20-991.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8144) Web console: UI issue in tables under Chrome
[ https://issues.apache.org/jira/browse/IGNITE-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-8144. -- Resolution: Fixed > Web console: UI issue in tables under Chrome > > > Key: IGNITE-8144 > URL: https://issues.apache.org/jira/browse/IGNITE-8144 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin >Priority: Minor > Attachments: screenshot-1.png > > > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593511#comment-16593511
]
Roman Guseinov commented on IGNITE-9367:
[~ilyak] , could you please review the PR
[https://github.com/apache/ignite/pull/4621] ?
TC results (Platform C++ (Linux)) are here
[https://ci.ignite.apache.org/viewLog.html?buildId=1743759=queuedBuildOverviewTab]
Thanks.
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7775) Web console. Error in log on second click by cancel on profile page.
[
https://issues.apache.org/jira/browse/IGNITE-7775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Shabalin resolved IGNITE-7775.
--
Resolution: Cannot Reproduce
> Web console. Error in log on second click by cancel on profile page.
>
>
> Key: IGNITE-7775
> URL: https://issues.apache.org/jira/browse/IGNITE-7775
> Project: Ignite
> Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Dmitriy Shabalin
>Priority: Minor
>
> Opening of base page on Cancel click spend a lot of time.
> If Cancel button is pressed second time error message will be printed into
> console:
> Transition Rejection($id: 52 type: 2, message: The transition has been
> superseded by a different transition, detail: Transition#73(
> 'base.settings.profile'{} -> 'base.configuration.clusters'{} ))
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7227) Web console: Wrong count of user in filtered table
[ https://issues.apache.org/jira/browse/IGNITE-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-7227: Assignee: Alexey Kuznetsov (was: Dmitriy Shabalin) > Web console: Wrong count of user in filtered table > -- > > Key: IGNITE-7227 > URL: https://issues.apache.org/jira/browse/IGNITE-7227 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > > # Open Admin panel > # Select some user > # Filter table. > In label with selected user count showed wrong count of showed rows in table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-6447) Web console: the panel with text 'Demo mode' hides buttons on Query screen
[ https://issues.apache.org/jira/browse/IGNITE-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-6447. -- Resolution: Won't Fix > Web console: the panel with text 'Demo mode' hides buttons on Query screen > -- > > Key: IGNITE-6447 > URL: https://issues.apache.org/jira/browse/IGNITE-6447 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Dmitriy Shabalin >Priority: Major > Attachments: screenshot-1.png > > > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4936) Web Console: Improve the scroll behavior
[ https://issues.apache.org/jira/browse/IGNITE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-4936: Assignee: Alexey Kuznetsov (was: Dmitriy Shabalin) > Web Console: Improve the scroll behavior > > > Key: IGNITE-4936 > URL: https://issues.apache.org/jira/browse/IGNITE-4936 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Attachments: 2.png > > > We need to finalize the tables: > # improve the scroll behavior -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9385) Redesign and Refactor UI part 2
[ https://issues.apache.org/jira/browse/IGNITE-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-9385: Assignee: Alexey Kuznetsov (was: Dmitriy Shabalin) > Redesign and Refactor UI part 2 > --- > > Key: IGNITE-9385 > URL: https://issues.apache.org/jira/browse/IGNITE-9385 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Dmitriy Shabalin >Assignee: Alexey Kuznetsov >Priority: Major > > We should refactor all screens to use latest modern controls as on > "Configuration" screen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9309) LocalNodeMovingPartitionsCount metrics may calculates incorrect due to processFullPartitionUpdate
[
https://issues.apache.org/jira/browse/IGNITE-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593502#comment-16593502
]
Dmitry Sherstobitov commented on IGNITE-9309:
-
[~avinogradov] [~Mmuzaf]
I've moved files from 7165 here.
Please look at [~Jokser] comment
> LocalNodeMovingPartitionsCount metrics may calculates incorrect due to
> processFullPartitionUpdate
> -
>
> Key: IGNITE-9309
> URL: https://issues.apache.org/jira/browse/IGNITE-9309
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Priority: Major
> Attachments: GridCacheRebalancingCancelTestNoReproduce.java,
> node-2-jstack.log, node-NO_REBALANCE-7165.log
>
>
> [~qvad] have found incorrect {{LocalNodeMovingPartitionsCount}} metrics
> calculation on client node {{JOIN\LEFT}}. Full issue reproducer is absent.
> Probable scenario:
> {code}
> Repeat 10 times:
> 1. stop node
> 2. clean lfs
> 3. add stopped node (trigger rebalance)
> 4. 3 times: start 2 clients, wait for topology snapshot, close clients
> 5. for each cache group check JMX metrics LocalNodeMovingPartitionsCount
> (like waitForFinishRebalance())
> {code}
> Whole discussion and all configuration details can be found in comments of
> [IGNITE-7165|https://issues.apache.org/jira/browse/IGNITE-7165].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-4883) Web Console: Fix grouping in tables on Admin Panel Screen
[ https://issues.apache.org/jira/browse/IGNITE-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin reassigned IGNITE-4883: Assignee: Alexey Kuznetsov (was: Dmitriy Shabalin) > Web Console: Fix grouping in tables on Admin Panel Screen > - > > Key: IGNITE-4883 > URL: https://issues.apache.org/jira/browse/IGNITE-4883 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > > Tab Countries: > - don't show number on Country column > - by default, do sorting by number of users (descendingly), not by alphabet > - show only number on User column (delete the title 'total rows') > - fix the bug: when user click in the Exclude input and then press Enter btn, > we do not need to download .csv > Companies Tab: > - don't show number on Company column > - by default, do sorting by number of users (descendingly), not by alphabet > - show only number on User column (delete the title 'total rows') > It is necessary to fix the main column when scrolling: > - Users - user > - Companies - company and user > - Contries - country and user -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9309) LocalNodeMovingPartitionsCount metrics may calculates incorrect due to processFullPartitionUpdate
[
https://issues.apache.org/jira/browse/IGNITE-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Sherstobitov updated IGNITE-9309:
Attachment: node-NO_REBALANCE-7165.log
node-2-jstack.log
GridCacheRebalancingCancelTestNoReproduce.java
> LocalNodeMovingPartitionsCount metrics may calculates incorrect due to
> processFullPartitionUpdate
> -
>
> Key: IGNITE-9309
> URL: https://issues.apache.org/jira/browse/IGNITE-9309
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Priority: Major
> Attachments: GridCacheRebalancingCancelTestNoReproduce.java,
> node-2-jstack.log, node-NO_REBALANCE-7165.log
>
>
> [~qvad] have found incorrect {{LocalNodeMovingPartitionsCount}} metrics
> calculation on client node {{JOIN\LEFT}}. Full issue reproducer is absent.
> Probable scenario:
> {code}
> Repeat 10 times:
> 1. stop node
> 2. clean lfs
> 3. add stopped node (trigger rebalance)
> 4. 3 times: start 2 clients, wait for topology snapshot, close clients
> 5. for each cache group check JMX metrics LocalNodeMovingPartitionsCount
> (like waitForFinishRebalance())
> {code}
> Whole discussion and all configuration details can be found in comments of
> [IGNITE-7165|https://issues.apache.org/jira/browse/IGNITE-7165].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6055) SQL: Add String length constraint
[
https://issues.apache.org/jira/browse/IGNITE-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593486#comment-16593486
]
Vladimir Ozerov commented on IGNITE-6055:
-
[~NIzhikov], I would only ensure that all tests are fine on TC. Then merge.
> SQL: Add String length constraint
> -
>
> Key: IGNITE-6055
> URL: https://issues.apache.org/jira/browse/IGNITE-6055
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: sql-engine
> Fix For: 2.7
>
>
> We should support {{CHAR(X)}} and {{VARCHAR{X}} syntax. Currently, we ignore
> it. First, it affects semantics. E.g., one can insert a string with greater
> length into a cache/table without any problems. Second, it limits efficiency
> of our default configuration. E.g., index inline cannot be applied to
> {{String}} data type as we cannot guess it's length.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9387) [ML] Model updating
Yury Babak created IGNITE-9387: -- Summary: [ML] Model updating Key: IGNITE-9387 URL: https://issues.apache.org/jira/browse/IGNITE-9387 Project: Ignite Issue Type: Improvement Components: ml Reporter: Yury Babak Assignee: Alexey Platonov Fix For: 2.7 In trainer interface we need to support model updating by batches after first training -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9386) control.sh --tx can produce confusing results when limit is set to small value
Alexei Scherbakov created IGNITE-9386: - Summary: control.sh --tx can produce confusing results when limit is set to small value Key: IGNITE-9386 URL: https://issues.apache.org/jira/browse/IGNITE-9386 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov This is happening because currently the limit is applied to primary and backup transactions, which breaks output post-filtering (removal of primary and backup transactions from output if near is present). Possible solution: apply limit only to near valid transactions. If some txs have no near part (broken tx topology), they should be always visible in output, probably with special "broken" marking. Best way to achieve this - implement tx paging on client side (using continuous mapping) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8149) MVCC TX: Size method should use tx snapshot
[ https://issues.apache.org/jira/browse/IGNITE-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593465#comment-16593465 ] Ivan Pavlukhin edited comment on IGNITE-8149 at 8/27/18 10:41 AM: -- Basic idea of size calculation is based on following points: * Introduced TxCounters entity is used for accumulation various counters of running transaction. * During transaction execution size delta is accumulated in TxCounters by mutating operations. * Delta is accumulated similarly on primary and backup partitions (and is not sent across network). * Size changes become visible in the end of transaction. was (Author: pavlukhin): Basic idea of size calculation is based on following points: * Introduced TxCounters entity is used for accumulation various counters of running transaction. * During transaction execution size delta is accumulated in TxCounters by mutating operations. * Size changes become visible in the end of transaction. > MVCC TX: Size method should use tx snapshot > --- > > Key: IGNITE-8149 > URL: https://issues.apache.org/jira/browse/IGNITE-8149 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Igor Seliverstov >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > Currently cache.size() returns number of entries in cache trees while there > can be several versions of one key-value pairs. > We should use tx snapshot and count all passed mvcc filter entries instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7226) Web console: Norification placeholder on empty user table
[ https://issues.apache.org/jira/browse/IGNITE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Shabalin resolved IGNITE-7226. -- Resolution: Fixed > Web console: Norification placeholder on empty user table > - > > Key: IGNITE-7226 > URL: https://issues.apache.org/jira/browse/IGNITE-7226 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin >Priority: Major > > # Open Admin panel > # Filter all data in table. > Table showed without data and any information message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8149) MVCC TX: Size method should use tx snapshot
[ https://issues.apache.org/jira/browse/IGNITE-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593465#comment-16593465 ] Ivan Pavlukhin commented on IGNITE-8149: Basic idea of size calculation is based on following points: * Introduced TxCounters entity is used for accumulation various counters of running transaction. * During transaction execution size delta is accumulated in TxCounters by mutating operations. * Size changes become visible in the end of transaction. > MVCC TX: Size method should use tx snapshot > --- > > Key: IGNITE-8149 > URL: https://issues.apache.org/jira/browse/IGNITE-8149 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Igor Seliverstov >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > Currently cache.size() returns number of entries in cache trees while there > can be several versions of one key-value pairs. > We should use tx snapshot and count all passed mvcc filter entries instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9385) Redesign and Refactor UI part 2
Dmitriy Shabalin created IGNITE-9385: Summary: Redesign and Refactor UI part 2 Key: IGNITE-9385 URL: https://issues.apache.org/jira/browse/IGNITE-9385 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Dmitriy Shabalin Assignee: Dmitriy Shabalin We should refactor all screens to use latest modern controls as on "Configuration" screen. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9367) CPP: ODBC client crashes after executing query with closed connection
[
https://issues.apache.org/jira/browse/IGNITE-9367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593455#comment-16593455
]
ASF GitHub Bot commented on IGNITE-9367:
GitHub user gromtech opened a pull request:
https://github.com/apache/ignite/pull/4621
IGNITE-9367 CPP: ODBC client crashes after executing query…
...by using a closed connection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9367
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4621.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4621
commit 3898e7ccb16e61039d93720e6f0865acbc9acd34
Author: Roman Guseinov
Date: 2018-08-27T10:26:01Z
IGNITE-9367 CPP: ODBC client crashes after executing query with closed
connection
> CPP: ODBC client crashes after executing query with closed connection
> -
>
> Key: IGNITE-9367
> URL: https://issues.apache.org/jira/browse/IGNITE-9367
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.6
> Environment: Ubuntu 16.04
>Reporter: Roman Guseinov
>Assignee: Roman Guseinov
>Priority: Major
> Labels: cpp
> Attachments: odbc-crash-reproducer.cpp, server-config.xml
>
>
> This scenario should not lead an application crash. It seems we should throw
> an exception like "Connection is closed" instead.
> Thread dump:
> {code:java}
> Thread #1 [odbc-crash-repr] 18020 [core: 0] (Suspended : Signal :
> SIGSEGV:Segmentation fault)
> ignite::odbc::Connection::TryRestoreConnection() at connection.cpp:628
> 0x454264
> ignite::odbc::Connection::EnsureConnected() at connection.cpp:607 0x4549cd
> ignite::odbc::Connection::SyncMessage ignite::odbc::QueryExecuteResponse>() at connection.h:168 0x45c705
> ignite::odbc::query::DataQuery::MakeRequestExecute() at data_query.cpp:217
> 0x45c705
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:629
> 0x42d32e
> ignite::odbc::Statement::InternalExecuteSqlQuery() at statement.cpp:586
> 0x42d499
> ignite::odbc::Statement::ExecuteSqlQuery() at statement.cpp:576 0x42d4c1
> ignite::SQLExecDirect() at odbc.cpp:395 0x42614c
> GetDataWithOdbc() at odbc-crash-reproducer.cpp:151 0x40898a
> QueryData() at odbc-crash-reproducer.cpp:172 0x408af2
> <...more frames...>
> {code}
> Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9373) MVCC tests fail
[ https://issues.apache.org/jira/browse/IGNITE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-9373: --- Attachment: MvccTestResults.tar.gz > MVCC tests fail > --- > > Key: IGNITE-9373 > URL: https://issues.apache.org/jira/browse/IGNITE-9373 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Andrew Mashenkov >Priority: Major > Attachments: MvccTestResults.tar.gz > > > Number of tests in MVCC test suites fail. Most of the fails is a regression > introduces by new changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9265) MVCC TX: Two rows with the same key in one MERGE statement produce an exception
[
https://issues.apache.org/jira/browse/IGNITE-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593441#comment-16593441
]
Andrew Mashenkov commented on IGNITE-9265:
--
PR with tests added.
> MVCC TX: Two rows with the same key in one MERGE statement produce an
> exception
> ---
>
> Key: IGNITE-9265
> URL: https://issues.apache.org/jira/browse/IGNITE-9265
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Andrew Mashenkov
>Priority: Major
>
> In case the operation like {{MERGE INTO INTEGER (_key, _val) KEY(_key) VALUES
> (1,1),(1,2)}} is called an exception is occurred.
> Correct behavior: each next update on the same key overwrites pervious one
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9265) MVCC TX: Two rows with the same key in one MERGE statement produce an exception
[ https://issues.apache.org/jira/browse/IGNITE-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593440#comment-16593440 ] ASF GitHub Bot commented on IGNITE-9265: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/4620 IGNITE-9265: MVCC TX: Two rows with the same key in one MERGE statement produce an exception Tests added. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9265 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4620.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4620 commit 3818bc9d74b2bba594ef89cc2d1ac975da816b54 Author: Igor Seliverstov Date: 2017-12-27T14:33:18Z fix tests. commit eb7a615c9d32e648eceeafb09893b226fe276467 Author: Igor Seliverstov Date: 2017-12-27T14:47:39Z fix exception types. commit f4ce065ce863a741e0d14901e087ff69856b7d9f Author: Alexander Paschenko Date: 2017-12-27T16:23:23Z Merge branch 'master' into ignite-5571 commit 73bedeb4979d5474be654c6f8f80c168c9a0606f Author: Alexander Paschenko Date: 2017-12-27T19:00:36Z IGNITE-5571 More tests commit ccf16fcc4d819e33b71a3322ae99d48755ee6b76 Author: Alexander Paschenko Date: 2017-12-28T07:49:25Z IGNITE-7259: Fixed GridIndexRebuildSelfTest. This closes #3304. commit 53466fc059d027edb24b3d7f5da05b6be2e997fc Author: Igor Seliverstov Date: 2017-12-28T11:24:16Z fix partition checking. commit b9aa9ebca0dca79fec278415beb5753ef49a4c60 Author: Igor Seliverstov Date: 2017-12-29T12:18:30Z fix mvcc version checking on lock acquire commit a86af95ea1ee08c2f66751a8e2fc440e4671d686 Author: Igor Seliverstov Date: 2018-01-11T12:45:02Z TODOs, right tickets numbers, minors commit 59ba16afcab00326a60f53b3a7592d2978f19313 Author: Igor Seliverstov Date: 2018-01-11T14:45:53Z Merge branch 'master' into ignite-4191-master commit 79d876bce306802bf097a69030e1fcca61cec859 Author: Igor Seliverstov Date: 2018-01-11T14:49:22Z Merge branch 'master' into ignite-4191-master commit 9bd874c8d132f23842ae4bf8caa2c633b42b0789 Author: Igor Seliverstov Date: 2018-01-11T14:52:15Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java commit cbae5040399f433c0689df76e697df5a637ca1bc Author: Igor Seliverstov Date: 2018-01-11T15:29:13Z Disable DROP COLUMN with enabled mvcc commit c5bb6c68a3faf9f236ae8a1639bfaf495c825eb7 Author: Igor Seliverstov Date: 2018-01-12T09:09:52Z Merge branch 'master' into ignite-4191-master commit 02f4ffa82a6ebaaaeaf96c31f15c4e8191c188d0 Author: Igor Seliverstov Date: 2018-01-12T09:23:00Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/jdbc/thin/JdbcThinTcpIo.java # modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcConnectionContext.java # modules/indexing/src/test/java/org/apache/ignite/testsuites/IgniteCacheQuerySelfTestSuite.java commit 21f9acdee409265f98893a2910e04effa63bcc2d Author: Igor Seliverstov Date: 2018-01-12T10:34:45Z Merge branch 'master' into ignite-4191-master # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/GridCacheOffheapManager.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/H2Tree.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/H2TreeIndex.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2ExtrasInnerIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2ExtrasLeafIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2InnerIO.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/database/io/H2LeafIO.java commit 5684b7224d077e285af35c5741d50332dec31eae Author: Igor Seliverstov Date: 2018-01-12T10:36:04Z Merge branch 'master' into ignite-4191-master commit 284c4335897fc82388baa99c960693b59a460e61 Author: Alexander Paschenko Date: 2018-01-17T09:20:35Z Merge remote-tracking branch 'apache/master' into ignite-5571 # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/jdbc/JdbcRequestHandler.java # modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/IgniteH2Indexing.java #
[jira] [Commented] (IGNITE-7616) GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect values due to invalid interface registration.
[ https://issues.apache.org/jira/browse/IGNITE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593431#comment-16593431 ] Max Shonichev commented on IGNITE-7616: --- Wouldn't it be better expose correct interface instead of struggling with conversion of values to incompatible interface? > GridDataStreamExecutor and GridCallbackExecutor JMX beans return incorrect > values due to invalid interface registration. > > > Key: IGNITE-7616 > URL: https://issues.apache.org/jira/browse/IGNITE-7616 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.4 >Reporter: Max Shonichev >Assignee: David Harvey >Priority: Major > Labels: jmx > Fix For: 2.7 > > > Two of newly added management beans as a result of implementing feature > request https://issues.apache.org/jira/browse/IGNITE-7217 have bugs: > # GridDataStreamExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible StripedExecutor. > # GridCallbackExecutor is registered as conforming to ThreadPoolMXBean > interface, though actually it is an incompatible > IgniteStripedThreadPoolExecutor. > # ThreadPoolMXBeanAdapter checks whether adapted instance is > ThreadPoolExecutor, and as interfaces are incompatible, most of the JMX > attributes of GridCallbackExecutor and GridDataStreamExecutor are returned as > -1 or null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9384) Transaction state PREPARED may be set too early or too late
[
https://issues.apache.org/jira/browse/IGNITE-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9384:
-
Ignite Flags: (was: Docs Required)
> Transaction state PREPARED may be set too early or too late
> ---
>
> Key: IGNITE-9384
> URL: https://issues.apache.org/jira/browse/IGNITE-9384
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7
>
>
> I see the following issues in the {{GridDhtTxPrepareFutureAdapter}} class:
> 1) {{PREPARED}} state on near local transaction may be set during the future
> completion. I think the {{onComplete(res)}} method should be corrected as
> follows:
> {code}
> if (last || tx.isSystemInvalidate() && !(tx.near() && tx.local()))
> tx.state(PREPARED);
> ...
> {code}
> 2) In {{onDone}} we have the following code:
> {code}
> if (REPLIED_UPD.compareAndSet(this, 0, 1)) {
> GridNearTxPrepareResponse res =
> createPrepareResponse(this.err);
> try {
> sendPrepareResponse(res);
> }
> finally {
> // Will call super.onDone().
> onComplete(res);
> }
> return true;
> }
> ...
> {code}
> This code will send near prepare response to the near node before the local
> DHT transaction sets it's state to {{PREPARED}} which violates the invariant
> that all transactions are prepared before any of the transactions is
> committed. I think these two methods should be swapped, but we need to
> carefully check the error handling (note that {{onComplete}} is called in
> {{finally}} block).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9384) Transaction state PREPARED may be set too early or too late
[
https://issues.apache.org/jira/browse/IGNITE-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-9384:
-
Fix Version/s: 2.7
> Transaction state PREPARED may be set too early or too late
> ---
>
> Key: IGNITE-9384
> URL: https://issues.apache.org/jira/browse/IGNITE-9384
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.7
>
>
> I see the following issues in the {{GridDhtTxPrepareFutureAdapter}} class:
> 1) {{PREPARED}} state on near local transaction may be set during the future
> completion. I think the {{onComplete(res)}} method should be corrected as
> follows:
> {code}
> if (last || tx.isSystemInvalidate() && !(tx.near() && tx.local()))
> tx.state(PREPARED);
> ...
> {code}
> 2) In {{onDone}} we have the following code:
> {code}
> if (REPLIED_UPD.compareAndSet(this, 0, 1)) {
> GridNearTxPrepareResponse res =
> createPrepareResponse(this.err);
> try {
> sendPrepareResponse(res);
> }
> finally {
> // Will call super.onDone().
> onComplete(res);
> }
> return true;
> }
> ...
> {code}
> This code will send near prepare response to the near node before the local
> DHT transaction sets it's state to {{PREPARED}} which violates the invariant
> that all transactions are prepared before any of the transactions is
> committed. I think these two methods should be swapped, but we need to
> carefully check the error handling (note that {{onComplete}} is called in
> {{finally}} block).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9384) Transaction state PREPARED may be set too early or too late
Alexey Goncharuk created IGNITE-9384:
Summary: Transaction state PREPARED may be set too early or too
late
Key: IGNITE-9384
URL: https://issues.apache.org/jira/browse/IGNITE-9384
Project: Ignite
Issue Type: Bug
Reporter: Alexey Goncharuk
I see the following issues in the {{GridDhtTxPrepareFutureAdapter}} class:
1) {{PREPARED}} state on near local transaction may be set during the future
completion. I think the {{onComplete(res)}} method should be corrected as
follows:
{code}
if (last || tx.isSystemInvalidate() && !(tx.near() && tx.local()))
tx.state(PREPARED);
...
{code}
2) In {{onDone}} we have the following code:
{code}
if (REPLIED_UPD.compareAndSet(this, 0, 1)) {
GridNearTxPrepareResponse res = createPrepareResponse(this.err);
try {
sendPrepareResponse(res);
}
finally {
// Will call super.onDone().
onComplete(res);
}
return true;
}
...
{code}
This code will send near prepare response to the near node before the local DHT
transaction sets it's state to {{PREPARED}} which violates the invariant that
all transactions are prepared before any of the transactions is committed. I
think these two methods should be swapped, but we need to carefully check the
error handling (note that {{onComplete}} is called in {{finally}} block).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8318) MVCC TX: Scan query call throws an exception when it is mixed with Key-Value API in the same transaction.
[
https://issues.apache.org/jira/browse/IGNITE-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov reassigned IGNITE-8318:
---
Assignee: Andrew Mashenkov
> MVCC TX: Scan query call throws an exception when it is mixed with Key-Value
> API in the same transaction.
> --
>
> Key: IGNITE-8318
> URL: https://issues.apache.org/jira/browse/IGNITE-8318
> Project: Ignite
> Issue Type: Bug
> Components: cache, mvcc, sql
>Reporter: Roman Kondakov
>Assignee: Andrew Mashenkov
>Priority: Major
>
> Scan queries should not throw Exceptions in key-value API transactions.
> Reproducer: {{CacheMvccTransactionsTest#testPutAllGetAll_SingleNode_Scan}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7314) Iterators could return multiple values of the same key when MVCC is enabled
[
https://issues.apache.org/jira/browse/IGNITE-7314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-7314:
Issue Type: Bug (was: Task)
> Iterators could return multiple values of the same key when MVCC is enabled
> ---
>
> Key: IGNITE-7314
> URL: https://issues.apache.org/jira/browse/IGNITE-7314
> Project: Ignite
> Issue Type: Bug
> Components: cache, mvcc
>Reporter: Vladimir Ozerov
>Assignee: Roman Kondakov
>Priority: Major
> Fix For: 2.7
>
>
> It MVCC is enabled most of tests in {{IgniteCacheFullApiSelfTestSuite}} works
> fine. However, they are really *slow*. So slow, that TC cannot cope with them
> and kills the build after 1h30m of execution.
> Root cause: iterators return too much values as they do not use any specific
> version by default ({{null}} is passed). Essentially, we need to add MVCC
> support to iterators and "global" operations, which use them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7265) BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails
[
https://issues.apache.org/jira/browse/IGNITE-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-7265:
Issue Type: Bug (was: Task)
> BPlusTreeSelfTest.testIterateConcurrentPutRemove_1 fails
>
>
> Key: IGNITE-7265
> URL: https://issues.apache.org/jira/browse/IGNITE-7265
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Vladimir Ozerov
>Priority: Major
> Fix For: 2.7
>
>
> {code}
> java.lang.AssertionError: Assertion error on row: 26
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2221)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.put(BPlusTree.java:2156)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.iterateConcurrentPutRemove(BPlusTreeSelfTest.java:2202)
> at
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.testIterateConcurrentPutRemove_1(BPlusTreeSelfTest.java:2169)
> 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:2008)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1923)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.AssertionError: 27
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusMetaIO.setLevelsCount(BPlusMetaIO.java:98)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusMetaIO.addRoot(BPlusMetaIO.java:155)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AddRoot.run(BPlusTree.java:661)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AddRoot.run(BPlusTree.java:650)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:277)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:241)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$10500(BPlusTree.java:82)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertWithSplit(BPlusTree.java:3073)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:2949)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$2500(BPlusTree.java:2831)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:420)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:401)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5153)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5138)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:342)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:261)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$11100(BPlusTree.java:82)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.tryInsert(BPlusTree.java:3143)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$7500(BPlusTree.java:2831)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2464)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2185)
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9373) MVCC tests fail
[ https://issues.apache.org/jira/browse/IGNITE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-9373: --- Assignee: Andrew Mashenkov (was: Ivan Pavlukhin) > MVCC tests fail > --- > > Key: IGNITE-9373 > URL: https://issues.apache.org/jira/browse/IGNITE-9373 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Andrew Mashenkov >Priority: Major > > Number of tests in MVCC test suites fail. Most of the fails is a regression > introduces by new changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7259) GridIndexRebuildSelfTest hangs
[ https://issues.apache.org/jira/browse/IGNITE-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-7259: --- Assignee: Andrew Mashenkov > GridIndexRebuildSelfTest hangs > -- > > Key: IGNITE-7259 > URL: https://issues.apache.org/jira/browse/IGNITE-7259 > Project: Ignite > Issue Type: Task > Components: mvcc, sql >Reporter: Vladimir Ozerov >Assignee: Andrew Mashenkov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8936) Remove AffinityAssignment#clientEventChange as not used
[ https://issues.apache.org/jira/browse/IGNITE-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593388#comment-16593388 ] Maxim Muzafarov commented on IGNITE-8936: - [~zzzadruga] Changes looks good to me, given TC as usual. [~northdragon] Will you step in? > Remove AffinityAssignment#clientEventChange as not used > --- > > Key: IGNITE-8936 > URL: https://issues.apache.org/jira/browse/IGNITE-8936 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Minor > Labels: newbie > Attachments: ClientEventChange (1).png > > > We should try to keep Ignite project code as simple as possible. > Motivation: > http://apache-ignite-developers.2346864.n4.nabble.com/Cases-of-using-AffinityAssignment-clientEventChange-method-td32068.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9370) Web console: Failed to open demo for Queries page.
[
https://issues.apache.org/jira/browse/IGNITE-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reassigned IGNITE-9370:
--
Assignee: Andrey Novikov (was: Vasiliy Sisko)
> Web console: Failed to open demo for Queries page.
> --
>
> Key: IGNITE-9370
> URL: https://issues.apache.org/jira/browse/IGNITE-9370
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Andrey Novikov
>Priority: Major
>
> On opening of Queries page in Demo mode only error is shown:
> {code:java}
> Invalid format of message: "node:rest"{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8149) MVCC TX: Size method should use tx snapshot
[ https://issues.apache.org/jira/browse/IGNITE-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-8149: Fix Version/s: 2.7 > MVCC TX: Size method should use tx snapshot > --- > > Key: IGNITE-8149 > URL: https://issues.apache.org/jira/browse/IGNITE-8149 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Igor Seliverstov >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > Currently cache.size() returns number of entries in cache trees while there > can be several versions of one key-value pairs. > We should use tx snapshot and count all passed mvcc filter entries instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-4816) Issue with refresh rate on queries
[ https://issues.apache.org/jira/browse/IGNITE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-4816. -- > Issue with refresh rate on queries > -- > > Key: IGNITE-4816 > URL: https://issues.apache.org/jira/browse/IGNITE-4816 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > > Next query execution start before previous one is finished -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-4816) Issue with refresh rate on queries
[ https://issues.apache.org/jira/browse/IGNITE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593354#comment-16593354 ] Pavel Konstantinov commented on IGNITE-4816: Checked on the master. Cannot reproduce anymore. > Issue with refresh rate on queries > -- > > Key: IGNITE-4816 > URL: https://issues.apache.org/jira/browse/IGNITE-4816 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov >Priority: Major > > Next query execution start before previous one is finished -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8559) WAL rollOver can be blocked by WAL iterator reservation
[
https://issues.apache.org/jira/browse/IGNITE-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593351#comment-16593351
]
Ivan Rakov commented on IGNITE-8559:
[~akalashnikov], overall design looks good.
I've left some comments in upsource review, mostly about abbreviations and code
style.
> WAL rollOver can be blocked by WAL iterator reservation
> ---
>
> Key: IGNITE-8559
> URL: https://issues.apache.org/jira/browse/IGNITE-8559
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Critical
> Fix For: 2.7
>
>
> I've got the following thread dump from one of the Ignite nodes (only
> meaningful threads are kept for simplicity)
> WAL archiver is waiting for locked segment release
> TX commit is waiting for WAL rollover
> WAL rollover is blocked by the archiver
> Exchange is blocked by TX commit
> {code}
> "sys-stripe-55-#56%GRID%GridNodeName%" #246 daemon prio=5 os_prio=0
> tid=0x7fdd1eeff000 nid=0x164252 waiting on condition [0x7fdb36eec000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x7fe0a5e96278> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976)
> at
> org.apache.ignite.internal.util.IgniteUtils.awaitQuiet(IgniteUtils.java:7400)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.awaitNext(FileWriteAheadLogManager.java:2819)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileWriteHandle.access$2900(FileWriteAheadLogManager.java:2390)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.rollOver(FileWriteAheadLogManager.java:1065)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:715)
> at
> org.gridgain.grid.internal.processors.cache.database.snapshot.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:2436)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$9.applyx(GridCacheDatabaseSharedManager.java:942)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$9.applyx(GridCacheDatabaseSharedManager.java:935)
> at
> org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1341)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:415)
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:409)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:287)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:282)
> at
> org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.insertDataRow(AbstractFreeList.java:509)
> at
> org.apache.ignite.internal.processors.cache.persistence.RowStore.addRow(RowStore.java:102)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.createRow(IgniteCacheOffheapManagerImpl.java:1252)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.createRow(GridCacheOffheapManager.java:1370)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:4429)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$UpdateClosure.call(GridCacheMapEntry.java:4374)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:3083)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$6200(BPlusTree.java:2977)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1726)
> at
>
[jira] [Created] (IGNITE-9383) Add to the documentation that Ignite cluster requires that each nodes have direct connection to any nodes of grid.
Evgenii Zhuravlev created IGNITE-9383: - Summary: Add to the documentation that Ignite cluster requires that each nodes have direct connection to any nodes of grid. Key: IGNITE-9383 URL: https://issues.apache.org/jira/browse/IGNITE-9383 Project: Ignite Issue Type: Improvement Components: documentation Affects Versions: 2.6 Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9370) Web console: Failed to open demo for Queries page.
[
https://issues.apache.org/jira/browse/IGNITE-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593321#comment-16593321
]
Pavel Konstantinov commented on IGNITE-9370:
tested on the branch.
> Web console: Failed to open demo for Queries page.
> --
>
> Key: IGNITE-9370
> URL: https://issues.apache.org/jira/browse/IGNITE-9370
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
>
> On opening of Queries page in Demo mode only error is shown:
> {code:java}
> Invalid format of message: "node:rest"{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9370) Web console: Failed to open demo for Queries page.
[
https://issues.apache.org/jira/browse/IGNITE-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Konstantinov reassigned IGNITE-9370:
--
Assignee: Vasiliy Sisko (was: Pavel Konstantinov)
> Web console: Failed to open demo for Queries page.
> --
>
> Key: IGNITE-9370
> URL: https://issues.apache.org/jira/browse/IGNITE-9370
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Major
>
> On opening of Queries page in Demo mode only error is shown:
> {code:java}
> Invalid format of message: "node:rest"{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[
https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593305#comment-16593305
]
Vladimir Ozerov edited comment on IGNITE-9183 at 8/27/18 8:26 AM:
--
[~ivandasch], [~skosarev], [~akalashnikov], my comments:
1) Changes are applied to both {{CREATE TABLE}} and {{ALTER TABLE}} statements,
but only latter is tested. Need to test {{CREATE TABLE}} command as well,
taking in count the following cases: UUID as a key (unwrapped), UUID as a value
(unwrapped), UUID as a part of a composite key, UUID as a part of composite
value.
2) Does table created from {{CacheConfiguration}} with predefined
{{QueryEntity}} behave in the same way (i.e. {{UUID}} is translated to
{{UUID}}, not {{byte[]}})? We need to confirm it with tests.
3) Some Ignite users may rely on current behavior in their code, and this
change may break their applications. We need to allow users to force old
behavior with {{byte[]}}. You can use {{IgniteSystemProperties}} for this.
was (Author: vozerov):
[~ivandasch], [~skosarev], my comments:
1) Changes are applied to both {{CREATE TABLE}} and {{ALTER TABLE}} statements,
but only latter is tested. Need to test {{CREATE TABLE}} command as well,
taking in count the following cases: UUID as a key (unwrapped), UUID as a value
(unwrapped), UUID as a part of a composite key, UUID as a part of composite
value.
2) Does table created from {{CacheConfiguration}} with predefined
{{QueryEntity}} behave in the same way (i.e. {{UUID}} is translated to
{{UUID}}, not {{byte[]}})? We need to confirm it with tests.
3) Some Ignite users may rely on current behavior in their code, and this
change may break their applications. We need to allow users to force old
behavior with {{byte[]}}. You can use {{IgniteSystemProperties}} for this.
> Proper handling UUID columns, that are added by DDL.
>
>
> Key: IGNITE-9183
> URL: https://issues.apache.org/jira/browse/IGNITE-9183
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.5, 2.6
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.7
>
>
> Currently, if we added new UUID columnt thru DDL, it is saved to schema as
> byte[]. So it's impossible to use it with DML without placeholders and put
> values thru cache api without converting UUID to byte[].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[
https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593305#comment-16593305
]
Vladimir Ozerov edited comment on IGNITE-9183 at 8/27/18 8:25 AM:
--
[~ivandasch], [~skosarev], my comments:
1) Changes are applied to both {{CREATE TABLE}} and {{ALTER TABLE}} statements,
but only latter is tested. Need to test {{CREATE TABLE}} command as well,
taking in count the following cases: UUID as a key (unwrapped), UUID as a value
(unwrapped), UUID as a part of a composite key, UUID as a part of composite
value.
2) Does table created from {{CacheConfiguration}} with predefined
{{QueryEntity}} behave in the same way (i.e. {{UUID}} is translated to
{{UUID}}, not {{byte[]}})? We need to confirm it with tests.
3) Some Ignite users may rely on current behavior in their code, and this
change may break their applications. We need to allow users to force old
behavior with {{byte[]}}. You can use {{IgniteSystemProperties}} for this.
was (Author: vozerov):
[~ivandasch], [~skosarev], my comments:
1) Changes are applied to both \{{CREATE TABLE}} and \{{ALTER TABLE}}
statements, but only latter is tested. Need to test \{{CREATE TABLE}} command
as well, taking in count the following cases: UUID as a key (unwrapped), UUID
as a value (unwrapped), UUID as a part of a composite key, UUID as a part of
composite value.
2) Does table created from CacheConfiguration with predefined QueryEntity
behave in the same way (i.e. UUID is translated to UUID, not bete[])? We need
to confirm it with tests.
3) Some Ignite users may rely on current behavior in their codd, and this
change may break their applications. We need to allow users to force old
behavior with {{byte[]}}. You can use {{IgniteSystemProperties}} for this.
> Proper handling UUID columns, that are added by DDL.
>
>
> Key: IGNITE-9183
> URL: https://issues.apache.org/jira/browse/IGNITE-9183
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.5, 2.6
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.7
>
>
> Currently, if we added new UUID columnt thru DDL, it is saved to schema as
> byte[]. So it's impossible to use it with DML without placeholders and put
> values thru cache api without converting UUID to byte[].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9183) Proper handling UUID columns, that are added by DDL.
[
https://issues.apache.org/jira/browse/IGNITE-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593305#comment-16593305
]
Vladimir Ozerov commented on IGNITE-9183:
-
[~ivandasch], [~skosarev], my comments:
1) Changes are applied to both \{{CREATE TABLE}} and \{{ALTER TABLE}}
statements, but only latter is tested. Need to test \{{CREATE TABLE}} command
as well, taking in count the following cases: UUID as a key (unwrapped), UUID
as a value (unwrapped), UUID as a part of a composite key, UUID as a part of
composite value.
2) Does table created from CacheConfiguration with predefined QueryEntity
behave in the same way (i.e. UUID is translated to UUID, not bete[])? We need
to confirm it with tests.
3) Some Ignite users may rely on current behavior in their codd, and this
change may break their applications. We need to allow users to force old
behavior with {{byte[]}}. You can use {{IgniteSystemProperties}} for this.
> Proper handling UUID columns, that are added by DDL.
>
>
> Key: IGNITE-9183
> URL: https://issues.apache.org/jira/browse/IGNITE-9183
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.5, 2.6
>Reporter: Ivan Daschinskiy
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.7
>
>
> Currently, if we added new UUID columnt thru DDL, it is saved to schema as
> byte[]. So it's impossible to use it with DML without placeholders and put
> values thru cache api without converting UUID to byte[].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8936) Remove AffinityAssignment#clientEventChange as not used
[ https://issues.apache.org/jira/browse/IGNITE-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593304#comment-16593304 ] Nikolai Kulagin commented on IGNITE-8936: - Remove field clientEvtChange and method clientEventChange() PR: [https://github.com/apache/ignite/pull/4448|https://github.com/apache/ignite/pull/4448] TC: [https://ci.ignite.apache.org/viewLog.html?buildId=1723097=buildResultsDiv=IgniteTests24Java8_RunAll=] Project is buildable, tests are ok, flacky as usual. [~Mmuzaf], please, review my change. > Remove AffinityAssignment#clientEventChange as not used > --- > > Key: IGNITE-8936 > URL: https://issues.apache.org/jira/browse/IGNITE-8936 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Minor > Labels: newbie > Attachments: ClientEventChange (1).png > > > We should try to keep Ignite project code as simple as possible. > Motivation: > http://apache-ignite-developers.2346864.n4.nabble.com/Cases-of-using-AffinityAssignment-clientEventChange-method-td32068.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9382) Node.js fails to process large payloads
[ https://issues.apache.org/jira/browse/IGNITE-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh reassigned IGNITE-9382: Assignee: Toru Yabuki > Node.js fails to process large payloads > --- > > Key: IGNITE-9382 > URL: https://issues.apache.org/jira/browse/IGNITE-9382 > Project: Ignite > Issue Type: Bug > Components: thin client >Reporter: Roman Shtykh >Assignee: Toru Yabuki >Priority: Major > > Looks like finalizing response is done too early. > This can be easily checked with an SQL _limit_ 1 and _limit 100_. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9382) Node.js fails to process large payloads
Roman Shtykh created IGNITE-9382: Summary: Node.js fails to process large payloads Key: IGNITE-9382 URL: https://issues.apache.org/jira/browse/IGNITE-9382 Project: Ignite Issue Type: Bug Components: thin client Reporter: Roman Shtykh Looks like finalizing response is done too early. This can be easily checked with an SQL _limit_ 1 and _limit 100_. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9370) Web console: Failed to open demo for Queries page.
[
https://issues.apache.org/jira/browse/IGNITE-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-9370:
-
Assignee: Pavel Konstantinov (was: Vasiliy Sisko)
> Web console: Failed to open demo for Queries page.
> --
>
> Key: IGNITE-9370
> URL: https://issues.apache.org/jira/browse/IGNITE-9370
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Major
>
> On opening of Queries page in Demo mode only error is shown:
> {code:java}
> Invalid format of message: "node:rest"{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9370) Web console: Failed to open demo for Queries page.
[
https://issues.apache.org/jira/browse/IGNITE-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593259#comment-16593259
]
Vasiliy Sisko commented on IGNITE-9370:
---
Fixed execution of REST commands in demo mode.
> Web console: Failed to open demo for Queries page.
> --
>
> Key: IGNITE-9370
> URL: https://issues.apache.org/jira/browse/IGNITE-9370
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Major
>
> On opening of Queries page in Demo mode only error is shown:
> {code:java}
> Invalid format of message: "node:rest"{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-3303) Apache Flink Integration - Flink source to run a continuous query against one or multiple caches
[ https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593239#comment-16593239 ] Saikat Maitra commented on IGNITE-3303: --- [~dpavlov], [~amashenkov] I have updated the PR with additional tests. Can you please review and share feedback. This PR is related to IgniteSink but allows to stream data from Ignite. PR https://github.com/apache/ignite/pull/870/files Regards, Saikat > Apache Flink Integration - Flink source to run a continuous query against one > or multiple caches > > > Key: IGNITE-3303 > URL: https://issues.apache.org/jira/browse/IGNITE-3303 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Saikat Maitra >Priority: Major > Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png, > testFlinkIgniteSourceWithLargeBatch.log, win7.PNG > > > Apache Flink integration > +++ *Ignite as a bidirectional Connector* +++ > As a Flink source => run a continuous query against one or multiple > caches [4]. > Related discussion : > http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9370) Web console: Failed to open demo for Queries page.
[
https://issues.apache.org/jira/browse/IGNITE-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-9370:
-
Assignee: Vasiliy Sisko
> Web console: Failed to open demo for Queries page.
> --
>
> Key: IGNITE-9370
> URL: https://issues.apache.org/jira/browse/IGNITE-9370
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Major
>
> On opening of Queries page in Demo mode only error is shown:
> {code:java}
> Invalid format of message: "node:rest"{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
