[jira] [Commented] (IGNITE-11699) Node can't start after forced shutdown if the wal archiver disabled
[
https://issues.apache.org/jira/browse/IGNITE-11699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832556#comment-16832556
]
Ignite TC Bot commented on IGNITE-11699:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3738433]]
{color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3738439]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3728479buildTypeId=IgniteTests24Java8_RunAll]
> Node can't start after forced shutdown if the wal archiver disabled
> ---
>
> Key: IGNITE-11699
> URL: https://issues.apache.org/jira/browse/IGNITE-11699
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: Pavel Vinokurov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
> Attachments: disabled-wal-archive-reproducer.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a server node killed with the disabled wal archive, it could fail on start
> with following exception:
> {code:java}
> [18:37:53,887][SEVERE][sys-stripe-1-#2][G] Failed to execute runnable.
> java.lang.IllegalStateException: Failed to get page IO instance (page content
> is corrupted)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:85)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:97)
> at
> org.apache.ignite.internal.pagemem.wal.record.delta.MetaPageUpdatePartitionDataRecord.applyDelta(MetaPageUpdatePartitionDataRecord.java:109)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyPageDelta(GridCacheDatabaseSharedManager.java:2532)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$performBinaryMemoryRestore$11(GridCacheDatabaseSharedManager.java:2327)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApplyPage$12(GridCacheDatabaseSharedManager.java:2441)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApply$13(GridCacheDatabaseSharedManager.java:2479)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:550)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> The reproducer is attached(works only on Linux).
> Steps to run the reproducer.
> 1. Copy config/server.xml into IGNITE_HOME/config folder;
> 2. Set IGNITE_HOME in the CorruptionReproducer class;
> 3. Launch CorruptionReproducer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11699) Node can't start after forced shutdown if the wal archiver disabled
[
https://issues.apache.org/jira/browse/IGNITE-11699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832551#comment-16832551
]
Vyacheslav Koptilin commented on IGNITE-11699:
--
Hello [~ivan.glukos], [~dpavlov],
Thanks for the review. I added a new test to cover this case.
> Node can't start after forced shutdown if the wal archiver disabled
> ---
>
> Key: IGNITE-11699
> URL: https://issues.apache.org/jira/browse/IGNITE-11699
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Affects Versions: 2.7
>Reporter: Pavel Vinokurov
>Assignee: Vyacheslav Koptilin
>Priority: Major
> Fix For: 2.8
>
> Attachments: disabled-wal-archive-reproducer.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a server node killed with the disabled wal archive, it could fail on start
> with following exception:
> {code:java}
> [18:37:53,887][SEVERE][sys-stripe-1-#2][G] Failed to execute runnable.
> java.lang.IllegalStateException: Failed to get page IO instance (page content
> is corrupted)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:85)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:97)
> at
> org.apache.ignite.internal.pagemem.wal.record.delta.MetaPageUpdatePartitionDataRecord.applyDelta(MetaPageUpdatePartitionDataRecord.java:109)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyPageDelta(GridCacheDatabaseSharedManager.java:2532)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$performBinaryMemoryRestore$11(GridCacheDatabaseSharedManager.java:2327)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApplyPage$12(GridCacheDatabaseSharedManager.java:2441)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$stripedApply$13(GridCacheDatabaseSharedManager.java:2479)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:550)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> The reproducer is attached(works only on Linux).
> Steps to run the reproducer.
> 1. Copy config/server.xml into IGNITE_HOME/config folder;
> 2. Set IGNITE_HOME in the CorruptionReproducer class;
> 3. Launch CorruptionReproducer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11832) Creating cache with EvictionPolicy and without onHeap cache kills the cluster
[ https://issues.apache.org/jira/browse/IGNITE-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-11832: --- Priority: Critical (was: Major) > Creating cache with EvictionPolicy and without onHeap cache kills the cluster > - > > Key: IGNITE-11832 > URL: https://issues.apache.org/jira/browse/IGNITE-11832 > Project: Ignite > Issue Type: Bug >Reporter: Evgenii Zhuravlev >Priority: Critical > Labels: usability > > After this, the cluster can be restored only by deleting the folder with the > problem cache. We should add some kind of validation to avoid these > situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11832) Creating cache with EvictionPolicy and without onHeap cache kills the cluster
[ https://issues.apache.org/jira/browse/IGNITE-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgenii Zhuravlev updated IGNITE-11832: --- Labels: usability (was: ) > Creating cache with EvictionPolicy and without onHeap cache kills the cluster > - > > Key: IGNITE-11832 > URL: https://issues.apache.org/jira/browse/IGNITE-11832 > Project: Ignite > Issue Type: Bug >Reporter: Evgenii Zhuravlev >Priority: Major > Labels: usability > > After this, the cluster can be restored only by deleting the folder with the > problem cache. We should add some kind of validation to avoid these > situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11832) Creating cache with EvictionPolicy and without onHeap cache kills the cluster
Evgenii Zhuravlev created IGNITE-11832: -- Summary: Creating cache with EvictionPolicy and without onHeap cache kills the cluster Key: IGNITE-11832 URL: https://issues.apache.org/jira/browse/IGNITE-11832 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev After this, the cluster can be restored only by deleting the folder with the problem cache. We should add some kind of validation to avoid these situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11831) Eviction doesn't work properly for data region with big objects of different sizes
[
https://issues.apache.org/jira/browse/IGNITE-11831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832411#comment-16832411
]
Evgenii Zhuravlev commented on IGNITE-11831:
can be fixed by adding
> Eviction doesn't work properly for data region with big objects of different
> sizes
> --
>
> Key: IGNITE-11831
> URL: https://issues.apache.org/jira/browse/IGNITE-11831
> Project: Ignite
> Issue Type: Bug
>Reporter: Evgenii Zhuravlev
>Priority: Major
>
> Reproducer:
> {code:java}
> public class ExampleNodeStartup {
> /**
> * Start up an empty node with example compute configuration.
> *
> * @param args Command line arguments, none required.
> * @throws IgniteException If failed.
> */
> public static void main(String[] args) throws IgniteException {
> Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
> IgniteCache keywordCache =
> ignite.getOrCreateCache("keyword");
> for(int i=0;i<1000;i++){
> int mega = new Random().nextInt(3) + 1;
> keywordCache.put(UUID.randomUUID().toString(), new byte[mega *
> 1024 * 1024]);
> System.out.println("current:"+i);
> }
> }
> }
> {code}
> data region configuration:
> {code:java}
>
> class="org.apache.ignite.configuration.DataStorageConfiguration">
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
> value="RANDOM_2_LRU"/>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11831) Eviction doesn't work properly for data region with big objects of different sizes
Evgenii Zhuravlev created IGNITE-11831:
--
Summary: Eviction doesn't work properly for data region with big
objects of different sizes
Key: IGNITE-11831
URL: https://issues.apache.org/jira/browse/IGNITE-11831
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
Reproducer:
{code:java}
public class ExampleNodeStartup {
/**
* Start up an empty node with example compute configuration.
*
* @param args Command line arguments, none required.
* @throws IgniteException If failed.
*/
public static void main(String[] args) throws IgniteException {
Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
IgniteCache keywordCache =
ignite.getOrCreateCache("keyword");
for(int i=0;i<1000;i++){
int mega = new Random().nextInt(3) + 1;
keywordCache.put(UUID.randomUUID().toString(), new byte[mega * 1024
* 1024]);
System.out.println("current:"+i);
}
}
}
{code}
data region configuration:
{code:java}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
