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

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

{panel:title=Branch: [pull/10130/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10130/head] Base: [master] : New Tests 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}PDS (Indexing){color} [[tests 
1|https://ci2.ignite.apache.org/viewLog.html?buildId=6502553]]
* {color:#013220}IgnitePdsWithIndexingCoreTestSuite: 
WalOnNodeStartTest.testWalReformatWithResize - PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=6502590&buildTypeId=IgniteTests24Java8_RunAll]

> 'Invalid cross-device link error' exception when extending WAL segments size
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-16872
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16872
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: ise
>
> If required WAL segments size is more than current WAL segments size 
> (configuration changes) Ignite extend this size on startup (see 
> {{{}FileWriteAheadLogManager#formatWorkSegments{}}}). To do this each segment 
> copied to the new temp file, temp file is extended and temp file is moved to 
> the original segment file (using {{ATOMIC_MOVE}} option). But temp files are 
> created in the current work dir ({{{}file().getName(){}}} used instead of 
> {{{}file().getAbsolutePath(){}}}:
> {code:java}
> File tmpDst = new File(fd.file().getName() + TMP_SUFFIX);
> {code}
> And if WAL path is configured to another device there can be an exception 
> {{{}AtomicMoveNotSupportedException{}}}:
> {noformat}
> Caused by: java.nio.file.AtomicMoveNotSupportedException: 
> 0000000000000000.wal.tmp -> 
> /opt/ignite/ssd/data/wal/consistentId/0000000000000000.wal: Invalid 
> cross-device link
>         at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:394) ~[?:1.8.0_321]
>         at 
> sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) 
> ~[?:1.8.0_321]
>         at java.nio.file.Files.move(Files.java:1395) ~[?:1.8.0_321]
>         at 
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.formatWorkSegments(FileWriteAheadLogManager.java:3471){noformat}
> We should create temp files in the same directory as WAL segments (on the 
> same device).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to