Re: How to properly close igfs file after appending it
Is it possible to provide a reproducer? On Fri, Jun 9, 2017 at 9:11 AM, ishan-jain <jain.isha...@gmail.com> wrote: > Ivan please ellaborate > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/How-to-properly-close-igfs-file-after-appending-it- > tp11613p13551.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
Re: How to properly close igfs file after appending it
Ivan please ellaborate -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-properly-close-igfs-file-after-appending-it-tp11613p13551.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: How to properly close igfs file after appending it
What do you mean by not open any transactions? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-properly-close-igfs-file-after-appending-it-tp11613p13550.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: How to properly close igfs file after appending it
Hi, Prashant, are you trying to append concurrently from several streams? The situation you observe means that you're trying to append a file that is currently open for writing in another output stream. (When a file is open for append, a special lock is placed to the file meta information in meta cache to prevent concurrent file appending.) You should not open any transactions, IGFS implementation creates all necessary transactions for you. If you're appending the file with many small portions of data, it would be much more efficient use one output stream than to open and close a new stream for each portion. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-properly-close-igfs-file-after-appending-it-tp11613p11619.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
