[jira] [Assigned] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts

2019-09-17 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov reassigned IGNITE-11461:
---

Assignee: (was: Dmitriy Pavlov)

> Automatic modules support for Apache Ignite: find and resolve packages 
> conflicts
> 
>
> Key: IGNITE-11461
> URL: https://issues.apache.org/jira/browse/IGNITE-11461
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.8
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Example of failure in a modular environment:
> Error:java: the unnamed module reads package 
> org.apache.ignite.internal.processors.cache.persistence.file from both 
> ignite.core and ignite.direct.io
> This type of failure is named package inference, but it is strictly 
> prohibited 
> http://openjdk.java.net/projects/jigsaw/spec/reqs/#non-interference 
> Ignite compatibility with Jigsaw is tested in a separate project. See details 
> in
> https://github.com/apache/ignite/tree/ignite-11461-java11/modules/dev-utils/ignite-modules-test#ignite-modular-environment-test-project
>  
> Following table contains currenly investigated Ignite modules if this 
> applicability as automatic modules:
> ||Module||Run In Modular Environment||Changeable using private API only || 
> Notes ||
> |ignite-code|(/)|(/)| |
> |ignite-indexing|(x) [IGNITE-11464] | (?) Refacrtoing to use 
> ignite-indexing-text may be a breaking change | Lucene artifacts exclusion is 
> required by user manually. |
> |ignite-compress | (x) | (/) not releaseed | 
> org.apache.ignite.internal.processors.compress package conflict |
> |ignite-direct-io|(x) blocked by indexind | (/) | 
> org.apache.ignite.internal.processors.cache.persistence.file package conflict 
> |
> |ignite-spring|(x) [IGNITE-11467] blocked by indexing | (x) 
> org.apache.ignite.IgniteSpringBean affected | |
> |ignite-ml |(x) blocked by indexing | | |
> |ignite-log4j|(/)|(/) | But may not compile with other logging dependencies - 
> EOL https://blogs.apache.org/logging/entry/moving_on_to_log4j_2 |
> |ignite-log4j2|(/)|(/)| |
> |ignite-slf4j | (/)|(/)| |
> |ignite-rest-http | (x) IGNITE-11469 & Mirgate to log4j2x [IGNITE-11486] | 
> (/) | Usage with slf4j may break compilation because conflict of packages |
> |ignite-hibernate_5.3 and others | (x) [IGNITE-11485] | (?) | avoid of API 
> breaking is possibleif hibernate core classes not used by third party code |
> |ignite-zookeeper| (x) IGNITE-11486 | (/) | | 
> |ignite-spring-data_2-0 | (x) blocked by spring | org.apache.commons.logging 
> from both commons.logging and spring.jcl conflict | 
> https://jira.spring.io/browse/SPR-16605 | 
> |ignite-ml | (/) master (x) 2.7 | | | 
> |ignite-cassandra-store | (x)  [IGNITE-11467]  blocked by spring  | (/) | 
> Only spring needs to be fixed | 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (IGNITE-11464) Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix queries and visor package conflicts

2019-09-17 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov reassigned IGNITE-11464:
---

Assignee: (was: Dmitriy Pavlov)

> Support Automatic modules for ignite-indexing: bypass or fix Lucene, fix 
> queries and visor package conflicts
> 
>
> Key: IGNITE-11464
> URL: https://issues.apache.org/jira/browse/IGNITE-11464
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> error: the unnamed module reads package org.apache.lucene.search from both 
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.document from both 
> lucene.sandbox and lucene.core
> error: the unnamed module reads package org.apache.lucene.analysis.standard 
> from both lucene.core and lucene.analyzers.common
> error: the unnamed module reads package 
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing 
> and ignite.core
> error: the unnamed module reads package 
> org.apache.ignite.internal.visor.verify from both ignite.indexing and 
> ignite.core 
> 
> C:\projects\incubator-ignite\modules\dev-utils\ignite-modules-test\src\test\java\module-info.java:18:
>  error: module ignite_modules_test reads package org.apache.lucene.search 
> from both lucene.sandbox and lucene.core
> module ignite_modules_test 
> {noformat}
>  
> Some of these errors probably can be fixed by workarounds for dependencies:
> 2 errors coming from duplicate packages declared in code and indexing:
> - error: module ignite.core reads package 
> org.apache.ignite.internal.processors.cache.query from both ignite.indexing 
> and ignite.core
> - error: module ignite.core reads package 
> org.apache.ignite.internal.visor.verify from both ignite.indexing and 
> ignite.core



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (IGNITE-7182) Slow sorting of pages collection on checkpoint begin can cause zero dropdown even with throttling enabled

2019-09-17 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov resolved IGNITE-7182.

Fix Version/s: (was: 2.8)
   Resolution: Won't Fix

Benchmarking does not show any performance boost from another sorting

> Slow sorting of pages collection on checkpoint begin can cause zero dropdown 
> even with throttling enabled
> -
>
> Key: IGNITE-7182
> URL: https://issues.apache.org/jira/browse/IGNITE-7182
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Ivan Rakov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> Tests show that GridCacheDatabaseSharedManager#splitAndSortCpPagesIfNeeded 
> call can last several seconds on nodes with big amount of memory (>10GB). We 
> should optimize sorting algorithm, possibly making it multithreaded.
> Another option to make pages write throttling more smooth is to get rid of 
> this heuristic:
> {noformat}
> // Starting with 0.05 to avoid throttle right after 
> checkpoint start
> // 7/12 is maximum ratio of dirty pages
> dirtyRatioThreshold = (dirtyRatioThreshold * 0.95 + 0.05) * 7 
> / 12;
> {noformat}
> We should replace "magic" lower bound 0.05 * 7 / 12 with the real percentage 
> of dirty pages at the moment of 
> GridCacheDatabaseSharedManager.Checkpointer#markCheckpointBegin call return.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (IGNITE-7584) Smooth decrease WAL write speed if low work segments left

2019-09-17 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-7584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov resolved IGNITE-7584.

Fix Version/s: (was: 2.8)
   Resolution: Won't Fix

> Smooth decrease WAL write speed if low work segments left
> -
>
> Key: IGNITE-7584
> URL: https://issues.apache.org/jira/browse/IGNITE-7584
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> Smooth decrease of the write speed in WAL when approaching the exhaustion of 
> current segments in the working directory.
> Now archiver segment switch involves file copying and may be bottleneck of 
> speed of grid operation.
> Now if out of work segments occurs, grid put speed drop down to 0 ops/sec 
> ocurred.
> This isssue was fixed under IGNITE-7017 with providing new 'NoArchvier' mode, 
> but in case archiver based WAL is already used by end-user, it is required to 
> have opportunity to smooth decrease speed instead of drop to 0.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-5355) Create task with release tools

2019-09-16 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930631#comment-16930631
 ] 

Dmitriy Pavlov commented on IGNITE-5355:


[~lexa], I would not name it as a top-1 priority, better to say: It is nice to 
have. 

BTW, Release notes field is already available in the JIRA, so if someone 
contributes such tool - it is convenient and needed investment into release 
automation.
If we don't have this kind of tool, we can release Ignite without it.

Which is why I was asking about if you want to finalize this ticket or we can 
close it (as incomplete/won't fix/fixed). If you're interested, probably it's 
worth to start a new discussion about this tool and share the intent to 
do/finalize it. We can understand the vision of all community members 

> Create task with release tools
> --
>
> Key: IGNITE-5355
> URL: https://issues.apache.org/jira/browse/IGNITE-5355
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Aleksey Chetaev
>Assignee: Aleksey Chetaev
>Priority: Major
>
> 1. Create task for auto-generate HTML formatted releases notes



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12139) RPM for 2.7.5 release built from incorrect version

2019-09-16 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16930489#comment-16930489
 ] 

Dmitriy Pavlov commented on IGNITE-12139:
-

[~vveider], [~dmagda] should we somehow update/fix release process to avoid 
such issues in the future?

> RPM for 2.7.5 release built from incorrect version
> --
>
> Key: IGNITE-12139
> URL: https://issues.apache.org/jira/browse/IGNITE-12139
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.7.5
>Reporter: Jan Kupec
>Assignee: Peter Ivanov
>Priority: Minor
>
> The {{apache-ignite-2.7.5}} RPM found in the [official RPM 
> repository|https://ignite.apache.org/download.cgi#rpm-package] has been built 
> from commit *{{c9521338}}*, which is several weeks of development away from 
> the head of the {{ignite-2.7.5}} release branch (*{{be4f2a15}}*) and 
> apparently contains incompatible changes.
> Is this a result of a human error or an error in the automated build system? 
> Can this easily be fixed?



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-9562:
---
Release Note: Fixed an issue where an outdated node with a destroyed cache 
caused the cluster to hang

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2249)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
>   at 
> 

[jira] [Updated] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12061:

Release Note: Fixed a bug that made it impossible to change the inline_size 
property of an existing index after it was dropped and recreated with a 
different value

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12060:

Release Note: Fixed an issue where a row size was calculated incorrectly 
for shared cache groups, which caused a tree corruption

> Incorrect row size calculation, lead to tree corruption
> ---
>
> Key: IGNITE-12060
> URL: https://issues.apache.org/jira/browse/IGNITE-12060
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>
> We do not correctly calculate old row size and new row size for check 
> in-place update. One of them may include cacheId but other not. Size 
> dependent on shared group or not.
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap in exchange history

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11767:

Release Note: Reduced java heap footprint by optimizing 
GridDhtPartitionsFullMessage maps in exchange history 

> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> --
>
> Key: IGNITE-11767
> URL: https://issues.apache.org/jira/browse/IGNITE-11767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before 
> putting msg in exchFuts linked list to be stowed away.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12081) Page replacement can reload invalid page during checkpoint

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12081:

Release Note: Fixed an issue that could cause data corruption during 
checkpointing

> Page replacement can reload invalid page during checkpoint
> --
>
> Key: IGNITE-12081
> URL: https://issues.apache.org/jira/browse/IGNITE-12081
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There is a race between {{writeCheckpointPages}} and page replacement process:
>  * Checkpointer thread begins a checkpoint
>  * Checkpointer thread calls {{getPageForCheckpoint()}}, which will copy page 
> content *and clear dirty flag*
>  * Page replacement tries to find a page for replacement and chooses this 
> page, the page is thrown away
>  * Before the page is written back to the store, the page is acquired again.
> As a result, an older copy of the page is brought back to memory, which 
> causes all kinds of corruption exceptions and assertions.
> The attached unit test demonstrates the issue. It is likely that all 
> baselines are affected starting from 2.4
> As a part of this ticket, we must add more unit-tests for checkpointing 
> protocol invariants we rely on.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-10451) .NET: Persistence does not work with custom affinity function

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-10451:

Release Note: .NET: Native persistence now works with a custom affinity 
function

> .NET: Persistence does not work with custom affinity function
> -
>
> Key: IGNITE-10451
> URL: https://issues.apache.org/jira/browse/IGNITE-10451
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET, 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> To reproduce: assign custom affinity function in 
> {{PersistenceTest.TestCacheDataSurvivesNodeRestart}}.
> As a result, node restart fails with the following exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException : An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   > Apache.Ignite.Core.Common.JavaException : class 
> org.apache.ignite.IgniteException: An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1027)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:48)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> Caused by: class org.apache.ignite.IgniteCheckedException: An error occurred 
> during cache configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:902)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:844)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:891)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.restoreCacheConfigurations(GridCacheProcessor.java:756)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1300(GridCacheProcessor.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5456)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:412)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4473)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1047)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
>   ... 1 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> deserialize object with given class loader: 
> sun.misc.Launcher$AppClassLoader@18b4aac2
>   at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:147)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:898)
>   ... 15 more
> Caused by: java.lang.IllegalArgumentException: Ignite instance name thread 
> local must be set or this method should be accessed under 
> org.apache.ignite.thread.IgniteThread
>   at 
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1413)
>   at 
> 

