[jira] [Commented] (IGNITE-5565) Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module.
[ https://issues.apache.org/jira/browse/IGNITE-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603940#comment-16603940 ] Lokesh Sharma commented on IGNITE-5565: --- What's the status of this issue? Can I do something to fix this? > Replace Cron4J with Quartz or Spring scheduler for ignite-schedule module. > -- > > Key: IGNITE-5565 > URL: https://issues.apache.org/jira/browse/IGNITE-5565 > Project: Ignite > Issue Type: Task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Sergey Kosarev >Priority: Major > Labels: newbie > > 1) Cron4J is very old: > Latest Cron4j 2.2.5 released: 28-Dec-2011 > Latest Quarz 2.3.0 released: 20-Apr-2017 > 2) Not very friendly license: > CronJ4 licensed under GNU LESSER GENERAL PUBLIC LICENSE > Quartz is freely usable, licensed under the Apache 2.0 license. > So, if we replace Cron4J with Quartz we can move ignite-schedule module > from lgpl profile to main distribution. > Also spring's scheduler could be considered as Cron4J alternative. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603878#comment-16603878 ] Roman Guseinov commented on IGNITE-8987: [~agoncharuk] , thank you. > Ignite hangs during getting of atomic structure after autoactivation > > > Key: IGNITE-8987 > URL: https://issues.apache.org/jira/browse/IGNITE-8987 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.7 > > Attachments: reproducer.java > > > I investigate the use cases with autoactivation and creating of the > IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it > called after the last node from BLT was started. > Steps to reproduce: > First iteration: > > Do next in one thread: > 1)Start server 1 > 2)Start server 2 > 3)Activate the cluster > 4)Create the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > atomicConfiguration, > 10, > true); > Second iteration: > 1)Start server 1 > 2)Start server 2 (Autoactivation will be started) > 3)Get the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > 10, > true); //could be false because TestName was already created in iteration 1 > In this case, we hang in awaitInitialization() method in > DataStructureProcessor.getAtomic() method. > In case if I added some sleep timeout between step 2 and 3 in the second > iteration then everything was ok. Looks like we have some race here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9371) Web console: Failed to open Activity details dialog.
[
https://issues.apache.org/jira/browse/IGNITE-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov reassigned IGNITE-9371:
Assignee: Ilya Borisov
> Web console: Failed to open Activity details dialog.
>
>
> Key: IGNITE-9371
> URL: https://issues.apache.org/jira/browse/IGNITE-9371
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Ilya Borisov
>Priority: Major
>
> # Open Admin page and select any user.
> # Select Activity details dialog in table Actions menu
> Error in log is printed:
> {code:java}
> TypeError: ActivitiesUserDialog is not a constructor
> at IgniteListOfRegisteredUsersCtrl.showActivities (controller.js:104)
> at fn (eval at compile (angular.js:15869), :4:167)
> at callback (angular.js:28101)
> at ChildScope.$eval (angular.js:18838)
> at ChildScope.$apply (angular.js:18937)
> at HTMLAnchorElement. (angular.js:28106)
> at HTMLAnchorElement.dispatch (jquery.js:5206)
> at HTMLAnchorElement.elemData.handle (jquery.js:5014) undefined{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=16603827#comment-16603827 ] Saikat Maitra commented on IGNITE-3303: --- [~amashenkov] [~agoncharuk] Thank you for reviewing the changes. I will make the updates and share RunAll tests build link in the ticket. 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 >Assignee: 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-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=16603733#comment-16603733
]
Denis Magda commented on IGNITE-9305:
-
[~xtern], thanks, let's merge the changes then after someone from the community
reviews them.
--
Denis
> 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-8485) TDE - Phase-1
[
https://issues.apache.org/jira/browse/IGNITE-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603538#comment-16603538
]
Nikolay Izhikov commented on IGNITE-8485:
-
[~vozerov]
I've fixed all comments from your first code review:
1. {{encrypted}} renamed to {{isEncryptionEnabled}}
2. Ticket to add {{isEncryptionEnabled}} created.
3. .Net SPI implementation created.
4. CRC of encrypted page calculated and stored in the persistent store. We can
check persisted data integrity on reading from a file.
5. {{EncryptionKey}} removed. {{Serializable}} used instead.
6. I've keep {{NoonEncryptionSpi}} - it required in for a internal logic.
7. {{keySize}} and {{masterKeName}} are now can be setted by user.
8. MVCC PageIO checked.
9. {{GenerateEncryptionKeyRequst}} now send via communication SPI.
10. SPI implementation renamed to AESEncryptionSpi and moved to the
corresponding package.
11. Some tests added.
PDS tests group are executed with encryption mode forced for all caches.
PR - https://github.com/apache/ignite/pull/4634
Tests - https://ci.ignite.apache.org/viewLog.html?buildId=1794649
Please, take a look on main PR one more time -
https://github.com/apache/ignite/pull/4167
> TDE - Phase-1
> -
>
> Key: IGNITE-8485
> URL: https://issues.apache.org/jira/browse/IGNITE-8485
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Critical
> Fix For: 2.7
>
>
> Basic support for a Transparent Data Encryption should be implemented:
> 1. Usage of standard JKS, Java Security.
> 2. Persistent Data Encryption/Decryption.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9467) Custom SQL function: Hexadecimal string with odd number of characters
Joe Feise created IGNITE-9467: - Summary: Custom SQL function: Hexadecimal string with odd number of characters Key: IGNITE-9467 URL: https://issues.apache.org/jira/browse/IGNITE-9467 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Joe Feise I have been trying to use a custom SQL function which expects an array of doubles, as explained here: [https://stackoverflow.com/questions/33097103/how-to-sum-an-array-of-doubles-with-ignite-data-grid-sql] I get this error: select arraysum(value_double) from time_series; [Hexadecimal string with odd number of characters: "-9.386298778519813E-152"; SQL statement: select arraysum(value_double) from time_series [90003-195]|http://192.168.6.247:64909/query.do?jsessionid=456cb3c32fa9887ebfaaf775c4f3beff] 90003/90003 It seems that Ignite tries to read the double value as a hex string. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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
]
Andrey Gura reassigned IGNITE-9384:
---
Assignee: Andrey Gura
> 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
>Assignee: Andrey Gura
>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-9466) AsyncFileIO may not close channel after method close invocation
Sergey Antonov created IGNITE-9466:
--
Summary: AsyncFileIO may not close channel after method close
invocation
Key: IGNITE-9466
URL: https://issues.apache.org/jira/browse/IGNITE-9466
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
{code:java}
/** {@inheritDoc} */
@Override public void close() throws IOException {
for (ChannelOpFuture asyncFut : asyncFuts) {
try {
asyncFut.getUninterruptibly(); // Ignore interrupts while waiting
for channel close.
}
catch (IgniteCheckedException e) {
throw new IOException(e);
}
}
ch.close();
}{code}
If `asyncFut.getUninterruptibly()` throw exception, the channel associated with
AsyncFileIO will not be closed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-9464) MVCC TX: cache GET supports Mvcc tx mode.
[ https://issues.apache.org/jira/browse/IGNITE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov resolved IGNITE-9464. -- Resolution: Duplicate > MVCC TX: cache GET supports Mvcc tx mode. > - > > Key: IGNITE-9464 > URL: https://issues.apache.org/jira/browse/IGNITE-9464 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9464) MVCC TX: cache GET supports Mvcc tx mode.
[ https://issues.apache.org/jira/browse/IGNITE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov closed IGNITE-9464. > MVCC TX: cache GET supports Mvcc tx mode. > - > > Key: IGNITE-9464 > URL: https://issues.apache.org/jira/browse/IGNITE-9464 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7371) MVCC TX Repeatable read semantic
[ https://issues.apache.org/jira/browse/IGNITE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-7371: Assignee: Andrew Mashenkov > MVCC TX Repeatable read semantic > > > Key: IGNITE-7371 > URL: https://issues.apache.org/jira/browse/IGNITE-7371 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Igor Seliverstov >Assignee: Andrew Mashenkov >Priority: Major > > Repeatable read isolation implies that each GET operation whithin tx gets a > last commited version of entry *at the time the tx was started*. Curentrly we > get a last commited version of entry *at the time the first read operation > invokes on a particular key whithin tx.* We need to fix this unconsistence. -- 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=16603232#comment-16603232 ] Alexey Goncharuk commented on IGNITE-3303: -- [~samaitra], I've added some comments as well. Also, make sure to include a TC RunAll tests build link to the ticket. Thanks! > 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 >Assignee: 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] [Created] (IGNITE-9465) Node.js client: improve complex object flags processing
Alexey Kosenchuk created IGNITE-9465: Summary: Node.js client: improve complex object flags processing Key: IGNITE-9465 URL: https://issues.apache.org/jira/browse/IGNITE-9465 Project: Ignite Issue Type: Bug Components: thin client Reporter: Alexey Kosenchuk Assignee: ekaterina.vergizova Fix For: 2.7 1) fix the issue in the full schema support 2) do not throw exception when object with HAS_RAW_DATA flag is received 3) support OFFSET_*_BYTE flags/optimizations when writing data -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9464) MVCC TX: cache GET supports Mvcc tx mode.
[ https://issues.apache.org/jira/browse/IGNITE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-9464: Assignee: Andrew Mashenkov > MVCC TX: cache GET supports Mvcc tx mode. > - > > Key: IGNITE-9464 > URL: https://issues.apache.org/jira/browse/IGNITE-9464 > Project: Ignite > Issue Type: New Feature > Components: cache, mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9464) MVCC TX: cache GET supports Mvcc tx mode.
Andrew Mashenkov created IGNITE-9464: Summary: MVCC TX: cache GET supports Mvcc tx mode. Key: IGNITE-9464 URL: https://issues.apache.org/jira/browse/IGNITE-9464 Project: Ignite Issue Type: New Feature Components: cache, mvcc Reporter: Andrew Mashenkov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9360) Destroy SnapTreeMap and related classes
[ https://issues.apache.org/jira/browse/IGNITE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603228#comment-16603228 ] ASF GitHub Bot commented on IGNITE-9360: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4608 > Destroy SnapTreeMap and related classes > --- > > Key: IGNITE-9360 > URL: https://issues.apache.org/jira/browse/IGNITE-9360 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Fix For: 2.7 > > > It's not used anywhere and noone wants it, and it's a solid block of code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9360) Destroy SnapTreeMap and related classes
[ https://issues.apache.org/jira/browse/IGNITE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603226#comment-16603226 ] Dmitriy Govorukhin commented on IGNITE-9360: [~ilyak] Thanks for the contribution, merged to master. > Destroy SnapTreeMap and related classes > --- > > Key: IGNITE-9360 > URL: https://issues.apache.org/jira/browse/IGNITE-9360 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Fix For: 2.7 > > > It's not used anywhere and noone wants it, and it's a solid block of code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9463) [ML] Update ML tutorial with new model composition/update features
Aleksey Zinoviev created IGNITE-9463: Summary: [ML] Update ML tutorial with new model composition/update features Key: IGNITE-9463 URL: https://issues.apache.org/jira/browse/IGNITE-9463 Project: Ignite Issue Type: New Feature Components: ml Affects Versions: 2.7 Reporter: Aleksey Zinoviev Assignee: Aleksey Zinoviev Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-6454) Data structure suite timeout: test is not able to fail after interruption
[
https://issues.apache.org/jira/browse/IGNITE-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603193#comment-16603193
]
Denis Garus edited comment on IGNITE-6454 at 9/4/18 3:36 PM:
-
I think we need add some tests to this ticket. They hang with the same log.
GridCachePartitionedDataStructuresFailoverSelfTest#testReentrantLockConstantTopologyChangeNonFailoverSafe
GridCachePartitionedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe
GridCacheReplicatedDataStructuresFailoverSelfTest#testReentrantLockConstantTopologyChangeNonFailoverSafe
GridCacheReplicatedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe
I've created PR for that
https://github.com/apache/ignite/pull/4682
was (Author: garus.d.g):
I think we need add some tests to this ticket. They hang with the same log.
GridCachePartitionedDataStructuresFailoverSelfTest#testReentrantLockConstantTopologyChangeNonFailoverSafe
GridCachePartitionedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe
GridCacheReplicatedDataStructuresFailoverSelfTest#testReentrantLockConstantTopologyChangeNonFailoverSafe
GridCacheReplicatedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe
> Data structure suite timeout: test is not able to fail after interruption
> -
>
> Key: IGNITE-6454
> URL: https://issues.apache.org/jira/browse/IGNITE-6454
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
> Attachments:
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip,
>
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip
>
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteDataStrucutures=%3Cdefault%3E=buildTypeStatusDiv
> Most often timeout is caused by following tests:
> GridCacheReplicatedDataStructuresFailoverSelfTest
> - testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> - testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> And most of thread dumps contains the following
> {noformat}
> ] :[Step 4/5] Thread
> [name="test-runner-#35143%replicated.GridCacheReplicatedDataStructuresFailoverSelfTest%",
> id=38586, state=RUNNABLE, blockCnt=0, waitCnt=60]
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Native Method)
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Throwable.java:783)
> [20:34:26] : [Step 4/5] - locked o.a.i.IgniteException@754033e
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.(Throwable.java:265)
> [20:34:26] : [Step 4/5] at
> java.lang.Exception.(Exception.java:66)
> [20:34:26] : [Step 4/5] at
> java.lang.RuntimeException.(RuntimeException.java:62)
> [20:34:26] : [Step 4/5] at
> o.a.i.IgniteException.(IgniteException.java:44)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.validate(GridCacheLockImpl.java:275)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.access$1000(GridCacheLockImpl.java:122)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1200)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.doTestReentrantLock(GridCacheAbstractDataStructuresFailoverSelfTest.java:785)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:739)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [20:34:26] : [Step 4/5] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [20:34:26] : [Step 4/5] at
> java.lang.reflect.Method.invoke(Method.java:606)
> [20:34:26] : [Step 4/5] at
> junit.framework.TestCase.runTest(TestCase.java:176)
> [20:34:26] : [Step 4/5] at
>
[jira] [Comment Edited] (IGNITE-9171) Use lazy mode with results pre-fetch
[
https://issues.apache.org/jira/browse/IGNITE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603198#comment-16603198
]
Taras Ledkov edited comment on IGNITE-9171 at 9/4/18 3:35 PM:
--
[~vozerov], please take a look at the benchmark results.
Benchmark configuration:
- 4 servers, 8 clients (AWS {{m5.xlarge}} image).
- 1 backups;
Benchmark names agenda:
- rN - results set size (one row, 1K and 2k rows, 1M rows)
- lazy - lazy mode on.
Operations per second:
|||| master || ignite-9171 ||
| r1| 154,550.61 | 153,534.05|
| r1K | 6,097.21 | 6,027.85 |
| r2K | 3,523.90 | 3,478.26 |
| r1M | 16.51| 16.45 |
| r1-lazy | 24,474.02| 146,916.20|
| r1K-lazy | 2,014.16 | 6,043.35 |
| r2K-lazy | 1,839.11 | 3,503.99 |
| r1M-lazy | 21.09| 21.00 |
was (Author: tledkov-gridgain):
[~vozerov], please take a look at the benchmark results.
Benchmark configuration:
- 4 servers, 8 clients.
- 1 backups;
Benchmark names agenda:
- rN - results set size (one row, 1K and 2k rows, 1M rows)
- lazy - lazy mode on.
Operations per second:
|||| master || ignite-9171 ||
| r1| 154,550.61 | 153,534.05|
| r1K | 6,097.21 | 6,027.85 |
| r2K | 3,523.90 | 3,478.26 |
| r1M | 16.51| 16.45 |
| r1-lazy | 24,474.02| 146,916.20|
| r1K-lazy | 2,014.16 | 6,043.35 |
| r2K-lazy | 1,839.11 | 3,503.99 |
| r1M-lazy | 21.09| 21.00 |
> Use lazy mode with results pre-fetch
>
>
> Key: IGNITE-9171
> URL: https://issues.apache.org/jira/browse/IGNITE-9171
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
>
> Current implementation of the {{lazy}} mode always starts separate thread for
> {{MapQueryLazyWorker}}. It causes excessive overhead for requests that
> produces small results set.
> We have to begin execute query at the {{QUERY_POOL}} thread pool and fetch
> first page of the results. In case results set is bigger than one page
> {{MapQueryLazyWorker}} is started and link with {{MapNodeResults}} to handle
> next pages lazy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-6454) Data structure suite timeout: test is not able to fail after interruption
[
https://issues.apache.org/jira/browse/IGNITE-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603205#comment-16603205
]
ASF GitHub Bot commented on IGNITE-6454:
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4682
IGNITE-6454 muted flaky tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite IGNITE-6454
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4682.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 #4682
commit 75646c063f93cb32dd4e85a4441ef431f44cf3dd
Author: dgarus
Date: 2018-09-04T15:32:12Z
IGNITE-6454 muted flaky tests
> Data structure suite timeout: test is not able to fail after interruption
> -
>
> Key: IGNITE-6454
> URL: https://issues.apache.org/jira/browse/IGNITE-6454
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
> Attachments:
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip,
>
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip
>
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteDataStrucutures=%3Cdefault%3E=buildTypeStatusDiv
> Most often timeout is caused by following tests:
> GridCacheReplicatedDataStructuresFailoverSelfTest
> - testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> - testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> And most of thread dumps contains the following
> {noformat}
> ] :[Step 4/5] Thread
> [name="test-runner-#35143%replicated.GridCacheReplicatedDataStructuresFailoverSelfTest%",
> id=38586, state=RUNNABLE, blockCnt=0, waitCnt=60]
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Native Method)
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Throwable.java:783)
> [20:34:26] : [Step 4/5] - locked o.a.i.IgniteException@754033e
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.(Throwable.java:265)
> [20:34:26] : [Step 4/5] at
> java.lang.Exception.(Exception.java:66)
> [20:34:26] : [Step 4/5] at
> java.lang.RuntimeException.(RuntimeException.java:62)
> [20:34:26] : [Step 4/5] at
> o.a.i.IgniteException.(IgniteException.java:44)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.validate(GridCacheLockImpl.java:275)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.access$1000(GridCacheLockImpl.java:122)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1200)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.doTestReentrantLock(GridCacheAbstractDataStructuresFailoverSelfTest.java:785)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:739)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [20:34:26] : [Step 4/5] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [20:34:26] : [Step 4/5] at
> java.lang.reflect.Method.invoke(Method.java:606)
> [20:34:26] : [Step 4/5] at
> junit.framework.TestCase.runTest(TestCase.java:176)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> [20:34:26] : [Step 4/5] at java.lang.Thread.run(Thread.java:745)
> [20:34:26] : [Step 4/5]
> {noformat}
> That can be indicator that threads are interrupted and flag
>
[jira] [Commented] (IGNITE-9171) Use lazy mode with results pre-fetch
[
https://issues.apache.org/jira/browse/IGNITE-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603198#comment-16603198
]
Taras Ledkov commented on IGNITE-9171:
--
[~vozerov], please take a look at the benchmark results.
Benchmark configuration:
- 4 servers, 8 clients.
- 1 backups;
Benchmark names agenda:
- rN - results set size (one row, 1K and 2k rows, 1M rows)
- lazy - lazy mode on.
Operations per second:
|||| master || ignite-9171 ||
| r1| 154,550.61 | 153,534.05|
| r1K | 6,097.21 | 6,027.85 |
| r2K | 3,523.90 | 3,478.26 |
| r1M | 16.51| 16.45 |
| r1-lazy | 24,474.02| 146,916.20|
| r1K-lazy | 2,014.16 | 6,043.35 |
| r2K-lazy | 1,839.11 | 3,503.99 |
| r1M-lazy | 21.09| 21.00 |
> Use lazy mode with results pre-fetch
>
>
> Key: IGNITE-9171
> URL: https://issues.apache.org/jira/browse/IGNITE-9171
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql-stability
> Fix For: 2.7
>
>
> Current implementation of the {{lazy}} mode always starts separate thread for
> {{MapQueryLazyWorker}}. It causes excessive overhead for requests that
> produces small results set.
> We have to begin execute query at the {{QUERY_POOL}} thread pool and fetch
> first page of the results. In case results set is bigger than one page
> {{MapQueryLazyWorker}} is started and link with {{MapNodeResults}} to handle
> next pages lazy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9419) Avoid saving cache configuration synchronously during PME
[ https://issues.apache.org/jira/browse/IGNITE-9419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-9419: Issue Type: Improvement (was: Bug) > Avoid saving cache configuration synchronously during PME > - > > Key: IGNITE-9419 > URL: https://issues.apache.org/jira/browse/IGNITE-9419 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.7 > > > Currently, we save cache configuration during PME at the activation phase > here > org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.CachesInfo#updateCachesInfo > . We should avoid this, as it performs operations to a disk. We should save > it asynchronously or lazy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6454) Data structure suite timeout: test is not able to fail after interruption
[
https://issues.apache.org/jira/browse/IGNITE-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603193#comment-16603193
]
Denis Garus commented on IGNITE-6454:
-
I think we need add some tests to this ticket. They hang with the same log.
GridCachePartitionedDataStructuresFailoverSelfTest#testReentrantLockConstantTopologyChangeNonFailoverSafe
GridCachePartitionedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe
GridCacheReplicatedDataStructuresFailoverSelfTest#testReentrantLockConstantTopologyChangeNonFailoverSafe
GridCacheReplicatedDataStructuresFailoverSelfTest#testFairReentrantLockConstantTopologyChangeNonFailoverSafe
> Data structure suite timeout: test is not able to fail after interruption
> -
>
> Key: IGNITE-6454
> URL: https://issues.apache.org/jira/browse/IGNITE-6454
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
> Attachments:
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip,
>
> lastStartedTest_GridCacheReplicatedDataStructuresFailoverSelfTest.testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe.log.zip
>
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteDataStrucutures=%3Cdefault%3E=buildTypeStatusDiv
> Most often timeout is caused by following tests:
> GridCacheReplicatedDataStructuresFailoverSelfTest
> - testReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> - testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe()
> And most of thread dumps contains the following
> {noformat}
> ] :[Step 4/5] Thread
> [name="test-runner-#35143%replicated.GridCacheReplicatedDataStructuresFailoverSelfTest%",
> id=38586, state=RUNNABLE, blockCnt=0, waitCnt=60]
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Native Method)
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.fillInStackTrace(Throwable.java:783)
> [20:34:26] : [Step 4/5] - locked o.a.i.IgniteException@754033e
> [20:34:26] : [Step 4/5] at
> java.lang.Throwable.(Throwable.java:265)
> [20:34:26] : [Step 4/5] at
> java.lang.Exception.(Exception.java:66)
> [20:34:26] : [Step 4/5] at
> java.lang.RuntimeException.(RuntimeException.java:62)
> [20:34:26] : [Step 4/5] at
> o.a.i.IgniteException.(IgniteException.java:44)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.validate(GridCacheLockImpl.java:275)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl$Sync.access$1000(GridCacheLockImpl.java:122)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.datastructures.GridCacheLockImpl.lock(GridCacheLockImpl.java:1200)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.doTestReentrantLock(GridCacheAbstractDataStructuresFailoverSelfTest.java:785)
> [20:34:26] : [Step 4/5] at
> o.a.i.i.processors.cache.datastructures.GridCacheAbstractDataStructuresFailoverSelfTest.testFairReentrantLockConstantMultipleTopologyChangeNonFailoverSafe(GridCacheAbstractDataStructuresFailoverSelfTest.java:739)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [20:34:26] : [Step 4/5] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [20:34:26] : [Step 4/5] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [20:34:26] : [Step 4/5] at
> java.lang.reflect.Method.invoke(Method.java:606)
> [20:34:26] : [Step 4/5] at
> junit.framework.TestCase.runTest(TestCase.java:176)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> [20:34:26] : [Step 4/5] at
> o.a.i.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> [20:34:26] : [Step 4/5] at java.lang.Thread.run(Thread.java:745)
> [20:34:26] : [Step 4/5]
> {noformat}
> That can be indicator that threads are interrupted and flag
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl#interruptAll
> is set,
> than org.apache.ignite.IgniteException is thrown, but it is ignored by test
> and test continues to execute
--
This
[jira] [Commented] (IGNITE-9054) ScanQuery responses are serialized with Optimized Marshaller
[ https://issues.apache.org/jira/browse/IGNITE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603189#comment-16603189 ] ASF GitHub Bot commented on IGNITE-9054: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4592 > ScanQuery responses are serialized with Optimized Marshaller > > > Key: IGNITE-9054 > URL: https://issues.apache.org/jira/browse/IGNITE-9054 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: easyfix > Attachments: 22530.diff > > > When you do ContinuousQuery on a cache, its initial query sends results via > OptimizedMarshaller (which has binary compatibility implications) but its > continuous part uses BinaryMarshaller. They should both be using > BinaryMarshaller. Fix seems to be one-liner, see patch and userlist thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9274) Pass transaction label to cache events
[
https://issues.apache.org/jira/browse/IGNITE-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603183#comment-16603183
]
Yury Gerzhedovich commented on IGNITE-9274:
---
[~vozerov], TC run has been successfully done -
[https://ci.ignite.apache.org/viewLog.html?buildId=1792649;]
> Pass transaction label to cache events
> --
>
> Key: IGNITE-9274
> URL: https://issues.apache.org/jira/browse/IGNITE-9274
> Project: Ignite
> Issue Type: Task
> Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Yury Gerzhedovich
>Priority: Major
> Fix For: 2.7
>
>
> It is possible to set transaction label - \{{IgniteTransactions.withLabel}}.
> We need to pass this label to related cache and transaction events:
> 1) EVT_TX_STARTED, EVT_TX_COMMITTED, EVT_TX_ROLLED_BACK, EVT_TX_SUSPENDED,
> EVT_TX_RESUMED
> 2) EVT_CACHE_OBJECT_READ, EVT_CACHE_OBJECT_PUT, EVT_CACHE_OBJECT_REMOVED
> For TX events most probably everything is already passed (see
> \{{TransactionStateChangedEvent}}), we only need to add tests.
> For put/remove events we need to investigate correct messages to pass label,
> prepare requests appear to be good candidates for this.
> For read operation we may need to add pass label to get/lock requests
> ({{GridNearLockRequest}}, {{GridNearGetRequest}},
> {{GridNearSingleGetRequest}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9387) [ML] Model updating
[ https://issues.apache.org/jira/browse/IGNITE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603179#comment-16603179 ] ASF GitHub Bot commented on IGNITE-9387: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4659 > [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 >Priority: Major > 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] [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=16603163#comment-16603163
]
ASF GitHub Bot commented on IGNITE-9333:
akalash commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214726814
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/RelatedIssuesRef.java
##
@@ -0,0 +1,29 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.result;
+
+import javax.xml.bind.annotation.XmlAttribute;
+
+/**
+ * Related issues reference.
+ */
+public class RelatedIssuesRef {
Review comment:
extends AbstractRef like ChangesListRef
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] [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=16603162#comment-16603162
]
ASF GitHub Bot commented on IGNITE-9333:
akalash commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214728863
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/issues/IssueRef.java
##
@@ -0,0 +1,38 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.result.issues;
+
+import javax.xml.bind.annotation.XmlAttribute;
+
+/**
+ * Issue short version from list of build's related issues.
+ *
+ * See example of XML, e.g. here
+ * https://ci.ignite.apache.org/app/rest/latest/builds/id:1694977/relatedIssues
+ */
+public class IssueRef {
Review comment:
We already have IssueRef class but it means other entity and it is very
awkward. I think this is correct name(because TC have it), but perhaps old
class should be renamed.
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] [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=16603166#comment-16603166
]
ASF GitHub Bot commented on IGNITE-9333:
akalash commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214725893
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
##
@@ -290,14 +298,16 @@ private IgnitePersistentTeamcity(Ignite ignite,
IgniteTeamcityHelper teamcity) {
return mergeByIdToHistoricalOrder(persistedValue, builds);
});
+
+return buildRefs.stream().skip(cnt < buildRefs.size() ?
buildRefs.size() - cnt : 0).collect(Collectors.toList());
Review comment:
In what case it can be happen(cnt < buildRefs.size())?
And maybe better use some formatting for stream, because one line stream is
too hard to read.
```
buildRefs.stream()
.skip(cnt < buildRefs.size() ? buildRefs.size() - cnt : 0)
.collect(Collectors.toList());
```
?
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] [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=16603164#comment-16603164
]
ASF GitHub Bot commented on IGNITE-9333:
akalash commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214727827
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java
##
@@ -149,4 +155,69 @@ public TestFailuresSummary getBuildTestFails(
return res;
}
+
+@GET
+@Path("history")
+public BuildStatisticsSummary[] getBuildsHistory(
+@Nullable @QueryParam("server") String server,
+@Nullable @QueryParam("buildType") String buildType,
+@Nullable @QueryParam("branch") String branch,
+@Nullable @QueryParam("count") Integer count)
+throws ServiceUnauthorizedException {
+
+String srvId = isNullOrEmpty(server) ? "apache" : server;
+String buildTypeId = isNullOrEmpty(buildType) ?
"IgniteTests24Java8_RunAll" : buildType;
+String branchName = isNullOrEmpty(branch) ? "refs/heads/master" :
branch;
+int cnt = count == null ? 50 : count;
+
+final BackgroundUpdater updater =
CtxListener.getBackgroundUpdater(context);
+
+final ITcHelper tcHelper = CtxListener.getTcHelper(context);
+
+final ICredentialsProv prov = ICredentialsProv.get(req);
+
+try (IAnalyticsEnabledTeamcity teamcity = tcHelper.server(srvId,
prov)) {
+
+int[] finishedBuilds =
teamcity.getBuildNumbersFromHistory(buildTypeId, branchName, cnt);
+
+BuildStatisticsSummary[] buildsStatistics = new
BuildStatisticsSummary[finishedBuilds.length];
+
+for (int i = 0; i < finishedBuilds.length; i++) {
+int buildId = finishedBuilds[i];
+
+FullQueryParams param = new FullQueryParams();
+param.setBuildId(buildId);
+param.setBranch(branchName);
+param.setServerId(srvId);
+
+buildsStatistics[finishedBuilds.length - 1 - i] = updater.get(
+BUILDS_STATISTICS_SUMMARY_CACHE_NAME, prov, param,
+(k) -> getBuildStatisticsSummaryNoCache(srvId, buildId),
false);
+}
+
+return buildsStatistics;
+}
+}
+
+
+@GET
+@Path("historyNoCache")
Review comment:
Looks like this endpoint is not required. It can be just simple method.
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] [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=16603161#comment-16603161
]
ASF GitHub Bot commented on IGNITE-9333:
akalash commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214729838
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -0,0 +1,172 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model.current;
+
+import java.util.List;
+import java.util.Objects;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+import javax.annotation.Nonnull;
+import org.apache.ignite.ci.ITeamcity;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueUsage;
+import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrence;
+import org.apache.ignite.ci.util.TimeUtil;
+import org.apache.ignite.ci.web.IBackgroundUpdatable;
+
+/**
+ * Summary of build statistics.
+ */
+public class BuildStatisticsSummary extends UpdateInfo implements
IBackgroundUpdatable {
+/** Build with test and problems references. */
+public Build build;
+
+/** List of problem occurrences. */
+private List problems;
+
+/** List of related issues. */
+public List relatedIssues;
+
+/** Duration printable. */
+public String durationPrintable;
+
+/** Build run result printable. */
+public String result;
+
+public BuildStatisticsSummary(Build build){
+this.build = build;
+}
+
+/** Initialize build statistics. */
+public void initialize(@Nonnull final ITeamcity teamcity) {
+
+problems = teamcity.getProblems(build).getProblemsNonNull();
+
+relatedIssues =
teamcity.getIssuesUsagesList(build.relatedIssuesRef.href).getIssuesUsagesNonNull().stream()
+.map(IssueUsage::getIssue).collect(Collectors.toList());
+
+durationPrintable = TimeUtil
+.getDurationPrintable(build.getFinishDate().getTime() -
build.getStartDate().getTime());
+
+result = getResult();
+}
+
+private long getExecutionTimeoutCount() {
+return
getProblemsStream().filter(ProblemOccurrence::isExecutionTimeout).count();
+}
+
+private long getJvmCrashProblemCount() {
+return
getProblemsStream().filter(ProblemOccurrence::isJvmCrash).count();
+}
+
+private long getExitCodeProblemsCount() {
+return
getProblemsStream().filter(ProblemOccurrence::isExitCode).count();
+}
+
+private long getOomeProblemCount() {
+return getProblemsStream().filter(ProblemOccurrence::isOome).count();
+}
+
+private long getFailedTestsProblemCount() {
+return
getProblemsStream().filter(ProblemOccurrence::isFailedTests).count();
+}
+
+private long getSnapshotDepProblemCount() {
+return
getProblemsStream().filter(ProblemOccurrence::isSnapshotDepProblem).count();
+}
+
+private long getOtherProblemCount() {
+return getProblemsStream().filter(p ->
+!p.isFailedTests()
+&& !p.isSnapshotDepProblem()
+&& !p.isExecutionTimeout()
+&& !p.isJvmCrash()
+&& !p.isExitCode()
+&& !p.isOome()).count();
+}
+
+private Stream getProblemsStream() {
+if (problems == null)
+return Stream.empty();
+
+return problems.stream().filter(Objects::nonNull);
+}
+
+/**
+ * Build Run Result (filled if failed).
+ *
+ * @return printable result.
+ */
+private String getResult() {
+StringBuilder res = new StringBuilder();
+
+addKnownProblemCnt(res, "TIMEOUT", getExecutionTimeoutCount());
+addKnownProblemCnt(res, "JVM CRASH", getJvmCrashProblemCount());
+addKnownProblemCnt(res, "OOMe", getOomeProblemCount());
+addKnownProblemCnt(res, "EXIT CODE", getExitCodeProblemsCount());
+
[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=16603165#comment-16603165
]
ASF GitHub Bot commented on IGNITE-9333:
akalash commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214714321
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
##
@@ -240,14 +243,14 @@ private IgnitePersistentTeamcity(Ignite ignite,
IgniteTeamcityHelper teamcity) {
return loaded;
}
-private V timedLoadIfAbsentOrMerge(IgniteCache>
cache, int seconds, K key,
+private V timedLoadIfAbsentOrMerge(IgniteCache>
cache, int seconds, long cnt, K key,
BiFunction loadWithMerge) {
@Nullable final Expirable persistedBuilds = cache.get(key);
int fields = ObjectInterner.internFields(persistedBuilds);
if (persistedBuilds != null) {
-if (persistedBuilds.isAgeLessThanSecs(seconds))
+if (persistedBuilds.isAgeLessThanSecs(seconds) &&
persistedBuilds.isLastCntGreaterThanCurrentCnt(cnt))
Review comment:
Method name "isLastCntGreaterThanCurrentCnt" is not clear for me, I can't
catch which is last cnt and which is current cnt. Maybe better something like
"hasCounterGreaterThan"?
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] [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=16603160#comment-16603160
]
ASF GitHub Bot commented on IGNITE-9333:
akalash commented on a change in pull request #3: IGNITE-9333 Add statistics
page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3#discussion_r214726174
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
##
@@ -290,14 +298,16 @@ private IgnitePersistentTeamcity(Ignite ignite,
IgniteTeamcityHelper teamcity) {
return mergeByIdToHistoricalOrder(persistedValue, builds);
});
+
+return buildRefs.stream().skip(cnt < buildRefs.size() ?
buildRefs.size() - cnt : 0).collect(Collectors.toList());
}
@NotNull
private List mergeByIdToHistoricalOrder(List
persistedVal, List mostActualVal) {
final SortedMap merge = new TreeMap<>();
if (persistedVal != null)
-persistedVal.forEach(b -> merge.put(b.getId(), b));
+persistedVal.stream().forEach(b -> merge.put(b.getId(), b));
Review comment:
For what? It is same but longer, isn't it?
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] [Commented] (IGNITE-5553) Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
[
https://issues.apache.org/jira/browse/IGNITE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603153#comment-16603153
]
Maxim Muzafarov commented on IGNITE-5553:
-
[~xtern], [~avinogradov]
I've read the whole discussion on dev.list according to this change and
removing {{setDataMap}} seems to be a bit less risky and easier to implement
without huge {{IgniteSet}} slowdown impact.
I think prepared PR is ready for final review, whole its changes looks good to
me.
Anton, can you look at this PR as an expert in data structures an provide your
thoughts?
If everything is OK, I think we can start checking TC carefully.
> Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
> -
>
> Key: IGNITE-5553
> URL: https://issues.apache.org/jira/browse/IGNITE-5553
> Project: Ignite
> Issue Type: Bug
> Components: data structures, persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.7
>
>
> h2. Notes-4435
> When IgniteSet is restored from persistence, size of set is always 0, [link
> to test
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-7043871603266099589=testDetails].
> h2. Detailed description
> Unlike *IgniteQueue* which uses separate cache key to store its size
> *IgniteSet* stores it in a field of some class.
> Test from the link above shows very clearly that after restoring memory state
> from PDS all set values are restored correctly but size is lost.
> h2. Proposed solution
> One possible solution might be to do the same thing as *IgniteQueue* does:
> size of *IgniteSet* must be stored is cache instead of volatile in-memory
> fields of random classes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment
[ https://issues.apache.org/jira/browse/IGNITE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603134#comment-16603134 ] Denis Mekhanikov commented on IGNITE-9009: -- [~agoncharuk], done. Please take a look. > Local continuous query listeners may be called on partition reassignment > > > Key: IGNITE-9009 > URL: https://issues.apache.org/jira/browse/IGNITE-9009 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: ContinuousQueryReassignmentTest.java > > > When a node becomes primary for some partitions, then local continuous query > listeners receive updates on entries from that partitions. Such invocations > shouldn't happen. > Attached test class demonstrates this behaviour. > Dev list discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Backup-queue-for-local-continuous-query-td33391.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8545) If queryParallelism in nodes' caches configurations differ, query may hang, assert or return incomplete results
[ https://issues.apache.org/jira/browse/IGNITE-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Pudov reassigned IGNITE-8545: --- Assignee: Maxim Pudov > If queryParallelism in nodes' caches configurations differ, query may hang, > assert or return incomplete results > --- > > Key: IGNITE-8545 > URL: https://issues.apache.org/jira/browse/IGNITE-8545 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.6 >Reporter: Ilya Kasnacheev >Assignee: Maxim Pudov >Priority: Critical > Attachments: IgniteSqlSplitterQueryParallelismTest.java > > > I imagine it should not. See the attached file. > It happens both with client nodes and with server nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603122#comment-16603122
]
Vladislav Pyatkov commented on IGNITE-9422:
---
Looks good for me.
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.8
>
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9441) Failed to read WAL record at position
[
https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603121#comment-16603121
]
Anton Kalashnikov commented on IGNITE-9441:
---
[~DmitriyGovorukhin] take a look, please.
> Failed to read WAL record at position
> -
>
> Key: IGNITE-9441
> URL: https://issues.apache.org/jira/browse/IGNITE-9441
> Project: Ignite
> Issue Type: Test
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
> {noformat}
> [2018-08-31
> 10:00:51,550][ERROR][sys-#32855%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridCacheIoManager]
> Failed processing message [senderId=60a69491-d44f-482b-9e7a-5ab1e2c3,
> msg=GridDhtPartitionDemandMessage [rebalanceId=1,
> parts=IgniteDhtDemandedPartitionsMap
> [historical=CachePartitionPartialCountersMap {0=(1561,1591), 1=(1561,1591),
> 2=(1561,1591), 4=(1561,1591), 7=(1561,1591), 11=(1560,1591), 13=(1560,1591),
> 14=(1560,1591), 24=(1560,1591), 25=(1560,1590), 27=(1560,1590),
> 31=(1560,1590), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
> 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0)}], timeout=1,
> workerId=-1, topVer=AffinityTopologyVersion [topVer=30, minorTopVer=0],
> partCnt=12, super=GridCacheGroupIdMessage [grpId=94416770]]]
> class org.apache.ignite.IgniteException: Failed to read WAL record at
> position: 23721849 size: 67108864
> at
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1043)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:958)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:927)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:852)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:345)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:426)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:405)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:390)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
>
[jira] [Updated] (IGNITE-9441) Failed to read WAL record at position
[
https://issues.apache.org/jira/browse/IGNITE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kalashnikov updated IGNITE-9441:
--
Description:
IgnitePdsAtomicCacheHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
IgnitePdsAtomicCacheHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
IgnitePdsTxHistoricalRebalancingTest.testPartitionCounterConsistencyOnUnstableTopology
{noformat}
[2018-08-31
10:00:51,550][ERROR][sys-#32855%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridCacheIoManager]
Failed processing message [senderId=60a69491-d44f-482b-9e7a-5ab1e2c3,
msg=GridDhtPartitionDemandMessage [rebalanceId=1,
parts=IgniteDhtDemandedPartitionsMap
[historical=CachePartitionPartialCountersMap {0=(1561,1591), 1=(1561,1591),
2=(1561,1591), 4=(1561,1591), 7=(1561,1591), 11=(1560,1591), 13=(1560,1591),
14=(1560,1591), 24=(1560,1591), 25=(1560,1590), 27=(1560,1590), 31=(1560,1590),
0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0),
0=(0,0), 0=(0,0), 0=(0,0), 0=(0,0)}], timeout=1, workerId=-1,
topVer=AffinityTopologyVersion [topVer=30, minorTopVer=0], partCnt=12,
super=GridCacheGroupIdMessage [grpId=94416770]]]
class org.apache.ignite.IgniteException: Failed to read WAL record at position:
23721849 size: 67108864
at
org.apache.ignite.internal.util.lang.GridIteratorAdapter.next(GridIteratorAdapter.java:38)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.advance(GridCacheOffheapManager.java:1043)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.next(GridCacheOffheapManager.java:958)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:927)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$WALHistoricalIterator.nextX(GridCacheOffheapManager.java:852)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.nextX(IgniteRebalanceIteratorImpl.java:130)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:185)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.IgniteRebalanceIteratorImpl.next(IgniteRebalanceIteratorImpl.java:37)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionSupplier.handleDemandMessage(GridDhtPartitionSupplier.java:345)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.handleDemandMessage(GridDhtPreloader.java:426)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:405)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:390)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$700(GridCacheIoManager.java:101)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1613)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4100(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2768)
at
org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1529)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4400(GridIoManager.java:127)
at
org.apache.ignite.internal.managers.communication.GridIoManager$10.run(GridIoManager.java:1498)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
record at position: 23721849 size: 67108864
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:289)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:255)
at
[jira] [Commented] (IGNITE-9054) ScanQuery responses are serialized with Optimized Marshaller
[ https://issues.apache.org/jira/browse/IGNITE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603099#comment-16603099 ] ASF GitHub Bot commented on IGNITE-9054: GitHub user alamar reopened a pull request: https://github.com/apache/ignite/pull/4592 IGNITE-9054 Avoid using OptimizedMarshaller with initial ScanQuery. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-14092 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4592.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 #4592 commit d5ae876319086dacb1f7ff7fde8aed113892f744 Author: Ilya Kasnacheev Date: 2018-08-22T15:17:51Z IGNITE-9054 Avoid using OptimizedMarshaller with initial ScanQuery. > ScanQuery responses are serialized with Optimized Marshaller > > > Key: IGNITE-9054 > URL: https://issues.apache.org/jira/browse/IGNITE-9054 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: easyfix > Attachments: 22530.diff > > > When you do ContinuousQuery on a cache, its initial query sends results via > OptimizedMarshaller (which has binary compatibility implications) but its > continuous part uses BinaryMarshaller. They should both be using > BinaryMarshaller. Fix seems to be one-liner, see patch and userlist thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9401) Newly added testRollbackOnTopologyLockPessimistic has a race which leads to suite hang.
[ https://issues.apache.org/jira/browse/IGNITE-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev updated IGNITE-9401: -- Ignite Flags: (was: Docs Required) > Newly added testRollbackOnTopologyLockPessimistic has a race which leads to > suite hang. > > > Key: IGNITE-9401 > URL: https://issues.apache.org/jira/browse/IGNITE-9401 > Project: Ignite > Issue Type: Bug >Reporter: Alexei Scherbakov >Assignee: Alexei Scherbakov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9054) ScanQuery responses are serialized with Optimized Marshaller
[ https://issues.apache.org/jira/browse/IGNITE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603094#comment-16603094 ] ASF GitHub Bot commented on IGNITE-9054: Github user alamar closed the pull request at: https://github.com/apache/ignite/pull/4592 > ScanQuery responses are serialized with Optimized Marshaller > > > Key: IGNITE-9054 > URL: https://issues.apache.org/jira/browse/IGNITE-9054 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.5 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: easyfix > Attachments: 22530.diff > > > When you do ContinuousQuery on a cache, its initial query sends results via > OptimizedMarshaller (which has binary compatibility implications) but its > continuous part uses BinaryMarshaller. They should both be using > BinaryMarshaller. Fix seems to be one-liner, see patch and userlist thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment
[
https://issues.apache.org/jira/browse/IGNITE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603090#comment-16603090
]
Alexey Goncharuk commented on IGNITE-9009:
--
[~dmekhanikov], please update {{ContinuousQuery#setLocal}} javadoc to state the
fact that some CQ notifications may be missed during node failures when this
flag is used.
> Local continuous query listeners may be called on partition reassignment
>
>
> Key: IGNITE-9009
> URL: https://issues.apache.org/jira/browse/IGNITE-9009
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Denis Mekhanikov
>Assignee: Denis Mekhanikov
>Priority: Major
> Fix For: 2.8
>
> Attachments: ContinuousQueryReassignmentTest.java
>
>
> When a node becomes primary for some partitions, then local continuous query
> listeners receive updates on entries from that partitions. Such invocations
> shouldn't happen.
> Attached test class demonstrates this behaviour.
> Dev list discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/Backup-queue-for-local-continuous-query-td33391.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment
[ https://issues.apache.org/jira/browse/IGNITE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9009: - Ignite Flags: Docs Required > Local continuous query listeners may be called on partition reassignment > > > Key: IGNITE-9009 > URL: https://issues.apache.org/jira/browse/IGNITE-9009 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: ContinuousQueryReassignmentTest.java > > > When a node becomes primary for some partitions, then local continuous query > listeners receive updates on entries from that partitions. Such invocations > shouldn't happen. > Attached test class demonstrates this behaviour. > Dev list discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Backup-queue-for-local-continuous-query-td33391.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603081#comment-16603081
]
Roman Shtykh edited comment on IGNITE-9453 at 9/4/18 1:58 PM:
--
[~ivandasch] Ok, let me see tomorrow. But that'll be a hack, as you mentioned ;)
If you have some ideas, will be happy to hear.
was (Author: roman_s):
[~ivandasch] Ok, let me see. But that'll be a hack, as you mentioned ;)
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9366) SQL system view for node metrics
[
https://issues.apache.org/jira/browse/IGNITE-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603082#comment-16603082
]
Aleksey Plekhanov commented on IGNITE-9366:
---
[~vozerov] I've added new checks for this view accordnig to your comment,
please have a look again.
> SQL system view for node metrics
>
>
> Key: IGNITE-9366
> URL: https://issues.apache.org/jira/browse/IGNITE-9366
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: iep-13
> Fix For: 2.7
>
>
> Implement SQL system view to show metrics of each node (information is
> available locally on each node). View must contain NODE_ID column and the
> same set of metrics as provided by {{ClusterMetrics}} interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603081#comment-16603081
]
Roman Shtykh commented on IGNITE-9453:
--
[~ivandasch] Ok, let me see. But that'll be a hack, as you mentioned ;)
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment
[ https://issues.apache.org/jira/browse/IGNITE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Mekhanikov updated IGNITE-9009: - Description: When a node becomes primary for some partitions, then local continuous query listeners receive updates on entries from that partitions. Such invocations shouldn't happen. Attached test class demonstrates this behaviour. Dev list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Backup-queue-for-local-continuous-query-td33391.html was: When a node becomes primary for some partitions, then local continuous query listeners receive updates on entries from that partitions. Such invocations shouldn't happen. Attached test class demonstrates this behaviour. > Local continuous query listeners may be called on partition reassignment > > > Key: IGNITE-9009 > URL: https://issues.apache.org/jira/browse/IGNITE-9009 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: ContinuousQueryReassignmentTest.java > > > When a node becomes primary for some partitions, then local continuous query > listeners receive updates on entries from that partitions. Such invocations > shouldn't happen. > Attached test class demonstrates this behaviour. > Dev list discussion: > http://apache-ignite-developers.2346864.n4.nabble.com/Backup-queue-for-local-continuous-query-td33391.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603077#comment-16603077
]
Ivan Daschinskiy commented on IGNITE-9453:
--
[~roman_s] I suppose that it's possible to fix this by using reflection.
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9009) Local continuous query listeners may be called on partition reassignment
[ https://issues.apache.org/jira/browse/IGNITE-9009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603078#comment-16603078 ] Denis Mekhanikov commented on IGNITE-9009: -- [~agoncharuk], backups won't be notified, because they don't store the event queue. There are no ACKs sent to the backups. I think, local continuous queries should work in isolation from each other. If processing of cache events locally on all primary nodes is required, then [Cache#registerCacheEntryListener|https://static.javadoc.io/javax.cache/cache-api/1.0.0/javax/cache/Cache.html#registerCacheEntryListener(javax.cache.configuration.CacheEntryListenerConfiguration)] should be used. > Local continuous query listeners may be called on partition reassignment > > > Key: IGNITE-9009 > URL: https://issues.apache.org/jira/browse/IGNITE-9009 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > Attachments: ContinuousQueryReassignmentTest.java > > > When a node becomes primary for some partitions, then local continuous query > listeners receive updates on entries from that partitions. Such invocations > shouldn't happen. > Attached test class demonstrates this behaviour. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603075#comment-16603075
]
Roman Shtykh commented on IGNITE-9453:
--
[~ivandasch] I see now. Thanks!
WONT_FIX then for this issue?
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603069#comment-16603069
]
Ivan Daschinskiy commented on IGNITE-9453:
--
[~roman_s] This does'nt work for dynamic caches (ie "CREATE TABLE"),
getColumnTypeName returns BINARY.
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603067#comment-16603067
]
Roman Shtykh commented on IGNITE-9453:
--
Basically, my question also has a wider scope than this issue (probably that's
another question) – shall we use database-specific type name instead of the
fully-qualified name of the Java class? ;)
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603057#comment-16603057
]
Roman Shtykh edited comment on IGNITE-9453 at 9/4/18 1:39 PM:
--
[~ivandasch] Hmm, my variant returns the string with the database-specific type
for the given column. Can you look at it again please?
Here's what I have in my simple test.
{{{"successStatus":0,"error":null,"response":{"items":[["c101f07d-fa31-4fd4-9549-85479212e28b","c101f07d-fa31-4fd4-9549-85479212e28b"]],"last":true,"queryId":0,"fieldsMetadata":[
{"schemaName":"uuidCache","typeName":"UUID","fieldName":"_KEY","fieldTypeName":"UUID"}
,\{"schemaName":"uuidCache","typeName":"UUID","fieldName":"_VAL","fieldTypeName":"UUID"}]},"sessionToken":null}}}
Maybe we don't need getTypeClassName helper from from the issue you refer to?
was (Author: roman_s):
[~ivandasch] Hmm, my variant returns the string with the database-specific type
for the given column. Can you look at it again please?
Here's what I have in my simple test.
{{{"successStatus":0,"error":null,"response":\{"items":[["c101f07d-fa31-4fd4-9549-85479212e28b","c101f07d-fa31-4fd4-9549-85479212e28b"]],"last":true,"queryId":0,"fieldsMetadata":[{"schemaName":"uuidCache","typeName":"UUID","fieldName":"_KEY","fieldTypeName":"UUID"},\{"schemaName":"uuidCache","typeName":"UUID","fieldName":"_VAL","fieldTypeName":"UUID"}]},"sessionToken":null}}}
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603057#comment-16603057
]
Roman Shtykh commented on IGNITE-9453:
--
[~ivandasch] Hmm, my variant returns the string with the database-specific type
for the given column. Can you look at it again please?
Here's what I have in my simple test.
{{{"successStatus":0,"error":null,"response":\{"items":[["c101f07d-fa31-4fd4-9549-85479212e28b","c101f07d-fa31-4fd4-9549-85479212e28b"]],"last":true,"queryId":0,"fieldsMetadata":[{"schemaName":"uuidCache","typeName":"UUID","fieldName":"_KEY","fieldTypeName":"UUID"},\{"schemaName":"uuidCache","typeName":"UUID","fieldName":"_VAL","fieldTypeName":"UUID"}]},"sessionToken":null}}}
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603041#comment-16603041 ] ASF GitHub Bot commented on IGNITE-8987: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4664 > Ignite hangs during getting of atomic structure after autoactivation > > > Key: IGNITE-8987 > URL: https://issues.apache.org/jira/browse/IGNITE-8987 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.7 > > Attachments: reproducer.java > > > I investigate the use cases with autoactivation and creating of the > IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it > called after the last node from BLT was started. > Steps to reproduce: > First iteration: > > Do next in one thread: > 1)Start server 1 > 2)Start server 2 > 3)Activate the cluster > 4)Create the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > atomicConfiguration, > 10, > true); > Second iteration: > 1)Start server 1 > 2)Start server 2 (Autoactivation will be started) > 3)Get the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > 10, > true); //could be false because TestName was already created in iteration 1 > In this case, we hang in awaitInitialization() method in > DataStructureProcessor.getAtomic() method. > In case if I added some sleep timeout between step 2 and 3 in the second > iteration then everything was ok. Looks like we have some race here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603038#comment-16603038 ] Alexey Goncharuk commented on IGNITE-8987: -- Got it, the latch was re-created by the activation process and await was done on a wrong latch. Looks good, merging to master. > Ignite hangs during getting of atomic structure after autoactivation > > > Key: IGNITE-8987 > URL: https://issues.apache.org/jira/browse/IGNITE-8987 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.7 > > Attachments: reproducer.java > > > I investigate the use cases with autoactivation and creating of the > IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it > called after the last node from BLT was started. > Steps to reproduce: > First iteration: > > Do next in one thread: > 1)Start server 1 > 2)Start server 2 > 3)Activate the cluster > 4)Create the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > atomicConfiguration, > 10, > true); > Second iteration: > 1)Start server 1 > 2)Start server 2 (Autoactivation will be started) > 3)Get the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > 10, > true); //could be false because TestName was already created in iteration 1 > In this case, we hang in awaitInitialization() method in > DataStructureProcessor.getAtomic() method. > In case if I added some sleep timeout between step 2 and 3 in the second > iteration then everything was ok. Looks like we have some race here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603028#comment-16603028
]
Ivan Daschinskiy commented on IGNITE-9453:
--
[~roman_s] However, after this fix
[IGNITE-9183|https://issues.apache.org/jira/browse/IGNITE-9183], ignite handles
data correctly, this issue relates only to ResultSetMetaData. Data itself is ok.
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603025#comment-16603025
]
Ivan Daschinskiy commented on IGNITE-9453:
--
[~roman_s] I've already checked your variant, it also uses H2 internal utils
and returns bytearray. It seems that there is no way except patching H2 or
using reflection. This is a dirty hack, however.
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5553) Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
[ https://issues.apache.org/jira/browse/IGNITE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603018#comment-16603018 ] Pavel Pereslegin commented on IGNITE-5553: -- As described above, collocated IgniteSet uses on-heap caching known as "setDataMap" to support iterator, and I didn't find the optimal way to recover heap data after node restart ([details here|http://apache-ignite-developers.2346864.n4.nabble.com/IgniteSet-implementation-changes-required-tp23783p31923.html]). On devlist we decided to remove this optimization and the changes are ready according to this discussion. [~Mmuzaf], take a look at this patch please. > Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error > - > > Key: IGNITE-5553 > URL: https://issues.apache.org/jira/browse/IGNITE-5553 > Project: Ignite > Issue Type: Bug > Components: data structures, persistence >Affects Versions: 2.1 >Reporter: Dmitriy Pavlov >Assignee: Pavel Pereslegin >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test, test-fail > Fix For: 2.7 > > > h2. Notes-4435 > When IgniteSet is restored from persistence, size of set is always 0, [link > to test > history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-7043871603266099589=testDetails]. > h2. Detailed description > Unlike *IgniteQueue* which uses separate cache key to store its size > *IgniteSet* stores it in a field of some class. > Test from the link above shows very clearly that after restoring memory state > from PDS all set values are restored correctly but size is lost. > h2. Proposed solution > One possible solution might be to do the same thing as *IgniteQueue* does: > size of *IgniteSet* must be stored is cache instead of volatile in-memory > fields of random classes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9448) Change ZooKeeper version to 3.4.13
[ https://issues.apache.org/jira/browse/IGNITE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9448: - Ignite Flags: (was: Docs Required) > Change ZooKeeper version to 3.4.13 > -- > > Key: IGNITE-9448 > URL: https://issues.apache.org/jira/browse/IGNITE-9448 > Project: Ignite > Issue Type: Test > Components: zookeeper >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.7 > > > Should to change ZooKeeper dependency to last release - just now it is 3.4.13. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9448) Change ZooKeeper version to 3.4.13
[ https://issues.apache.org/jira/browse/IGNITE-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9448: - Fix Version/s: 2.7 > Change ZooKeeper version to 3.4.13 > -- > > Key: IGNITE-9448 > URL: https://issues.apache.org/jira/browse/IGNITE-9448 > Project: Ignite > Issue Type: Test > Components: zookeeper >Reporter: Vladislav Pyatkov >Assignee: Vladislav Pyatkov >Priority: Major > Fix For: 2.7 > > > Should to change ZooKeeper dependency to last release - just now it is 3.4.13. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinskiy updated IGNITE-9422:
-
Component/s: (was: zookeeper)
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.8
>
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinskiy updated IGNITE-9422:
-
Issue Type: Bug (was: Improvement)
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.8
>
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinskiy updated IGNITE-9422:
-
Fix Version/s: 2.8
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
> Fix For: 2.8
>
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9434) Create suites for MVCC tests on TC.
[ https://issues.apache.org/jira/browse/IGNITE-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-9434: - Labels: teamcity (was: MakeTeamcityGreenAgain teamcity) > Create suites for MVCC tests on TC. > --- > > Key: IGNITE-9434 > URL: https://issues.apache.org/jira/browse/IGNITE-9434 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Andrew Mashenkov >Priority: Blocker > Labels: teamcity > Fix For: 2.7 > > > MVCC tests suites should be created on Ignite TeamCity. > * org.apache.ignite.testsuites;.MvccQueryTrackerImpl > * org.apache.ignite.jdbc.suite.IgniteJdbcDriverMvccTestSuite > * org.apache.ignite.testsuites.IgniteCacheMvccTestSuite > "MVCC Run All" should be created as well to run mvcc tests only. > Mvcc tests should be added to "Run All" as well. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603010#comment-16603010
]
Ivan Daschinskiy commented on IGNITE-9422:
--
[~zstan] This issue occurs even if TCPDiscovery used, not only ZK.
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Improvement
> Components: zookeeper
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16603008#comment-16603008
]
ASF GitHub Bot commented on IGNITE-9422:
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4681
IGNITE-9422 Fixed NPE on clients when new binary meta from joined nod…
…e arrived.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9422
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4681.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 #4681
commit 9bdfab6aebac141a2a81df49f51addf84e7dcd26
Author: Ivan Daschinskiy
Date: 2018-09-04T12:40:41Z
IGNITE-9422 Fixed NPE on clients when new binary meta from joined node
arrived.
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Improvement
> Components: zookeeper
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9422) All client node fails with ZKDiscovery enabled.
[
https://issues.apache.org/jira/browse/IGNITE-9422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinskiy reassigned IGNITE-9422:
Assignee: Ivan Daschinskiy
> All client node fails with ZKDiscovery enabled.
> ---
>
> Key: IGNITE-9422
> URL: https://issues.apache.org/jira/browse/IGNITE-9422
> Project: Ignite
> Issue Type: Improvement
> Components: zookeeper
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Ivan Daschinskiy
>Priority: Major
>
> Found problem with using ZKDiscovery:
> {code:java}
> 2018-08-28 17:43:17,953 INFO
> [org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Newer version of existing
> BinaryMetadata[type
> Id=557511097, typeName=PublishedIndividual_D_PROXY] is received from node
> 33384a02-5cbb-4dd6-8318-6ee34c88a400; updating it locally
> 2018-08-28 17:43:17,954 ERROR
> [org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl]
> (zk-D_GRID%DplGridNodeName-EventThread) Fatal error in ZookeeperDiscovery.
> Stopping the node in orde
> r to prevent cluster wide instability.: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.onJoiningNodeDataReceived(CacheObjectBinaryProcessorImpl.java:1001)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:909)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processBulkJoin(ZookeeperDiscoveryImpl.java:2792)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2638)
> at
> org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoveryImpl.processNewEvents(ZookeeperDiscoveryImpl.java:2610)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9462) ADD originator to EVT_NODE_LEFT
[ https://issues.apache.org/jira/browse/IGNITE-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9462: - Description: EVT_NODE_LEFT event lacks information about the 'originator' of the node stop, if the node was stopped manually. We should check if the node is stopped by a signal, by node failure handler or by a user and add this information to the node left event, when it is available. We should add: 1) Thread name of the thread called Ignition.stop() 2) FQ-class name called Ignition.stop() 3) Cause of failure, if caused by a failure handler was:Pls add originator to EVT_NODE_LEFT, Thx > ADD originator to EVT_NODE_LEFT > --- > > Key: IGNITE-9462 > URL: https://issues.apache.org/jira/browse/IGNITE-9462 > Project: Ignite > Issue Type: Task >Reporter: Yuriy Sergeev >Priority: Major > > EVT_NODE_LEFT event lacks information about the 'originator' of the node > stop, if the node was stopped manually. > We should check if the node is stopped by a signal, by node failure handler > or by a user and add this information to the node left event, when it is > available. > We should add: > 1) Thread name of the thread called Ignition.stop() > 2) FQ-class name called Ignition.stop() > 3) Cause of failure, if caused by a failure handler -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9462) ADD originator to EVT_NODE_LEFT
Yuriy Sergeev created IGNITE-9462: - Summary: ADD originator to EVT_NODE_LEFT Key: IGNITE-9462 URL: https://issues.apache.org/jira/browse/IGNITE-9462 Project: Ignite Issue Type: Task Reporter: Yuriy Sergeev Pls add originator to EVT_NODE_LEFT, Thx -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8987) Ignite hangs during getting of atomic structure after autoactivation
[ https://issues.apache.org/jira/browse/IGNITE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602993#comment-16602993 ] Alexey Goncharuk commented on IGNITE-8987: -- [~guseinov], can you please describe the race that you've fixed? I am not sure that latch re-creation itself does not add another race. > Ignite hangs during getting of atomic structure after autoactivation > > > Key: IGNITE-8987 > URL: https://issues.apache.org/jira/browse/IGNITE-8987 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Andrey Aleksandrov >Assignee: Roman Guseinov >Priority: Major > Fix For: 2.7 > > Attachments: reproducer.java > > > I investigate the use cases with autoactivation and creating of the > IgniteAtomicSequence. It hangs on awaitInitialization() method in case if it > called after the last node from BLT was started. > Steps to reproduce: > First iteration: > > Do next in one thread: > 1)Start server 1 > 2)Start server 2 > 3)Activate the cluster > 4)Create the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > atomicConfiguration, > 10, > true); > Second iteration: > 1)Start server 1 > 2)Start server 2 (Autoactivation will be started) > 3)Get the IgniteAtomicSequence using next code: > IgniteAtomicSequence igniteAtomicSequence = ignite.atomicSequence( > "TestName", > 10, > true); //could be false because TestName was already created in iteration 1 > In this case, we hang in awaitInitialization() method in > DataStructureProcessor.getAtomic() method. > In case if I added some sleep timeout between step 2 and 3 in the second > iteration then everything was ok. Looks like we have some race here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9442) Collocated IgniteSet#close is not working on non-affinity node.
[
https://issues.apache.org/jira/browse/IGNITE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602965#comment-16602965
]
ASF GitHub Bot commented on IGNITE-9442:
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/4680
IGNITE-9442
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9442
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4680.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 #4680
commit fb7f21a41917b0ce1f58343376a5884aa3940bb2
Author: pereslegin-pa
Date: 2018-09-04T12:06:06Z
IGNITE-9442 Block set on all nodes.
> Collocated IgniteSet#close is not working on non-affinity node.
> ---
>
> Key: IGNITE-9442
> URL: https://issues.apache.org/jira/browse/IGNITE-9442
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>
> Simple reproducer:
> {code:java}
> public void testSetBlockOnCloseFromNonAffinityNode() throws Exception {
> Ignite node = startGridsMultiThreaded(2);
> ClusterNode locNode = node.cluster().localNode();
> IgniteSet set = node.set("test",
> new CollectionConfiguration().setCollocated(true).setNodeFilter(n
> -> !locNode.equals(n)));
> set.close();
> GridTestUtils.assertThrows(log, new Callable() {
> @Override public Void call() throws Exception {
> set.add(1);
> return null;
> }
> }, IllegalStateException.class, null);
> }
> {code}
> IgniteSet should be blocked on all nodes before cleanup data.
--
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=16602946#comment-16602946 ] Andrew Mashenkov commented on IGNITE-3303: -- [~samaitra], I've add some notes to the Upsource review. 1. I' not sure source.start\stop() methods update state correctly. 2. Minor changes needed to make test code better. > 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 >Assignee: 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-8927) Hangs when executing an SQL query when there are LOST partitions
[ https://issues.apache.org/jira/browse/IGNITE-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602942#comment-16602942 ] Vladimir Ozerov commented on IGNITE-8927: - Test run: https://ci.ignite.apache.org/viewLog.html?buildId=1792230=buildResultsDiv=IgniteTests24Java8_RunAllSql > Hangs when executing an SQL query when there are LOST partitions > > > Key: IGNITE-8927 > URL: https://issues.apache.org/jira/browse/IGNITE-8927 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Dmitriy Gladkikh >Assignee: Vladimir Ozerov >Priority: Major > Labels: sql-stability > Fix For: 2.7 > > > If there are partitions in the LOST state, SQL query hang. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-3303: Assignee: Saikat Maitra > 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 >Assignee: 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-8927) Hangs when executing an SQL query when there are LOST partitions
[ https://issues.apache.org/jira/browse/IGNITE-8927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602941#comment-16602941 ] ASF GitHub Bot commented on IGNITE-8927: GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4679 IGNITE-8927 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8927 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4679.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 #4679 commit 40fcd40cd713d012e1d9ce87b4612354f6e22bd3 Author: devozerov Date: 2018-09-04T09:48:54Z WIP. commit 7b6c902ee93fe8f98d000f86afa56571eac57c9a Author: devozerov Date: 2018-09-04T10:23:59Z WIP. commit 60e6c3057dbb6fbf598d3a32ad84e7b2890462f0 Author: devozerov Date: 2018-09-04T10:51:19Z WIP on test. Something is wrong with local query. > Hangs when executing an SQL query when there are LOST partitions > > > Key: IGNITE-8927 > URL: https://issues.apache.org/jira/browse/IGNITE-8927 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.5 >Reporter: Dmitriy Gladkikh >Assignee: Vladimir Ozerov >Priority: Major > Labels: sql-stability > Fix For: 2.7 > > > If there are partitions in the LOST state, SQL query hang. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9238) Test GridTaskFailoverAffinityRunTest.testNodeRestartClient hangs when coordinator forces client to reconnect on grid startup.
[
https://issues.apache.org/jira/browse/IGNITE-9238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602922#comment-16602922
]
Alexey Goncharuk commented on IGNITE-9238:
--
[~xtern], I do not understand how it can be that {{initVer.compareTo(readyVer)
< 0}}, but exchange for the client is not completed?
If a client joins on topology version {{initVer}}, then {{initVer <=
readyVer}}.
> Test GridTaskFailoverAffinityRunTest.testNodeRestartClient hangs when
> coordinator forces client to reconnect on grid startup.
> -
>
> Key: IGNITE-9238
> URL: https://issues.apache.org/jira/browse/IGNITE-9238
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Fix For: 2.7
>
> Attachments: Reproducer.java
>
>
> Example of such hang on TC:
> https://ci.ignite.apache.org/viewLog.html?buildId=1605243=buildResultsDiv=IgniteTests24Java8_ComputeGrid
> Log output:
> {noformat}
> ...
> [2018-08-07 12:20:09,804][WARN
> ][sys-#12799%internal.GridTaskFailoverAffinityRunTest1%][GridCachePartitionExchangeManager]
> Client node tries to connect but its exchange info is cleaned up from
> exchange history. Consider increasing 'IGNITE_EXCHANGE_HISTORY_SIZE' property
> or start clients in smaller batches. Current settings and versions:
> [IGNITE_EXCHANGE_HISTORY_SIZE=1000, initVer=AffinityTopologyVersion
> [topVer=3, minorTopVer=0], readyVer=AffinityTopologyVersion [topVer=4,
> minorTopVer=0]].
> [2018-08-07 12:20:09,804][INFO
> ][exchange-worker-#12782%internal.GridTaskFailoverAffinityRunTest1%][GridDhtPartitionsExchangeFuture]
> Completed partition exchange
> [localNode=511d5932-5f22-4919-807d-575c7f61,
> exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion
> [topVer=3, minorTopVer=0], evt=NODE_JOINED, evtNode=TcpDiscoveryNode
> [id=6b9a7a1d-07bf-4d20-882a-8462ada3, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet [/127.0.0.1:47502], discPort=47502, order=3, intOrder=3,
> lastExchangeTime=1533644409739, loc=false, ver=2.7.0#20180807-sha1:e96616f5,
> isClient=false], done=true], topVer=AffinityTopologyVersion [topVer=4,
> minorTopVer=0], durationFromInit=21]
> [2018-08-07 12:20:09,806][INFO
> ][exchange-worker-#12782%internal.GridTaskFailoverAffinityRunTest1%][time]
> Finished exchange init [topVer=AffinityTopologyVersion [topVer=3,
> minorTopVer=0], crd=true]
> [2018-08-07 12:20:09,807][INFO
> ][exchange-worker-#12782%internal.GridTaskFailoverAffinityRunTest1%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=4, minorTopVer=0], force=false, evt=NODE_JOINED,
> node=6b9a7a1d-07bf-4d20-882a-8462ada3]
> [2018-08-07 12:20:09,811][INFO
> ][sys-#12798%internal.GridTaskFailoverAffinityRunTest2%][GridDhtPartitionsExchangeFuture]
> Finish exchange future [startVer=AffinityTopologyVersion [topVer=4,
> minorTopVer=0], resVer=AffinityTopologyVersion [topVer=4, minorTopVer=0],
> err=null]
> [2018-08-07 12:20:09,813][INFO
> ][sys-#12798%internal.GridTaskFailoverAffinityRunTest2%][GridDhtPartitionsExchangeFuture]
> Completed partition exchange
> [localNode=a3206c1f-6d57-4fd6-8aa5-e22f3b42,
> exchange=GridDhtPartitionsExchangeFuture [topVer=AffinityTopologyVersion
> [topVer=4, minorTopVer=0], evt=NODE_JOINED, evtNode=TcpDiscoveryNode
> [id=a3206c1f-6d57-4fd6-8aa5-e22f3b42, addrs=ArrayList [127.0.0.1],
> sockAddrs=HashSet [/127.0.0.1:47503], discPort=47503, order=4, intOrder=4,
> lastExchangeTime=1533644409779, loc=true, ver=2.7.0#20180807-sha1:e96616f5,
> isClient=false], done=true], topVer=AffinityTopologyVersion [topVer=4,
> minorTopVer=0], durationFromInit=41]
> [2018-08-07 12:20:09,814][INFO
> ][grid-starter-testNodeRestartClient-1][GridTaskFailoverAffinityRunTest1] To
> start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
> [2018-08-07 12:20:09,815][INFO
> ][grid-starter-testNodeRestartClient-1][GridTaskFailoverAffinityRunTest1]
> [2018-08-07 12:20:09,815][INFO
> ][grid-starter-testNodeRestartClient-1][GridTaskFailoverAffinityRunTest1]
> >>> +---+
> >>> Ignite ver.
> >>> 2.7.0-SNAPSHOT#20180807-sha1:e96616f580930f267eab44f75d410fa29a876bcb
> >>> +---+
> >>> OS name: Linux 4.4.0-128-generic amd64
> >>> CPU(s): 5
> >>> Heap: 2.0GB
> >>> VM name: 20126@8790182f15a5
> >>> Ignite instance name: internal.GridTaskFailoverAffinityRunTest1
> >>> Local node [ID=511D5932-5F22-4919-807D-575C7F61, order=2,
> >>> clientMode=false]
> >>> Local node
[jira] [Updated] (IGNITE-9461) Implement random subspace method and provide an option to combine it with bagging
[
https://issues.apache.org/jira/browse/IGNITE-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-9461:
---
Ignite Flags: (was: Docs Required)
> Implement random subspace method and provide an option to combine it with
> bagging
> -
>
> Key: IGNITE-9461
> URL: https://issues.apache.org/jira/browse/IGNITE-9461
> Project: Ignite
> Issue Type: Task
> Components: ml
>Affects Versions: 2.6
>Reporter: Oleg Ignatenko
>Priority: Major
>
> Implement random subspace method (aka attribute bagging or feature bagging)
> to give ML API users more options to address overfitting. Also provide an
> option to combine this method with bagging.
> References:
> * [Wikipedia article|https://en.wikipedia.org/wiki/Random_subspace_method]
> {quote}Informally, this causes individual learners to not over-focus on
> features that appear highly predictive/descriptive in the training set, but
> fail to be as predictive for points outside that set. For this reason, random
> subspaces are an attractive choice for problems where the number of features
> is much larger than the number of training points, such as learning from fMRI
> data or gene expression data...{quote}
> * [Combining Bagging and Random Subspaces to Create Better
> Ensembles|https://pdfs.semanticscholar.org/d38f/979ad85d59fc93058279010efc73a24a712c.pdf]
> * [Bagging and the Random Subspace Method for Redundant Feature
> Spaces|https://link.springer.com/chapter/10.1007/3-540-48219-9_1]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9461) Implement random subspace method and provide an option to combine it with bagging
Oleg Ignatenko created IGNITE-9461:
--
Summary: Implement random subspace method and provide an option to
combine it with bagging
Key: IGNITE-9461
URL: https://issues.apache.org/jira/browse/IGNITE-9461
Project: Ignite
Issue Type: Task
Components: ml
Affects Versions: 2.6
Reporter: Oleg Ignatenko
Implement random subspace method (aka attribute bagging or feature bagging) to
give ML API users more options to address overfitting. Also provide an option
to combine this method with bagging.
References:
* [Wikipedia article|https://en.wikipedia.org/wiki/Random_subspace_method]
{quote}Informally, this causes individual learners to not over-focus on
features that appear highly predictive/descriptive in the training set, but
fail to be as predictive for points outside that set. For this reason, random
subspaces are an attractive choice for problems where the number of features is
much larger than the number of training points, such as learning from fMRI data
or gene expression data...{quote}
* [Combining Bagging and Random Subspaces to Create Better
Ensembles|https://pdfs.semanticscholar.org/d38f/979ad85d59fc93058279010efc73a24a712c.pdf]
* [Bagging and the Random Subspace Method for Redundant Feature
Spaces|https://link.springer.com/chapter/10.1007/3-540-48219-9_1]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-336) We need to add dynamic turn on/off cache statistics for Visor.
[ https://issues.apache.org/jira/browse/IGNITE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-336: - Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > We need to add dynamic turn on/off cache statistics for Visor. > -- > > Key: IGNITE-336 > URL: https://issues.apache.org/jira/browse/IGNITE-336 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-2 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > > We need create task to turn on/off of cache statistics collecting. > Create Visor command for toggling. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-336) We need to add dynamic turn on/off cache statistics for Visor.
[ https://issues.apache.org/jira/browse/IGNITE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602911#comment-16602911 ] Pavel Konstantinov commented on IGNITE-336: --- Works. > We need to add dynamic turn on/off cache statistics for Visor. > -- > > Key: IGNITE-336 > URL: https://issues.apache.org/jira/browse/IGNITE-336 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: sprint-2 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > > We need create task to turn on/off of cache statistics collecting. > Create Visor command for toggling. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9311) Add missing @Override annotation
[
https://issues.apache.org/jira/browse/IGNITE-9311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602908#comment-16602908
]
Roman Shtykh commented on IGNITE-9311:
--
[~Mmuzaf] Thanks! Please give me a couple of days (being pretty busy right now).
> Add missing @Override annotation
>
>
> Key: IGNITE-9311
> URL: https://issues.apache.org/jira/browse/IGNITE-9311
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
>
> New `Code Inspections` profile can be found
> {{\idea\ignite_inspections.xml}}.
> We will need to fix all methods with missed {{@Override}} annotation
> regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9408) Update mesos version
[ https://issues.apache.org/jira/browse/IGNITE-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602904#comment-16602904 ] Roman Shtykh commented on IGNITE-9408: -- [~ilyak] Thanks! Will merge. > Update mesos version > > > Key: IGNITE-9408 > URL: https://issues.apache.org/jira/browse/IGNITE-9408 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > 0.22.0 is being used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9460) Update styles on WC top menu
Alexander Kalinin created IGNITE-9460: - Summary: Update styles on WC top menu Key: IGNITE-9460 URL: https://issues.apache.org/jira/browse/IGNITE-9460 Project: Ignite Issue Type: Bug Components: UI Reporter: Alexander Kalinin Assignee: Alexander Kalinin 1) Remove underline on focus !https://snag.gy/RBMZyn.jpg! 2) Dropdown menus should look like generic dropdown !https://snag.gy/peXHDl.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602870#comment-16602870
]
Roman Shtykh edited comment on IGNITE-9453 at 9/4/18 10:32 AM:
---
Looks like it's not only about REST.
{{H2Utils.meta()}} calls {{ResultSetMetaData#getColumnClassName}} which returns
a Java type.
I think for SQL we have rather call {{ResultSetMetaData#getColumnTypeName}}
http://www.h2database.com/javadoc/org/h2/jdbc/JdbcResultSetMetaData.html
[~vozerov] what do you think?
was (Author: roman_s):
Looks like it's not only about REST.
{{H2Utils.meta()}} calls {{ResultSetMetaData#getColumnClassName}} which returns
a Java type.
I think for SQL we have rather call {{ResultSetMetaData#getColumnTypeName}}
[~vozerov] what do you think?
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9361) Remove IgniteInternalCache.isMongo*Cache() and other such stuff
[ https://issues.apache.org/jira/browse/IGNITE-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602878#comment-16602878 ] ASF GitHub Bot commented on IGNITE-9361: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4678 > Remove IgniteInternalCache.isMongo*Cache() and other such stuff > --- > > Key: IGNITE-9361 > URL: https://issues.apache.org/jira/browse/IGNITE-9361 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Fix For: 2.7 > > > Nobody needs it for a long time already. It's all internal API, we can drop > it outright. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602870#comment-16602870
]
Roman Shtykh edited comment on IGNITE-9453 at 9/4/18 10:31 AM:
---
Looks like it's not only about REST.
{{H2Utils.meta()}} calls {{ResultSetMetaData#getColumnClassName}} which returns
a Java type.
I think for SQL we have rather call {{ResultSetMetaData#getColumnTypeName}}
[~vozerov] what do you think?
was (Author: roman_s):
Looks like it's not only about REST.
{{H2Utils.meta()}} calls {{ResultSetMetaData#getColumnClassName}} which returns
a Java type.
I think for SQL we have rather call \{{ResultSetMetaData#getColumnTypeName }}
[~vozerov] what do you think?
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9361) Remove IgniteInternalCache.isMongo*Cache() and other such stuff
[ https://issues.apache.org/jira/browse/IGNITE-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602875#comment-16602875 ] Dmitriy Govorukhin commented on IGNITE-9361: [~ilyak] Thanks for the contribution, merged to master. > Remove IgniteInternalCache.isMongo*Cache() and other such stuff > --- > > Key: IGNITE-9361 > URL: https://issues.apache.org/jira/browse/IGNITE-9361 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Fix For: 2.7 > > > Nobody needs it for a long time already. It's all internal API, we can drop > it outright. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9311) Add missing @Override annotation
[
https://issues.apache.org/jira/browse/IGNITE-9311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602872#comment-16602872
]
Maxim Muzafarov commented on IGNITE-9311:
-
[~roman_s]
Can you review my changes?
Upsource --
[IGNT-CR-744|https://reviews.ignite.apache.org/ignite/review/IGNT-CR-744]
I've run TC and seems everything is as usual -- [#4075 (02 Sep 18
19:05)|https://ci.ignite.apache.org/viewLog.html?buildId=1780066=buildResultsDiv=IgniteTests24Java8_RunAll]
{{IgnitePdsDynamicCacheTest.testRestartAndCreate}} looks a bit suspicious, but
I've checked it additionally -- [Ignite Tests 2.4+ (Java 8) - PDS
1|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds1_IgniteTests24Java8=pull%2F4618%2Fhead=buildTypeStatusDiv]
> Add missing @Override annotation
>
>
> Key: IGNITE-9311
> URL: https://issues.apache.org/jira/browse/IGNITE-9311
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
>
> New `Code Inspections` profile can be found
> {{\idea\ignite_inspections.xml}}.
> We will need to fix all methods with missed {{@Override}} annotation
> regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602870#comment-16602870
]
Roman Shtykh commented on IGNITE-9453:
--
Looks like it's not only about REST.
{{H2Utils.meta()}} calls {{ResultSetMetaData#getColumnClassName}} which returns
a Java type.
I think for SQL we have rather call \{{ResultSetMetaData#getColumnTypeName }}
[~vozerov] what do you think?
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9361) Remove IgniteInternalCache.isMongo*Cache() and other such stuff
[ https://issues.apache.org/jira/browse/IGNITE-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602866#comment-16602866 ] ASF GitHub Bot commented on IGNITE-9361: GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/4678 IGNITE-9361 Remove IgniteInternalCache.isMongo*Cache() and other remn… …ants. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9361 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4678.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 #4678 commit 499d300ff74e31f32b5eafcaed06b1fff6c418d3 Author: Ilya Kasnacheev Date: 2018-08-23T16:08:48Z IGNITE-9361 Remove IgniteInternalCache.isMongo*Cache() and other remnants. > Remove IgniteInternalCache.isMongo*Cache() and other such stuff > --- > > Key: IGNITE-9361 > URL: https://issues.apache.org/jira/browse/IGNITE-9361 > Project: Ignite > Issue Type: Improvement >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Fix For: 2.7 > > > Nobody needs it for a long time already. It's all internal API, we can drop > it outright. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9408) Update mesos version
[ https://issues.apache.org/jira/browse/IGNITE-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602857#comment-16602857 ] Ilya Kasnacheev commented on IGNITE-9408: - Looks good to me! > Update mesos version > > > Key: IGNITE-9408 > URL: https://issues.apache.org/jira/browse/IGNITE-9408 > Project: Ignite > Issue Type: Task >Reporter: Roman Shtykh >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.7 > > > 0.22.0 is being used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9453) REST: UUID column type displayed like byte array
[
https://issues.apache.org/jira/browse/IGNITE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh reassigned IGNITE-9453:
Assignee: Roman Shtykh
> REST: UUID column type displayed like byte array
>
>
> Key: IGNITE-9453
> URL: https://issues.apache.org/jira/browse/IGNITE-9453
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.5
>Reporter: Stepan Pilschikov
>Assignee: Roman Shtykh
>Priority: Major
>
> Case:
> - Create table with uuid
> {code:sql}
> CREATE TABLE test(id int primary key, field varchar2(50), uuid UUID)
> {code}
> - Execute `select * from test` query with rest
> {code:bash}
> curl
> "http://localhost:8080/ignite?cmd=qryfldexe=10=SQL_PUBLIC_TEST=select%20%2A%20from%20test%3B;
> {code}
> Actual:
> {code:json}
> {
> "successStatus": 0,
> "sessionToken": null,
> "error": null,
> "response": {
> "items": [],
> "last": true,
> "fieldsMetadata": [
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "ID",
> "fieldTypeName": "java.lang.Integer"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "FIELD",
> "fieldTypeName": "java.lang.String"
> },
> {
> "schemaName": "PUBLIC",
> "typeName": "TEST",
> "fieldName": "UUID",
> "fieldTypeName": "[B"
> }
> ],
> "queryId": 0
> }
> }
> {code}
> Expected:
> uuid was displayed somehow but not "[B"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9433) Refactoring to improve constant usage for file suffixes
[ https://issues.apache.org/jira/browse/IGNITE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-9433: --- Ignite Flags: (was: Docs Required) > Refactoring to improve constant usage for file suffixes > --- > > Key: IGNITE-9433 > URL: https://issues.apache.org/jira/browse/IGNITE-9433 > Project: Ignite > Issue Type: Task >Reporter: Pavel Voronkin >Assignee: Pavel Voronkin >Priority: Major > Fix For: 2.7 > > > We need extract file suffix constants to avoid duplication of string > constants for zip files, like ".zip" and ".tmp" across the project -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8582) MVCC TX: Cache store read-through support
[ https://issues.apache.org/jira/browse/IGNITE-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-8582: -- Assignee: (was: Ivan Pavlukhin) > MVCC TX: Cache store read-through support > - > > Key: IGNITE-8582 > URL: https://issues.apache.org/jira/browse/IGNITE-8582 > Project: Ignite > Issue Type: Bug > Components: mvcc, sql >Reporter: Sergey Kalashnikov >Priority: Major > > Add support for read-through cache store for mvcc caches. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9062) MVCC SQL: H2 connection and statement cache refactoring
[ https://issues.apache.org/jira/browse/IGNITE-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-9062: -- Assignee: (was: Ivan Pavlukhin) > MVCC SQL: H2 connection and statement cache refactoring > --- > > Key: IGNITE-9062 > URL: https://issues.apache.org/jira/browse/IGNITE-9062 > Project: Ignite > Issue Type: Improvement > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Major > > H2 connection and statement caching logic is currently spread between several > variables. It seems feasible to extract and encapsulate such logic into some > H2ConnectionManager class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9292) MVCC SQL: Unexpected state exception when updating backup
[
https://issues.apache.org/jira/browse/IGNITE-9292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reassigned IGNITE-9292:
--
Assignee: (was: Ivan Pavlukhin)
> MVCC SQL: Unexpected state exception when updating backup
> -
>
> Key: IGNITE-9292
> URL: https://issues.apache.org/jira/browse/IGNITE-9292
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Ivan Pavlukhin
>Priority: Major
> Attachments: MvccInsertUpdateConcurrent.java
>
>
> Unexpected state exception is observed during concurrent execution insert and
> fast update for same key.
> One of observed with concurrent update and insert for the same key from the
> same node serializes as follows:
> 1. insert on primary
> 2. insert on backup
> 3. update on primary waits on lock
> 4. insert is prepared on backup
> 5. insert is prepared on primary
> 6. insert is committed on primary (before committing on backup)
> 7. update waiting on lock wakes up
> 8. update is executed on primary
> 9. update fails on backup because sees inserted row in prepared state
> It is one possible erroneous scenario. There might be others. TX log update
> procedure should be thoroughly reviewed.
> {noformat}
> [2018-08-16
> 16:32:25,452][ERROR][ForkJoinPool.commonPool-worker-2][DmlStatementsProcessor]
> Error during update [localNodeId=6709af72-2fe9-4eab-9ee5-be83eab0]
> class org.apache.ignite.IgniteCheckedException: Failed to update backup node:
> [localNodeId=6709af72-2fe9-4eab-9ee5-be83eab0,
> remoteNodeId=4ca5b185-c5d1-4756-8977-e57aec31]
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.onResult(GridDhtTxAbstractEnlistFuture.java:931)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistResponse(GridDhtTransactionalCacheAdapter.java:2245)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$1000(GridDhtTransactionalCacheAdapter.java:106)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$16.apply(GridDhtTransactionalCacheAdapter.java:237)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$16.apply(GridDhtTransactionalCacheAdapter.java:235)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:581)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:380)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:306)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:101)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:295)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1569)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1197)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:127)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1093)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:496)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Runtime failure on
> bounds: [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1047)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1887)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:523)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1080)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxRemote.mvccEnlistBatch(GridDhtTxRemote.java:451)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processDhtTxQueryEnlistRequest(GridDhtTransactionalCacheAdapter.java:2209)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$900(GridDhtTransactionalCacheAdapter.java:106)
