[jira] [Commented] (IGNITE-9425) NPE on index rebuild
[
https://issues.apache.org/jira/browse/IGNITE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602342#comment-16602342
]
ASF GitHub Bot commented on IGNITE-9425:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4647
> NPE on index rebuild
>
>
> Key: IGNITE-9425
> URL: https://issues.apache.org/jira/browse/IGNITE-9425
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>Priority: Major
> Fix For: 2.7
>
>
> Summary:
> This issue is seen when we have two caches mapped to two different regions
> (one with persistence and one without persistence)
> The client-side config should have the cache definitions
> The server-side config should have the data regions only
> Affinity should be defined on the cache without persistence
> We need to populate the data into both the caches and then restart the server
> and clients
> The issue will be seen when the client reconnects.
> Workaround:
> Add the cache configurations (for the caches without persistence) to the
> server-side config.
> Steps to reproduce:
> Ignite server
> - region1 (with persistence)
> - region2 (without persistence)
> client
> - cache1a from region1 – with custom affinity
> - cache2a fom region2 – with custom affinity
> 1. Populate data in both cache1a and cache2a.
> 2. Restart ignite server. It knows about cache1a from the persistent store.
> It doesn’t know about cache2a.
> 3. Restart client. When it connects to ignite, the server sees a nullpointer
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1243)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1239)
> 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
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.rebuildIndexesIfNeeded(GridCacheDatabaseSharedManager.java:1239)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1711)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:126)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:729)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9425) NPE on index rebuild
[
https://issues.apache.org/jira/browse/IGNITE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16602269#comment-16602269
]
Evgenii Zhuravlev commented on IGNITE-9425:
---
Fix look good to me
> NPE on index rebuild
>
>
> Key: IGNITE-9425
> URL: https://issues.apache.org/jira/browse/IGNITE-9425
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>Priority: Major
> Fix For: 2.7
>
>
> Summary:
> This issue is seen when we have two caches mapped to two different regions
> (one with persistence and one without persistence)
> The client-side config should have the cache definitions
> The server-side config should have the data regions only
> Affinity should be defined on the cache without persistence
> We need to populate the data into both the caches and then restart the server
> and clients
> The issue will be seen when the client reconnects.
> Workaround:
> Add the cache configurations (for the caches without persistence) to the
> server-side config.
> Steps to reproduce:
> Ignite server
> - region1 (with persistence)
> - region2 (without persistence)
> client
> - cache1a from region1 – with custom affinity
> - cache2a fom region2 – with custom affinity
> 1. Populate data in both cache1a and cache2a.
> 2. Restart ignite server. It knows about cache1a from the persistent store.
> It doesn’t know about cache2a.
> 3. Restart client. When it connects to ignite, the server sees a nullpointer
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1243)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1239)
> 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
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.rebuildIndexesIfNeeded(GridCacheDatabaseSharedManager.java:1239)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1711)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:126)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:729)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9425) NPE on index rebuild
[
https://issues.apache.org/jira/browse/IGNITE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597200#comment-16597200
]
Dmitry Karachentsev commented on IGNITE-9425:
-
[TC|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F4647%2Fhead]
tests look OK.
[~agoncharuk] please review.
> NPE on index rebuild
>
>
> Key: IGNITE-9425
> URL: https://issues.apache.org/jira/browse/IGNITE-9425
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>Priority: Major
> Fix For: 2.7
>
>
> Summary:
> This issue is seen when we have two caches mapped to two different regions
> (one with persistence and one without persistence)
> The client-side config should have the cache definitions
> The server-side config should have the data regions only
> Affinity should be defined on the cache without persistence
> We need to populate the data into both the caches and then restart the server
> and clients
> The issue will be seen when the client reconnects.
> Workaround:
> Add the cache configurations (for the caches without persistence) to the
> server-side config.
> Steps to reproduce:
> Ignite server
> - region1 (with persistence)
> - region2 (without persistence)
> client
> - cache1a from region1 – with custom affinity
> - cache2a fom region2 – with custom affinity
> 1. Populate data in both cache1a and cache2a.
> 2. Restart ignite server. It knows about cache1a from the persistent store.
> It doesn’t know about cache2a.
> 3. Restart client. When it connects to ignite, the server sees a nullpointer
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1243)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1239)
> 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
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.rebuildIndexesIfNeeded(GridCacheDatabaseSharedManager.java:1239)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1711)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:126)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:729)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9425) NPE on index rebuild
[
https://issues.apache.org/jira/browse/IGNITE-9425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16596500#comment-16596500
]
ASF GitHub Bot commented on IGNITE-9425:
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4647
IGNITE-9425 - Fix NPE on index rebuild
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9425
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4647.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4647
commit d26fb535865765b48fe955b3d95c544bb1ae1885
Author: dkarachentsev
Date: 2018-08-29T15:43:36Z
IGNITE-9425 - Fix NPE on index rebuild
> NPE on index rebuild
>
>
> Key: IGNITE-9425
> URL: https://issues.apache.org/jira/browse/IGNITE-9425
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
>Priority: Major
> Fix For: 2.7
>
>
> Summary:
> This issue is seen when we have two caches mapped to two different regions
> (one with persistence and one without persistence)
> The client-side config should have the cache definitions
> The server-side config should have the data regions only
> Affinity should be defined on the cache without persistence
> We need to populate the data into both the caches and then restart the server
> and clients
> The issue will be seen when the client reconnects.
> Workaround:
> Add the cache configurations (for the caches without persistence) to the
> server-side config.
> Steps to reproduce:
> Ignite server
> - region1 (with persistence)
> - region2 (without persistence)
> client
> - cache1a from region1 – with custom affinity
> - cache2a fom region2 – with custom affinity
> 1. Populate data in both cache1a and cache2a.
> 2. Restart ignite server. It knows about cache1a from the persistent store.
> It doesn’t know about cache2a.
> 3. Restart client. When it connects to ignite, the server sees a nullpointer
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1243)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$11.apply(GridCacheDatabaseSharedManager.java:1239)
> 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
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.rebuildIndexesIfNeeded(GridCacheDatabaseSharedManager.java:1239)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1711)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:126)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:729)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
