@Ivan Thanks for your reply. The fix is quite important to be able to use Ignite efficiently. If the fix is available in the 2.14 version, that'll be great!
Regards, Tejashree Ruikar On Tue, Aug 23, 2022 at 4:34 PM Ivan Bessonov <[email protected]> wrote: > Hi, > > I can't give you the exact estimation, cause I didn't yet look at the > scope of required changes. I'm afraid that simply replacing "move" with > "delete"&"rename" won't help in this case, files must be explicitly closed > before doing so. > There's a chance to get it done by the time 2.14 is released, although > code freeze is literally tomorrow and I'm a little busy right now and can't > proceed immediately with the fix. How urgent is this problem? > > пн, 22 авг. 2022 г. в 07:55, Tejashree Ruikar < > [email protected]>: > >> Hi Ivan, >> >> ++ Ashutosh >> >> Can this issue be fixed by splitting the problematic function >> *Files.move()* by *Files.copy()* (or *Files.write()*) followed by >> *Files.delete()*. Do you see any issues it might cause, especially >> because the operation won't be atomic anymore. >> Please share your thoughts. Also, if you can suggest any alternative >> solution, feel free to do so. >> >> Thank you. >> Regards, >> Tejashree Ruikar >> >> On Tue, Aug 16, 2022 at 10:30 AM Tejashree Ruikar < >> [email protected]> wrote: >> >>> Okay, thanks Ivan for the update. Is it scheduled to be fixed in any of >>> the upcoming updates or patches? >>> >>> Regards, >>> Tejashree Ruikar >>> >>> On Fri, Aug 12, 2022 at 7:45 PM Ivan Bessonov <[email protected]> >>> wrote: >>> >>>> Hi! >>>> >>>> Unfortunately, the problem is in Ignite itself. The node holds the file >>>> opened while renaming it, thus not allowing this renaming to happen on >>>> Windows platform. I don't think that there's a workaround here. >>>> >>>> пт, 12 авг. 2022 г. в 17:11, Ivan Bessonov <[email protected]>: >>>> >>>>> Hi! >>>>> >>>>> Unfortunately, the problem is in Ignite itself. The node holds the >>>>> file opened while renaming it, thus not allowing this renaming to happen >>>>> on >>>>> Windows platform. I don't think that there's a workaround here. >>>>> >>>>> пт, 12 авг. 2022 г. в 12:40, Tejashree Ruikar < >>>>> [email protected]>: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm using ControlScript to trigger the defragmentation task for an >>>>>> apache ignite node. The defragmentation completes successfully on a Linux >>>>>> node. >>>>>> But when executed on a Widows node, it fails with following exception: >>>>>> >>>>>> Aug 12, 2022 9:59:08 AM org.apache.ignite.logger.java.JavaLogger error >>>>>> SEVERE: Defragmentation failed >>>>>> class org.apache.ignite.IgniteException: >>>>>> C:\ProgramData\<SOME_FOLDER>\IgniteStorage\<CONSISTENT_ID>\cache-<CACHE_NAME>\part-dfrg-63.bin >>>>>> -> C:\ProgramData\<SOME_FOLDER>\IgniteStorage\<CONSISTENT_ID>\cache- >>>>>> <CACHE_NAME>\part-63.bin >>>>>> at >>>>>> org.apache.ignite.internal.processors.cache.persistence.defragmentation.DefragmentationFileUtils.batchRenameDefragmentedCacheGroupPartitions(DefragmentationFileUtils.java:234) >>>>>> at >>>>>> org.apache.ignite.internal.processors.cache.persistence.defragmentation.DefragmentationFileUtils.skipAlreadyDefragmentedCacheGroup(DefragmentationFileUtils.java:133) >>>>>> at >>>>>> org.apache.ignite.internal.processors.cache.persistence.defragmentation.CachePartitionDefragmentationManager.executeDefragmentation(CachePartitionDefragmentationManager.java:284) >>>>>> at >>>>>> org.apache.ignite.internal.processors.cache.persistence.defragmentation.maintenance.ExecuteDefragmentationAction.lambda$execute$0(ExecuteDefragmentationAction.java:73) >>>>>> at java.lang.Thread.run(Thread.java:748) >>>>>> Caused by: java.nio.file.AccessDeniedException: >>>>>> C:\ProgramData\<SOME_FOLDER>\IgniteStorage\<CONSISTENT_ID>\cache-<CACHE_NAME>\part-dfrg-63.bin >>>>>> -> >>>>>> C:\ProgramData\<SOME_FOLDER>\IgniteStorage\<CONSISTENT_ID>\cache-<CACHE_NAME>\part-63.bin >>>>>> at >>>>>> sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83) >>>>>> at >>>>>> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) >>>>>> at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:301) >>>>>> at >>>>>> sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:287) >>>>>> at java.nio.file.Files.move(Files.java:1395) >>>>>> at >>>>>> org.apache.ignite.internal.processors.cache.persistence.defragmentation.DefragmentationFileUtils.batchRenameDefragmentedCacheGroupPartitions(DefragmentationFileUtils.java:222) >>>>>> ... 4 more >>>>>> >>>>>> I've ensured that no other process is currently using that file and >>>>>> file permissions are adequate. I've even tried disabling/ uninstalling >>>>>> antivirus, but nothing worked. >>>>>> Is there a fix or workaround for this issue? >>>>>> >>>>>> Regards, >>>>>> Tejashree Ruikar >>>>>> >>>>>> This electronic communication and the information and any files >>>>>> transmitted with it, or attached to it, are confidential and are intended >>>>>> solely for the use of the individual or entity to whom it is addressed >>>>>> and >>>>>> may contain information that is confidential, legally privileged, >>>>>> protected >>>>>> by privacy laws, or otherwise restricted from disclosure to anyone else. >>>>>> If >>>>>> you are not the intended recipient or the person responsible for >>>>>> delivering >>>>>> the e-mail to the intended recipient, you are hereby notified that any >>>>>> use, >>>>>> copying, distributing, dissemination, forwarding, printing, or copying of >>>>>> this e-mail is strictly prohibited. If you received this e-mail in error, >>>>>> please return the e-mail to the sender, delete it from your computer, and >>>>>> destroy any printed copy of it. >>>>> >>>>> >>>>> >>>>> -- >>>>> Sincerely yours, >>>>> Ivan Bessonov >>>>> >>>> >>>> >>>> -- >>>> Sincerely yours, >>>> Ivan Bessonov >>>> >>> >> This electronic communication and the information and any files >> transmitted with it, or attached to it, are confidential and are intended >> solely for the use of the individual or entity to whom it is addressed and >> may contain information that is confidential, legally privileged, protected >> by privacy laws, or otherwise restricted from disclosure to anyone else. If >> you are not the intended recipient or the person responsible for delivering >> the e-mail to the intended recipient, you are hereby notified that any use, >> copying, distributing, dissemination, forwarding, printing, or copying of >> this e-mail is strictly prohibited. If you received this e-mail in error, >> please return the e-mail to the sender, delete it from your computer, and >> destroy any printed copy of it. > > > > -- > Sincerely yours, > Ivan Bessonov > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
smime.p7s
Description: S/MIME Cryptographic Signature