[jira] [Updated] (IGNITE-12057) Persistence files are stored to temp dir

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12057:

Release Note: Ignite work directory is now set to the current user's home 
directory by default, native persistence files will not be stored in the Temp 
directory anymore

> Persistence files are stored to temp dir
> 
>
> Key: IGNITE-12057
> URL: https://issues.apache.org/jira/browse/IGNITE-12057
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Anton Kalashnikov
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> h2. Description
> Check this thread:
> [https://stackoverflow.com/questions/56951913/ignite-persistent-schema-tables-disappeared-sometimes/56977212#56977212]
> This prospect almost dropped us because the company could figure out why 
> persistence files disappear upon restarts. They turned off WARN logging level 
> and could see our warning saying that the files are written to such a 
> directory.
> I've updated Ignite docs:
> [https://apacheignite.readme.io/docs/distributed-persistent-store#section-persistence-path-management]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12068) puzzling select result

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12068:

Release Note: Fixed a bug that caused a SELECT query with an equality 
predicate on a part of the primary compound key to return a single row even if 
the query matched multiple rows

> puzzling select result
> --
>
> Key: IGNITE-12068
> URL: https://issues.apache.org/jira/browse/IGNITE-12068
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7.5
> Environment: System version: CentOS Linux release 7.6.1810 (Core)
> Apache Ignite version: apache-ignite-2.7.5-1.noarch
>Reporter: JerryKwan
>Assignee: Ivan Pavlukhin
>Priority: Blocker
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> select using the first primary key only returns one record, but it should 
> return more records.
> The following is how to reproduce this problem
> 1, create a table using
> CREATE TABLE IF NOT EXISTS Person(
>  id int,
>  city_id int,
>  name varchar,
>  age int, 
>  company varchar,
>  PRIMARY KEY (id, city_id)
> );
> 2, insert some records
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4);
> INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4);
> 3, query using 'select * from Person' show all of the records, expected
> [http://www.passimage.in/i/03da31c8f23cf64580d5.png]
> 4, query using 'select * from Person where id=1', only get one record, NOT 
> expected
> [http://www.passimage.in/i/f5491491a70c5d796823.png]
> 5, query using 'select * from Person where city_id=4' get  two records, 
> expected
> [http://www.passimage.in/i/ff0ee4f5e882983d779d.png]
> Why  'select * from Person where id=1', only get one record? and how to fix 
> this? Is there any special operations/configurations to do?



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12061:

Reviewer: Andrew Mashenkov  (was: Yury Gerzhedovich)

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12061:

Ignite Flags: Release Notes Required

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-10451) .NET: Persistence does not work with custom affinity function

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-10451:

Ignite Flags: Docs Required,Release Notes Required  (was: Docs Required)

> .NET: Persistence does not work with custom affinity function
> -
>
> Key: IGNITE-10451
> URL: https://issues.apache.org/jira/browse/IGNITE-10451
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET, 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> To reproduce: assign custom affinity function in 
> {{PersistenceTest.TestCacheDataSurvivesNodeRestart}}.
> As a result, node restart fails with the following exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException : An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   > Apache.Ignite.Core.Common.JavaException : class 
> org.apache.ignite.IgniteException: An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1027)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:48)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> Caused by: class org.apache.ignite.IgniteCheckedException: An error occurred 
> during cache configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:902)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:844)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:891)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.restoreCacheConfigurations(GridCacheProcessor.java:756)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1300(GridCacheProcessor.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5456)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:412)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4473)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1047)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
>   ... 1 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> deserialize object with given class loader: 
> sun.misc.Launcher$AppClassLoader@18b4aac2
>   at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:147)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:898)
>   ... 15 more
> Caused by: java.lang.IllegalArgumentException: Ignite instance name thread 
> local must be set or this method should be accessed under 
> org.apache.ignite.thread.IgniteThread
>   at 
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1413)
>   at 
> 

[jira] [Updated] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-9562:
---
Ignite Flags: Docs Required,Release Notes Required  (was: Docs Required)

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2249)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
>   at 
> 

[jira] [Updated] (IGNITE-12113) control.sh terminates silently when JAVA_HOME is not set

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12113:

Ignite Flags: Release Notes Required

[~agoncharuk] could you please fill release note? Also, since the process is 
not yet automated, please commit it to txt value and to Release Notes.html

> control.sh terminates silently when JAVA_HOME is not set
> 
>
> Key: IGNITE-12113
> URL: https://issues.apache.org/jira/browse/IGNITE-12113
> Project: Ignite
>  Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.8, 2.7.6
>
> Attachments: 
> IGNITE-12113_Fix_silent_control_sh_fail_when_JAVA_HOME_is_empty.patch
>
>
> Running control.sh from ignite-2.7.6 release candidate on MacOS with empty 
> JAVA_HOME produces no output - the script terminates without any action.
> The reason is the following line in {{bin/control.sh}}:
> {code}
> javaMajorVersion "${JAVA_HOME}/bin/java"
> {code}
> Since {{JAVA_HOME}} is empty, the argument passed to the function is invalid 
> and the function terminates the script. I suggest replacing the 
> {{${JAVA_HOME}/bin/java}} with just {{$JAVA}} because it is already 
> determined earlier in the scope. The suggested fix works in my environment 
> for all options of {{JAVA_HOME}}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12057) Persistence files are stored to temp dir

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12057:

Ignite Flags: Docs Required,Release Notes Required  (was: Docs Required)

> Persistence files are stored to temp dir
> 
>
> Key: IGNITE-12057
> URL: https://issues.apache.org/jira/browse/IGNITE-12057
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Anton Kalashnikov
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> h2. Description
> Check this thread:
> [https://stackoverflow.com/questions/56951913/ignite-persistent-schema-tables-disappeared-sometimes/56977212#56977212]
> This prospect almost dropped us because the company could figure out why 
> persistence files disappear upon restarts. They turned off WARN logging level 
> and could see our warning saying that the files are written to such a 
> directory.
> I've updated Ignite docs:
> [https://apacheignite.readme.io/docs/distributed-persistent-store#section-persistence-path-management]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12081) Page replacement can reload invalid page during checkpoint

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12081:

Ignite Flags: Docs Required,Release Notes Required  (was: Docs Required)

> Page replacement can reload invalid page during checkpoint
> --
>
> Key: IGNITE-12081
> URL: https://issues.apache.org/jira/browse/IGNITE-12081
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There is a race between {{writeCheckpointPages}} and page replacement process:
>  * Checkpointer thread begins a checkpoint
>  * Checkpointer thread calls {{getPageForCheckpoint()}}, which will copy page 
> content *and clear dirty flag*
>  * Page replacement tries to find a page for replacement and chooses this 
> page, the page is thrown away
>  * Before the page is written back to the store, the page is acquired again.
> As a result, an older copy of the page is brought back to memory, which 
> causes all kinds of corruption exceptions and assertions.
> The attached unit test demonstrates the issue. It is likely that all 
> baselines are affected starting from 2.4
> As a part of this ticket, we must add more unit-tests for checkpointing 
> protocol invariants we rely on.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12060:

Ignite Flags: Release Notes Required

> Incorrect row size calculation, lead to tree corruption
> ---
>
> Key: IGNITE-12060
> URL: https://issues.apache.org/jira/browse/IGNITE-12060
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>
> We do not correctly calculate old row size and new row size for check 
> in-place update. One of them may include cacheId but other not. Size 
> dependent on shared group or not.
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap in exchange history

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11767:

Ignite Flags: Release Notes Required

> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> --
>
> Key: IGNITE-11767
> URL: https://issues.apache.org/jira/browse/IGNITE-11767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before 
> putting msg in exchFuts linked list to be stowed away.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12068) puzzling select result

2019-08-28 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12068:

Ignite Flags: Docs Required,Release Notes Required  (was: Docs Required)

> puzzling select result
> --
>
> Key: IGNITE-12068
> URL: https://issues.apache.org/jira/browse/IGNITE-12068
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7.5
> Environment: System version: CentOS Linux release 7.6.1810 (Core)
> Apache Ignite version: apache-ignite-2.7.5-1.noarch
>Reporter: JerryKwan
>Assignee: Ivan Pavlukhin
>Priority: Blocker
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> select using the first primary key only returns one record, but it should 
> return more records.
> The following is how to reproduce this problem
> 1, create a table using
> CREATE TABLE IF NOT EXISTS Person(
>  id int,
>  city_id int,
>  name varchar,
>  age int, 
>  company varchar,
>  PRIMARY KEY (id, city_id)
> );
> 2, insert some records
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4);
> INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4);
> 3, query using 'select * from Person' show all of the records, expected
> [http://www.passimage.in/i/03da31c8f23cf64580d5.png]
> 4, query using 'select * from Person where id=1', only get one record, NOT 
> expected
> [http://www.passimage.in/i/f5491491a70c5d796823.png]
> 5, query using 'select * from Person where city_id=4' get  two records, 
> expected
> [http://www.passimage.in/i/ff0ee4f5e882983d779d.png]
> Why  'select * from Person where id=1', only get one record? and how to fix 
> this? Is there any special operations/configurations to do?



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-5355) Create task with release tools

2019-08-26 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16915669#comment-16915669
 ] 

Dmitriy Pavlov commented on IGNITE-5355:


[~lexa] last 2 releases I was release manager. I've collected notes manually, 
and I described it here:
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.0.PrepareReleaseNotes

But I have an idea to ask INFRA for additional field Release Notes (and flag 
Release Notes Required). So once we have these fields it is easier to automate 
RN collection.

> Create task with release tools
> --
>
> Key: IGNITE-5355
> URL: https://issues.apache.org/jira/browse/IGNITE-5355
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Aleksey Chetaev
>Assignee: Aleksey Chetaev
>Priority: Major
>
> 1. Create task for auto-generate HTML formatted releases notes



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-10431) Make tests independent of page size

2019-08-21 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-10431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912425#comment-16912425
 ] 

Dmitriy Pavlov commented on IGNITE-10431:
-

[~DmitriyGovorukhin], could you please take a look at the change in PR# 6039? 
Should we accept or reject this change

