[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-19 Thread ASF GitHub Bot (JIRA) 


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

ASF GitHub Bot commented on IGNITE-9776:


Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4953


> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-19 Thread Alexey Goncharuk (JIRA) 


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

Alexey Goncharuk commented on IGNITE-9776:
--

Blockers are either present in master or not related to the changes.

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-19 Thread Ignite TC Bot (JIRA) 


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

Ignite TC Bot commented on IGNITE-9776:
---

{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=2115459]]
* HadoopExecutorServiceTest.testShutdown (last started)

{color:#d04437}Inspections (AOP){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=2115524]]

{color:#d04437}Inspections (Core){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=2115525]]

{color:#d04437}Platform .NET (Coverage)*{color} [[tests 
43|https://ci.ignite.apache.org/viewLog.html?buildId=2115540]]
* exe: SqlDmlTest.TestLogWarning - 1,0% fails in last 100 master runs.
* exe: CacheLinqTest.TestDateTime - 1,0% fails in last 100 master runs.
* exe: CacheLinqTest.TestDateTime - 1,0% fails in last 100 master runs.
* exe: CacheLinqTest.TestDateTime - 1,0% fails in last 100 master runs.
* exe: MessagingTest.TestMessageDataTypes - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestCallJavaService - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestCallJavaServiceDynamicProxy - 1,0% fails in last 100 
master runs.
* exe: ServicesTest.TestCancel - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestCancelException - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestDeployAllInputErrors - 1,0% fails in last 100 master 
runs.
* exe: ServicesTest.TestDeployClusterSingleton - 1,0% fails in last 100 master 
runs.
* exe: ServicesTest.TestDeployKeyAffinitySingleton - 1,0% fails in last 100 
master runs.
* exe: ServicesTest.TestDeployKeyAffinitySingletonBinarizable - 1,0% fails in 
last 100 master runs.
* exe: ServicesTest.TestDeployMultiple - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestDeployNodeSingleton - 1,0% fails in last 100 master 
runs.
* exe: ServicesTest.TestDeploymentExceptionSerializable - 1,0% fails in last 
100 master runs.
* exe: ServicesTest.TestExecuteException - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestFooterSetting - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestGetDynamicServiceProxy - 1,0% fails in last 100 master 
runs.
* exe: ServicesTest.TestGetDynamicServiceProxyLocal - 1,0% fails in last 100 
master runs.
* exe: ServicesTest.TestMarshalExceptionOnRead - 1,0% fails in last 100 master 
runs.
* exe: ServicesTest.TestMarshalExceptionOnWrite - 1,0% fails in last 100 master 
runs.
* exe: ServicesTest.TestServiceDescriptors - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestWithKeepBinaryBoth - 1,0% fails in last 100 master runs.
* exe: ServicesTest.TestWithKeepBinaryClient - 1,0% fails in last 100 master 
runs.
* exe: ServicesTestFullFooter.TestDeploy(False) - 1,0% fails in last 100 master 
runs.
* exe: ServicesTestFullFooter.TestDeploy(True) - 1,0% fails in last 100 master 
runs.
* exe: ServicesTestFullFooter.TestDeployAll(False) - 1,0% fails in last 100 
master runs.
* exe: ServicesTestFullFooter.TestDeployAll(True) - 1,0% fails in last 100 
master runs.
* exe: ServicesTestFullFooter.TestDeployAllException(False) - 1,0% fails in 
last 100 master runs.
* exe: ServicesTestFullFooter.TestDeployAllException(True) - 1,0% fails in last 
100 master runs.
* exe: ServicesTestFullFooter.TestDeployException(False) - 1,0% fails in last 
100 master runs.
* exe: ServicesTestFullFooter.TestDeployException(True) - 1,0% fails in last 
100 master runs.
* exe: ServicesTestFullFooter.TestDeployMultipleException(False) - 1,0% fails 
in last 100 master runs.
* exe: ServicesTestFullFooter.TestDeployMultipleException(True) - 1,0% fails in 
last 100 master runs.
* exe: ServicesTestFullFooter.TestDuckTyping(False) - 1,0% fails in last 100 
master runs.
* exe: ServicesTestFullFooter.TestDuckTyping(True) - 1,0% fails in last 100 
master runs.
* exe: ServicesTestFullFooter.TestGetServiceProxy(False) - 1,0% fails in last 
100 master runs.
* exe: ServicesTestFullFooter.TestGetServiceProxy(True) - 1,0% fails in last 
100 master runs.

{panel}
[TeamCity Run 
All|http://ci.ignite.apache.org/viewLog.html?buildId=2115549&buildTypeId=IgniteTests24Java8_RunAll]

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-18 Thread Alexey Goncharuk (JIRA) 


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

Alexey Goncharuk commented on IGNITE-9776:
--

[~astelmak], please rename the PR to include the ticket number so we can use 
MTCGA bot to verify the tests.

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-17 Thread Alexey Stelmak (JIRA) 


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

Alexey Stelmak commented on IGNITE-9776:


done.

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-16 Thread Alexey Goncharuk (JIRA) 


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

Alexey Goncharuk commented on IGNITE-9776:
--

[~astelmak], the tests commented in {{WalRolloverTypesTest}} are still hanging 
after your fix, please take a look.

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-14 Thread Andrey Kuznetsov (JIRA) 


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

Andrey Kuznetsov commented on IGNITE-9776:
--

[~astelmak], could you please resurrect failing methods in 
{{WalRolloverTypesTest}} as a part of your PR?

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-11 Thread Alexey Stelmak (JIRA) 


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

Alexey Stelmak commented on IGNITE-9776:


PR: https://github.com/apache/ignite/pull/4953

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-9776) FsyncModeFileWriteAheadLogManager can block forever in log() call

2018-10-09 Thread Vladimir Ozerov (JIRA) 


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

Vladimir Ozerov commented on IGNITE-9776:
-

Hi [~andrey-kuznetsov], 
Could you please share the status of this ticket? Are we going to fix it in AI 
2.7 still? If yes, then what is the deadline?

> FsyncModeFileWriteAheadLogManager can block forever in log() call
> -
>
> Key: IGNITE-9776
> URL: https://issues.apache.org/jira/browse/IGNITE-9776
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.7
>
> Attachments: FsyncWalRolloverDoesNotBlockTest.java
>
>
> If WAL archiver is disabled and WALRecord being logged has {{rollOver() == 
> true}}, then {{log()}} call blocks forever in {{FileArchiver}}'s (!) method:
> {noformat}
> nextAbsoluteSegmentIndex:1707, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> access$3200:1437, FsyncModeFileWriteAheadLogManager$FileArchiver 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> pollNextFile:1384, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> initNextWriteHandle:1243, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> rollOver:1130, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> log:712, FsyncModeFileWriteAheadLogManager 
> (org.apache.ignite.internal.processors.cache.persistence.wal)
> {noformat}
> Reproducer is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)