Andrei <[email protected]> writes:
> Hi,
>
> I couldn't find much related to this in the docs/FAQ so I'm asking here.
>
> 1.) What should I expect in terms of data consistency issues in case the
> underlying network connection is flaky or goes down completely for minutes
> (and for example I may have a daemon running which uses an s3ql file system
> for various data storage purposes)?
It should work just fine as long as your changes fit into the local
cache. Once that is exhausted, any attempt to make changes to the file
system will block until the network connection is back.
> 2.) Also, what is the intended behavior of s3ql in such cases? For this, I
> mean thngs like: does is hang until the network connection is restored (in
> case someone attempts to write to an s3ql file system) or does it write to
> cache instead hoping the connection will be restored etc. ?
The latter, until the cache is full. Then it falls back to the former.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