> Make tests independent of page size
> ---
>
> Key: IGNITE-10431
> URL: https://issues.apache.org/jira/browse/IGNITE-10431
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergi Vladykin
>Assignee: Oleg Ignatenko
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The following tests were added to Page Compression suite and they fail 
> because page size there increased to 8k.
> {code:java}
> org.apache.ignite.testsuites.IgnitePdsCompressionTestSuite2…g.apache.ignite.internal.processors.cache.persistence.db.wal
>  (4)
>  IgniteWALTailIsReachedDuringIterationOverArchiveTest.testStandAloneIterator  
>  IgniteWalFormatFileFailoverTest.testFailureHandlerTriggered  
>  IgniteWalFormatFileFailoverTest.testFailureHandlerTriggeredFsync 
>  IgniteWalIteratorExceptionDuringReadTest.test    
> org.apache.ignite.testsuites.IgnitePdsCompressionTestSuite2…e.ignite.internal.processors.cache.persistence.db.wal.reader
>  (9)
>  IgniteWalReaderTest.testCheckBoundsIterator  
>  IgniteWalReaderTest.testFillWalAndReadRecords    
>  IgniteWalReaderTest.testFillWalForExactSegmentsCount 
>  IgniteWalReaderTest.testFillWalWithDifferentTypes    
>  IgniteWalReaderTest.testPutAllTxIntoTwoNodes 
>  IgniteWalReaderTest.testRemoveOperationPresentedForDataEntry 
>  IgniteWalReaderTest.testRemoveOperationPresentedForDataEntryForAtomic    
>  IgniteWalReaderTest.testTxFillWalAndExtractDataRecords   
>  IgniteWalReaderTest.testTxRecordsReadWoBinaryMeta    
> org.apache.ignite.testsuites.IgnitePdsCompressionTestSuite2…ache.ignite.internal.processors.cache.persistence.wal.reader
>  (2)
>  StandaloneWalRecordsIteratorTest.testCorrectClosingFileDescriptors   
>  StandaloneWalRecordsIteratorTest.testStrictBounds 
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-5355) Create task with release tools

2019-08-21 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912407#comment-16912407
 ] 

Dmitriy Pavlov commented on IGNITE-5355:


[~lexa] would you proceed with this change?

PR is open
https://github.com/apache/ignite/pull/2379

but there is no activity there.

> Create task with release tools
> --
>
> Key: IGNITE-5355
> URL: https://issues.apache.org/jira/browse/IGNITE-5355
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Aleksey Chetaev
>Assignee: Aleksey Chetaev
>Priority: Major
>
> 1. Create task for auto-generate HTML formatted releases notes



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Comment Edited] (IGNITE-12082) [Release] Update versions for pre-build DEB/RPM and describe how to set these versions

2019-08-21 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911619#comment-16911619
 ] 

Dmitriy Pavlov edited comment on IGNITE-12082 at 8/21/19 2:06 PM:
--

Doc 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.3.UpdateDEB

Commits

https://github.com/gridgain/apache-ignite/commit/ad89c8e86ca0d8128260b946e6d55b43939e1f99

https://github.com/gridgain/apache-ignite/commit/284e5e875d650aeba1cc3fb486513b9d156d2656
 

https://github.com/apache/ignite/commit/7484b3f6c53e43525d7099fa45d04ae4a8f010ba


was (Author: dpavlov):
Doc 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.3.UpdateDEB

Commits

https://github.com/gridgain/apache-ignite/commit/ad89c8e86ca0d8128260b946e6d55b43939e1f99
https://github.com/gridgain/apache-ignite/commit/284e5e875d650aeba1cc3fb486513b9d156d2656
https://github.com/gridgain/apache-ignite/commit/284e5e875d650aeba1cc3fb486513b9d156d2656

> [Release] Update versions for pre-build DEB/RPM and describe how to set these 
> versions
> --
>
> Key: IGNITE-12082
> URL: https://issues.apache.org/jira/browse/IGNITE-12082
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>
> Problem:
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild=4513186_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6
> RC 0 for 2.7.6. the build was successful, but versions for packages remain 
> unchanged
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not 
> require Release manager to update versions, but pre-build DEB & RPM keeps 
> version from the previous release.
> Solution 1 (manual):
> We need to add a new step
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages
> e.g. 4.1.4, where will ask a release manager to update versions.
> May be similar with commit 
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb
> Solution 2 (automatic)
> patch ./scripts/update-versions.sh to set packages version to current project 
> version. This will not require any actions from the release manager since 
> versions will be updated at step 4.1 with other assemblies versions.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Comment Edited] (IGNITE-12082) [Release] Update versions for pre-build DEB/RPM and describe how to set these versions

2019-08-21 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911619#comment-16911619
 ] 

Dmitriy Pavlov edited comment on IGNITE-12082 at 8/21/19 2:06 PM:
--

Doc 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.3.UpdateDEB

Commits

https://github.com/apache/ignite/commit/ad89c8e86ca0d8128260b946e6d55b43939e1f99

https://github.com/apache/ignite/commit/284e5e875d650aeba1cc3fb486513b9d156d2656
 

https://github.com/apache/ignite/commit/7484b3f6c53e43525d7099fa45d04ae4a8f010ba


was (Author: dpavlov):
Doc 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.3.UpdateDEB

Commits

https://github.com/gridgain/apache-ignite/commit/ad89c8e86ca0d8128260b946e6d55b43939e1f99

https://github.com/gridgain/apache-ignite/commit/284e5e875d650aeba1cc3fb486513b9d156d2656
 

https://github.com/apache/ignite/commit/7484b3f6c53e43525d7099fa45d04ae4a8f010ba

> [Release] Update versions for pre-build DEB/RPM and describe how to set these 
> versions
> --
>
> Key: IGNITE-12082
> URL: https://issues.apache.org/jira/browse/IGNITE-12082
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>
> Problem:
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild=4513186_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6
> RC 0 for 2.7.6. the build was successful, but versions for packages remain 
> unchanged
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not 
> require Release manager to update versions, but pre-build DEB & RPM keeps 
> version from the previous release.
> Solution 1 (manual):
> We need to add a new step
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages
> e.g. 4.1.4, where will ask a release manager to update versions.
> May be similar with commit 
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb
> Solution 2 (automatic)
> patch ./scripts/update-versions.sh to set packages version to current project 
> version. This will not require any actions from the release manager since 
> versions will be updated at step 4.1 with other assemblies versions.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Comment Edited] (IGNITE-12082) [Release] Update versions for pre-build DEB/RPM and describe how to set these versions

2019-08-21 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911619#comment-16911619
 ] 

Dmitriy Pavlov edited comment on IGNITE-12082 at 8/21/19 2:05 PM:
--

Doc 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.3.UpdateDEB

Commits

https://github.com/gridgain/apache-ignite/commit/ad89c8e86ca0d8128260b946e6d55b43939e1f99
https://github.com/gridgain/apache-ignite/commit/284e5e875d650aeba1cc3fb486513b9d156d2656
https://github.com/gridgain/apache-ignite/commit/284e5e875d650aeba1cc3fb486513b9d156d2656


was (Author: dpavlov):
Doc 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.3.UpdateDEB

Commit 
https://github.com/dspavlov/ignite/commit/ad89c8e86ca0d8128260b946e6d55b43939e1f99

> [Release] Update versions for pre-build DEB/RPM and describe how to set these 
> versions
> --
>
> Key: IGNITE-12082
> URL: https://issues.apache.org/jira/browse/IGNITE-12082
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>
> Problem:
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild=4513186_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6
> RC 0 for 2.7.6. the build was successful, but versions for packages remain 
> unchanged
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not 
> require Release manager to update versions, but pre-build DEB & RPM keeps 
> version from the previous release.
> Solution 1 (manual):
> We need to add a new step
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages
> e.g. 4.1.4, where will ask a release manager to update versions.
> May be similar with commit 
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb
> Solution 2 (automatic)
> patch ./scripts/update-versions.sh to set packages version to current project 
> version. This will not require any actions from the release manager since 
> versions will be updated at step 4.1 with other assemblies versions.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12083) [Release] Change release scripts according pre-build DEB/RPM folders

2019-08-21 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12083:

Labels: 2.7.6-rc1  (was: )

> [Release] Change release scripts according pre-build DEB/RPM folders
> 
>
> Key: IGNITE-12083
> URL: https://issues.apache.org/jira/browse/IGNITE-12083
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Problem: 
> svn: E02: Can't stat '/mnt/c/dev_env/release-2.7.6-rc0/packaging/pkg': No 
> such file or directory
> Solution 1:
> change release scripts accordingly, PR#5
> Solution 2:
> change folder from 'packages' to packaging on Teamcity.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12082) [Release] Update versions for pre-build DEB/RPM and describe how to set these versions

2019-08-21 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12082:

Labels: 2.7.6-rc1  (was: )

> [Release] Update versions for pre-build DEB/RPM and describe how to set these 
> versions
> --
>
> Key: IGNITE-12082
> URL: https://issues.apache.org/jira/browse/IGNITE-12082
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>
> Problem:
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild=4513186_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6
> RC 0 for 2.7.6. the build was successful, but versions for packages remain 
> unchanged
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not 
> require Release manager to update versions, but pre-build DEB & RPM keeps 
> version from the previous release.
> Solution 1 (manual):
> We need to add a new step
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages
> e.g. 4.1.4, where will ask a release manager to update versions.
> May be similar with commit 
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb
> Solution 2 (automatic)
> patch ./scripts/update-versions.sh to set packages version to current project 
> version. This will not require any actions from the release manager since 
> versions will be updated at step 4.1 with other assemblies versions.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-21 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12061:

Labels: 2.7.6-rc1  (was: )

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 5h 40m
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-5227) StackOverflowError in GridCacheMapEntry#checkOwnerChanged()

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-5227:
---
Fix Version/s: 2.8

> StackOverflowError in GridCacheMapEntry#checkOwnerChanged()
> ---
>
> Key: IGNITE-5227
> URL: https://issues.apache.org/jira/browse/IGNITE-5227
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Alexey Goncharuk
>Assignee: Stepachev Maksim
>Priority: Critical
> Fix For: 2.8
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> A simple test reproducing this error:
> {code}
> /**
>  * @throws Exception if failed.
>  */
> public void testBatchUnlock() throws Exception {
>startGrid(0);
>grid(0).createCache(new CacheConfiguration Integer>(DEFAULT_CACHE_NAME)
> .setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL));
> try {
> final CountDownLatch releaseLatch = new CountDownLatch(1);
> IgniteInternalFuture fut = GridTestUtils.runAsync(new 
> Callable() {
> @Override public Object call() throws Exception {
> IgniteCache cache = grid(0).cache(null);
> Lock lock = cache.lock("key");
> try {
> lock.lock();
> releaseLatch.await();
> }
> finally {
> lock.unlock();
> }
> return null;
> }
> });
> Map putMap = new LinkedHashMap<>();
> putMap.put("key", "trigger");
> for (int i = 0; i < 10_000; i++)
> putMap.put("key-" + i, "value");
> IgniteCache asyncCache = 
> grid(0).cache(null).withAsync();
> asyncCache.putAll(putMap);
> IgniteFuture resFut = asyncCache.future();
> Thread.sleep(1000);
> releaseLatch.countDown();
> fut.get();
> resFut.get();
> }
> finally {
> stopAllGrids();
> }
> {code}
> We should replace a recursive call with a simple iteration over the linked 
> list.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-5227) StackOverflowError in GridCacheMapEntry#checkOwnerChanged()

2019-08-20 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911525#comment-16911525
 ] 

Dmitriy Pavlov commented on IGNITE-5227:


Folks, why do you resolve the ticket without fix version? Some day it becomes a 
pain in the neck for release manager to find out where the fix is.

