[jira] [Assigned] (IGNITE-11338) Web Console: Current cache "jump" after edit on "Basic configuration" screen
[ https://issues.apache.org/jira/browse/IGNITE-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov reassigned IGNITE-11338: - Assignee: Alexey Kuznetsov (was: Ilya Borisov) > Web Console: Current cache "jump" after edit on "Basic configuration" screen > > > Key: IGNITE-11338 > URL: https://issues.apache.org/jira/browse/IGNITE-11338 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 1.55h > Remaining Estimate: 0h > > Steps to reproduce: > # Create new cluster. > # Add 3 caches (just click 3 times on "Add new cache") > # Click on first cache with name "Cache" and add a letter "x" to the end of > its name. > # It will "jump" to the end of list. > # And current "editable" item become cache with name "Cache1" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11351) Basic "Starting Ignite inside an OSGi container" doesn't work
Xander Uiterlinden created IGNITE-11351: --- Summary: Basic "Starting Ignite inside an OSGi container" doesn't work Key: IGNITE-11351 URL: https://issues.apache.org/jira/browse/IGNITE-11351 Project: Ignite Issue Type: Bug Components: osgi Affects Versions: 2.7 Environment: Apache Felix, JDK 1.8 Reporter: Xander Uiterlinden Attachments: ignite-osgi-patch.diff When running the example from [https://apacheignite.readme.io/v1.5/docs/osgi-starting-inside-a-container] you're getting the following error. Failed to start Ignite via OSGi Activator [errMsg=Failed to find empty constructor for class: o.a.i.i.processors.platform.websession.PlatformDotNetSessionLockResult]class Looking at the codebase this class does indeed not have an empty constructor. When adding that, you'll be running into the next issue which is a classloader issue. Ignite needs to be started with the correct context classloader for it to start successfully. Please find the attached patch that resolves both problems. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11338) Web Console: Current cache "jump" after edit on "Basic configuration" screen
[ https://issues.apache.org/jira/browse/IGNITE-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771665#comment-16771665 ] Ilya Borisov edited comment on IGNITE-11338 at 2/19/19 7:54 AM: [~kuaw26] the issue was caused by a combination of several factors: 1. Basic configuration sorts caches by name. 2. Basic configuration cache changes are applied immediately and not on input blur. 3. component tracks items in edit by index and not id. To fix it, I updated all item operation in list-editable to use computed id instead of index. I also converted most of list-editable extra directives/components to TS in order to ensure correct list-editable controller method call signatures. What to test: 1. Reported issue should not happen, instead was (Author: klaster_1): [~kuaw26] the issue was caused by a combination of several factors: 1. Basic configuration sorts caches by name. 2. Basic configuration cache changes are applied immediately and not on input blur. 3. component tracks items in edit by index and not id. To fix it, I updated all item operation in list-editable to use computed id instead of index. I also converted most of list-editable extra directives/components to TS in order to ensure correct list-editable controller method call signatures. > Web Console: Current cache "jump" after edit on "Basic configuration" screen > > > Key: IGNITE-11338 > URL: https://issues.apache.org/jira/browse/IGNITE-11338 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Time Spent: 1h 13m > Remaining Estimate: 0h > > Steps to reproduce: > # Create new cluster. > # Add 3 caches (just click 3 times on "Add new cache") > # Click on first cache with name "Cache" and add a letter "x" to the end of > its name. > # It will "jump" to the end of list. > # And current "editable" item become cache with name "Cache1" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11338) Web Console: Current cache "jump" after edit on "Basic configuration" screen
[ https://issues.apache.org/jira/browse/IGNITE-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771665#comment-16771665 ] Ilya Borisov edited comment on IGNITE-11338 at 2/19/19 7:53 AM: [~kuaw26] the issue was caused by a combination of several factors: 1. Basic configuration sorts caches by name. 2. Basic configuration cache changes are applied immediately and not on input blur. 3. component tracks items in edit by index and not id. To fix it, I updated all item operation in list-editable to use computed id instead of index. I also converted most of list-editable extra directives/components to TS in order to ensure correct list-editable controller method call signatures. was (Author: klaster_1): [~kuaw26] the issue was caused by a combination of several factors: 1. Basic configuration sorts caches by name. 2. Basic configuration cache changes are applied immediately and not on input blur. 3. component tracks items in edit most by index and not id. To fix it, I updated all item operation in list-editable to use computed id instead of index. I also converted most of list-editable extra directives/components to TS in order to ensure correct list-editable controller method call signatures. > Web Console: Current cache "jump" after edit on "Basic configuration" screen > > > Key: IGNITE-11338 > URL: https://issues.apache.org/jira/browse/IGNITE-11338 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Time Spent: 1h 13m > Remaining Estimate: 0h > > Steps to reproduce: > # Create new cluster. > # Add 3 caches (just click 3 times on "Add new cache") > # Click on first cache with name "Cache" and add a letter "x" to the end of > its name. > # It will "jump" to the end of list. > # And current "editable" item become cache with name "Cache1" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11338) Web Console: Current cache "jump" after edit on "Basic configuration" screen
[ https://issues.apache.org/jira/browse/IGNITE-11338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771665#comment-16771665 ] Ilya Borisov commented on IGNITE-11338: --- [~kuaw26] the issue was caused by a combination of several factors: 1. Basic configuration sorts caches by name. 2. Basic configuration cache changes are applied immediately and not on input blur. 3. component tracks items in edit most by index and not id. To fix it, I updated all item operation in list-editable to use computed id instead of index. I also converted most of list-editable extra directives/components to TS in order to ensure correct list-editable controller method call signatures. > Web Console: Current cache "jump" after edit on "Basic configuration" screen > > > Key: IGNITE-11338 > URL: https://issues.apache.org/jira/browse/IGNITE-11338 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Borisov >Priority: Major > Time Spent: 1h 13m > Remaining Estimate: 0h > > Steps to reproduce: > # Create new cluster. > # Add 3 caches (just click 3 times on "Add new cache") > # Click on first cache with name "Cache" and add a letter "x" to the end of > its name. > # It will "jump" to the end of list. > # And current "editable" item become cache with name "Cache1" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11350) doInParallel interruption is not properly handled in ExchangeFuture.
Pavel Voronkin created IGNITE-11350: --- Summary: doInParallel interruption is not properly handled in ExchangeFuture. Key: IGNITE-11350 URL: https://issues.apache.org/jira/browse/IGNITE-11350 Project: Ignite Issue Type: Bug Reporter: Pavel Voronkin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11332) Add jmx ability to exclude node from topology.
[
https://issues.apache.org/jira/browse/IGNITE-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771640#comment-16771640
]
Vladislav Pyatkov commented on IGNITE-11332:
I left comments in GitHub.
Also it will be better, if you add test when you clarify behavior of excluded
nodes.
I think excluded nodes should by segmented and stopped, but who knows...
> Add jmx ability to exclude node from topology.
> --
>
> Key: IGNITE-11332
> URL: https://issues.apache.org/jira/browse/IGNITE-11332
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In very rare corner cases may occur situation that physically unreachable
> host still present in topology that may leads to hanging overall cluster
> operations.
> Add ability to exclude with specific warning.
> {code:java}
> /**
> * Exclude node from cluster.
> *
> * @param nodeId Node id.
> */
> @MXBeanDescription("Exclude node from cluster.")
> public void excludeNode(UUID nodeId);{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11350) doInParallel interruption is not properly handled in ExchangeFuture.
[ https://issues.apache.org/jira/browse/IGNITE-11350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11350: Attachment: GridGain_Tests_8.4_Java_8_Binary_Objects_DR_7222.log > doInParallel interruption is not properly handled in ExchangeFuture. > > > Key: IGNITE-11350 > URL: https://issues.apache.org/jira/browse/IGNITE-11350 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > > While sys pool tasks interrupted on stop > detectLostPartitions() and resetLostPartitions() might endup > IgniteCheckedInterruptedException thrown which will cause node hang on stop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11350) doInParallel interruption is not properly handled in ExchangeFuture.
[ https://issues.apache.org/jira/browse/IGNITE-11350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11350: Description: While sys pool tasks interrupted on stop detectLostPartitions() and resetLostPartitions() might endup IgniteCheckedInterruptedException thrown which will cause node hang on stop. > doInParallel interruption is not properly handled in ExchangeFuture. > > > Key: IGNITE-11350 > URL: https://issues.apache.org/jira/browse/IGNITE-11350 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > > While sys pool tasks interrupted on stop > detectLostPartitions() and resetLostPartitions() might endup > IgniteCheckedInterruptedException thrown which will cause node hang on stop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11350) doInParallel interruption is not properly handled in ExchangeFuture.
[ https://issues.apache.org/jira/browse/IGNITE-11350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Voronkin updated IGNITE-11350: Attachment: (was: GridGain_Tests_8.4_Java_8_Binary_Objects_DR_7222.log) > doInParallel interruption is not properly handled in ExchangeFuture. > > > Key: IGNITE-11350 > URL: https://issues.apache.org/jira/browse/IGNITE-11350 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > > While sys pool tasks interrupted on stop > detectLostPartitions() and resetLostPartitions() might endup > IgniteCheckedInterruptedException thrown which will cause node hang on stop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771616#comment-16771616
]
Pavel Tupitsyn commented on IGNITE-11233:
-
[~dpavlov] TC seemed ok on the branch, so yes, I think it's ready.
> Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite
> for some configurations, Compilation error
>
>
> Key: IGNITE-11233
> URL: https://issues.apache.org/jira/browse/IGNITE-11233
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc=ignite-11213=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy=ignite-11213=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd=ignite-11213=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11=ignite-11213=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=3007897&_focus=904
> {noformat}
> [21:28:31][Step 1/1] [INFO] Compiling 9 source files to
> /data/teamcity/work/9198da4c51c3e112/modules/tools/target/classes
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java
> uses or overrides a deprecated API that is marked for removal.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
> Recompile with -Xlint:removal for details.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java
> uses unchecked or unsafe operations.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
> Recompile with -Xlint:unchecked for details.
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR] COMPILATION ERROR :
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[21,29]
> package com.sun.tools.doclets does not exist
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[30,42]
> cannot find symbol
> [21:28:32][Step 1/1] symbol: class Taglet
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[37,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[44,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[51,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[58,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[65,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[72,5]
> method does not override or implement a method from a supertype
>
[jira] [Commented] (IGNITE-11245) Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT parameter.
[
https://issues.apache.org/jira/browse/IGNITE-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771554#comment-16771554
]
Ignite TC Bot commented on IGNITE-11245:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3118566buildTypeId=IgniteTests24Java8_RunAll]
> Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT parameter.
> ---
>
> Key: IGNITE-11245
> URL: https://issues.apache.org/jira/browse/IGNITE-11245
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Andrey Kalinin
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Replace unused IGNITE_BINARY_META_UPDATE_TIMEOUT with
> IGNITE_WAIT_SCHEMA_UPDATE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10476) Merge similar tests.
[
https://issues.apache.org/jira/browse/IGNITE-10476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771555#comment-16771555
]
Ignite TC Bot commented on IGNITE-10476:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3118201buildTypeId=IgniteTests24Java8_RunAll]
> Merge similar tests.
>
>
> Key: IGNITE-10476
> URL: https://issues.apache.org/jira/browse/IGNITE-10476
> Project: Ignite
> Issue Type: Test
>Reporter: Andrew Mashenkov
>Assignee: Andrey Kalinin
>Priority: Minor
> Labels: MakeTeamcityGreenAgain
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CacheNamesSelfTest and CacheNamesWithSpecialCharactersTest looks similar and
> can be merged.
> We already have test suite these tests are related to, so we can merge them
> into GridCacheConfigurationValidationSelfTest.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6789) Web Console: Rework sorting of caches list on Queries screen to ignore case
[ https://issues.apache.org/jira/browse/IGNITE-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-6789: - Component/s: wizards > Web Console: Rework sorting of caches list on Queries screen to ignore case > --- > > Key: IGNITE-6789 > URL: https://issues.apache.org/jira/browse/IGNITE-6789 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.4 > > > Currently caches are sorted case sensitive that is not very useful -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11277) Use maven plugin as default code style checker for project
[
https://issues.apache.org/jira/browse/IGNITE-11277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771440#comment-16771440
]
Ignite TC Bot commented on IGNITE-11277:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3116888buildTypeId=IgniteTests24Java8_RunAll]
> Use maven plugin as default code style checker for project
> --
>
> Key: IGNITE-11277
> URL: https://issues.apache.org/jira/browse/IGNITE-11277
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: inspections
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, {{[Inspections] Core suite}} [1] on TC doesn't work well enough.
> The suite has a {{FAILED}} status for more than 2 months due to some issues
> on TeamCity application [2]. It confuses most of the members of the Apache
> Ignite community.
> Moreover, this suite is no longer checks configured rules. For instance, in
> the master branch, 11 {{Unused imports}} can be found (e.g. for
> {{IgniteCachePutAllRestartTest}
> [3]).
> I think the maven-checkstyle-plugin should be used as the default code style
> checker.
> _Advantages:_
> * An IDE agnostic way for code checks
> * Can be used with different CI and build tools
> * Executable from the command line
> * Single configuration
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> [2] https://youtrack.jetbrains.com/issue/TW-58504
> [3]
> https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCachePutAllRestartTest.java#L29
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10928) After huge load on cluster and restart with walCompactionEnabled=True errors on log
[
https://issues.apache.org/jira/browse/IGNITE-10928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771390#comment-16771390
]
Ignite TC Bot commented on IGNITE-10928:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3117243buildTypeId=IgniteTests24Java8_RunAll]
> After huge load on cluster and restart with walCompactionEnabled=True errors
> on log
> ---
>
> Key: IGNITE-10928
> URL: https://issues.apache.org/jira/browse/IGNITE-10928
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.5
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
> {code}
> {code:java}
> [15:30:56,809][INFO][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28310114 size: -1, ptr=FileWALPointer [idx=35, fileOff=28310114,
> len=0]
> [15:30:56,811][INFO][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28303753 size: -1, ptr=FileWALPointer [idx=36, fileOff=28303753,
> len=0]
> [15:30:56,811][SEVERE][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Compression of WAL segment [idx=35] was skipped due to unexpected error
> class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
> position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:292)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:258)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:154)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:123)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:52)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2039)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:1974)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:1950)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:394)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:235)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:243)
> ... 10 more
> Caused by: java.nio.channels.ClosedByInterruptException
> at
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
> at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:164)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:58)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileIODecorator.read(FileIODecorator.java:51)
> at
>
[jira] [Commented] (IGNITE-10928) After huge load on cluster and restart with walCompactionEnabled=True errors on log
[
https://issues.apache.org/jira/browse/IGNITE-10928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771379#comment-16771379
]
Ignite TC Bot commented on IGNITE-10928:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3117203]]
* IgniteCacheDataStructuresSelfTestSuite:
GridCacheReplicatedDataStructuresFailoverSelfTest.testSemaphoreMultipleTopologyChangeNonFailoverSafe
- 0,0% fails in last 430 master runs.
* IgniteCacheDataStructuresSelfTestSuite:
GridCacheReplicatedDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
- 0,0% fails in last 430 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3117243buildTypeId=IgniteTests24Java8_RunAll]
> After huge load on cluster and restart with walCompactionEnabled=True errors
> on log
> ---
>
> Key: IGNITE-10928
> URL: https://issues.apache.org/jira/browse/IGNITE-10928
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.5
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
> {code}
> {code:java}
> [15:30:56,809][INFO][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28310114 size: -1, ptr=FileWALPointer [idx=35, fileOff=28310114,
> len=0]
> [15:30:56,811][INFO][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28303753 size: -1, ptr=FileWALPointer [idx=36, fileOff=28303753,
> len=0]
> [15:30:56,811][SEVERE][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Compression of WAL segment [idx=35] was skipped due to unexpected error
> class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
> position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:292)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:258)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:154)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:123)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:52)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2039)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:1974)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:1950)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:394)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:235)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:243)
> ... 10 more
> Caused by: java.nio.channels.ClosedByInterruptException
> at
>
[jira] [Commented] (IGNITE-10414) IF NOT EXISTS in CREATE TABLE doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771347#comment-16771347
]
Ignite TC Bot commented on IGNITE-10414:
{panel:title=- Run :: SQL: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3117373]]
* exe: ContinuousQueryAbstractTest.TestTimeout - 0,0% fails in last 603 master
runs.
{panel}
[TeamCity *- Run :: SQL*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3117375buildTypeId=IgniteTests24Java8_RunAllSql]
> IF NOT EXISTS in CREATE TABLE doesn't work
> --
>
> Key: IGNITE-10414
> URL: https://issues.apache.org/jira/browse/IGNITE-10414
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.6, 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reproducer:
>
> {code:java}
>Ignite ignite = Ignition.start();
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> {code}
> Error:
> {code:java}
> (err) DDL operation failureSchemaOperationException [code=3, msg=Table
> already exists: CITY]
> at
> org.apache.ignite.internal.processors.query.QueryUtils.checkQueryEntityConflicts(QueryUtils.java:1214)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:351)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1981)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1896)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2174)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2169)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2677)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$0(GridQueryProcessor.java:2183)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2203)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2164)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2125)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:685)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Exception in thread "main" javax.cache.CacheException: Table already exists:
> CITY
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:697)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Table already
> exists: CITY
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:642)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:503)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1981)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1896)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2174)
> at
>
[jira] [Commented] (IGNITE-955) Local listener in continuous queries should not be mandatory
[
https://issues.apache.org/jira/browse/IGNITE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771343#comment-16771343
]
Ignite TC Bot commented on IGNITE-955:
--
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3116181buildTypeId=IgniteTests24Java8_RunAll]
> Local listener in continuous queries should not be mandatory
>
>
> Key: IGNITE-955
> URL: https://issues.apache.org/jira/browse/IGNITE-955
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
>Affects Versions: sprint-4
>Reporter: Valentin Kulichenko
>Assignee: PetrovMikhail
>Priority: Major
> Labels: Usability
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to support the use case when remote filter is needed, but local
> listener is not (filter always returns {{false}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10873) CorruptedTreeException during simultaneous cache put operations
[
https://issues.apache.org/jira/browse/IGNITE-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771326#comment-16771326
]
Ivan Rakov commented on IGNITE-10873:
-
Seems like the problem was in GridQueryProcessor busy lock. Query processor
stops before cache processor, and complex operation (that comprises both index
and data store updates) may be stopped in the middle due to busy lock
acquisition failure.
I can't reproduce the issue on PR branch regardless of whether SQL onheap cache
is enabled.
> CorruptedTreeException during simultaneous cache put operations
> ---
>
> Key: IGNITE-10873
> URL: https://issues.apache.org/jira/browse/IGNITE-10873
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Affects Versions: 2.7
>Reporter: Pavel Vinokurov
>Assignee: Ivan Rakov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> [2019-01-09 20:47:04,376][ERROR][pool-9-thread-9][GridDhtAtomicCache]
> Unexpected exception during cache update
> org.h2.message.DbException: General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@780acfb4[ key: .. ][ GTEST, null, 254, null,
> null, null, null, 0, null, null, null, null, null, null, null, 0, 0, 0, null,
> 0, 0, 0, 0, 0, 0, 0, null, 0, 0, null, 0, null, 0, null, 0, null, null, null,
> 0, 0, 0, 0, 0, 0, null, null, null, null, null, null, null, 0.0, 0, 0.0, 0,
> 0.0, 0, null, 0, 0, 0, 0, null, null, null, null, null, null, null, null,
> null, null, null, null, null, null, null, null ]" [5-197]
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:307)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:302)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:546)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:479)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:768)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1905)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:404)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2633)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1646)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1621)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1935)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:428)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2295)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2494)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1951)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1780)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
> at
>
[jira] [Created] (IGNITE-11349) MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1
Roman Kondakov created IGNITE-11349: --- Summary: MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1 Key: IGNITE-11349 URL: https://issues.apache.org/jira/browse/IGNITE-11349 Project: Ignite Issue Type: Bug Components: mvcc, sql Reporter: Roman Kondakov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10873) CorruptedTreeException during simultaneous cache put operations
[
https://issues.apache.org/jira/browse/IGNITE-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov updated IGNITE-10873:
Fix Version/s: 2.8
> CorruptedTreeException during simultaneous cache put operations
> ---
>
> Key: IGNITE-10873
> URL: https://issues.apache.org/jira/browse/IGNITE-10873
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Affects Versions: 2.7
>Reporter: Pavel Vinokurov
>Assignee: Ivan Rakov
>Priority: Critical
> Fix For: 2.8
>
>
> {code}
> [2019-01-09 20:47:04,376][ERROR][pool-9-thread-9][GridDhtAtomicCache]
> Unexpected exception during cache update
> org.h2.message.DbException: General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@780acfb4[ key: .. ][ GTEST, null, 254, null,
> null, null, null, 0, null, null, null, null, null, null, null, 0, 0, 0, null,
> 0, 0, 0, 0, 0, 0, 0, null, 0, 0, null, 0, null, 0, null, 0, null, null, null,
> 0, 0, 0, 0, 0, 0, null, null, null, null, null, null, null, 0.0, 0, 0.0, 0,
> 0.0, 0, null, 0, 0, 0, 0, null, null, null, null, null, null, null, null,
> null, null, null, null, null, null, null, null ]" [5-197]
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:307)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:302)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:546)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:479)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:768)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1905)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:404)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2633)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1646)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1621)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1935)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:428)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2295)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2494)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1951)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1780)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:611)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2449)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2426)
> at
>
[jira] [Commented] (IGNITE-10720) Decrease time to save metadata during checkpoint
[
https://issues.apache.org/jira/browse/IGNITE-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771293#comment-16771293
]
Ignite TC Bot commented on IGNITE-10720:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3115774buildTypeId=IgniteTests24Java8_RunAll]
> Decrease time to save metadata during checkpoint
>
>
> Key: IGNITE-10720
> URL: https://issues.apache.org/jira/browse/IGNITE-10720
> Project: Ignite
> Issue Type: Improvement
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Looks like it's not neccessery save all metadata(like free list) under write
> checkpoint lock because sometimes it's too long.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771260#comment-16771260
]
Dmitriy Pavlov commented on IGNITE-11233:
-
[~ptupitsyn] I've created PR from your branch
https://github.com/apache/ignite/pull/6127 to easily see changes. Is it ready
to be merged?
> Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite
> for some configurations, Compilation error
>
>
> Key: IGNITE-11233
> URL: https://issues.apache.org/jira/browse/IGNITE-11233
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc=ignite-11213=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy=ignite-11213=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd=ignite-11213=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11=ignite-11213=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=3007897&_focus=904
> {noformat}
> [21:28:31][Step 1/1] [INFO] Compiling 9 source files to
> /data/teamcity/work/9198da4c51c3e112/modules/tools/target/classes
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java
> uses or overrides a deprecated API that is marked for removal.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
> Recompile with -Xlint:removal for details.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
>
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java
> uses unchecked or unsafe operations.
> [21:28:32][Step 1/1] [INFO]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
> Recompile with -Xlint:unchecked for details.
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR] COMPILATION ERROR :
> [21:28:32][Step 1/1] [INFO]
> -
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[21,29]
> package com.sun.tools.doclets does not exist
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[30,42]
> cannot find symbol
> [21:28:32][Step 1/1] symbol: class Taglet
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[37,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[44,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[51,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[58,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[65,5]
> method does not override or implement a method from a supertype
> [21:28:32][Step 1/1] [ERROR]
> /data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[72,5]
> method
[jira] [Updated] (IGNITE-10928) After huge load on cluster and restart with walCompactionEnabled=True errors on log
[
https://issues.apache.org/jira/browse/IGNITE-10928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov updated IGNITE-10928:
Ignite Flags: (was: Docs Required)
> After huge load on cluster and restart with walCompactionEnabled=True errors
> on log
> ---
>
> Key: IGNITE-10928
> URL: https://issues.apache.org/jira/browse/IGNITE-10928
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.5
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
> {code}
> {code:java}
> [15:30:56,809][INFO][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28310114 size: -1, ptr=FileWALPointer [idx=35, fileOff=28310114,
> len=0]
> [15:30:56,811][INFO][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28303753 size: -1, ptr=FileWALPointer [idx=36, fileOff=28303753,
> len=0]
> [15:30:56,811][SEVERE][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Compression of WAL segment [idx=35] was skipped due to unexpected error
> class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
> position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:292)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:258)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:154)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:123)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:52)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2039)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:1974)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:1950)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:394)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:235)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:243)
> ... 10 more
> Caused by: java.nio.channels.ClosedByInterruptException
> at
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
> at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:164)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:58)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileIODecorator.read(FileIODecorator.java:51)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.ensure(SimpleFileInput.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:89)
> at
>
[jira] [Commented] (IGNITE-10928) After huge load on cluster and restart with walCompactionEnabled=True errors on log
[
https://issues.apache.org/jira/browse/IGNITE-10928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771226#comment-16771226
]
Sergey Antonov commented on IGNITE-10928:
-
Full stacktrace
{code:java}
[2019-02-18
18:33:31,615][ERROR][wal-file-compressor-%wal.WalCompactionEnabledAfterRestartTest%-1-#98%wal.WalCompactionEnabledAfterRestartTest%][FileWriteAheadLogManager]
Compression of WAL segment [idx=1] was skipped due to unexpected error
class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
position: 5242830 size: -1
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:305)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:269)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:158)
at
org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:127)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:53)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2122)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:2047)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:2023)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
record at position: 5242830 size: -1
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:393)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:236)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:254)
... 10 more
Caused by: java.nio.channels.ClosedByInterruptException
at
java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:164)
at
org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:96)
at
org.apache.ignite.internal.processors.cache.persistence.file.FileIODecorator.read(FileIODecorator.java:66)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.ensure(SimpleFileInput.java:119)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:88)
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.readFully(FileInput.java:151)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer$2.readWithHeaders(RecordV2Serializer.java:150)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:372)
... 12 more
Suppressed: class
org.apache.ignite.internal.processors.cache.persistence.wal.crc.IgniteDataIntegrityViolationException:
val: -204434216 writtenCrc: 693900246
at
org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.close(FileInput.java:105)
at
org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:379)
... 12 more
{code}
> After huge load on cluster and restart with walCompactionEnabled=True errors
> on log
> ---
>
> Key: IGNITE-10928
> URL: https://issues.apache.org/jira/browse/IGNITE-10928
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.5
>Reporter: ARomantsov
>Assignee: Sergey
[jira] [Commented] (IGNITE-10414) IF NOT EXISTS in CREATE TABLE doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771211#comment-16771211
]
Ignite TC Bot commented on IGNITE-10414:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3115561]]
* ZookeeperDiscoverySpiTestSuite1:
ZookeeperClientTest.testCreateAllRequestOverflow - 0,0% fails in last 398
master runs.
{color:#d04437}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3115615]]
* IgniteBinaryCacheQueryTestSuite: SqlSystemViewsSelfTest.testTablesView - 0,0%
fails in last 376 master runs.
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3115542]]
* IgniteClientTestSuite:
ClientTcpSslDirectMultiNodeSelfTest.testTopologyListener - 0,0% fails in last
432 master runs.
{color:#d04437}Spring{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3115550]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3115639buildTypeId=IgniteTests24Java8_RunAll]
> IF NOT EXISTS in CREATE TABLE doesn't work
> --
>
> Key: IGNITE-10414
> URL: https://issues.apache.org/jira/browse/IGNITE-10414
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.6, 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reproducer:
>
> {code:java}
>Ignite ignite = Ignition.start();
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> {code}
> Error:
> {code:java}
> (err) DDL operation failureSchemaOperationException [code=3, msg=Table
> already exists: CITY]
> at
> org.apache.ignite.internal.processors.query.QueryUtils.checkQueryEntityConflicts(QueryUtils.java:1214)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:351)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1981)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1896)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2174)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2169)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2677)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$0(GridQueryProcessor.java:2183)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2203)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2164)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2125)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:685)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Exception in thread "main" javax.cache.CacheException: Table already exists:
> CITY
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:697)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Table already
> exists: CITY
> at
>
[jira] [Comment Edited] (IGNITE-11277) Use maven plugin as default code style checker for project
[
https://issues.apache.org/jira/browse/IGNITE-11277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771200#comment-16771200
]
Maxim Muzafarov edited comment on IGNITE-11277 at 2/18/19 4:35 PM:
---
Сhanges that have been made:
# Configured {{maven-checkstyle-plugin}} for all the Apache Ignite project
# {{checkstyle}} profile configured and is active by default
# These checkstyle rules are configured
** {{FileTabCharacter}} (an {{ProblematicWhitespace}} analogue inspection)
** {{UnusedImports}} (an {{UnusedImport}} analogue inspection)
** {{ModifierOrder}} (a {{MissortedModifiers}} analogue inspection)
# These inspections rules don't have direct analogue or working not the same
** {{SizeReplaceableByIsEmpty}} doesn't have a direct analogue of checkstyle
modules
** {{MissingOverrideAnnotation}} inspection has a
[{{MissingOverride}}|http://checkstyle.sourceforge.net/config_annotation.html#MissingOverride]
analogue module for the checkstyle plugin. It is working not the same way.
Must be implemented in the separate ticket
** {{RedundantSuppression}} inspection doesn't have the direct analogue of
checkstyle module
# All additional files have been fixed (e.g. all unused imports removed) to
make project compile.
was (Author: mmuzaf):
Сhanges that have been made:
# Configured {{maven-checkstyle-plugin}} for all the Apache Ignite project
# {{checkstyle}} profile configured and is active by default
# These checkstyle rules are configured
** {{FileTabCharacter}} (an {{ProblematicWhitespace}} analogue inspection)
** {{UnusedImports}} (an {{UnusedImport}} analogue inspection)
** {{ModifierOrder}} (a {{MissortedModifiers}} analogue inspection)
# These inspections rules don't have direct analogue or working not the same
** {{SizeReplaceableByIsEmpty}} doesn't have a direct analogue of checkstyle
modules
** {{MissingOverrideAnnotation}} inspection has a
[{{MissingOverride}}|http://checkstyle.sourceforge.net/config_annotation.html#MissingOverride]
analogue module for the checkstyle plugin. It is working not the same way.
Must be implemented in the separate ticket
** {{RedundantSuppression}} inspection doesn't have the direct analogue of
checkstyle module
# All additional files are fixed (e.g. unused imports removed) to make project
compile.
> Use maven plugin as default code style checker for project
> --
>
> Key: IGNITE-11277
> URL: https://issues.apache.org/jira/browse/IGNITE-11277
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: inspections
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, {{[Inspections] Core suite}} [1] on TC doesn't work well enough.
> The suite has a {{FAILED}} status for more than 2 months due to some issues
> on TeamCity application [2]. It confuses most of the members of the Apache
> Ignite community.
> Moreover, this suite is no longer checks configured rules. For instance, in
> the master branch, 11 {{Unused imports}} can be found (e.g. for
> {{IgniteCachePutAllRestartTest}
> [3]).
> I think the maven-checkstyle-plugin should be used as the default code style
> checker.
> _Advantages:_
> * An IDE agnostic way for code checks
> * Can be used with different CI and build tools
> * Executable from the command line
> * Single configuration
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> [2] https://youtrack.jetbrains.com/issue/TW-58504
> [3]
> https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCachePutAllRestartTest.java#L29
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11277) Use maven plugin as default code style checker for project
[
https://issues.apache.org/jira/browse/IGNITE-11277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771200#comment-16771200
]
Maxim Muzafarov commented on IGNITE-11277:
--
Сhanges that have been made:
# Configured {{maven-checkstyle-plugin}} for all the Apache Ignite project
# {{checkstyle}} profile configured and is active by default
# These checkstyle rules are configured
** {{FileTabCharacter}} (an {{ProblematicWhitespace}} analogue inspection)
** {{UnusedImports}} (an {{UnusedImport}} analogue inspection)
** {{ModifierOrder}} (a {{MissortedModifiers}} analogue inspection)
# These inspections rules don't have direct analogue or working not the same
** {{SizeReplaceableByIsEmpty}} doesn't have a direct analogue of checkstyle
modules
** {{MissingOverrideAnnotation}} inspection has a
[{{MissingOverride}}|http://checkstyle.sourceforge.net/config_annotation.html#MissingOverride]
analogue module for the checkstyle plugin. It is working not the same way.
Must be implemented in the separate ticket
** {{RedundantSuppression}} inspection doesn't have the direct analogue of
checkstyle module
# All additional files are fixed (e.g. unused imports removed) to make project
compile.
> Use maven plugin as default code style checker for project
> --
>
> Key: IGNITE-11277
> URL: https://issues.apache.org/jira/browse/IGNITE-11277
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: inspections
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, {{[Inspections] Core suite}} [1] on TC doesn't work well enough.
> The suite has a {{FAILED}} status for more than 2 months due to some issues
> on TeamCity application [2]. It confuses most of the members of the Apache
> Ignite community.
> Moreover, this suite is no longer checks configured rules. For instance, in
> the master branch, 11 {{Unused imports}} can be found (e.g. for
> {{IgniteCachePutAllRestartTest}
> [3]).
> I think the maven-checkstyle-plugin should be used as the default code style
> checker.
> _Advantages:_
> * An IDE agnostic way for code checks
> * Can be used with different CI and build tools
> * Executable from the command line
> * Single configuration
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
> [2] https://youtrack.jetbrains.com/issue/TW-58504
> [3]
> https://github.com/apache/ignite/blob/master/modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteCachePutAllRestartTest.java#L29
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10928) After huge load on cluster and restart with walCompactionEnabled=True errors on log
[
https://issues.apache.org/jira/browse/IGNITE-10928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771169#comment-16771169
]
Sergey Antonov commented on IGNITE-10928:
-
The errors prints on recovery stage. After cluster activation all wal archives
were correctly compacted.
> After huge load on cluster and restart with walCompactionEnabled=True errors
> on log
> ---
>
> Key: IGNITE-10928
> URL: https://issues.apache.org/jira/browse/IGNITE-10928
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.5
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
>
> {code:java}
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
> {code}
> {code:java}
> [15:30:56,809][INFO][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28310114 size: -1, ptr=FileWALPointer [idx=35, fileOff=28310114,
> len=0]
> [15:30:56,811][INFO][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28303753 size: -1, ptr=FileWALPointer [idx=36, fileOff=28303753,
> len=0]
> [15:30:56,811][SEVERE][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Compression of WAL segment [idx=35] was skipped due to unexpected error
> class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
> position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:292)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:258)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:154)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:123)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:52)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2039)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:1974)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:1950)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:394)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:235)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:243)
> ... 10 more
> Caused by: java.nio.channels.ClosedByInterruptException
> at
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
> at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:164)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:58)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileIODecorator.read(FileIODecorator.java:51)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.ensure(SimpleFileInput.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:89)
> at
>
[jira] [Updated] (IGNITE-11348) Ping node procedure may fail when another node leaves the cluster
[ https://issues.apache.org/jira/browse/IGNITE-11348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-11348: - Description: Additional pinging of node on join implemented in IGNITE-5569 may incorrectly fail leading to shutting down joining node. The reason for this is that if another node from the same host bound to the same discovery port as joining node has left the cluster right before joining node, socket used for pinging gets closed. This leads to the situation when pinging node considers joining node as "unreachable" and fails it with JOIN_IMPOSSIBLE error code. Workaround: simply start again node failed on join. was: Additional pinging of node on join implemented in IGNITE-5569 may incorrectly fail leading to shutting down joining node. The reason for this is that if another node from the same host bound to the same discovery port as joining node has left the cluster right before joining node, socket used for pinging gets closed. This leads to the situation when pinging node considers joining node as "unreachable" and fails it with JOIN_IMPOSSIBLE error code. Workaround: just to start again node failed on join. > Ping node procedure may fail when another node leaves the cluster > - > > Key: IGNITE-11348 > URL: https://issues.apache.org/jira/browse/IGNITE-11348 > Project: Ignite > Issue Type: Bug >Reporter: Sergey Chugunov >Assignee: Sergey Chugunov >Priority: Critical > Fix For: 2.8 > > > Additional pinging of node on join implemented in IGNITE-5569 may incorrectly > fail leading to shutting down joining node. > The reason for this is that if another node from the same host bound to the > same discovery port as joining node has left the cluster right before joining > node, socket used for pinging gets closed. > This leads to the situation when pinging node considers joining node as > "unreachable" and fails it with JOIN_IMPOSSIBLE error code. > Workaround: simply start again node failed on join. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11348) Ping node procedure may fail when another node leaves the cluster
Sergey Chugunov created IGNITE-11348: Summary: Ping node procedure may fail when another node leaves the cluster Key: IGNITE-11348 URL: https://issues.apache.org/jira/browse/IGNITE-11348 Project: Ignite Issue Type: Bug Reporter: Sergey Chugunov Assignee: Sergey Chugunov Fix For: 2.8 Additional pinging of node on join implemented in IGNITE-5569 may incorrectly fail leading to shutting down joining node. The reason for this is that if another node from the same host bound to the same discovery port as joining node has left the cluster right before joining node, socket used for pinging gets closed. This leads to the situation when pinging node considers joining node as "unreachable" and fails it with JOIN_IMPOSSIBLE error code. Workaround: just to start again node failed on join. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7664) SQL: throw sane exception on unsupported SQL statements
[
https://issues.apache.org/jira/browse/IGNITE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771156#comment-16771156
]
Taras Ledkov edited comment on IGNITE-7664 at 2/18/19 3:17 PM:
---
Should we disable {{SHOW SCHEMAS / TABLES / COLUMNS FROM ... }} statements?
was (Author: tledkov-gridgain):
Should we disable {{SHOW SCHEMAS | TABLES | COLUMNS FROM ... }} statements?
> SQL: throw sane exception on unsupported SQL statements
> ---
>
> Key: IGNITE-7664
> URL: https://issues.apache.org/jira/browse/IGNITE-7664
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Paschenko
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql-stability
>
> Inspired by this SO issue:
> [https://stackoverflow.com/questions/48708238/ignite-database-create-schema-assertionerror]
> We should handle unsupported stuff more gracefully both in core code and
> drivers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11273) IgniteCassandraStoreTestSuite failed under Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11273:
Ignite Flags: (was: Docs Required)
> IgniteCassandraStoreTestSuite failed under Java 11
> --
>
> Key: IGNITE-11273
> URL: https://issues.apache.org/jira/browse/IGNITE-11273
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> https://ci.ignite.apache.org/viewLog.html?buildId=3027678=IgniteTests24Java8_CassandraStore
> store.IgniteCassandraStoreTestSuite
> {noformat}
> java.lang.RuntimeException: Failed to start embedded Cassandra instance
> at
> org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:59)
> Caused by: java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
> Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length
> 5
> at
> org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7664) SQL: throw sane exception on unsupported SQL statements
[
https://issues.apache.org/jira/browse/IGNITE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771156#comment-16771156
]
Taras Ledkov edited comment on IGNITE-7664 at 2/18/19 3:17 PM:
---
Should we disable {{SHOW SCHEMAS | TABLES | COLUMNS FROM}} ... statements?
was (Author: tledkov-gridgain):
Should we disable {{SHOW SCHEMAS / TABLES / COLUMNS FROM ... }} statements?
> SQL: throw sane exception on unsupported SQL statements
> ---
>
> Key: IGNITE-7664
> URL: https://issues.apache.org/jira/browse/IGNITE-7664
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Paschenko
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql-stability
>
> Inspired by this SO issue:
> [https://stackoverflow.com/questions/48708238/ignite-database-create-schema-assertionerror]
> We should handle unsupported stuff more gracefully both in core code and
> drivers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7664) SQL: throw sane exception on unsupported SQL statements
[
https://issues.apache.org/jira/browse/IGNITE-7664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771156#comment-16771156
]
Taras Ledkov commented on IGNITE-7664:
--
Should we disable {{SHOW SCHEMAS | TABLES | COLUMNS FROM ... }} statements?
> SQL: throw sane exception on unsupported SQL statements
> ---
>
> Key: IGNITE-7664
> URL: https://issues.apache.org/jira/browse/IGNITE-7664
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Reporter: Alexander Paschenko
>Assignee: Taras Ledkov
>Priority: Major
> Labels: sql-stability
>
> Inspired by this SO issue:
> [https://stackoverflow.com/questions/48708238/ignite-database-create-schema-assertionerror]
> We should handle unsupported stuff more gracefully both in core code and
> drivers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11347) DistributedMetaStoragePersistentTest.testUnstableTopology is flaky
Ivan Bessonov created IGNITE-11347: -- Summary: DistributedMetaStoragePersistentTest.testUnstableTopology is flaky Key: IGNITE-11347 URL: https://issues.apache.org/jira/browse/IGNITE-11347 Project: Ignite Issue Type: Test Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 2.8 https://ci.ignite.apache.org/project.html?tab=testDetails=IgniteTests24Java8=-976745117458855384=1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8571) Baseline auto-adjust feature
[ https://issues.apache.org/jira/browse/IGNITE-8571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771149#comment-16771149 ] Anton Kalashnikov commented on IGNITE-8571: --- [~ibessonov], thanks for notes I have fixed it. > Baseline auto-adjust feature > > > Key: IGNITE-8571 > URL: https://issues.apache.org/jira/browse/IGNITE-8571 > Project: Ignite > Issue Type: New Feature >Reporter: Eduard Shangareev >Assignee: Anton Kalashnikov >Priority: Major > Labels: IEP-4, Phase-2 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Now we have only one way to change BLAT - manually update it via console.sh > or API. > We need to add the possibility to change it automatically. Adjust to current > topology. > So, I propose 2 new distributed parameters which would be responsible to tune > this feature. > 1. Flag autoAdjustEnabled - true/false. Easy. Manual baseline control or auto > adjusting baseline. > 2. autoAdjustTimeout - time which we would wait after the actual topology > change. But it would be reset if new discovery event happened. (node > join/exit). > We need to change API next way: > org.apache.ignite.IgniteCluster: > * isBaselineAutoAdjustEnabled() > * setBaselineAutoAdjustEnabled(boolean enabled); > * setBaselineAutoAdjustTimeout(long timeoutInMs); > Also, we need to ensure that all nodes would have the same > parameters(distributed parameters). > And we should be able to survive coordinator left during parameters changes. > When autoAdjustEnabled is true we should be block ability to manual baseline > change. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11243) Not working control.sh / control.bat in master NPE in output
[ https://issues.apache.org/jira/browse/IGNITE-11243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771132#comment-16771132 ] Vladislav Pyatkov commented on IGNITE-11243: Looks good to me. > Not working control.sh / control.bat in master NPE in output > > > Key: IGNITE-11243 > URL: https://issues.apache.org/jira/browse/IGNITE-11243 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Sergey Kosarev >Priority: Blocker > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > ./bin/control.sh --host --port --baseline > Cluster state: active > Error: java.lang.NullPointerException > control.bat --host --port --baseline > Cluster state: active > Error: java.lang.NullPointerException > Press any key to continue . . . > No info in cluster logs matched with call, look like problem in utility run > This bug was introuced by IGNITE-8894 and reproduced when new utility runs on > an old version node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11243) Not working control.sh / control.bat in master NPE in output
[
https://issues.apache.org/jira/browse/IGNITE-11243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771118#comment-16771118
]
Ignite TC Bot commented on IGNITE-11243:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3103452buildTypeId=IgniteTests24Java8_RunAll]
> Not working control.sh / control.bat in master NPE in output
>
>
> Key: IGNITE-11243
> URL: https://issues.apache.org/jira/browse/IGNITE-11243
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8
>Reporter: ARomantsov
>Assignee: Sergey Kosarev
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> ./bin/control.sh --host --port --baseline
> Cluster state: active
> Error: java.lang.NullPointerException
> control.bat --host --port --baseline
> Cluster state: active
> Error: java.lang.NullPointerException
> Press any key to continue . . .
> No info in cluster logs matched with call, look like problem in utility run
> This bug was introuced by IGNITE-8894 and reproduced when new utility runs on
> an old version node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10559) MVCC TX: Use extracted partitions to reduce target nodes for Query Update
[ https://issues.apache.org/jira/browse/IGNITE-10559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771109#comment-16771109 ] Igor Seliverstov commented on IGNITE-10559: --- [~tledkov-gridgain], looks OK, merged to master > MVCC TX: Use extracted partitions to reduce target nodes for Query Update > - > > Key: IGNITE-10559 > URL: https://issues.apache.org/jira/browse/IGNITE-10559 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Igor Seliverstov >Assignee: Taras Ledkov >Priority: Minor > Labels: iep-24 > Time Spent: 10m > Remaining Estimate: 0h > > We may avoid "query reduce" step on update queries without sorting/grouping > by simply sending them to all data nodes and executing update operation > locally. Using extracted from SQL partitions will reduce target nodes count > and save resources. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9314) MVCC TX: Datastreamer operations
[
https://issues.apache.org/jira/browse/IGNITE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-9314:
---
Description:
Need to change DataStreamer semantics.
{{allowOverwrite=false}} mode currently is inconsistent with interval
_partition counters_ update approach used by MVCC transactions.
{{allowOverwrite=true}} mode is terribly slow when using single {{cache.put}}
operations (snapshot request, tx commit on coordinator overhead). Batched mode
using {{cache.putAll}} should handle write conflicts and possible deadlocks.
Also there is a problem when {{DataStreamer}} with {{allowOverwrite == false}}
does not insert value when versions for entry exist but they all are aborted.
Proper transactional semantics should developed for such case. After that
attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
method (called during streamer processing) when all existing mvcc row versions
are aborted or last committed one is _remove_ version.
was:
Need to change DataStreamer semantics (make it transactional)
Currently clients can see DataStreamer partial writes and two subsequent
selects, which are run in scope of one transaction at load time, may return
different results.
Related thread:
[http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
Also there is a problem when {{DataStreamer}} with {{allowOverwrite == false}}
does not insert value when versions for entry exist but they all are aborted.
Proper transactional semantics should developed for such case. After that
attention should be put on Cache.size method behavior. Cache.size addressed in
https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
improperly in
{{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
method (called during streamer processing) when all existing mvcc row versions
are aborted or last committed one is _remove_ version.
> MVCC TX: Datastreamer operations
>
>
> Key: IGNITE-9314
> URL: https://issues.apache.org/jira/browse/IGNITE-9314
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.8
>
>
> Need to change DataStreamer semantics.
> {{allowOverwrite=false}} mode currently is inconsistent with interval
> _partition counters_ update approach used by MVCC transactions.
> {{allowOverwrite=true}} mode is terribly slow when using single {{cache.put}}
> operations (snapshot request, tx commit on coordinator overhead). Batched
> mode using {{cache.putAll}} should handle write conflicts and possible
> deadlocks.
> Also there is a problem when {{DataStreamer}} with {{allowOverwrite ==
> false}} does not insert value when versions for entry exist but they all are
> aborted. Proper transactional semantics should developed for such case. After
> that attention should be put on Cache.size method behavior. Cache.size
> addressed in https://issues.apache.org/jira/browse/IGNITE-8149 could be
> decremented improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
> method (called during streamer processing) when all existing mvcc row
> versions are aborted or last committed one is _remove_ version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11195) Platform C++ tests failed to find JVM for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771098#comment-16771098
]
Igor Sapego commented on IGNITE-11195:
--
[~dpavlov] I've checked the parameters tab of the run:
https://ci.ignite.apache.org/viewLog.html?buildId=2973675=IgniteTests24Java8_PlatformCWinX64Release=buildParameters_IgniteTests24Java8=ignite-11155
and I can see that JAVA_HOME set to %env.JDK_OPEN_11%, but I can not find
env.JDK_OPEN_11. It looks like this may be an actual issue.
> Platform C++ tests failed to find JVM for Java 11 build
> ---
>
> Key: IGNITE-11195
> URL: https://issues.apache.org/jira/browse/IGNITE-11195
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> 482 C++ tests failed with error
> {noformat}
> std::exception: JVM library is not found (did you set JAVA_HOME environment
> variable?)
> {noformat}
> https://ci.ignite.apache.org/viewLog.html?buildId=2973675=IgniteTests24Java8_PlatformCWinX64Release=buildResultsDiv_IgniteTests24Java8=ignite-11155
> Looks like we need somehow handle new parameters in C++ tests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9947) JDBC thin: Batch update is not performed if streaming state changed before executeBatch()
[
https://issues.apache.org/jira/browse/IGNITE-9947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771099#comment-16771099
]
Taras Ledkov commented on IGNITE-9947:
--
[~pkouznet], [~vozerov].
The test looks like invalid a bit:
after the first {{fillParamsWithPerson(pstmt, 1);}} the batch wasn't added.
If the {{pstmt.addBatch();}} is added after this line, the second call of the
{{addBatch}} throws:
{{java.sql.SQLException: Statement has non-empty batch (call executeBatch() or
clearBatch() before enabling streaming).}}
I guess this is valid behavior because STREAMING mode is Ignite-specific.
> JDBC thin: Batch update is not performed if streaming state changed before
> executeBatch()
> -
>
> Key: IGNITE-9947
> URL: https://issues.apache.org/jira/browse/IGNITE-9947
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Pavel Kuznetsov
>Assignee: Taras Ledkov
>Priority: Major
>
> Thin driver is affected.
> How to reproduce:
> 0) Create table
> 1) Create PreparedStatement "INSERT INTO TAB VALUES (?, ?)"
> 2) Set statement's args and call .addBatch()
> 3) Turn on streaming
> 4) call .executeBatch()
> 5) Turn off streaming to flush streamer.
> After that table should contain batched data, but it doesn't
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10414) IF NOT EXISTS in CREATE TABLE doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771106#comment-16771106
]
Pavel Kuznetsov edited comment on IGNITE-10414 at 2/18/19 2:01 PM:
---
[~vozerov] , I fixed schemas that became invalid with this patch.
I made the frozen test not to freeze. Let's see to the new test results.
was (Author: pkouznet):
[~vozerov] , I fixed schemas that became invalid with this patch.
I made the frozen test not to freeze.
> IF NOT EXISTS in CREATE TABLE doesn't work
> --
>
> Key: IGNITE-10414
> URL: https://issues.apache.org/jira/browse/IGNITE-10414
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.6, 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reproducer:
>
> {code:java}
>Ignite ignite = Ignition.start();
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> {code}
> Error:
> {code:java}
> (err) DDL operation failureSchemaOperationException [code=3, msg=Table
> already exists: CITY]
> at
> org.apache.ignite.internal.processors.query.QueryUtils.checkQueryEntityConflicts(QueryUtils.java:1214)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:351)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1981)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1896)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2174)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2169)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2677)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$0(GridQueryProcessor.java:2183)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2203)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2164)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2125)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:685)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Exception in thread "main" javax.cache.CacheException: Table already exists:
> CITY
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:697)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Table already
> exists: CITY
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:642)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:503)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1981)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1896)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2174)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2169)
> at
>
[jira] [Commented] (IGNITE-10414) IF NOT EXISTS in CREATE TABLE doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771106#comment-16771106
]
Pavel Kuznetsov commented on IGNITE-10414:
--
[~vozerov] , I fixed schemas that became invalid with this patch.
I made the frozen test not to freeze.
> IF NOT EXISTS in CREATE TABLE doesn't work
> --
>
> Key: IGNITE-10414
> URL: https://issues.apache.org/jira/browse/IGNITE-10414
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4, 2.6, 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Kuznetsov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Reproducer:
>
> {code:java}
>Ignite ignite = Ignition.start();
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE
> TABLE IF NOT EXISTS City(id LONG PRIMARY KEY,"
> + " name VARCHAR) WITH \"template=replicated\""));
> {code}
> Error:
> {code:java}
> (err) DDL operation failureSchemaOperationException [code=3, msg=Table
> already exists: CITY]
> at
> org.apache.ignite.internal.processors.query.QueryUtils.checkQueryEntityConflicts(QueryUtils.java:1214)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:351)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1981)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1896)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2174)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2169)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2677)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.lambda$querySqlFields$0(GridQueryProcessor.java:2183)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuerySafe(GridQueryProcessor.java:2203)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2164)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2125)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:685)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Exception in thread "main" javax.cache.CacheException: Table already exists:
> CITY
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:697)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.query(IgniteCacheProxyImpl.java:636)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.query(GatewayProtectedCacheProxy.java:388)
> at
> org.apache.ignite.examples.ExampleNodeStartup.main(ExampleNodeStartup.java:40)
> Caused by: class
> org.apache.ignite.internal.processors.query.IgniteSQLException: Table already
> exists: CITY
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.convert(DdlStatementsProcessor.java:642)
> at
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:503)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunPrepared(IgniteH2Indexing.java:1981)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:1896)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2174)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2169)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2677)
> at
>
[jira] [Comment Edited] (IGNITE-9947) JDBC thin: Batch update is not performed if streaming state changed before executeBatch()
[
https://issues.apache.org/jira/browse/IGNITE-9947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771099#comment-16771099
]
Taras Ledkov edited comment on IGNITE-9947 at 2/18/19 1:57 PM:
---
[~pkouznet], [~vozerov].
The test looks like invalid a bit:
after the first {{fillParamsWithPerson(pstmt, 1);}} the batch wasn't added.
If the {{pstmt.addBatch();}} is added after this line, the second call of the
{{addBatch}} throws:
{{java.sql.SQLException: Statement has non-empty batch (call executeBatch() or
clearBatch() before enabling streaming).}}
I guess this is valid behavior because STREAMING mode is Ignite-specific.
I propose to close issue with *Not a Bug*.
was (Author: tledkov-gridgain):
[~pkouznet], [~vozerov].
The test looks like invalid a bit:
after the first {{fillParamsWithPerson(pstmt, 1);}} the batch wasn't added.
If the {{pstmt.addBatch();}} is added after this line, the second call of the
{{addBatch}} throws:
{{java.sql.SQLException: Statement has non-empty batch (call executeBatch() or
clearBatch() before enabling streaming).}}
I guess this is valid behavior because STREAMING mode is Ignite-specific.
> JDBC thin: Batch update is not performed if streaming state changed before
> executeBatch()
> -
>
> Key: IGNITE-9947
> URL: https://issues.apache.org/jira/browse/IGNITE-9947
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.6
>Reporter: Pavel Kuznetsov
>Assignee: Taras Ledkov
>Priority: Major
>
> Thin driver is affected.
> How to reproduce:
> 0) Create table
> 1) Create PreparedStatement "INSERT INTO TAB VALUES (?, ?)"
> 2) Set statement's args and call .addBatch()
> 3) Turn on streaming
> 4) call .executeBatch()
> 5) Turn off streaming to flush streamer.
> After that table should contain batched data, but it doesn't
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9314) MVCC TX: Datastreamer operations
[
https://issues.apache.org/jira/browse/IGNITE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771100#comment-16771100
]
Ivan Pavlukhin commented on IGNITE-9314:
After a discussion with [~gvvinblade], [~amashenkov], [~agoncharuk],
[~ivan.glukos] it was found that streaming via primary node can lead to
unhandled data inconsistency between partition replicas, so this approach
cannot guarantee data consistency in failover scenarios.
It also known that current implementation of `IgniteDataStreamer` has multiple
problems which can lead to inconsistent data. The most promising approach is
streaming to exclusively locked table. In that case inserts can be done using
special _initial version_ and incrementing counters one by one at a time of
insert.
Other approaches can be studied. Among them is using special
_write-conflict-free_ semantics for streamer updates. But any other approach
should be thoroughly evaluated.
> MVCC TX: Datastreamer operations
>
>
> Key: IGNITE-9314
> URL: https://issues.apache.org/jira/browse/IGNITE-9314
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.8
>
>
> Need to change DataStreamer semantics (make it transactional)
> Currently clients can see DataStreamer partial writes and two subsequent
> selects, which are run in scope of one transaction at load time, may return
> different results.
> Related thread:
>
> [http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
> Also there is a problem when {{DataStreamer}} with {{allowOverwrite ==
> false}} does not insert value when versions for entry exist but they all are
> aborted. Proper transactional semantics should developed for such case. After
> that attention should be put on Cache.size method behavior. Cache.size
> addressed in https://issues.apache.org/jira/browse/IGNITE-8149 could be
> decremented improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
> method (called during streamer processing) when all existing mvcc row
> versions are aborted or last committed one is _remove_ version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11346) Remote client authentication failed for the CommandHandler in the case where it optional on the server
Maxim Karavaev created IGNITE-11346: --- Summary: Remote client authentication failed for the CommandHandler in the case where it optional on the server Key: IGNITE-11346 URL: https://issues.apache.org/jira/browse/IGNITE-11346 Project: Ignite Issue Type: Bug Components: clients, security, thin client Affects Versions: 2.7 Reporter: Maxim Karavaev h2. Preposition: Custom _GridSecurityProcessor_ implementation allows optional authentication. With other words, if some credentials are presents then authentication performed, otherwise - not (some restricted SecurityContext returned). REST API works fine. If credentials are present or the auth request was made then the auth works as desired, if not - it also works but only for some authorized requests. h2. The problem: _CommandHandler_ which is used for controlling a cluster through the CLI script _command.sh|bat_ doesn't respect credential parameters and sends auth request only in case of authentication exception for a regular request. In the described case of optional authentication it never happens, so the result always depends on the "default" Permissions. h2. Possible solution: Change _GridClientNioTcpConnection_ to always send first an auth request in case of provided credentials. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11105) [TC Bot] Support Teamcity servers aliases
[ https://issues.apache.org/jira/browse/IGNITE-11105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771074#comment-16771074 ] Dmitriy Pavlov commented on IGNITE-11105: - This issue fix consists from several commits > [TC Bot] Support Teamcity servers aliases > - > > Key: IGNITE-11105 > URL: https://issues.apache.org/jira/browse/IGNITE-11105 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > Implement feature of aliasing TeamCity builds bat. Alias will act as a > pointer to the real name of a server. > It is necessary for a feature of linking builds with separate JIRA projects > and/or GitHub forks without duplicating of all builds database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11345) remove deprecation for beforeTestsStarted and afterTestsStopped
[
https://issues.apache.org/jira/browse/IGNITE-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771041#comment-16771041
]
Oleg Ignatenko edited comment on IGNITE-11345 at 2/18/19 1:16 PM:
--
(i) No runs at Teamcity are needed for this change because presence nor absence
of {{@Deprecated}} annotation can't impact tests execution in any way.
Note to reviewers: please make sure that diff contains exactly 6 lines
commenting out {{@Deprecated}} annotation with the reference to IGNITE-11240
and removing deprecation notice from javadoc and that there is nothing else
besides these 6 lines in the diff.
[~avinogradov] this is the change we discussed recently at dev list. If
anything there is not as you expected, please let me know.
was (Author: oignatenko):
(i) No runs at Teamcity are needed for this change because presence nor absence
of {{@Deprecated}} annotation can't impact tests execution in any way.
Note to reviewers: please make sure that diff contains exactly two lines
commenting out {{@Deprecated}} annotation with the reference to IGNITE-11240
and that there is nothing else besides these two lines in the diff.
[~avinogradov] this is the change we discussed recently at dev list. If
anything there is not as you expected, please let me know.
> remove deprecation for beforeTestsStarted and afterTestsStopped
> ---
>
> Key: IGNITE-11345
> URL: https://issues.apache.org/jira/browse/IGNITE-11345
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This task is created per discussion at dev list: [beforeTestsStarted() was
> deprecated, what should we use
> instead?|http://apache-ignite-developers.2346864.n4.nabble.com/beforeTestsStarted-was-deprecated-what-should-we-use-instead-td40625.html]
> We are going to remove deprecation from {{beforeTestsStarted}} and
> {{afterTestsStopped}}. The reason for this is that the way recommended
> instead of these methods makes it less convenient to start and stop the grid.
> Note that regarding the mentioned inconvenient way, we also plan to improve
> it (IGNITE-11240). After it is done, we need to consider recovering
> deprecation for these methods because as follows from above, inconvenience of
> using the recommended way is the only reason to remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10928) After huge load on cluster and restart with walCompactionEnabled=True errors on log
[
https://issues.apache.org/jira/browse/IGNITE-10928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Antonov reassigned IGNITE-10928:
---
Assignee: Sergey Antonov
> After huge load on cluster and restart with walCompactionEnabled=True errors
> on log
> ---
>
> Key: IGNITE-10928
> URL: https://issues.apache.org/jira/browse/IGNITE-10928
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.5
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
>
> {code:java}
>
> class="org.apache.ignite.configuration.DataRegionConfiguration">
>
>
>
>
>
> {code}
> {code:java}
> [15:30:56,809][INFO][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28310114 size: -1, ptr=FileWALPointer [idx=35, fileOff=28310114,
> len=0]
> [15:30:56,811][INFO][wal-file-compressor-%null%-3-#70][FileWriteAheadLogManager]
> Stopping WAL iteration due to an exception: Failed to read WAL record at
> position: 28303753 size: -1, ptr=FileWALPointer [idx=36, fileOff=28303753,
> len=0]
> [15:30:56,811][SEVERE][wal-file-compressor-%null%-1-#68][FileWriteAheadLogManager]
> Compression of WAL segment [idx=35] was skipped due to unexpected error
> class org.apache.ignite.IgniteCheckedException: Failed to read WAL record at
> position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.handleRecordException(AbstractWalRecordsIterator.java:292)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:258)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:154)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.SingleSegmentLogicalRecordsIterator.advance(SingleSegmentLogicalRecordsIterator.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:123)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:52)
> at
> org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.compressSegmentToFile(FileWriteAheadLogManager.java:2039)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body0(FileWriteAheadLogManager.java:1974)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager$FileCompressorWorker.body(FileWriteAheadLogManager.java:1950)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to read WAL
> record at position: 28310114 size: -1
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV1Serializer.readWithCrc(RecordV1Serializer.java:394)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.serializer.RecordV2Serializer.readRecord(RecordV2Serializer.java:235)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advanceRecord(AbstractWalRecordsIterator.java:243)
> ... 10 more
> Caused by: java.nio.channels.ClosedByInterruptException
> at
> java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
> at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:164)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.RandomAccessFileIO.read(RandomAccessFileIO.java:58)
> at
> org.apache.ignite.internal.processors.cache.persistence.file.FileIODecorator.read(FileIODecorator.java:51)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.SimpleFileInput.ensure(SimpleFileInput.java:119)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.ensure(FileInput.java:89)
> at
> org.apache.ignite.internal.processors.cache.persistence.wal.io.FileInput$Crc32CheckingFileInput.readFully(FileInput.java:152)
> at
[jira] [Commented] (IGNITE-11332) Add jmx ability to exclude node from topology.
[
https://issues.apache.org/jira/browse/IGNITE-11332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771048#comment-16771048
]
Ignite TC Bot commented on IGNITE-11332:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3113028buildTypeId=IgniteTests24Java8_RunAll]
> Add jmx ability to exclude node from topology.
> --
>
> Key: IGNITE-11332
> URL: https://issues.apache.org/jira/browse/IGNITE-11332
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In very rare corner cases may occur situation that physically unreachable
> host still present in topology that may leads to hanging overall cluster
> operations.
> Add ability to exclude with specific warning.
> {code:java}
> /**
> * Exclude node from cluster.
> *
> * @param nodeId Node id.
> */
> @MXBeanDescription("Exclude node from cluster.")
> public void excludeNode(UUID nodeId);{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11345) remove deprecation for beforeTestsStarted and afterTestsStopped
[
https://issues.apache.org/jira/browse/IGNITE-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771041#comment-16771041
]
Oleg Ignatenko commented on IGNITE-11345:
-
(i) No runs at Teamcity are needed for this change because presence nor absence
of {{@Deprecated}} annotation can't impact tests execution in any way.
Note to reviewers: please make sure that diff contains exactly two lines
commenting out {{@Deprecated}} annotation with the reference to IGNITE-11240
and that there is nothing else besides these two lines in the diff.
[~avinogradov] this is the change we discussed recently at dev list. If
anything there is not as you expected, please let me know.
> remove deprecation for beforeTestsStarted and afterTestsStopped
> ---
>
> Key: IGNITE-11345
> URL: https://issues.apache.org/jira/browse/IGNITE-11345
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This task is created per discussion at dev list: [beforeTestsStarted() was
> deprecated, what should we use
> instead?|http://apache-ignite-developers.2346864.n4.nabble.com/beforeTestsStarted-was-deprecated-what-should-we-use-instead-td40625.html]
> We are going to remove deprecation from {{beforeTestsStarted}} and
> {{afterTestsStopped}}. The reason for this is that the way recommended
> instead of these methods makes it less convenient to start and stop the grid.
> Note that regarding the mentioned inconvenient way, we also plan to improve
> it (IGNITE-11240). After it is done, we need to consider recovering
> deprecation for these methods because as follows from above, inconvenience of
> using the recommended way is the only reason to remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11345) remove deprecation for beforeTestsStarted and afterTestsStopped
[
https://issues.apache.org/jira/browse/IGNITE-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-11345:
Labels: MakeTeamcityGreenAgain (was: )
> remove deprecation for beforeTestsStarted and afterTestsStopped
> ---
>
> Key: IGNITE-11345
> URL: https://issues.apache.org/jira/browse/IGNITE-11345
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> This task is created per discussion at dev list: [beforeTestsStarted() was
> deprecated, what should we use
> instead?|http://apache-ignite-developers.2346864.n4.nabble.com/beforeTestsStarted-was-deprecated-what-should-we-use-instead-td40625.html]
> We are going to remove deprecation from {{beforeTestsStarted}} and
> {{afterTestsStopped}}. The reason for this is that the way recommended
> instead of these methods makes it less convenient to start and stop the grid.
> Note that regarding the mentioned inconvenient way, we also plan to improve
> it (IGNITE-11240). After it is done, we need to consider recovering
> deprecation for these methods because as follows from above, inconvenience of
> using the recommended way is the only reason to remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11345) remove deprecation for beforeTestsStarted and afterTestsStopped
Oleg Ignatenko created IGNITE-11345:
---
Summary: remove deprecation for beforeTestsStarted and
afterTestsStopped
Key: IGNITE-11345
URL: https://issues.apache.org/jira/browse/IGNITE-11345
Project: Ignite
Issue Type: Task
Affects Versions: 2.8
Reporter: Oleg Ignatenko
This task is created per discussion at dev list: [beforeTestsStarted() was
deprecated, what should we use
instead?|http://apache-ignite-developers.2346864.n4.nabble.com/beforeTestsStarted-was-deprecated-what-should-we-use-instead-td40625.html]
We are going to remove deprecation from {{beforeTestsStarted}} and
{{afterTestsStopped}}. The reason for this is that the way recommended instead
of these methods makes it less convenient to start and stop the grid.
Note that regarding the mentioned inconvenient way, we also plan to improve it
(IGNITE-11240). After it is done, we need to consider recovering deprecation
for these methods because as follows from above, inconvenience of using the
recommended way is the only reason to remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11345) remove deprecation for beforeTestsStarted and afterTestsStopped
[
https://issues.apache.org/jira/browse/IGNITE-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko reassigned IGNITE-11345:
---
Assignee: Oleg Ignatenko
> remove deprecation for beforeTestsStarted and afterTestsStopped
> ---
>
> Key: IGNITE-11345
> URL: https://issues.apache.org/jira/browse/IGNITE-11345
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> This task is created per discussion at dev list: [beforeTestsStarted() was
> deprecated, what should we use
> instead?|http://apache-ignite-developers.2346864.n4.nabble.com/beforeTestsStarted-was-deprecated-what-should-we-use-instead-td40625.html]
> We are going to remove deprecation from {{beforeTestsStarted}} and
> {{afterTestsStopped}}. The reason for this is that the way recommended
> instead of these methods makes it less convenient to start and stop the grid.
> Note that regarding the mentioned inconvenient way, we also plan to improve
> it (IGNITE-11240). After it is done, we need to consider recovering
> deprecation for these methods because as follows from above, inconvenience of
> using the recommended way is the only reason to remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11243) Not working control.sh / control.bat in master NPE in output
[ https://issues.apache.org/jira/browse/IGNITE-11243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771026#comment-16771026 ] Vladislav Pyatkov commented on IGNITE-11243: I leaved comments on GitHub, in additional, could you please added a test where this issue is reproduced. > Not working control.sh / control.bat in master NPE in output > > > Key: IGNITE-11243 > URL: https://issues.apache.org/jira/browse/IGNITE-11243 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Sergey Kosarev >Priority: Blocker > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > ./bin/control.sh --host --port --baseline > Cluster state: active > Error: java.lang.NullPointerException > control.bat --host --port --baseline > Cluster state: active > Error: java.lang.NullPointerException > Press any key to continue . . . > No info in cluster logs matched with call, look like problem in utility run > This bug was introuced by IGNITE-8894 and reproduced when new utility runs on > an old version node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11345) remove deprecation for beforeTestsStarted and afterTestsStopped
[
https://issues.apache.org/jira/browse/IGNITE-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-11345:
Fix Version/s: 2.8
> remove deprecation for beforeTestsStarted and afterTestsStopped
> ---
>
> Key: IGNITE-11345
> URL: https://issues.apache.org/jira/browse/IGNITE-11345
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> This task is created per discussion at dev list: [beforeTestsStarted() was
> deprecated, what should we use
> instead?|http://apache-ignite-developers.2346864.n4.nabble.com/beforeTestsStarted-was-deprecated-what-should-we-use-instead-td40625.html]
> We are going to remove deprecation from {{beforeTestsStarted}} and
> {{afterTestsStopped}}. The reason for this is that the way recommended
> instead of these methods makes it less convenient to start and stop the grid.
> Note that regarding the mentioned inconvenient way, we also plan to improve
> it (IGNITE-11240). After it is done, we need to consider recovering
> deprecation for these methods because as follows from above, inconvenience of
> using the recommended way is the only reason to remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11345) remove deprecation for beforeTestsStarted and afterTestsStopped
[
https://issues.apache.org/jira/browse/IGNITE-11345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Ignatenko updated IGNITE-11345:
Ignite Flags: (was: Docs Required)
> remove deprecation for beforeTestsStarted and afterTestsStopped
> ---
>
> Key: IGNITE-11345
> URL: https://issues.apache.org/jira/browse/IGNITE-11345
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> This task is created per discussion at dev list: [beforeTestsStarted() was
> deprecated, what should we use
> instead?|http://apache-ignite-developers.2346864.n4.nabble.com/beforeTestsStarted-was-deprecated-what-should-we-use-instead-td40625.html]
> We are going to remove deprecation from {{beforeTestsStarted}} and
> {{afterTestsStopped}}. The reason for this is that the way recommended
> instead of these methods makes it less convenient to start and stop the grid.
> Note that regarding the mentioned inconvenient way, we also plan to improve
> it (IGNITE-11240). After it is done, we need to consider recovering
> deprecation for these methods because as follows from above, inconvenience of
> using the recommended way is the only reason to remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11091) Visor shows all indexes in upper case
[
https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771010#comment-16771010
]
Ignite TC Bot commented on IGNITE-11091:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3015773buildTypeId=IgniteTests24Java8_RunAll]
> Visor shows all indexes in upper case
> -
>
> Key: IGNITE-11091
> URL: https://issues.apache.org/jira/browse/IGNITE-11091
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7
>Reporter: Igor Akkuratov
>Assignee: Igor Akkuratov
>Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11050) Potential deadlock caused by DhtColocatedLockFuture#map being called inside topology read lock
[
https://issues.apache.org/jira/browse/IGNITE-11050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepachev Maksim reassigned IGNITE-11050:
-
Assignee: Alexey Goncharuk (was: Stepachev Maksim)
I fixed it. Could you do a review?
> Potential deadlock caused by DhtColocatedLockFuture#map being called inside
> topology read lock
> --
>
> Key: IGNITE-11050
> URL: https://issues.apache.org/jira/browse/IGNITE-11050
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I observed the following stacktrace on TC during tests analysis:
> {code}
> Thread
> [name="exchange-worker-#18471%near.GridCachePartitionedNodeRestartTest0%",
> id=23715, state=WAITING, blockCnt=860, waitCnt=775]
> Lock
> [object=java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync@2bfb6b49,
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
> at
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
> at
> o.a.i.i.util.StripedCompositeReadWriteLock$WriteLock.lock0(StripedCompositeReadWriteLock.java:173)
> at
> o.a.i.i.util.StripedCompositeReadWriteLock$WriteLock.lock(StripedCompositeReadWriteLock.java:142)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.localPartition0(GridDhtPartitionTopologyImpl.java:925)
> at
> o.a.i.i.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.localPartition(GridDhtPartitionTopologyImpl.java:826)
> at
> o.a.i.i.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.localPartition(GridCachePartitionedConcurrentMap.java:70)
> at
> o.a.i.i.processors.cache.distributed.dht.GridCachePartitionedConcurrentMap.putEntryIfObsoleteOrAbsent(GridCachePartitionedConcurrentMap.java:89)
> at
> o.a.i.i.processors.cache.GridCacheAdapter.entryEx(GridCacheAdapter.java:1019)
> at
> o.a.i.i.processors.cache.distributed.dht.GridDhtCacheAdapter.entryEx(GridDhtCacheAdapter.java:544)
> at
> o.a.i.i.processors.cache.transactions.IgniteTxManager.txUnlock(IgniteTxManager.java:1764)
> at
> o.a.i.i.processors.cache.transactions.IgniteTxManager.unlockMultiple(IgniteTxManager.java:1775)
> at
> o.a.i.i.processors.cache.transactions.IgniteTxManager.rollbackTx(IgniteTxManager.java:1347)
> at
> o.a.i.i.processors.cache.transactions.IgniteTxLocalAdapter.userRollback(IgniteTxLocalAdapter.java:1075)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxLocal.localFinish(GridNearTxLocal.java:3602)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishFuture.doFinish(GridNearTxFinishFuture.java:440)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxFinishFuture.finish(GridNearTxFinishFuture.java:390)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxLocal.rollbackNearTxLocalAsync(GridNearTxLocal.java:3833)
> at
> o.a.i.i.processors.cache.distributed.near.GridNearTxLocal.rollbackNearTxLocalAsync(GridNearTxLocal.java:3784)
> at
> o.a.i.i.processors.cache.GridCacheAdapter$53.applyx(GridCacheAdapter.java:4409)
> at
> o.a.i.i.processors.cache.GridCacheAdapter$53.applyx(GridCacheAdapter.java:4399)
> at o.a.i.i.util.lang.IgniteClosureX.apply(IgniteClosureX.java:38)
> at
> o.a.i.i.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:78)
> at
> o.a.i.i.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:70)
> at
> o.a.i.i.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:30)
> at
> o.a.i.i.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:399)
> at
> o.a.i.i.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at
> o.a.i.i.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at
> o.a.i.i.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:511)
> at
>
[jira] [Commented] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770996#comment-16770996 ] Sergey Antonov commented on IGNITE-11091: - [~iakkuratov] Please fill ticket description. > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770991#comment-16770991 ] Sergey Antonov commented on IGNITE-11091: - [~iakkuratov] I left a few comments in PR. Please fix it. > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Task > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-11091: Issue Type: Bug (was: Task) > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8368) Reimplement queries notebooks list table wth pc-items-table'
[ https://issues.apache.org/jira/browse/IGNITE-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-8368: - Assignee: Pavel Konstantinov (was: Alexander Kalinin) [~pkonstantinov] Line fixed. Please test > Reimplement queries notebooks list table wth pc-items-table' > > > Key: IGNITE-8368 > URL: https://issues.apache.org/jira/browse/IGNITE-8368 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > Time Spent: 1.2h > Remaining Estimate: 0h > > Currently notebooks list table is implemented with pure ui-grid directive. > But now we have a component 'pc-items-table', which enfolds higher > abstractions. For better managability we should reimplement this table with > pc-items-table. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10545) [ML] Kullback–Leibler divergence
[ https://issues.apache.org/jira/browse/IGNITE-10545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov resolved IGNITE-10545. -- Resolution: Won't Fix In my opinion this task is redundant because Kullback-Leibler divergence in most cases are theoretical metric used as target for classifiers. From requirement of apriori distribution for metric computing point of view this task can be closed with status 'won't fix'. > [ML] Kullback–Leibler divergence > > > Key: IGNITE-10545 > URL: https://issues.apache.org/jira/browse/IGNITE-10545 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > > For comparing several distributions we need to implement such metric. > > [wiki link|https://en.wikipedia.org/wiki/Kullback%E2%80%93Leibler_divergence] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10548) [ML] Classificator based on GMM
[ https://issues.apache.org/jira/browse/IGNITE-10548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov reassigned IGNITE-10548: Assignee: Alexey Platonov > [ML] Classificator based on GMM > --- > > Key: IGNITE-10548 > URL: https://issues.apache.org/jira/browse/IGNITE-10548 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > > Implement supervised classifier learning over GMM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11344) High performance drop in master vs 2.7
Ivan Artukhov created IGNITE-11344: -- Summary: High performance drop in master vs 2.7 Key: IGNITE-11344 URL: https://issues.apache.org/jira/browse/IGNITE-11344 Project: Ignite Issue Type: Bug Reporter: Ivan Artukhov Attachments: Screenshot from 2019-02-18 12-53-15.png, Screenshot from 2019-02-18 12-53-40.png Builds under test: * Apache Ignite from branch *master*, nightly build at 2019-02-15 * Apache Ignite 2.7 Benchmark: * atomic put-all (IgnitePutAllBenchmark), batch size: 100 Environment: * 4 servers, 8 clients (64 threads) * *In-memory* mode (the drop is not as high when persistence is enabled) Results for FULL_SYNC (-16.19% drop in master): !Screenshot from 2019-02-18 12-53-40.png! Results for PRIMARY_SYNC (-23.41% drop in master): !Screenshot from 2019-02-18 12-53-15.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11086) IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of seconds.
[
https://issues.apache.org/jira/browse/IGNITE-11086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770943#comment-16770943
]
Ivan Bessonov commented on IGNITE-11086:
[~6uest] changes look good, thank you! Please proceed with merge.
> IGNITE_REST_SECURITY_TOKEN_TIMEOUT parameter is set in deciseconds instead of
> seconds.
> --
>
> Key: IGNITE-11086
> URL: https://issues.apache.org/jira/browse/IGNITE-11086
> Project: Ignite
> Issue Type: Bug
> Components: rest
>Affects Versions: 2.7
>Reporter: Vitaliy Biryukov
>Assignee: Andrey Kalinin
>Priority: Major
> Labels: newbie
> Time Spent: 10m
> Remaining Estimate: 0h
>
> According to javaDoc IGNITE_REST_SECURITY_TOKEN_TIMEOUT should be set in
> seconds.
> Can be fixed by multiplying this parameter by 1000 instead of 100 in
> GridRestProcessor's constructor:
> {code:java}
> sesTokTtl =
> IgniteSystemProperties.getLong(IGNITE_REST_SECURITY_TOKEN_TIMEOUT,
> DFLT_SES_TOKEN_INVALIDATE_INTERVAL) * 100;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10545) [ML] Kullback–Leibler divergence
[ https://issues.apache.org/jira/browse/IGNITE-10545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Platonov reassigned IGNITE-10545: Assignee: Alexey Platonov > [ML] Kullback–Leibler divergence > > > Key: IGNITE-10545 > URL: https://issues.apache.org/jira/browse/IGNITE-10545 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Yury Babak >Assignee: Alexey Platonov >Priority: Major > > For comparing several distributions we need to implement such metric. > > [wiki link|https://en.wikipedia.org/wiki/Kullback%E2%80%93Leibler_divergence] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10011) Pages leak suspicion in PDS
[ https://issues.apache.org/jira/browse/IGNITE-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov reassigned IGNITE-10011: --- Assignee: (was: Sergey Antonov) > Pages leak suspicion in PDS > --- > > Key: IGNITE-10011 > URL: https://issues.apache.org/jira/browse/IGNITE-10011 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Ilya Kasnacheev >Priority: Major > Labels: performance > Fix For: 2.8 > > Attachments: Main.java > > > See the attached Main which adds 500k records to 3 caches, then clears them, > rinse, repeat. > When ran with default settings, totalAllocatedSize will slowly double over > the course of a few hours and then continue to grow. > When ran with 2 FreeList buckets, it will double every time, 600M -> 1200M -> > 1800M -> etc. > See the userlist discussion -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11149) Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc
[ https://issues.apache.org/jira/browse/IGNITE-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770917#comment-16770917 ] Ivan Bessonov commented on IGNITE-11149: [~6uest] looks good, thank you! > Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc > - > > Key: IGNITE-11149 > URL: https://issues.apache.org/jira/browse/IGNITE-11149 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Sergey Antonov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > After IGNITE-10505 default value of IGNITE_DISABLE_WAL_DURING_REBALANCING was > changed from false to true. But javadoc wasn't updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11156) FreeLists are overflowed with pages with almost no free space left
[
https://issues.apache.org/jira/browse/IGNITE-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770905#comment-16770905
]
Ivan Rakov commented on IGNITE-11156:
-
Stopping activity as per benchmarks didn't show any boost.
> FreeLists are overflowed with pages with almost no free space left
> --
>
> Key: IGNITE-11156
> URL: https://issues.apache.org/jira/browse/IGNITE-11156
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code:java}
> /** */
> private static final int MIN_PAGE_FREE_SPACE = 8;
> {code}
> If data page has 8 unused bytes or more, it will be stored in a free list. As
> result, free lists mostly contain "free pages" that are actually useless:
> pair of (boolean, boolean) takes approximately 50 bytes. I think, we'll
> increase this constant to something like 40, memory will be used more
> efficiently and WAL usage will decrease in result.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11149) Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc
[ https://issues.apache.org/jira/browse/IGNITE-11149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770902#comment-16770902 ] Sergey Antonov commented on IGNITE-11149: - [~6uest] looks good for me! [~ibessonov] could you review changes too? > Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc > - > > Key: IGNITE-11149 > URL: https://issues.apache.org/jira/browse/IGNITE-11149 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Sergey Antonov >Assignee: Andrey Kalinin >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > After IGNITE-10505 default value of IGNITE_DISABLE_WAL_DURING_REBALANCING was > changed from false to true. But javadoc wasn't updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10873) CorruptedTreeException during simultaneous cache put operations
[
https://issues.apache.org/jira/browse/IGNITE-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Rakov reassigned IGNITE-10873:
---
Assignee: Ivan Rakov (was: Ilya Kasnacheev)
> CorruptedTreeException during simultaneous cache put operations
> ---
>
> Key: IGNITE-10873
> URL: https://issues.apache.org/jira/browse/IGNITE-10873
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence, sql
>Affects Versions: 2.7
>Reporter: Pavel Vinokurov
>Assignee: Ivan Rakov
>Priority: Critical
>
> {code}
> [2019-01-09 20:47:04,376][ERROR][pool-9-thread-9][GridDhtAtomicCache]
> Unexpected exception during cache update
> org.h2.message.DbException: General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on row: Row@780acfb4[ key: .. ][ GTEST, null, 254, null,
> null, null, null, 0, null, null, null, null, null, null, null, 0, 0, 0, null,
> 0, 0, 0, 0, 0, 0, 0, null, 0, 0, null, 0, null, 0, null, 0, null, null, null,
> 0, 0, 0, 0, 0, 0, null, null, null, null, null, null, null, 0.0, 0, 0.0, 0,
> 0.0, 0, null, 0, 0, 0, 0, null, null, null, null, null, null, null, null,
> null, null, null, null, null, null, null, null ]" [5-197]
> at org.h2.message.DbException.get(DbException.java:168)
> at org.h2.message.DbException.convert(DbException.java:307)
> at
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:302)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.addToIndex(GridH2Table.java:546)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:479)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:768)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:1905)
> at
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:404)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishUpdate(IgniteCacheOffheapManagerImpl.java:2633)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke0(IgniteCacheOffheapManagerImpl.java:1646)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1621)
> at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1935)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:428)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:2295)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2494)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1951)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1780)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1668)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:611)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2449)
> at
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2426)
> at
>
[jira] [Updated] (IGNITE-11343) [ML] Create a stub of Python API module
[ https://issues.apache.org/jira/browse/IGNITE-11343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-11343: Ignite Flags: (was: Docs Required) > [ML] Create a stub of Python API module > --- > > Key: IGNITE-11343 > URL: https://issues.apache.org/jira/browse/IGNITE-11343 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.8 >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > We need to create a stub of Ignite ML Python API module that: > 1. Able to start Py4J server on Java side. > 2. Able to build Python package that connects to the server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11343) [ML] Create a stub of Python API module
[ https://issues.apache.org/jira/browse/IGNITE-11343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-11343: Description: We need to create a stub of Ignite ML Python API module that: 1. Able to start Py4J server on Java side. 2. Able to build Python package that connects to the server and provides a way to call Java API from Python without any wrappers. was: We need to create a stub of Ignite ML Python API module that: 1. Able to start Py4J server on Java side. 2. Able to build Python package that connects to the server. > [ML] Create a stub of Python API module > --- > > Key: IGNITE-11343 > URL: https://issues.apache.org/jira/browse/IGNITE-11343 > Project: Ignite > Issue Type: Sub-task > Components: ml >Affects Versions: 2.8 >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > We need to create a stub of Ignite ML Python API module that: > 1. Able to start Py4J server on Java side. > 2. Able to build Python package that connects to the server and provides a > way to call Java API from Python without any wrappers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11342) [ML] Umbrella: Create a Python API for Ignite ML
[ https://issues.apache.org/jira/browse/IGNITE-11342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-11342: Affects Version/s: 2.8 > [ML] Umbrella: Create a Python API for Ignite ML > > > Key: IGNITE-11342 > URL: https://issues.apache.org/jira/browse/IGNITE-11342 > Project: Ignite > Issue Type: New Feature > Components: ml >Affects Versions: 2.8 >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > Currently Apache Ignite ML provides only Java API. The most popular language > of data analysts is Python. To allow data analysts work with Ignite ML we > need to provide Python API. > The architecture of this Python API should be based on > [Py4J|https://www.py4j.org/] library. This library allows to starts a simple > server of Java side and then translate all calls from Python API into calls > of corresponding Java API and interact with the server via TCP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11343) [ML] Create a stub of Python API module
Anton Dmitriev created IGNITE-11343: --- Summary: [ML] Create a stub of Python API module Key: IGNITE-11343 URL: https://issues.apache.org/jira/browse/IGNITE-11343 Project: Ignite Issue Type: Sub-task Components: ml Affects Versions: 2.8 Reporter: Anton Dmitriev Assignee: Anton Dmitriev Fix For: 2.8 We need to create a stub of Ignite ML Python API module that: 1. Able to start Py4J server on Java side. 2. Able to build Python package that connects to the server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11342) [ML] Umbrella: Create a Python API for Ignite ML
[ https://issues.apache.org/jira/browse/IGNITE-11342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-11342: Fix Version/s: 2.8 > [ML] Umbrella: Create a Python API for Ignite ML > > > Key: IGNITE-11342 > URL: https://issues.apache.org/jira/browse/IGNITE-11342 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > Fix For: 2.8 > > > Currently Apache Ignite ML provides only Java API. The most popular language > of data analysts is Python. To allow data analysts work with Ignite ML we > need to provide Python API. > The architecture of this Python API should be based on > [Py4J|https://www.py4j.org/] library. This library allows to starts a simple > server of Java side and then translate all calls from Python API into calls > of corresponding Java API and interact with the server via TCP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11342) [ML] Umbrella: Create a Python API for Ignite ML
[ https://issues.apache.org/jira/browse/IGNITE-11342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Dmitriev updated IGNITE-11342: Summary: [ML] Umbrella: Create a Python API for Ignite ML (was: [ML] Create a Python API for Ignite ML) > [ML] Umbrella: Create a Python API for Ignite ML > > > Key: IGNITE-11342 > URL: https://issues.apache.org/jira/browse/IGNITE-11342 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Anton Dmitriev >Assignee: Anton Dmitriev >Priority: Major > > Currently Apache Ignite ML provides only Java API. The most popular language > of data analysts is Python. To allow data analysts work with Ignite ML we > need to provide Python API. > The architecture of this Python API should be based on > [Py4J|https://www.py4j.org/] library. This library allows to starts a simple > server of Java side and then translate all calls from Python API into calls > of corresponding Java API and interact with the server via TCP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11342) [ML] Create a Python API for Ignite ML
Anton Dmitriev created IGNITE-11342: --- Summary: [ML] Create a Python API for Ignite ML Key: IGNITE-11342 URL: https://issues.apache.org/jira/browse/IGNITE-11342 Project: Ignite Issue Type: New Feature Components: ml Reporter: Anton Dmitriev Assignee: Anton Dmitriev Currently Apache Ignite ML provides only Java API. The most popular language of data analysts is Python. To allow data analysts work with Ignite ML we need to provide Python API. The architecture of this Python API should be based on [Py4J|https://www.py4j.org/] library. This library allows to starts a simple server of Java side and then translate all calls from Python API into calls of corresponding Java API and interact with the server via TCP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11243) Not working control.sh / control.bat in master NPE in output
[ https://issues.apache.org/jira/browse/IGNITE-11243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Kosarev updated IGNITE-11243: Description: ./bin/control.sh --host --port --baseline Cluster state: active Error: java.lang.NullPointerException control.bat --host --port --baseline Cluster state: active Error: java.lang.NullPointerException Press any key to continue . . . No info in cluster logs matched with call, look like problem in utility run This bug was introuced by IGNITE-8894 and reproduced when new utility runs on an old version node. was: ./bin/control.sh --host --port --baseline Cluster state: active Error: java.lang.NullPointerException control.bat --host --port --baseline Cluster state: active Error: java.lang.NullPointerException Press any key to continue . . . No info in cluster logs matched with call, look like problem in utility run > Not working control.sh / control.bat in master NPE in output > > > Key: IGNITE-11243 > URL: https://issues.apache.org/jira/browse/IGNITE-11243 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.8 >Reporter: ARomantsov >Assignee: Sergey Kosarev >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > ./bin/control.sh --host --port --baseline > Cluster state: active > Error: java.lang.NullPointerException > control.bat --host --port --baseline > Cluster state: active > Error: java.lang.NullPointerException > Press any key to continue . . . > No info in cluster logs matched with call, look like problem in utility run > This bug was introuced by IGNITE-8894 and reproduced when new utility runs on > an old version node. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
