[jira] [Commented] (IGNITE-11848) [IEP-35] Monitoring Phase 1
[ https://issues.apache.org/jira/browse/IGNITE-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860607#comment-16860607 ] Nikolay Izhikov commented on IGNITE-11848: -- "Platform .NET" also timeouts in master https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_PlatformNet_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv > [IEP-35] Monitoring Phase 1 > -- > > Key: IGNITE-11848 > URL: https://issues.apache.org/jira/browse/IGNITE-11848 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 3.5h > Remaining Estimate: 0h > > Umbrella ticket for the IEP-35. Monitoring and profiling. > Phase 1 should include: > * NextGen monitoring subsystem implementation to manage > ** metrics > ** -lists- (will be implemented in the following tickets) > ** exporters > * JMX, SQLView, Log exporters > * Migration of existing metrics to new manager > * -Lists for all Ignite user API- -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11848) [IEP-35] Monitoring Phase 1
[
https://issues.apache.org/jira/browse/IGNITE-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860604#comment-16860604
]
Ignite TC Bot commented on IGNITE-11848:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=4089954]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4089983buildTypeId=IgniteTests24Java8_RunAll]
> [IEP-35] Monitoring Phase 1
> --
>
> Key: IGNITE-11848
> URL: https://issues.apache.org/jira/browse/IGNITE-11848
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Umbrella ticket for the IEP-35. Monitoring and profiling.
> Phase 1 should include:
> * NextGen monitoring subsystem implementation to manage
> ** metrics
> ** -lists- (will be implemented in the following tickets)
> ** exporters
> * JMX, SQLView, Log exporters
> * Migration of existing metrics to new manager
> * -Lists for all Ignite user API-
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10281) Log to file all jars in classpath on start node.
[ https://issues.apache.org/jira/browse/IGNITE-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860680#comment-16860680 ] Denis Chudov commented on IGNITE-10281: --- This .NET timeout is not related with my commit, as it also happens in default branch. > Log to file all jars in classpath on start node. > > > Key: IGNITE-10281 > URL: https://issues.apache.org/jira/browse/IGNITE-10281 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > We should print all jars in classpath for analize jar's hell. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10281) Log to file all jars in classpath on start node.
[ https://issues.apache.org/jira/browse/IGNITE-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-10281: Ignite Flags: (was: Docs Required) > Log to file all jars in classpath on start node. > > > Key: IGNITE-10281 > URL: https://issues.apache.org/jira/browse/IGNITE-10281 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Antonov >Assignee: Denis Chudov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > We should print all jars in classpath for analize jar's hell. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11911) GridToStringBuilder allocates redundant memory
Aleksey Plekhanov created IGNITE-11911:
--
Summary: GridToStringBuilder allocates redundant memory
Key: IGNITE-11911
URL: https://issues.apache.org/jira/browse/IGNITE-11911
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Aleksey Plekhanov
A lot of classes in Ignite uses {{GridToStringBuilder}} to implement their
{{toString()}} method. {{GridToStringBuilder}} uses thread local buffer to
generate string representation. This buffer extended on demand but never
shrank. On the final step {{GridToStringBuilder}} uses java {{StringBuilder}}
class to produce output string and uses own buffer size as {{StringBuilder}}
initial capacity. This leads to unnecessary memory allocation since we only
need to allocate memory for meaningful data, but not for all buffer.
Reproducer:
{code:java}
public void testSB() {
GridToStringBuilder.toString(C1.class, new C1(1_000_000));
GridToStringBuilder.toString(C1.class, new C1(100));
}
public class C1 {
private String f;
C1(int len) {
f = new String(new char[len]);
}
}
{code}
Here on the second line about 1 million chars StringBuilder will be allocated,
but only about 100 chars needed.
Problem code (SBLimitedLength.java:293):
{code:java}
StringBuilder res = new StringBuilder(impl().capacity() + tailLen + 100);
{code}
Here {{length()}} method can be used instead of {{capacity()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11910) JDBC v2: adds 'schema' to URL parameters, makes 'cache' parameter is optional fpr the most cases
Taras Ledkov created IGNITE-11910: - Summary: JDBC v2: adds 'schema' to URL parameters, makes 'cache' parameter is optional fpr the most cases Key: IGNITE-11910 URL: https://issues.apache.org/jira/browse/IGNITE-11910 Project: Ignite Issue Type: Bug Components: jdbc Reporter: Taras Ledkov Assignee: Taras Ledkov Fix For: 2.8 We have to do changes for the JDBC v2: - makes 'cache' parameter is optional. - add 'schema' parameter to URL. When cache and schema parameters are not defined 'PUBLIC' schema is used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-11900) Fix ClassPathContentLoggingTest test
[ https://issues.apache.org/jira/browse/IGNITE-11900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Chudov resolved IGNITE-11900. --- Resolution: Fixed This was fixed in https://issues.apache.org/jira/browse/IGNITE-10281 before it had been merged to master. > Fix ClassPathContentLoggingTest test > > > Key: IGNITE-11900 > URL: https://issues.apache.org/jira/browse/IGNITE-11900 > Project: Ignite > Issue Type: Bug >Reporter: Denis Chudov >Assignee: Denis Chudov >Priority: Major > > This test failed in TC because of incorrect path separator in > beforeTestsStarted. Should be File.pathSeparator instead of ';'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11911) GridToStringBuilder allocates redundant memory
[
https://issues.apache.org/jira/browse/IGNITE-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-11911:
--
Assignee: Aleksey Plekhanov
> GridToStringBuilder allocates redundant memory
> --
>
> Key: IGNITE-11911
> URL: https://issues.apache.org/jira/browse/IGNITE-11911
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>
> A lot of classes in Ignite uses {{GridToStringBuilder}} to implement their
> {{toString()}} method. {{GridToStringBuilder}} uses thread local buffer to
> generate string representation. This buffer extended on demand but never
> shrank. On the final step {{GridToStringBuilder}} uses java {{StringBuilder}}
> class to produce output string and uses own buffer size as {{StringBuilder}}
> initial capacity. This leads to unnecessary memory allocation since we only
> need to allocate memory for meaningful data, but not for all buffer.
> Reproducer:
>
> {code:java}
> public void testSB() {
> GridToStringBuilder.toString(C1.class, new C1(1_000_000));
> GridToStringBuilder.toString(C1.class, new C1(100));
> }
> public class C1 {
> private String f;
> C1(int len) {
> f = new String(new char[len]);
> }
> }
> {code}
> Here on the second line about 1 million chars StringBuilder will be
> allocated, but only about 100 chars needed.
>
> Problem code (SBLimitedLength.java:293):
>
> {code:java}
> StringBuilder res = new StringBuilder(impl().capacity() + tailLen + 100);
> {code}
> Here {{length()}} method can be used instead of {{capacity()}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8884) .NET: CachePartialUpdateException: failed to update keys (using Cache.PutAsync)
[
https://issues.apache.org/jira/browse/IGNITE-8884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandr Shapkin reassigned IGNITE-8884:
Assignee: Alexandr Shapkin
> .NET: CachePartialUpdateException: failed to update keys (using
> Cache.PutAsync)
> ---
>
> Key: IGNITE-8884
> URL: https://issues.apache.org/jira/browse/IGNITE-8884
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.5
> Environment: Windows 10.
> Apache Ignite 2.5.0.
> .NETFramework,Version=v4.6.1
> Packages:
> * Apache.Ignite - 2.5.0
> * Apache.Ignite.Log4Net - 2.5.0
> * Apache.Ignite.NLog - 2.5.0
> * NLog - 4.0.0
>
>
>Reporter: Roman Guseinov
>Assignee: Alexandr Shapkin
>Priority: Major
> Labels: dot_net
> Attachments: Program.cs
>
>
> The issue happens when we try to call PutAsync(KeyObject, ValueObject) where
> ValueObject's field refers to KeyObject. Reproducer is attached.
>
> {code:java}
> Apache.Ignite.Core.Cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [server_node.TradeId [idHash=573136580,
> hash=31459296, Number=2]]
> at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
> at
> System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
> task)
> at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
> at server_node.Program.d__2.MoveNext() in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 61
> --- End of stack trace from previous location where exception was thrown ---
> at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
> at
> System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
> task)
> at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
> at server_node.Program.Main(String[] args) in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 22
> {code}
>
> Also, when we use the default logger, Cache.PutAsync doesn't throw an
> exception but when we try to get value back from the cache the different
> exception happens:
>
> {code:java}
> System.ArgumentException: Seek before origin: -25
> at Apache.Ignite.Core.Impl.Memory.PlatformMemoryStream.Seek(Int32 offset,
> SeekOrigin origin)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadHandleObject[T](Int32 pos,
> Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadObject[T](String fieldName)
> at lambda_method(Closure , Object , IBinaryReader )
> at
> Apache.Ignite.Core.Impl.Binary.BinaryReflectiveSerializerInternal.Apache.Ignite.Core.Impl.Binary.IBinarySerializerInternal.ReadBinary[T](BinaryReader
> reader, IBinaryTypeDescriptor desc, Int32 pos, Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos,
> Type typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadBinaryObject[T](Boolean
> doDetach)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type
> typeOverride)
> at Apache.Ignite.Core.Impl.Binary.Marshaller.Unmarshal[T](IBinaryStream
> stream, Boolean keepBinary)
> at Apache.Ignite.Core.Impl.PlatformJniTarget.InStreamOutLong[TR](Int32 type,
> Action`1 outAction, Func`3 inAction, Func`2 readErrorAction)
> at Apache.Ignite.Core.Impl.Cache.CacheImpl`2.Get(TK key)
> at server_node.Program.d__2.MoveNext() in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 62
> --- End of stack trace from previous location where exception was thrown ---
> at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
> at
> System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task
> task)
> at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
> at server_node.Program.Main(String[] args) in
> C:\Users\user\source\repos\IginteAsyncTest\server-node\server-node\Program.cs:line
> 22
> {code}
>
> There are two workarounds:
> # Do not use the same object as key and the value's field.
> # Put data into the cache using the synchronous method.
>
> Reproducer is attached: [^Program.cs]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11867) Fix flaky test GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
[
https://issues.apache.org/jira/browse/IGNITE-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861029#comment-16861029
]
Ignite TC Bot commented on IGNITE-11867:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric
|https://ci.ignite.apache.org/viewLog.html?buildId=4094131]]
{color:#d04437}MVCC PDS 4{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4094133]]
{color:#d04437}MVCC PDS 3{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4094726]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4087571buildTypeId=IgniteTests24Java8_RunAll]
> Fix flaky test
> GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
> -
>
> Key: IGNITE-11867
> URL: https://issues.apache.org/jira/browse/IGNITE-11867
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> java.lang.AssertionError: Value for 4 is null
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingWithAsyncClearingTest.testCorrectRebalancingCurrentlyRentingPartitions(GridCacheRebalancingWithAsyncClearingTest.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2148)
> at java.lang.Thread.run(Thread.java:748){noformat}
> EDIT: The issue is related to recently contributed IGNITE-10078. In specific
> scenario due to race partition clearing could be started while partition is
> passing through ongoing rebalancing started on previous topology version.
> I fixed it by preventing partition clearing on newer topology version. In
> such case if rebalance will be finished and partition will go in OWNING state
> further clearing is not needed any more, otherwise partition should be
> scheduled for clearing again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11030) Cache page corruption after a page being rotated having partition ID=0
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Fix Version/s: (was: 2.8)
> Cache page corruption after a page being rotated having partition ID=0
> --
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
> Fix For: 2.7.5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> - TC Bot was stopped with kill command (default signal).
> - Shutdown hook calls ignite close
> But after updating to V190122 TC Bot DB was became unrecoverable for
> "teamcityTestRunHist" cache with exception
> {noformat}
> Failure periodic check failed: javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> com.google.common.util.concurrent.UncheckedExecutionException:
> javax.cache.CacheException: class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on lookup row: SearchRow
> [key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
> [idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
> branch=281], hash=1241170874, cacheId=0]
> at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
> at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
> at
> com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
> at
> org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
> at
> org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
> at
> org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
> at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
> at
> java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
> at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
> at java.util.TimSort.sort(TimSort.java:220)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1462)
> at
> org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at
> org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
> at
> org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at
> java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at
> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
> at
[jira] [Updated] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11216:
Fix Version/s: (was: 2.8)
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11299) During SSL Handshake GridNioServer.processWrite is invoked constantly
[ https://issues.apache.org/jira/browse/IGNITE-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11299: Fix Version/s: (was: 2.8) > During SSL Handshake GridNioServer.processWrite is invoked constantly > - > > Key: IGNITE-11299 > URL: https://issues.apache.org/jira/browse/IGNITE-11299 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Blocker > Labels: important, ssl > Fix For: 2.7.5 > > Time Spent: 1h > Remaining Estimate: 0h > > Causes busy looping in processSelectionKeyOptimized() > This also causes problems on Windows/Java 11 since if key is always ready for > writing it will never be shown as ready for reading. > The reason for this behavior that during handshake we never un-listen OP_WRITE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11766) cpp: JVM library not found for openjdk 11 on windows
[
https://issues.apache.org/jira/browse/IGNITE-11766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11766:
Fix Version/s: (was: 2.8)
> cpp: JVM library not found for openjdk 11 on windows
>
>
> Key: IGNITE-11766
> URL: https://issues.apache.org/jira/browse/IGNITE-11766
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Trying to run compiled ignite.exe from platforms/cpp on windows
> {code}
> An error occurred: JVM library is not found (did you set JAVA_HOME
> environment variable?)
> {code}
> Think problem that platforms\cpp\jni\os\win\src\utils -> JAVA_DDL =
> "\\jre\\bin\\server\\jvm.dll"
> searching for jre in jdk directory
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11600) Fix launch script and GridUnsafe for Java 12
[ https://issues.apache.org/jira/browse/IGNITE-11600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11600: Fix Version/s: (was: 2.8) > Fix launch script and GridUnsafe for Java 12 > > > Key: IGNITE-11600 > URL: https://issues.apache.org/jira/browse/IGNITE-11600 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Dmitriy Pavlov >Priority: Critical > Labels: important > Fix For: 2.7.5 > > Time Spent: 1h > Remaining Estimate: 0h > > bin/ignite.bat:251 > if "%MAJOR_JAVA_VER%" == "11" ( > need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11595) Fix broken Javadoc stylesheet
[
https://issues.apache.org/jira/browse/IGNITE-11595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11595:
Fix Version/s: (was: 2.8)
> Fix broken Javadoc stylesheet
> -
>
> Key: IGNITE-11595
> URL: https://issues.apache.org/jira/browse/IGNITE-11595
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After moving to JDK 8 build the bug in Javadoc HTML view was introduced due
> to new javadoc.css from JDK 8 which was overridden by hardcode
> ({{[pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/pom.xml#L195]}},
>
> {{[parent/pom.xml|https://github.com/apache/ignite/blob/221cd6c97a364171e24562cb45d067de9097bd4f/parent/pom.xml#L792]}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Fix Version/s: (was: 2.8)
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Labels: important
> Fix For: 2.7.5
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
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
]
Dmitriy Pavlov updated IGNITE-10873:
Fix Version/s: (was: 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.7.5
>
> Time Spent: 20m
> 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
> 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-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:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11233:
Fix Version/s: (was: 2.8)
> 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
> Fix For: 2.7.5
>
> Time Spent: 20m
> 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
> [21:28:32][Step 1/1] [ERROR]
>
[jira] [Updated] (IGNITE-11737) Apache Ignite 2.7.5 Linux packages version update
[ https://issues.apache.org/jira/browse/IGNITE-11737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11737: Fix Version/s: (was: 2.8) > Apache Ignite 2.7.5 Linux packages version update > - > > Key: IGNITE-11737 > URL: https://issues.apache.org/jira/browse/IGNITE-11737 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.7.5 > > Time Spent: 20m > Remaining Estimate: 0h > > Update DEB and RPM packages' versions in Apache Ignite for the next version > (2.7.5) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11366) python thin client: add python examples in release build
[ https://issues.apache.org/jira/browse/IGNITE-11366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11366: Fix Version/s: (was: 2.8) > python thin client: add python examples in release build > > > Key: IGNITE-11366 > URL: https://issues.apache.org/jira/browse/IGNITE-11366 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.7.5 > > Time Spent: 20m > Remaining Estimate: 0h > > Examples directory should be added in release build because they exists in > sources and they really help to understand how to work with this client > I think they understandable enough for end user > Also they have readme.md which is contain link on examples documentation > > What should be in release build in /ignite/platforms/python > * examples (dir) > * pyignite (dir) > * requirements (dir) > * LICENSE > * README.md > * setup.py -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11796) WAL recovery stopped with 'Partition consistency failure: newPageId'
[
https://issues.apache.org/jira/browse/IGNITE-11796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11796:
Fix Version/s: (was: 2.8)
> WAL recovery stopped with 'Partition consistency failure: newPageId'
>
>
> Key: IGNITE-11796
> URL: https://issues.apache.org/jira/browse/IGNITE-11796
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
> Fix For: 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://repository.apache.org/content/repositories/orgapacheignite-1436/ test
> using TC bot showed that there can be a situation when DB contains an
> incorrect record. This record probably does not lead to corruption (because
> 2.7.0 works well with this DB).
> But validation introduced in
> https://issues.apache.org/jira/browse/IGNITE-11030 stops WAL recovery.
> {noformat}
> java.util.concurrent.ExecutionException: java.lang.AssertionError: Partition
> consistency failure: newPageId=1f3d3 (newPartId: 0)
> pageId=101001af3d3 (partId: 26)
> at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:205)
> at
> org.apache.ignite.ci.di.IgniteTcBotModule.lambda$configure$0(IgniteTcBotModule.java:61)
> at
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:85)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
> at
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:59)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
> at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1050)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1086)
> at
> org.apache.ignite.ci.web.auth.AuthenticationFilter.filter(AuthenticationFilter.java:127)
> at
> org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:108)
> at
> org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:44)
> at org.glassfish.jersey.process.internal.Stages.process(Stages.java:173)
> at
> org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:245)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265)
> at
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:232)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:679)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:392)
> at
> org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:365)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:318)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
> at
>
[jira] [Updated] (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:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11195:
Fix Version/s: (was: 2.8)
> 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
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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] [Updated] (IGNITE-11572) Node restart in ignite.sh was broken by IGNITE-11216
[
https://issues.apache.org/jira/browse/IGNITE-11572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11572:
Fix Version/s: (was: 2.8)
> Node restart in ignite.sh was broken by IGNITE-11216
>
>
> Key: IGNITE-11572
> URL: https://issues.apache.org/jira/browse/IGNITE-11572
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Goncharuk
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See TC tests in master:
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_StartNodes=buildTypeStatusDiv_IgniteTests24Java8=%3Cdefault%3E
> All node restart tests are failing because nodes stop, but not restarted.
> Looks like the changes in {{ignite.sh}} caused the node restart loop to exit
> after the first {{CommandLineStartup}} execution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11436) sqlline is not working on Java 9+
[
https://issues.apache.org/jira/browse/IGNITE-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11436:
Fix Version/s: (was: 2.8)
> sqlline is not working on Java 9+
> -
>
> Key: IGNITE-11436
> URL: https://issues.apache.org/jira/browse/IGNITE-11436
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Anton Kurbanov
>Assignee: Anton Kurbanov
>Priority: Major
> Labels: important
> Fix For: 2.7.5
>
>
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/var/lib/teamcity/data/work/ead1d0aeaa1f7813/i2test/var/suite-client/art-gg-pro/libs/ignite-core-2.7.2-p1.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.util.IgniteUtils
> at org.apache.ignite.internal.IgnitionEx.(IgnitionEx.java:209)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.loadConfiguration(JdbcConnection.java:323)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.getIgnite(JdbcConnection.java:295)
> at
> org.apache.ignite.internal.jdbc2.JdbcConnection.(JdbcConnection.java:229)
> at org.apache.ignite.IgniteJdbcDriver.connect(IgniteJdbcDriver.java:437)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:156)
> at sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:204)
> at sqlline.Commands.connect(Commands.java:1095)
> at sqlline.Commands.connect(Commands.java:1001)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> sqlline.ReflectiveCommandHandler.execute(ReflectiveCommandHandler.java:38)
> at sqlline.SqlLine.dispatch(SqlLine.java:791)
> at sqlline.SqlLine.initArgs(SqlLine.java:566)
> at sqlline.SqlLine.begin(SqlLine.java:643)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10003) Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read lock timeout detected
[
https://issues.apache.org/jira/browse/IGNITE-10003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-10003:
Fix Version/s: (was: 2.8)
> Raise SYSTEM_WORKER_BLOCKED instead of CRITICAL_ERROR when checkpoint read
> lock timeout detected
>
>
> Key: IGNITE-10003
> URL: https://issues.apache.org/jira/browse/IGNITE-10003
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Trivial
> Fix For: 2.7.5
>
>
> {{GridCacheDatabaseSharedManager#failCheckpointReadLock}} should report
> {{SYSTEM_WORKER_BLOCKED}} to failure handler: it is closer to the truth and
> default consequenses are not so severe as opposed to {{CRITICAL_ERROR}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11848) [IEP-35] Monitoring Phase 1
[ https://issues.apache.org/jira/browse/IGNITE-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861178#comment-16861178 ] Pavel Kovalenko commented on IGNITE-11848: -- [~NIzhikov] Thank you for the contribution and actively participating in the review process. At the moment I have no objections regarding the change. > [IEP-35] Monitoring Phase 1 > -- > > Key: IGNITE-11848 > URL: https://issues.apache.org/jira/browse/IGNITE-11848 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 3.5h > Remaining Estimate: 0h > > Umbrella ticket for the IEP-35. Monitoring and profiling. > Phase 1 should include: > * NextGen monitoring subsystem implementation to manage > ** metrics > ** -lists- (will be implemented in the following tickets) > ** exporters > * JMX, SQLView, Log exporters > * Migration of existing metrics to new manager > * -Lists for all Ignite user API- -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11153:
Fix Version/s: (was: 2.8)
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: important
> Fix For: 2.7.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> JAXB module was removed from Java 11.
> Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
> {noformat}
> elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> --add-modules=java.transaction \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ $version -eq 11 ] ; then
> JVM_OPTS="\
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> ${JVM_OPTS}"
> {noformat}
> But control.sh for master still declares --add-modules java.xml.bind \
> {noformat}
> JVM_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
> --add-modules java.xml.bind \
> ${JVM_OPTS}"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11265) Node stop causes JVM Crashes in page memory
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11265: Fix Version/s: (was: 2.8) > Node stop causes JVM Crashes in page memory > --- > > Key: IGNITE-11265 > URL: https://issues.apache.org/jira/browse/IGNITE-11265 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Eduard Shangareev >Priority: Critical > Fix For: 2.7.5 > > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > Time Spent: 20m > Remaining Estimate: 0h > > Reproduced on Teamcity:All crash dumps complain about the same method > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock > Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log > Other recent examples > Queries 1 > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log > Client Nodes > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log > Zookeeper Discovery > https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11869) control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, if user pages wasn't modified in checkpoint.
[ https://issues.apache.org/jira/browse/IGNITE-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861397#comment-16861397 ] Dmitriy Govorukhin commented on IGNITE-11869: - [~antonovsergey93] I reviewed your changes, and I have a serious concern. Absolutely incorrect store dirtyUserPagesPresent flag in PageMemory. PageMemory should not know anything that not related pages, this flag sets True for not UTILITY_CACHE_GROUP_ID is it abstraction leak. > control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, > if user pages wasn't modified in checkpoint. > -- > > Key: IGNITE-11869 > URL: https://issues.apache.org/jira/browse/IGNITE-11869 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We shouldn't throw GridNotIdleException, if checkpoint contains dirty pages > related to ignite-sys-cache (system background activities) only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11911) GridToStringBuilder allocates redundant memory
[
https://issues.apache.org/jira/browse/IGNITE-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861549#comment-16861549
]
Ignite TC Bot commented on IGNITE-11911:
{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=4095191buildTypeId=IgniteTests24Java8_RunAll]
> GridToStringBuilder allocates redundant memory
> --
>
> Key: IGNITE-11911
> URL: https://issues.apache.org/jira/browse/IGNITE-11911
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A lot of classes in Ignite uses {{GridToStringBuilder}} to implement their
> {{toString()}} method. {{GridToStringBuilder}} uses thread local buffer to
> generate string representation. This buffer extended on demand but never
> shrank. On the final step {{GridToStringBuilder}} uses java {{StringBuilder}}
> class to produce output string and uses own buffer size as {{StringBuilder}}
> initial capacity. This leads to unnecessary memory allocation since we only
> need to allocate memory for meaningful data, but not for all buffer.
> Reproducer:
>
> {code:java}
> public void testSB() {
> GridToStringBuilder.toString(C1.class, new C1(1_000_000));
> GridToStringBuilder.toString(C1.class, new C1(100));
> }
> public class C1 {
> private String f;
> C1(int len) {
> f = new String(new char[len]);
> }
> }
> {code}
> Here on the second line about 1 million chars StringBuilder will be
> allocated, but only about 100 chars needed.
>
> Problem code (SBLimitedLength.java:293):
>
> {code:java}
> StringBuilder res = new StringBuilder(impl().capacity() + tailLen + 100);
> {code}
> Here {{length()}} method can be used instead of {{capacity()}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