> StackOverflowError in GridCacheMapEntry#checkOwnerChanged()
> ---
>
> Key: IGNITE-5227
> URL: https://issues.apache.org/jira/browse/IGNITE-5227
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Alexey Goncharuk
>Assignee: Stepachev Maksim
>Priority: Critical
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> A simple test reproducing this error:
> {code}
> /**
>  * @throws Exception if failed.
>  */
> public void testBatchUnlock() throws Exception {
>startGrid(0);
>grid(0).createCache(new CacheConfiguration Integer>(DEFAULT_CACHE_NAME)
> .setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL));
> try {
> final CountDownLatch releaseLatch = new CountDownLatch(1);
> IgniteInternalFuture fut = GridTestUtils.runAsync(new 
> Callable() {
> @Override public Object call() throws Exception {
> IgniteCache cache = grid(0).cache(null);
> Lock lock = cache.lock("key");
> try {
> lock.lock();
> releaseLatch.await();
> }
> finally {
> lock.unlock();
> }
> return null;
> }
> });
> Map putMap = new LinkedHashMap<>();
> putMap.put("key", "trigger");
> for (int i = 0; i < 10_000; i++)
> putMap.put("key-" + i, "value");
> IgniteCache asyncCache = 
> grid(0).cache(null).withAsync();
> asyncCache.putAll(putMap);
> IgniteFuture resFut = asyncCache.future();
> Thread.sleep(1000);
> releaseLatch.countDown();
> fut.get();
> resFut.get();
> }
> finally {
> stopAllGrids();
> }
> {code}
> We should replace a recursive call with a simple iteration over the linked 
> list.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12087) Transactional putAll - significant performance drop on big batches of entries.

2019-08-20 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911520#comment-16911520
 ] 

Dmitriy Pavlov commented on IGNITE-12087:
-

[~mstepachev] could you take a look at this issue?

> Transactional putAll - significant performance drop on big batches of entries.
> --
>
> Key: IGNITE-12087
> URL: https://issues.apache.org/jira/browse/IGNITE-12087
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Pereslegin
>Priority: Major
>
> After IGNITE-5227 have been fixed I found significant performance drop in 
> putAll operation.
> Insertion of 30_000 entries before IGNITE-5227 took ~1 second.
> After IGNITE-5227 - 130 seconds (~100x slower).
> I checked a different batch size:
> 10_000 - 10 seconds
> 20_000 - 48 seconds
> 30_000 - 130 seconds
> and I was not able to wait for the result of 100_000 entries.
> Reproducer
> {code:java}
> public class CheckPutAll extends GridCommonAbstractTest {
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> CacheConfiguration ccfg = new CacheConfiguration(DEFAULT_CACHE_NAME);
> ccfg.setAtomicityMode(TRANSACTIONAL);
> cfg.setCacheConfiguration(ccfg);
> return cfg;
> }
> @Test
> public void check() throws Exception {
> int cnt = 30_000;
> Map data = new HashMap<>(U.capacity(cnt));
> for (int i = 0; i < cnt; i++)
> data.put(i, i);
> Ignite node0 = startGrid(0);
> IgniteCache cache0 = 
> node0.cache(DEFAULT_CACHE_NAME);
> cache0.putAll(data);
> }
> }{code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12071) Test failures after IGNITE-9562 fix in IGFS suite

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12071:

Fix Version/s: (was: 2.7.6)
   2.8

> Test failures after IGNITE-9562 fix in IGFS suite
> -
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.8
>
>
> https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
> *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>  - eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (IGNITE-12071) Test failures after IGNITE-9562 fix in IGFS suite

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov resolved IGNITE-12071.
-
Resolution: Fixed

Not reproduced in 2.7.6, resolving the issue, committed as part of another fix 
for master, here 
https://github.com/apache/ignite/pull/6765/files#diff-3b0297f8e0e757b6b5ede921d629c6b5R608

> Test failures after IGNITE-9562 fix in IGFS suite
> -
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.8
>
>
> https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
> *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>  - eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Assigned] (IGNITE-11393) Create IgniteLinkTaglet.toString() implementation for Java9+

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov reassigned IGNITE-11393:
---

Assignee: (was: Dmitriy Pavlov)

> Create IgniteLinkTaglet.toString() implementation for Java9+
> 
>
> Key: IGNITE-11393
> URL: https://issues.apache.org/jira/browse/IGNITE-11393
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> New implementation was added according to the new Java API for Javadoc.
> But the main method kept empty, need to implement toString() to process 
> IgniteLink annotation



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12082) [Release] Update versions for pre-build DEB/RPM and describe how to set these versions

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12082:

Summary: [Release] Update versions for pre-build DEB/RPM and describe how 
to set these versions  (was: [Release] Automate version assignment to pre-build 
DEB/RPM or describe how to set packages version to RC version)

> [Release] Update versions for pre-build DEB/RPM and describe how to set these 
> versions
> --
>
> Key: IGNITE-12082
> URL: https://issues.apache.org/jira/browse/IGNITE-12082
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.7.6
>
>
> Problem:
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild=4513186_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6
> RC 0 for 2.7.6. the build was successful, but versions for packages remain 
> unchanged
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not 
> require Release manager to update versions, but pre-build DEB & RPM keeps 
> version from the previous release.
> Solution 1 (manual):
> We need to add a new step
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages
> e.g. 4.1.4, where will ask a release manager to update versions.
> May be similar with commit 
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb
> Solution 2 (automatic)
> patch ./scripts/update-versions.sh to set packages version to current project 
> version. This will not require any actions from the release manager since 
> versions will be updated at step 4.1 with other assemblies versions.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Comment Edited] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-20 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911357#comment-16911357
 ] 

Dmitriy Pavlov edited comment on IGNITE-12061 at 8/20/19 1:41 PM:
--

[~zstan] thank you for contribution,
[~jooger], [~Pavlukhin], thank you for review, 
[~amashenkov], thank you for review and merging ticket.

[~zstan] unfortunately I can't automatically cherry-pick fix to 2.7.6. Could 
you please prepare 2-7-6 based branch and create new PR for it? 

An example is https://issues.apache.org/jira/browse/IGNITE-9562 and PR 
https://github.com/apache/ignite/pull/6781

Also, since there is a risk of introducing bugs during merge, I suggest running 
TC Run All on the resulting branch.


was (Author: dpavlov):
[~amashenkov], thank you for review and merging ticket.

[~zstan] unfortunately I can't automatically cherry-pick fix to 2.7.6. Could 
you please prepare 2-7-6 based branch and create new PR for it? 

An example is https://issues.apache.org/jira/browse/IGNITE-9562 and PR 
https://github.com/apache/ignite/pull/6781

Also, since there is a risk of introducing bugs during merge, I suggest running 
TC Run All on the resulting branch.

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.7.6
>
>  Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-20 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911357#comment-16911357
 ] 

Dmitriy Pavlov commented on IGNITE-12061:
-

[~amashenkov], thank you for review and merging ticket.

[~zstan] unfortunately I can't automatically cherry-pick fix to 2.7.6. Could 
you please prepare 2-7-6 based branch and create new PR for it? 

An example is https://issues.apache.org/jira/browse/IGNITE-9562 and PR 
https://github.com/apache/ignite/pull/6781

Also, since there is a risk of introducing bugs during merge, I suggest running 
TC Run All on the resulting branch.

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.7.6
>
>  Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Reopened] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov reopened IGNITE-12061:
-

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.7.6
>
>  Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-12071) Test failures after IGNITE-9562 fix in IGFS suite

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12071:

Ignite Flags:   (was: Docs Required)

> Test failures after IGNITE-9562 fix in IGFS suite
> -
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.7.6
>
>
> https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
> *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>  - eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-9562:
---
Labels: 2.7.6-rc1  (was: )

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
>  Labels: 2.7.6-rc1
> Fix For: 2.7.6
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2249)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:353)
>   at 

[jira] [Updated] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-20 Thread Dmitriy Pavlov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-9562:
---
Fix Version/s: (was: 2.8)

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.7.6
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2249)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:353)
>   at 
> 

[jira] [Commented] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-19 Thread Dmitriy Pavlov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910608#comment-16910608
 ] 

Dmitriy Pavlov commented on IGNITE-9562:


[~ivan.glukos] [~mstepachev] thank you for review.

I could merge it to 2.7.6 once TC Bot visa is more or less like N blockers 
found, where N< 5.

Now there is 9: 
https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F6781%2Fhead=Latest=ignite-2.7.6

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.8, 2.7.6
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> 

[jira] [Updated] (IGNITE-12083) Change release scripts according pre-build DEB/RPM folders

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12083:

Description: svn: E02: Can't stat 
'/mnt/c/dev_env/release-2.7.6-rc0/packaging/pkg': No such file or directory

> Change release scripts according pre-build DEB/RPM folders
> --
>
> Key: IGNITE-12083
> URL: https://issues.apache.org/jira/browse/IGNITE-12083
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.7.6
>
>
> svn: E02: Can't stat '/mnt/c/dev_env/release-2.7.6-rc0/packaging/pkg': No 
> such file or directory



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (IGNITE-12083) Change release scripts according pre-build DEB/RPM folders

2019-08-18 Thread Dmitriy Pavlov (JIRA)
Dmitriy Pavlov created IGNITE-12083:
---

 Summary: Change release scripts according pre-build DEB/RPM folders
 Key: IGNITE-12083
 URL: https://issues.apache.org/jira/browse/IGNITE-12083
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
 Fix For: 2.7.6






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (IGNITE-12082) Automate version assignment to pre-build DEB/RPM or describe how to set packages version to RC version

2019-08-18 Thread Dmitriy Pavlov (JIRA)
Dmitriy Pavlov created IGNITE-12082:
---

 Summary: Automate version assignment to pre-build DEB/RPM or 
describe how to set packages version to RC version
 Key: IGNITE-12082
 URL: https://issues.apache.org/jira/browse/IGNITE-12082
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
 Fix For: 2.7.6


https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild=4513186_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6

RC 0 for 2.7.6. the build was successful, but versions for packages remain 
unchanged

https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not 
require Release manager to update versions, but pre-build DEB & RPM keeps 
version from previous release.

We need to add a new step
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages
e.g. 4.1.4, where will ask a release manager to update versions.

May be similar with commit 
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12068) puzzling select result

2019-08-18 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909973#comment-16909973
 ] 

Dmitriy Pavlov commented on IGNITE-12068:
-

[~Pavlukhin] thank you for preparing release notes. I was thinking about how to 
describe the issue, but you've already shared it.

> puzzling select result
> --
>
> Key: IGNITE-12068
> URL: https://issues.apache.org/jira/browse/IGNITE-12068
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7.5
> Environment: System version: CentOS Linux release 7.6.1810 (Core)
> Apache Ignite version: apache-ignite-2.7.5-1.noarch
>Reporter: JerryKwan
>Assignee: Ivan Pavlukhin
>Priority: Blocker
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> select using the first primary key only returns one record, but it should 
> return more records.
> The following is how to reproduce this problem
> 1, create a table using
> CREATE TABLE IF NOT EXISTS Person(
>  id int,
>  city_id int,
>  name varchar,
>  age int, 
>  company varchar,
>  PRIMARY KEY (id, city_id)
> );
> 2, insert some records
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4);
> INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4);
> 3, query using 'select * from Person' show all of the records, expected
> [http://www.passimage.in/i/03da31c8f23cf64580d5.png]
> 4, query using 'select * from Person where id=1', only get one record, NOT 
> expected
> [http://www.passimage.in/i/f5491491a70c5d796823.png]
> 5, query using 'select * from Person where city_id=4' get  two records, 
> expected
> [http://www.passimage.in/i/ff0ee4f5e882983d779d.png]
> Why  'select * from Person where id=1', only get one record? and how to fix 
> this? Is there any special operations/configurations to do?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12081) Page replacement can reload invalid page during checkpoint

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12081:

Labels: 2.7.6-rc0  (was: )

> Page replacement can reload invalid page during checkpoint
> --
>
> Key: IGNITE-12081
> URL: https://issues.apache.org/jira/browse/IGNITE-12081
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There is a race between {{writeCheckpointPages}} and page replacement process:
>  * Checkpointer thread begins a checkpoint
>  * Checkpointer thread calls {{getPageForCheckpoint()}}, which will copy page 
> content *and clear dirty flag*
>  * Page replacement tries to find a page for replacement and chooses this 
> page, the page is thrown away
>  * Before the page is written back to the store, the page is acquired again.
> As a result, an older copy of the page is brought back to memory, which 
> causes all kinds of corruption exceptions and assertions.
> The attached unit test demonstrates the issue. It is likely that all 
> baselines are affected starting from 2.4
> As a part of this ticket, we must add more unit-tests for checkpointing 
> protocol invariants we rely on.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12081) Page replacement can reload invalid page during checkpoint

2019-08-18 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909952#comment-16909952
 ] 

