Re: igfs.withAsync is still synchronous in most file operations?

[Vladimir Ozerov]

Hi Nicolae,

This is not very easy question.

First, "withAsync()" was introduced to IGFS mainly to support task
execution (methods "execute(...)"). For now it is pretty clear that these
methods are of very little use because there are much more convenient
frameworks to achieve the same goals - Hadoop and Spark. And IGFS can be
plugged into them easily. So I think there are rather high chances that
almost all async methods will be removed in Apache Ignite 2.0.

Second, we already has a kind of asynchrony for file writes. We have
special mode DUAL_ASYNC which flushes data to the secondary file system
asynchronously. Having two "flavors" of asynchrony makes API complex and
dirty.

But having said that I still think that asynchronous execution on standard
file system operations like "mkdirs", "remove", etc. could be useful. E.g.
removal of a directory with million files may take substantial time, and
user may want this process to happen in a background.

I hope we will come to some clear solution in Apache Ignite 2.0 and most
methods will have async counterparts.

Vladimir.


On Thu, Jul 21, 2016 at 12:48 AM, vkulichenko  wrote:

> Hi,
>
> Async execution is supported only for methods that are marked with
> @IgniteAsyncSupported annotation. read/write/create/delete operations are
> not among them.
>
> I'm not aware of any plans to provide this support. Can someone else from
> the community chime in?
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/igfs-withAsync-is-still-synchronous-in-most-file-operations-tp6420p6425.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: igfs.withAsync is still synchronous in most file operations?

[vkulichenko]

Hi,

Async execution is supported only for methods that are marked with
@IgniteAsyncSupported annotation. read/write/create/delete operations are
not among them.

I'm not aware of any plans to provide this support. Can someone else from
the community chime in?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/igfs-withAsync-is-still-synchronous-in-most-file-operations-tp6420p6425.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

igfs.withAsync is still synchronous in most file operations?

[Marasoiu Nicolae]

Hi,

We noticed that IgfsAsyncImpl? is delegating to IgfsImpl in most filesystem 
methods, thus being blocking for all those methods which 
read/write/create/delete files and list/create directories.

We were expecting for the igfs.withAsync to work like cache.withAsync, which 
returns a fully asynchronous proxy which returns null and has a future 
available that can be listened to.

Is there a plan in a future release to make igfs async option fully available?

Thanks,
?

Met vriendelijke groeten/Meilleures salutations/Best regards

Nicolae Marasoiu
Agile Developer
E nicolae.maras...@cegeka.com

[http://signature.cegeka.com/mailsignature_cgk.png]
CEGEKA * 15-17 Ion Mihalache Blvd. Tower Center Building, 4th,5th,6th fl * 
RO-011171 Bucharest (RO) * T +32 11 24 02 34 * www.cegeka.com
Volg Cegeka: [http://signature.cegeka.com/twitter.png] 
  [http://signature.cegeka.com/linkedin.png] 
  
[http://signature.cegeka.com/facebook.png]   
[http://signature.cegeka.com/google-plus.png]