[
https://issues.apache.org/jira/browse/IGNITE-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16385966#comment-16385966
]
Ilya Lantukh commented on IGNITE-7809:
--------------------------------------
After fixing those tests I still observe flaky fails and hang-ups on TC due to
problems, unrelated to the initial one.
Also, they fail locally on my PC with the following exception:
{noformat}
class org.apache.ignite.IgniteCheckedException: Failed to initialize WAL
segment:
C:\Projects\ignite\work\db\wal\node00-3bc7e86d-8f7d-4930-b5ea-337ceadeb2da\0000000000000006.wal
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:320)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$RecordsIterator.initReadHandle(FsyncModeFileWriteAheadLogManager.java:2972)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$RecordsIterator.advanceSegment(FsyncModeFileWriteAheadLogManager.java:3073)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.advance(AbstractWalRecordsIterator.java:155)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:112)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.onNext(AbstractWalRecordsIterator.java:46)
at
org.apache.ignite.internal.util.GridCloseableIteratorAdapter.nextX(GridCloseableIteratorAdapter.java:41)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2173)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1394)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1141)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1120)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:706)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.file.FileSystemException:
C:\Projects\ignite\work\db\wal\node00-3bc7e86d-8f7d-4930-b5ea-337ceadeb2da\0000000000000006.wal:
The process cannot access the file because it is being used by another process.
at
sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
at
sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:90)
at
sun.nio.fs.WindowsChannelFactory.newAsynchronousFileChannel(WindowsChannelFactory.java:202)
at
sun.nio.fs.WindowsFileSystemProvider.newAsynchronousFileChannel(WindowsFileSystemProvider.java:140)
at
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:248)
at
java.nio.channels.AsynchronousFileChannel.open(AsynchronousFileChannel.java:301)
at
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.<init>(AsyncFileIO.java:57)
at
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:53)
at
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIOFactory.create(AsyncFileIOFactory.java:41)
at
org.apache.ignite.internal.processors.cache.persistence.wal.AbstractWalRecordsIterator.initReadHandle(AbstractWalRecordsIterator.java:265)
... 14 more
{noformat}
It seems to be Windows-specific problem (I run it on Windows 10).
> Ignite PDS 2 & PDS 2 Direct IO: stable failures of
> IgniteWalFlushDefaultSelfTest
> --------------------------------------------------------------------------------
>
> Key: IGNITE-7809
> URL: https://issues.apache.org/jira/browse/IGNITE-7809
> Project: Ignite
> Issue Type: Task
> Components: persistence
> Affects Versions: 2.4
> Reporter: Dmitriy Pavlov
> Assignee: Ilya Lantukh
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Probably after last WAL default changes 'IGNITE-7594 Fixed performance drop
> after WAL optimization for FSYNC' 2 tests in 2 build configs began to fail
> Ignite PDS 2 (Direct IO) [ tests 2 ]
> IgnitePdsNativeIoTestSuite2:
> IgniteWalFlushDefaultSelfTest.testFailAfterStart (fail rate 13,0%)
> IgnitePdsNativeIoTestSuite2:
> IgniteWalFlushDefaultSelfTest.testFailWhileStart (fail rate 13,0%)
> Ignite PDS 2 [ tests 2 ]
> IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailAfterStart
> (fail rate 8,4%)
> IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailWhileStart
> (fail rate 8,4%)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