Dmitriy Pavlov commented on IGNITE-12081:
-

Blockers not related to this fix (always happen because TC Bot does not compare 
base branch build problem occurrences).

The fix is looking good for me, Dmitriy, thank for your contribution and for 
preparing fix for 2.7.6.

Merged to 2.7.6. (via ./apply-pull-request.sh 6787 -tb ignite-2.7.6)

> Page replacement can reload invalid page during checkpoint
> --
>
> Key: IGNITE-12081
> URL: https://issues.apache.org/jira/browse/IGNITE-12081
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a race between {{writeCheckpointPages}} and page replacement process:
>  * Checkpointer thread begins a checkpoint
>  * Checkpointer thread calls {{getPageForCheckpoint()}}, which will copy page 
> content *and clear dirty flag*
>  * Page replacement tries to find a page for replacement and chooses this 
> page, the page is thrown away
>  * Before the page is written back to the store, the page is acquired again.
> As a result, an older copy of the page is brought back to memory, which 
> causes all kinds of corruption exceptions and assertions.
> The attached unit test demonstrates the issue. It is likely that all 
> baselines are affected starting from 2.4
> As a part of this ticket, we must add more unit-tests for checkpointing 
> protocol invariants we rely on.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12057) Persistence files are stored to temp dir

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12057:

Labels: 2.7.6-rc0  (was: )

> Persistence files are stored to temp dir
> 
>
> Key: IGNITE-12057
> URL: https://issues.apache.org/jira/browse/IGNITE-12057
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Anton Kalashnikov
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> h2. Description
> Check this thread:
> [https://stackoverflow.com/questions/56951913/ignite-persistent-schema-tables-disappeared-sometimes/56977212#56977212]
> This prospect almost dropped us because the company could figure out why 
> persistence files disappear upon restarts. They turned off WARN logging level 
> and could see our warning saying that the files are written to such a 
> directory.
> I've updated Ignite docs:
> [https://apacheignite.readme.io/docs/distributed-persistent-store#section-persistence-path-management]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12068) puzzling select result

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12068:

Labels: 2.7.6-rc0  (was: )

> puzzling select result
> --
>
> Key: IGNITE-12068
> URL: https://issues.apache.org/jira/browse/IGNITE-12068
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7.5
> Environment: System version: CentOS Linux release 7.6.1810 (Core)
> Apache Ignite version: apache-ignite-2.7.5-1.noarch
>Reporter: JerryKwan
>Assignee: Ivan Pavlukhin
>Priority: Blocker
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> select using the first primary key only returns one record, but it should 
> return more records.
> The following is how to reproduce this problem
> 1, create a table using
> CREATE TABLE IF NOT EXISTS Person(
>  id int,
>  city_id int,
>  name varchar,
>  age int, 
>  company varchar,
>  PRIMARY KEY (id, city_id)
> );
> 2, insert some records
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);
> INSERT INTO Person (id, name, city_id) VALUES (1, 'John Dean', 4);
> INSERT INTO Person (id, name, city_id) VALUES (2, 'Alex', 4);
> 3, query using 'select * from Person' show all of the records, expected
> [http://www.passimage.in/i/03da31c8f23cf64580d5.png]
> 4, query using 'select * from Person where id=1', only get one record, NOT 
> expected
> [http://www.passimage.in/i/f5491491a70c5d796823.png]
> 5, query using 'select * from Person where city_id=4' get  two records, 
> expected
> [http://www.passimage.in/i/ff0ee4f5e882983d779d.png]
> Why  'select * from Person where id=1', only get one record? and how to fix 
> this? Is there any special operations/configurations to do?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12060:

Labels: 2.7.6-rc0  (was: )

> Incorrect row size calculation, lead to tree corruption
> ---
>
> Key: IGNITE-12060
> URL: https://issues.apache.org/jira/browse/IGNITE-12060
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>
> We do not correctly calculate old row size and new row size for check 
> in-place update. One of them may include cacheId but other not. Size 
> dependent on shared group or not.
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap in exchange history

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11767:

Labels: 2.7.6-rc0  (was: )

> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> --
>
> Key: IGNITE-11767
> URL: https://issues.apache.org/jira/browse/IGNITE-11767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before 
> putting msg in exchFuts linked list to be stowed away.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-18 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909937#comment-16909937
 ] 

Dmitriy Pavlov commented on IGNITE-9562:


according to Eduard comments
 IgniteCacheRestartTestSuite2: IgniteCachePutAllRestartTest.testStopNode   
- needs to be researched
PDS 1 [ tests 5 ]   
  IgnitePdsTestSuite: IgnitePdsDestroyCacheTest.testDestroyCachesAbruptly   
   - can be Ignored/failed because of 
https://issues.apache.org/jira/browse/IGNITE-8717

Cache 7 [ tests 2 ]  
  IgniteCacheTestSuite7: CacheMetricsManageTest.testJmxPdsStatisticsEnable 
- this is an issue, need to be fixed.

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.8, 2.7.6
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> 

[jira] [Updated] (IGNITE-10451) .NET: Persistence does not work with custom affinity function

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-10451:

Labels: .NET 2.7.6-rc0  (was: .NET)

> .NET: Persistence does not work with custom affinity function
> -
>
> Key: IGNITE-10451
> URL: https://issues.apache.org/jira/browse/IGNITE-10451
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET, 2.7.6-rc0
> Fix For: 2.7.6
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> To reproduce: assign custom affinity function in 
> {{PersistenceTest.TestCacheDataSurvivesNodeRestart}}.
> As a result, node restart fails with the following exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException : An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   > Apache.Ignite.Core.Common.JavaException : class 
> org.apache.ignite.IgniteException: An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1027)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:48)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> Caused by: class org.apache.ignite.IgniteCheckedException: An error occurred 
> during cache configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:902)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:844)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:891)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.restoreCacheConfigurations(GridCacheProcessor.java:756)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1300(GridCacheProcessor.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5456)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:412)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4473)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1047)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
>   ... 1 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> deserialize object with given class loader: 
> sun.misc.Launcher$AppClassLoader@18b4aac2
>   at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:147)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:898)
>   ... 15 more
> Caused by: java.lang.IllegalArgumentException: Ignite instance name thread 
> local must be set or this method should be accessed under 
> org.apache.ignite.thread.IgniteThread
>   at 
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1413)
>   at 
> 

[jira] [Updated] (IGNITE-11736) Make the TeamCity console quiet.

2019-08-18 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11736:

Labels: 2.7.6-rc0  (was: )

> Make the TeamCity console quiet.
> 
>
> Key: IGNITE-11736
> URL: https://issues.apache.org/jira/browse/IGNITE-11736
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
>  Labels: 2.7.6-rc0
> Fix For: 2.7.6
>
> Attachments: quiet-console-checkbox.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As a result of this discussion: 
> [https://lists.apache.org/list.html?d...@ignite.apache.org:lte=1M:Make%20the%20TeamCity%20console%20quiet.]
>  
>  # Rollover will be locked. Pros: Only one big file in an archive. Cons: Max 
> size of the file isn't limited. 2. Run all will contain a parameter for 
> switch off the quiet mode. 3. New config: log4j-tc-test.xml for TeamCity 
> environment.
> TC fixes:
> Add a checkbox into the general run window. *By default* the checkbox *is 
> active*. If the checkbox is *active*, the TeamCity adds next params for java 
> run: *-DIGNITE_TEST_PROP_LOG4J_FILE=log4j-tc-test.xml -DIGNITE_QUIET=true* 
> otherwise *empty params*.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12071) Test failures after IGNITE-9562 fix in IGFS suite

2019-08-18 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909924#comment-16909924
 ] 

Dmitriy Pavlov commented on IGNITE-12071:
-

[~EdShangGG], [~ivan.glukos], is my understanding correct that fix for these 
tests if the following one-liner

https://github.com/apache/ignite/pull/6765/files#diff-3b0297f8e0e757b6b5ede921d629c6b5R608

?

> Test failures after IGNITE-9562 fix in IGFS suite
> -
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.7.6
>
>
> https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
> *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>  - eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12071) Test failures after IGNITE-9562 fix in IGFS suite

2019-08-18 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16909923#comment-16909923
 ] 

Dmitriy Pavlov commented on IGNITE-12071:
-

This issue is fixed under https://issues.apache.org/jira/browse/IGNITE-12059 , 
still need to cherry-pick fix to 2.7.6 once fix 
https://issues.apache.org/jira/browse/IGNITE-9562 is there

> Test failures after IGNITE-9562 fix in IGFS suite
> -
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.7.6
>
>
> https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
> *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>  - eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap in exchange history

2019-08-16 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11767:

Fix Version/s: (was: 2.8)

> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> --
>
> Key: IGNITE-11767
> URL: https://issues.apache.org/jira/browse/IGNITE-11767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before 
> putting msg in exchFuts linked list to be stowed away.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-15 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908316#comment-16908316
 ] 

Dmitriy Pavlov commented on IGNITE-12061:
-

[~Pavlukhin] could you please merge it if you agree?

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12077) Improve Checkstyle or other inspections profile to avoid using GG- reference in Ignite code base

2019-08-15 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12077:

Ignite Flags:   (was: Docs Required)

> Improve Checkstyle or other inspections profile to avoid using GG- reference 
> in Ignite code base
> 
>
> Key: IGNITE-12077
> URL: https://issues.apache.org/jira/browse/IGNITE-12077
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> Time to time tests are Ignored or todo added with reference to 
>  GG-  tickets "
> For example here
> https://github.com/apache/ignite/pull/6748/files#diff-2dd1dad039cddd36610c62a3dc2c1a28R223
> It is suggested to add some inspection check on TC to reject patches if there 
> is a line 
> containing: 
> - ": //ggsystems.atlassian.net/" 
> - or at the same time Ignore or todo and "GG- [0-9] *" 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (IGNITE-12077) Improve Checkstyle or other inspections profile to avoid using GG- reference in Ignite code base

2019-08-15 Thread Dmitriy Pavlov (JIRA)
Dmitriy Pavlov created IGNITE-12077:
---

 Summary: Improve Checkstyle or other inspections profile to avoid 
using GG- reference in Ignite code base
 Key: IGNITE-12077
 URL: https://issues.apache.org/jira/browse/IGNITE-12077
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov


Time to time tests are Ignored or todo added with reference to 
 GG-  tickets "
For example here
https://github.com/apache/ignite/pull/6748/files#diff-2dd1dad039cddd36610c62a3dc2c1a28R223

It is suggested to add some inspection check on TC to reject patches if there 
is a line 
containing: 
- ": //ggsystems.atlassian.net/" 
- or at the same time Ignore or todo and "GG- [0-9] *" 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-11736) Make the TeamCity console quiet.

2019-08-15 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908240#comment-16908240
 ] 

Dmitriy Pavlov commented on IGNITE-11736:
-

Cherry-picked to 2.7.6, 
https://github.com/apache/ignite/commit/891e49fe1eeb28bc6b655024086c3f4d1324fda4

> Make the TeamCity console quiet.
> 
>
> Key: IGNITE-11736
> URL: https://issues.apache.org/jira/browse/IGNITE-11736
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.7.6
>
> Attachments: quiet-console-checkbox.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As a result of this discussion: 
> [https://lists.apache.org/list.html?d...@ignite.apache.org:lte=1M:Make%20the%20TeamCity%20console%20quiet.]
>  
>  # Rollover will be locked. Pros: Only one big file in an archive. Cons: Max 
> size of the file isn't limited. 2. Run all will contain a parameter for 
> switch off the quiet mode. 3. New config: log4j-tc-test.xml for TeamCity 
> environment.
> TC fixes:
> Add a checkbox into the general run window. *By default* the checkbox *is 
> active*. If the checkbox is *active*, the TeamCity adds next params for java 
> run: *-DIGNITE_TEST_PROP_LOG4J_FILE=log4j-tc-test.xml -DIGNITE_QUIET=true* 
> otherwise *empty params*.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-11736) Make the TeamCity console quiet.

2019-08-15 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11736:

Fix Version/s: 2.7.6

> Make the TeamCity console quiet.
> 
>
> Key: IGNITE-11736
> URL: https://issues.apache.org/jira/browse/IGNITE-11736
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Stepachev Maksim
>Assignee: Stepachev Maksim
>Priority: Major
> Fix For: 2.7.6
>
> Attachments: quiet-console-checkbox.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As a result of this discussion: 
> [https://lists.apache.org/list.html?d...@ignite.apache.org:lte=1M:Make%20the%20TeamCity%20console%20quiet.]
>  
>  # Rollover will be locked. Pros: Only one big file in an archive. Cons: Max 
> size of the file isn't limited. 2. Run all will contain a parameter for 
> switch off the quiet mode. 3. New config: log4j-tc-test.xml for TeamCity 
> environment.
> TC fixes:
> Add a checkbox into the general run window. *By default* the checkbox *is 
> active*. If the checkbox is *active*, the TeamCity adds next params for java 
> run: *-DIGNITE_TEST_PROP_LOG4J_FILE=log4j-tc-test.xml -DIGNITE_QUIET=true* 
> otherwise *empty params*.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12032) Server node prints exception when ODBC driver disconnects

2019-08-15 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12032:

Fix Version/s: (was: 2.7.6)
   2.8

> Server node prints exception when ODBC driver disconnects
> -
>
> Key: IGNITE-12032
> URL: https://issues.apache.org/jira/browse/IGNITE-12032
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.7.5
>Reporter: Evgenii Zhuravlev
>Priority: Major
>  Labels: newbie, usability
> Fix For: 2.8
>
>
> Whenever a process using ODBC clients is finished, it's printing in the 
> node logs this exception: 
> {code:java}
> *[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
>  
> Failed to process selector key [s 
> es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker 
> [readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192 
> ], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0, 
> bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo 
> rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null, 
> finished=false, heartbeatTs=1564289118230, hashCo 
> de=1829856117, interrupted=false, 
> runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null, 
> readBuf=null, inRecove 
> ry=null, outRecovery=null, super=GridNioSessionImpl 
> [locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre 
> ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588, 
> bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623 
> 5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioAsyn 
> cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser, 
> directMode=false]], accepted=true, markedForClos 
> e=false]]] 
> java.io.IOException: An existing connection was forcibly closed by the 
> remote host 
> at sun.nio.ch.SocketDispatcher.read0(Native Method) 
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) 
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) 
> at sun.nio.ch.IOUtil.read(IOUtil.java:197) 
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
>  
> 04) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
>  
> oServer.java:2389) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
>  
> 6) 
> at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
>  
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) 
> at java.lang.Thread.run(Thread.java:748)* 
> {code}
> It's absolutely normal behavior when ODBC client disconnects from the node, 
> so, we shouldn't print exception in the log. We should replace it with 
> something like INFO message about ODBC client disconnection.
> Thread from user list: 
> http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap in exchange history

2019-08-15 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11767:

Fix Version/s: 2.7.6

> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> --
>
> Key: IGNITE-11767
> URL: https://issues.apache.org/jira/browse/IGNITE-11767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.8, 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before 
> putting msg in exchFuts linked list to be stowed away.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-11953) BTree corruption caused by byte array values

2019-08-15 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908145#comment-16908145
 ] 

Dmitriy Pavlov commented on IGNITE-11953:
-

Agreed in private with Dmitriy G. that this issue is more generic than 
https://issues.apache.org/jira/browse/IGNITE-12060

I've returned it to assigned on 2.8. 
 

> BTree corruption caused by byte array values
> 
>
> Key: IGNITE-11953
> URL: https://issues.apache.org/jira/browse/IGNITE-11953
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> In some cases for caches with cache group, we can get BTree corruption 
> exception.
> {code}
> 09:53:58,890][SEVERE][sys-stripe-10-#11][] Critical system error detected. 
> Will be handled accordingly to configured handler [hnd=CustomFailureHandler 
> [ignoreCriticalErrors=false, disabled=false][StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=class o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing 
> a transaction has produced runtime exception]]class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Committing a transaction has produced runtime exception
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:800)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:922)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:799)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:608)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:478)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:535)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1055)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:931)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:887)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:209)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:207)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1129)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:594)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:504)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>  Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl [part=427, 
> val=Grkg1DUF3yQE6tC9Se50mi5w.T, hasValBytes=true], hash=1872857770, 
> cacheId=-420893003]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1811)
>   at 
> 

[jira] [Updated] (IGNITE-11953) BTree corruption caused by byte array values

2019-08-15 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11953:

Fix Version/s: (was: 2.7.6)
   2.8

> BTree corruption caused by byte array values
> 
>
> Key: IGNITE-11953
> URL: https://issues.apache.org/jira/browse/IGNITE-11953
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.8
>
>
> In some cases for caches with cache group, we can get BTree corruption 
> exception.
> {code}
> 09:53:58,890][SEVERE][sys-stripe-10-#11][] Critical system error detected. 
> Will be handled accordingly to configured handler [hnd=CustomFailureHandler 
> [ignoreCriticalErrors=false, disabled=false][StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=class o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing 
> a transaction has produced runtime exception]]class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Committing a transaction has produced runtime exception
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:800)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:922)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:799)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:608)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:478)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:535)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1055)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:931)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:887)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:209)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:207)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1129)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:594)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:504)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>  Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl [part=427, 
> val=Grkg1DUF3yQE6tC9Se50mi5w.T, hasValBytes=true], hash=1872857770, 
> cacheId=-420893003]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1811)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1620)
>   at 
> 

[jira] [Commented] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap in exchange history

2019-08-15 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908130#comment-16908130
 ] 

Dmitriy Pavlov commented on IGNITE-11767:
-

[~ilyak] thank you, I've created https://github.com/apache/ignite/pull/6780 for 
check PR using AI TC Bot

> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> --
>
> Key: IGNITE-11767
> URL: https://issues.apache.org/jira/browse/IGNITE-11767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before 
> putting msg in exchFuts linked list to be stowed away.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Comment Edited] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-15 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907266#comment-16907266
 ] 

Dmitriy Pavlov edited comment on IGNITE-9562 at 8/15/19 2:06 PM:
-

[~ivan.glukos], could you please cherry-pick commit to Ignite 2.7.6 branch once 
all tests are fixed in master 
?https://github.com/apache/ignite/commit/27e9f705c1f65baae20b7dc3c03e988217dbe3f6


was (Author: dpavlov):
Could you please cherry-pick commit to Ignite 2.7.6 branch once all tests are 
fixed in master 
?https://github.com/apache/ignite/commit/27e9f705c1f65baae20b7dc3c03e988217dbe3f6

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.8, 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> 

[jira] [Updated] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-15 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-9562:
---
Fix Version/s: 2.7.6

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.8, 2.7.6
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2249)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:353)
>   at 
> 

[jira] [Commented] (IGNITE-11953) BTree corruption caused by byte array values

2019-08-15 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908069#comment-16908069
 ] 

Dmitriy Pavlov commented on IGNITE-11953:
-

[~DmitriyGovorukhin], kindly reminder, please respond

> BTree corruption caused by byte array values
> 
>
> Key: IGNITE-11953
> URL: https://issues.apache.org/jira/browse/IGNITE-11953
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.7.6
>
>
> In some cases for caches with cache group, we can get BTree corruption 
> exception.
> {code}
> 09:53:58,890][SEVERE][sys-stripe-10-#11][] Critical system error detected. 
> Will be handled accordingly to configured handler [hnd=CustomFailureHandler 
> [ignoreCriticalErrors=false, disabled=false][StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=class o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing 
> a transaction has produced runtime exception]]class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Committing a transaction has produced runtime exception
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:800)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:922)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:799)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:608)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:478)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:535)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1055)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:931)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:887)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:209)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:207)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1129)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:594)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:504)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>  Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl [part=427, 
> val=Grkg1DUF3yQE6tC9Se50mi5w.T, hasValBytes=true], hash=1872857770, 
> cacheId=-420893003]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1811)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1620)
>   at 
> 

[jira] [Updated] (IGNITE-12054) Upgrade Spark module to 2.4

2019-08-15 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12054:

Fix Version/s: (was: 2.7.6)
   2.8

> Upgrade Spark module to 2.4
> ---
>
> Key: IGNITE-12054
> URL: https://issues.apache.org/jira/browse/IGNITE-12054
> Project: Ignite
>  Issue Type: Task
>  Components: spark
>Affects Versions: 2.7.5
>Reporter: Denis Magda
>Assignee: Nikolay Izhikov
>Priority: Blocker
> Fix For: 2.8
>
>
> Users can't use APIs that are already available in Spark 2.4:
> https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite
> Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as 
> a separate module that can support multiple Spark versions.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption

2019-08-14 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12060:

Fix Version/s: (was: 2.8)
   2.7.6

> Incorrect row size calculation, lead to tree corruption
> ---
>
> Key: IGNITE-12060
> URL: https://issues.apache.org/jira/browse/IGNITE-12060
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.7.6
>
>
> We do not correctly calculate old row size and new row size for check 
> in-place update. One of them may include cacheId but other not. Size 
> dependent on shared group or not.
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption

2019-08-14 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907301#comment-16907301
 ] 

Dmitriy Pavlov commented on IGNITE-12060:
-

Cherry-picked to 2.7.6 
https://github.com/apache/ignite/commit/610f06e32bd045cfabaf5ae4813783a5616b0889

> Incorrect row size calculation, lead to tree corruption
> ---
>
> Key: IGNITE-12060
> URL: https://issues.apache.org/jira/browse/IGNITE-12060
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.7.6
>
>
> We do not correctly calculate old row size and new row size for check 
> in-place update. One of them may include cacheId but other not. Size 
> dependent on shared group or not.
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-10451) .NET: Persistence does not work with custom affinity function

2019-08-14 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907299#comment-16907299
 ] 

Dmitriy Pavlov commented on IGNITE-10451:
-

Cherry-picked to 2.7.6 
https://github.com/apache/ignite/pull/6775/commits/93d0f89cf59fa02b9e3dda2b463835d6608667a4

> .NET: Persistence does not work with custom affinity function
> -
>
> Key: IGNITE-10451
> URL: https://issues.apache.org/jira/browse/IGNITE-10451
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.8
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> To reproduce: assign custom affinity function in 
> {{PersistenceTest.TestCacheDataSurvivesNodeRestart}}.
> As a result, node restart fails with the following exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException : An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   > Apache.Ignite.Core.Common.JavaException : class 
> org.apache.ignite.IgniteException: An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1027)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:48)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> Caused by: class org.apache.ignite.IgniteCheckedException: An error occurred 
> during cache configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:902)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:844)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:891)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.restoreCacheConfigurations(GridCacheProcessor.java:756)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1300(GridCacheProcessor.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5456)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:412)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4473)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1047)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
>   ... 1 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> deserialize object with given class loader: 
> sun.misc.Launcher$AppClassLoader@18b4aac2
>   at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:147)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:898)
>   ... 15 more
> Caused by: java.lang.IllegalArgumentException: Ignite instance name thread 
> local must be set or this method should be accessed under 
> org.apache.ignite.thread.IgniteThread
>   at 
> 

[jira] [Updated] (IGNITE-10451) .NET: Persistence does not work with custom affinity function

2019-08-14 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-10451:

Fix Version/s: (was: 2.8)
   2.7.6

> .NET: Persistence does not work with custom affinity function
> -
>
> Key: IGNITE-10451
> URL: https://issues.apache.org/jira/browse/IGNITE-10451
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.7.6
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> To reproduce: assign custom affinity function in 
> {{PersistenceTest.TestCacheDataSurvivesNodeRestart}}.
> As a result, node restart fails with the following exception:
> {code}
> Apache.Ignite.Core.Common.IgniteException : An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   > Apache.Ignite.Core.Common.JavaException : class 
> org.apache.ignite.IgniteException: An error occurred during cache 
> configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1027)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:48)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformIgnition.start(PlatformIgnition.java:74)
> Caused by: class org.apache.ignite.IgniteCheckedException: An error occurred 
> during cache configuration loading from file 
> [file=C:\Users\tps0\AppData\Local\Temp\Ignite_ihxso0zq.tw0\Store\node00-263cfb5e-ec70-4378-8cbb-62b6fcc8043b\cache-persistentCache\cache_data.dat]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:902)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheConfigurations(FilePageStoreManager.java:844)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.addCacheOnJoinFromConfig(GridCacheProcessor.java:891)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.restoreCacheConfigurations(GridCacheProcessor.java:756)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.access$1300(GridCacheProcessor.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor$CacheRecoveryLifecycle.onReadyForRead(GridCacheProcessor.java:5456)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetastorageReadyForRead(GridCacheDatabaseSharedManager.java:412)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.readMetastore(GridCacheDatabaseSharedManager.java:724)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.notifyMetaStorageSubscribersOnReadyForRead(GridCacheDatabaseSharedManager.java:4473)
>   at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1047)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2040)
>   at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1732)
>   at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
>   at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:656)
>   at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java:43)
>   ... 1 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to 
> deserialize object with given class loader: 
> sun.misc.Launcher$AppClassLoader@18b4aac2
>   at 
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal0(JdkMarshaller.java:147)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:93)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.readCacheData(FilePageStoreManager.java:898)
>   ... 15 more
> Caused by: java.lang.IllegalArgumentException: Ignite instance name thread 
> local must be set or this method should be accessed under 
> org.apache.ignite.thread.IgniteThread
>   at 
> org.apache.ignite.internal.IgnitionEx.localIgnite(IgnitionEx.java:1413)
>   at 
> 

[jira] [Updated] (IGNITE-12071) Test failures after IGNITE-9562 fix in IGFS suite

2019-08-14 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12071:

Summary: Test failures after IGNITE-9562 fix in IGFS suite  (was: Test 
failures after IGNITE-9562 fix)

> Test failures after IGNITE-9562 fix in IGFS suite
> -
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.7.6
>
>
> https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
> *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>  - eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12071) Test failures after IGNITE-9562 fix

2019-08-14 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12071:

Description: 
# 
https://lists.apache.org/thread.html/94424a86283ba720a9ebcff37adc4782d271a07bc6470e148b57a715@%3Cdev.ignite.apache.org%3E

Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
planned to the 2.7.6 it is a blocker for the release 


 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2692660105095122533=%3Cdefault%3E=testDetails

 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectDynamicCacheStartRequest 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1915110918646717850=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - eduard shangareev  
https://ci.ignite.apache.org/viewModification.html?modId=889258


  was:
https://lists.apache.org/thread.html/94424a86283ba720a9ebcff37adc4782d271a07bc6470e148b57a715@%3Cdev.ignite.apache.org%3E

Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
planned to the 2.7.6 it is a blocker for the release 


 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2692660105095122533=%3Cdefault%3E=testDetails

 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectDynamicCacheStartRequest 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1915110918646717850=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - eduard shangareev  
https://ci.ignite.apache.org/viewModification.html?modId=889258



> Test failures after IGNITE-9562 fix
> ---
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.7.6
>
>
> # 
> https://lists.apache.org/thread.html/94424a86283ba720a9ebcff37adc4782d271a07bc6470e148b57a715@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
>  *New test failure in master-nightly 
> DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2692660105095122533=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> DiskPageCompressionConfigValidationTest.testIncorrectDynamicCacheStartRequest 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1915110918646717850=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>- eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12071) Test failures after IGNITE-9562 fix

2019-08-14 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12071:

Description: 
https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E

Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
planned to the 2.7.6 it is a blocker for the release 

*New test failure in master-nightly 
IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails

 *New test failure in master-nightly 
IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - eduard shangareev  
https://ci.ignite.apache.org/viewModification.html?modId=889258


  was:
# 
https://lists.apache.org/thread.html/94424a86283ba720a9ebcff37adc4782d271a07bc6470e148b57a715@%3Cdev.ignite.apache.org%3E

Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
planned to the 2.7.6 it is a blocker for the release 


 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2692660105095122533=%3Cdefault%3E=testDetails

 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectDynamicCacheStartRequest 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1915110918646717850=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - eduard shangareev  
https://ci.ignite.apache.org/viewModification.html?modId=889258



> Test failures after IGNITE-9562 fix
> ---
>
> Key: IGNITE-12071
> URL: https://issues.apache.org/jira/browse/IGNITE-12071
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Eduard Shangareev
>Priority: Blocker
> Fix For: 2.7.6
>
>
> https://lists.apache.org/thread.html/50375927a1375189c0aeec7dcaabc43ba83b7acee94524a3483d0c1b@%3Cdev.ignite.apache.org%3E
> Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
> planned to the 2.7.6 it is a blocker for the release 
> *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFilePrimary 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-8890685422557348790=%3Cdefault%3E=testDetails
>  *New test failure in master-nightly 
> IgfsCachePerBlockLruEvictionPolicySelfTest.testFileDualExclusion 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=3724804704021179739=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by 
>  - eduard shangareev  
> https://ci.ignite.apache.org/viewModification.html?modId=889258



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-14 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907266#comment-16907266
 ] 

Dmitriy Pavlov commented on IGNITE-9562:


Could you please cherry-pick commit to Ignite 2.7.6 branch once all tests are 
fixed in master 
?https://github.com/apache/ignite/commit/27e9f705c1f65baae20b7dc3c03e988217dbe3f6

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2249)
>   at 
> 

[jira] [Updated] (IGNITE-12059) DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails

2019-08-14 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12059:

Fix Version/s: 2.7.6

> DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration 
> fails
> ---
>
> Key: IGNITE-12059
> URL: https://issues.apache.org/jira/browse/IGNITE-12059
> Project: Ignite
>  Issue Type: Bug
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>Priority: Major
> Fix For: 2.8, 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration 
> fails because validation was removed in IGNITE-9562.
> Need to restore this validation.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Created] (IGNITE-12071) Test failures after IGNITE-9562 fix

2019-08-14 Thread Dmitriy Pavlov (JIRA)
Dmitriy Pavlov created IGNITE-12071:
---

 Summary: Test failures after IGNITE-9562 fix
 Key: IGNITE-12071
 URL: https://issues.apache.org/jira/browse/IGNITE-12071
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov
Assignee: Eduard Shangareev
 Fix For: 2.7.6


https://lists.apache.org/thread.html/94424a86283ba720a9ebcff37adc4782d271a07bc6470e148b57a715@%3Cdev.ignite.apache.org%3E

Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is 
planned to the 2.7.6 it is a blocker for the release 


 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2692660105095122533=%3Cdefault%3E=testDetails

 *New test failure in master-nightly 
DiskPageCompressionConfigValidationTest.testIncorrectDynamicCacheStartRequest 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1915110918646717850=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - eduard shangareev  
https://ci.ignite.apache.org/viewModification.html?modId=889258




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-11953) BTree corruption caused by byte array values

2019-08-14 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907198#comment-16907198
 ] 

Dmitriy Pavlov commented on IGNITE-11953:
-

[~DmitriyGovorukhin], could you please refer to commit made for this ticket ?

I've tried to search using its name IGNITE-11953 but can't see anything 
https://github.com/apache/ignite/search?q=IGNITE-11953_q=IGNITE-11953

> BTree corruption caused by byte array values
> 
>
> Key: IGNITE-11953
> URL: https://issues.apache.org/jira/browse/IGNITE-11953
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.7.6
>
>
> In some cases for caches with cache group, we can get BTree corruption 
> exception.
> {code}
> 09:53:58,890][SEVERE][sys-stripe-10-#11][] Critical system error detected. 
> Will be handled accordingly to configured handler [hnd=CustomFailureHandler 
> [ignoreCriticalErrors=false, disabled=false][StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=class o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing 
> a transaction has produced runtime exception]]class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Committing a transaction has produced runtime exception
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:800)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:922)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:799)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:608)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:478)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:535)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1055)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:931)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:887)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:209)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:207)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1129)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:594)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:504)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>  Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl [part=427, 
> val=Grkg1DUF3yQE6tC9Se50mi5w.T, hasValBytes=true], hash=1872857770, 
> cacheId=-420893003]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1811)
>   at 
> 

[jira] [Commented] (IGNITE-11767) GridDhtPartitionsFullMessage retains huge maps on heap in exchange history

2019-08-14 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907194#comment-16907194
 ] 

Dmitriy Pavlov commented on IGNITE-11767:
-

[~ilyak], could you please cherry-pick this commit 
https://github.com/apache/ignite/commit/478277e5e3fe1a535ea905f8beab42926453825a

to 2.7.6 branch and assign fixVersion=2.7.6 once commit is there? 
Unfortunately, change can't be merged more or less automatically.

> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> --
>
> Key: IGNITE-11767
> URL: https://issues.apache.org/jira/browse/IGNITE-11767
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Blocker
> Fix For: 2.8
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ExchangeHistory keeps a FinishState for every topology version.
> FinishState contains msg, which contains at least two huge maps:
> partCntrs2 and partsSizesBytes.
> We should probably strip msg, removing those two data structures before 
> putting msg in exchFuts linked list to be stowed away.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12064) Check license headers by checkstyle plugin

2019-08-13 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906351#comment-16906351
 ] 

Dmitriy Pavlov commented on IGNITE-12064:
-

I see rat plugin used in other Apache projects, so it is possible it is a 
standard for ASF projects. 

I'm not sure, but we should double-check it before we implement this change.

> Check license headers by checkstyle plugin
> --
>
> Key: IGNITE-12064
> URL: https://issues.apache.org/jira/browse/IGNITE-12064
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
>  Labels: checkstyle
>
> Currently, the {{apache-rat-plugin}} is used to check that source files 
> contain the specific license header. The suite {{[Licenses Headers]}} is 
> configured on TC to do so.
> It is possible to achieve the same thing with {{checkstyle-plugin}} (such it 
> is already run on each build). This will save TC resources consumed to run 
> both suites and simplify Ignite {{pom.xml}}.
> [1] https://checkstyle.sourceforge.io/config_header.html



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-13 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906168#comment-16906168
 ] 

Dmitriy Pavlov commented on IGNITE-12061:
-

For now, I've set 2.7.6 if we manage to include it into scope. If not, maybe 
fix version should be set to 2.8

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.

2019-08-13 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-12061:

Fix Version/s: 2.7.6

> Silently fail while try to recreate already existing index with differ 
> inline_size.
> ---
>
> Key: IGNITE-12061
> URL: https://issues.apache.org/jira/browse/IGNITE-12061
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.5, 2.7, 2.7.5
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.7.6
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> INLINE_SIZE differ from previous value is  not correctly sets.
> 1. create index idx0(c1, c2)
> 2. drop idx0
> 3. create index idx0(c1, c2) inline_size 100;
> inline_size remains the same, in this case default = 10.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-11953) BTree corruption caused by byte array values

2019-08-13 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906158#comment-16906158
 ] 

Dmitriy Pavlov commented on IGNITE-11953:
-

[~dmagda], could you please avoid setting version to resolved tickets without 
cherry-picking commit?

If you want a ticket to be included into release, mention it in the discussion. 
This case it potentially lost commit. Now release is quite small and it is not 
a problem, but it would become a problem for 2.8 & 3.0.

> BTree corruption caused by byte array values
> 
>
> Key: IGNITE-11953
> URL: https://issues.apache.org/jira/browse/IGNITE-11953
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
>Priority: Major
> Fix For: 2.7.6
>
>
> In some cases for caches with cache group, we can get BTree corruption 
> exception.
> {code}
> 09:53:58,890][SEVERE][sys-stripe-10-#11][] Critical system error detected. 
> Will be handled accordingly to configured handler [hnd=CustomFailureHandler 
> [ignoreCriticalErrors=false, disabled=false][StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=class o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing 
> a transaction has produced runtime exception]]class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Committing a transaction has produced runtime exception
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:800)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:922)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:799)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:608)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.finishTx(GridDhtTxLocal.java:478)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.commitDhtLocalAsync(GridDhtTxLocal.java:535)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1055)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:931)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:887)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:209)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:207)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1129)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:594)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:393)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:319)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1568)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1196)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1092)
>   at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:504)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
>  Runtime failure on search row: SearchRow [key=KeyCacheObjectImpl [part=427, 
> val=Grkg1DUF3yQE6tC9Se50mi5w.T, hasValBytes=true], hash=1872857770, 
> cacheId=-420893003]
>   at 
> 

[jira] [Updated] (IGNITE-9562) Destroyed cache that resurrected on an old offline node breaks PME

2019-08-08 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-9562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-9562:
---
Summary: Destroyed cache that resurrected on an old offline node breaks PME 
 (was: Destroyed cache that resurrected on a old offline node breaks PME)

> Destroyed cache that resurrected on an old offline node breaks PME
> --
>
> Key: IGNITE-9562
> URL: https://issues.apache.org/jira/browse/IGNITE-9562
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.5
>Reporter: Pavel Kovalenko
>Assignee: Eduard Shangareev
>Priority: Critical
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Given:
> 2 nodes, persistence enabled.
> 1) Stop 1 node
> 2) Destroy cache through client
> 3) Start stopped node
> When the stopped node joins to cluster it starts all caches that it has seen 
> before stopping.
> If that cache was cluster-widely destroyed it leads to breaking the crash 
> recovery process or PME.
> Root cause - we don't start/collect caches from the stopped node on another 
> part of a cluster.
> In case of PARTITIONED cache mode that scenario breaks crash recovery:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:696)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2449)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:679)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2445)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2321)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1568)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1308)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1255)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:766)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2577)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2457)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> In case of REPLICATED cache mode that scenario breaks PME coordinator process:
> {noformat}
> [2018-09-12 
> 18:50:36,407][ERROR][sys-#148%distributed.CacheStopAndRessurectOnOldNodeTest0%][GridCacheIoManager]
>  Failed to process message [senderId=4b6fd0d4-b756-4a9f-90ca-f0ee2511, 
> messageType=class 
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsSingleMessage]
> java.lang.AssertionError: 3080586
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.clientTopology(GridCachePartitionExchangeManager.java:815)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:3621)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.processSingleMessage(GridDhtPartitionsExchangeFuture.java:2439)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$100(GridDhtPartitionsExchangeFuture.java:137)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2261)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:2249)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
>   at 
> 

[jira] [Updated] (IGNITE-10337) [TC Bot] Test ticket

2019-08-07 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-10337:

Ignite Flags:   (was: Docs Required)

> [TC Bot] Test ticket
> 
>
> Key: IGNITE-10337
> URL: https://issues.apache.org/jira/browse/IGNITE-10337
> Project: Ignite
>  Issue Type: Task
>Reporter: PetrovMikhail
>Priority: Trivial
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (IGNITE-10337) [TC Bot] Test ticket

2019-08-07 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov resolved IGNITE-10337.
-
Resolution: Invalid

> [TC Bot] Test ticket
> 
>
> Key: IGNITE-10337
> URL: https://issues.apache.org/jira/browse/IGNITE-10337
> Project: Ignite
>  Issue Type: Task
>Reporter: PetrovMikhail
>Priority: Trivial
>




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Commented] (IGNITE-11962) [TC Bot] Test treated as recently contributed even if there were runs outside 21 days

2019-08-05 Thread Dmitriy Pavlov (JIRA)


[ 
https://issues.apache.org/jira/browse/IGNITE-11962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16900221#comment-16900221
 ] 

Dmitriy Pavlov commented on IGNITE-11962:
-

V20190805

> [TC Bot] Test treated as recently contributed even if there were runs outside 
> 21 days
> -
>
> Key: IGNITE-11962
> URL: https://issues.apache.org/jira/browse/IGNITE-11962
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Before notifying about recently contributed test it is necessary to 
> double-check
>  - if there were runs outside 21 days limit 
>  - if test failures count is not equal to the suite execution count
>  - every time test was executed, the suite was executed as well
> (this may protect from flaking appearing-disappearing tests init errors).



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (IGNITE-10094) TC: Introduce overnight builds

2019-08-05 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov resolved IGNITE-10094.
-
Resolution: Fixed

Run all nightly was set up.

TC Bot triggers nightly run alls (now limited by 6 run-alls per 24h) 

TC Bot detects failures.

The scale factor was supported by a number of tests.

TC Bot saves scale factor used. Since V20190805 TC Bot can filter runs by the 
scale factor.

> TC: Introduce overnight builds
> --
>
> Key: IGNITE-10094
> URL: https://issues.apache.org/jira/browse/IGNITE-10094
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Priority: Major
>
> Creating this ticket to collect all efforts on shortening a single TC run and 
> introduce overnight TC runs.
> From the infrastructure side, we need to create a separate run configuration 
> (for example, Run All Nightly). To begin, Run All Nightly will delegate to 
> Run All and later we will move several long-running suites to the nightly 
> run. Nightly Run All should have a nightly trigger.
> From the TC bot side, we need to configure it to push nightly builds when TC 
> is idle and additionally to track new failures in nightly runs.
> From the code side, we need to define an environment property that should 
> distinguish a quick run from the nightly run. Later this property will be 
> used to scale tests duration.
> [~dpavlov], [~sergey-chugunov], [~vveider], can you chime in?



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Updated] (IGNITE-11991) [TC Bot]: Rerun possible blockers sets incorrect "SCALE FACTOR" build parameter

2019-08-04 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-11991:

Ignite Flags:   (was: Docs Required)

> [TC Bot]: Rerun possible blockers sets incorrect "SCALE FACTOR" build 
> parameter
> ---
>
> Key: IGNITE-11991
> URL: https://issues.apache.org/jira/browse/IGNITE-11991
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Kuznetsov
>Priority: Major
>
> 1) Issue "Trigger build" during PR check from the Bot UI. Scheduled build has 
> parameter SCALE FACTOR=0.1 which is ok, because we want to get results sooner.
> 2) Issue "Rerun possible blockers" and see that SF for the "rerun" TC builds 
> is 1.0 (default).
> Expected that SF of the rerun builds should be the same as in the initial 
> RunAll build.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


[jira] [Resolved] (IGNITE-5555) Ignite PDS 1: JVM crash on teamcity (Rare)

2019-07-25 Thread Dmitriy Pavlov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov resolved IGNITE-.

   Resolution: Cannot Reproduce
Fix Version/s: (was: 2.8)

> Ignite PDS 1: JVM crash on teamcity (Rare)
> --
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, test-fail
> Attachments: crash_report, hs_err_pid7100.log.txt, thread_dump
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Most recent crashes
> https://ci.ignite.apache.org/viewLog.html?buildId=1095007=IgniteTests24Java8_IgnitePds1=buildResultsDiv
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ] 
>  BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started) 
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=1086130=buildResultsDiv=IgniteTests24Java8_IgnitePds1
> {noformat}
>Ignite PDS 1 [ tests 0 JVM CRASH ] 
>  BPlusTreeReuseListPageMemoryImplTest.testEmptyCursors (last started) 
> {noformat}
> (older failure
> http://ci.ignite.apache.org/viewLog.html?buildId=675694=buildResultsDiv=Ignite20Tests_IgnitePds1#)
> Stacktrace indicates failure was in ignite code related to B+tree
> {noformat}J 34156 C2 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.readLockPage(JLorg/apache/ignite/internal/pagemem/FullPageId;ZZ)J
>  (88 bytes) @ 0x7f98cfc24a5a [0x7f98cfc24540+0x51a]
> J 34634 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Search.run0(JJJLorg/apache/ignite/internal/processors/cache/persistence/tree/io/BPlusIO;Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Get;I)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (380 bytes) @ 0x7f98d32dd524 [0x7f98d32dd100+0x424]
> J 34633 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readPage(Lorg/apache/ignite/internal/pagemem/PageMemory;IJJLorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageLockListener;Lorg/apache/ignite/internal/processors/cache/persistence/tree/util/PageHandler;Ljava/lang/Object;ILjava/lang/Object;)Ljava/lang/Object;
>  (81 bytes) @ 0x7f98d2091c94 [0x7f98d2091a40+0x254]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca146c [0x7f98d2ca1180+0x2ec]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 34888 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Invoke;JJJI)Lorg/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree$Result;
>  (561 bytes) @ 0x7f98d2ca17f8 [0x7f98d2ca1180+0x678]
> J 35053 C2 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(Ljava/lang/Object;Ljava/lang/Object;Lorg/apache/ignite/internal/util/Igni
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)


  1   2   3   4   5   6   7   8   9   10   >