2013-03-19 22:46:29 +00:00
|
|
|
{- A pool of "git-annex transferkeys" processes
|
|
|
|
-
|
|
|
|
- Copyright 2013 Joey Hess <joey@kitenet.net>
|
|
|
|
-
|
|
|
|
- Licensed under the GNU GPL version 3 or higher.
|
|
|
|
-}
|
|
|
|
|
|
|
|
module Assistant.TransferrerPool where
|
|
|
|
|
|
|
|
import Assistant.Common
|
|
|
|
import Assistant.Types.TransferrerPool
|
|
|
|
import Logs.Transfer
|
2013-12-01 18:56:37 +00:00
|
|
|
import Utility.Batch
|
2013-11-12 18:54:02 +00:00
|
|
|
|
2013-03-19 22:46:29 +00:00
|
|
|
import qualified Command.TransferKeys as T
|
|
|
|
|
assistant: Start a new git-annex transferkeys process after a network connection change
So that remotes that use a persistent network connection are restarted.
A remote might keep open a long duration network connection, and could
fail to deal well with losing the connection. This is particularly a
concern now that we have external special reotes. An external
special remote that is implemented naively might open the connection only
when PREPARE is sent, and if it loses connection, throw errors on each
request that is made.
(Note that the ssh connection caching should not have this problem; if the
long-duration ssh process loses connection, the named pipe is disconnected
and the next ssh attempt will reconnect. Also, XMPP already deals with
disconnection robustly in its own way.)
There's no way for git-annex to know if a lost network connection actually
affects a given remote, which might have a transfer in process. It does not
make sense to force kill the transferkeys process every time the NetWatcher
detects a change. (Especially because the NetWatcher sometimes polls 1
change per hour.)
In any case, the NetWatcher only detects connection to a network, not
disconnection. So if a transfer is in progress over the network, and the
network goes down, that will need to time out on its own.
An alternate approch that was considered is to use a separate transferkeys
process for each remote, and detect when a request fails, and assume that
means that process is in a failing state and restart it. The problem with
that approach is that if a resource is not available and a remote fails
every time, it degrades to starting a new transferkeys process for every
file transfer, which is too expensive.
Instead, this commit only handles the network reconnection case, and restarts
transferkeys only once the network has reconnected and another transfer needs
to be made. So, a transferkeys process will be reused for 1 hour, or until the
next network connection.
----
The NotificationBroadcaster was rewritten to use TMVars rather than MSampleVars,
to allow checking without blocking if a notification has been received.
----
This commit was sponsored by Tobias Brunner.
2014-01-06 20:03:39 +00:00
|
|
|
import Control.Concurrent.STM hiding (check)
|
2013-03-19 22:46:29 +00:00
|
|
|
import Control.Exception (throw)
|
|
|
|
import Control.Concurrent
|
|
|
|
|
assistant: Start a new git-annex transferkeys process after a network connection change
So that remotes that use a persistent network connection are restarted.
A remote might keep open a long duration network connection, and could
fail to deal well with losing the connection. This is particularly a
concern now that we have external special reotes. An external
special remote that is implemented naively might open the connection only
when PREPARE is sent, and if it loses connection, throw errors on each
request that is made.
(Note that the ssh connection caching should not have this problem; if the
long-duration ssh process loses connection, the named pipe is disconnected
and the next ssh attempt will reconnect. Also, XMPP already deals with
disconnection robustly in its own way.)
There's no way for git-annex to know if a lost network connection actually
affects a given remote, which might have a transfer in process. It does not
make sense to force kill the transferkeys process every time the NetWatcher
detects a change. (Especially because the NetWatcher sometimes polls 1
change per hour.)
In any case, the NetWatcher only detects connection to a network, not
disconnection. So if a transfer is in progress over the network, and the
network goes down, that will need to time out on its own.
An alternate approch that was considered is to use a separate transferkeys
process for each remote, and detect when a request fails, and assume that
means that process is in a failing state and restart it. The problem with
that approach is that if a resource is not available and a remote fails
every time, it degrades to starting a new transferkeys process for every
file transfer, which is too expensive.
Instead, this commit only handles the network reconnection case, and restarts
transferkeys only once the network has reconnected and another transfer needs
to be made. So, a transferkeys process will be reused for 1 hour, or until the
next network connection.
----
The NotificationBroadcaster was rewritten to use TMVars rather than MSampleVars,
to allow checking without blocking if a notification has been received.
----
This commit was sponsored by Tobias Brunner.
2014-01-06 20:03:39 +00:00
|
|
|
{- Runs an action with a Transferrer from the pool.
|
|
|
|
-
|
|
|
|
- Only one Transferrer is left running in the pool at a time.
|
|
|
|
- So if this needed to start a new Transferrer, it's stopped when done.
|
|
|
|
-}
|
2013-12-01 19:37:51 +00:00
|
|
|
withTransferrer :: FilePath -> BatchCommandMaker -> TransferrerPool -> (Transferrer -> IO a) -> IO a
|
|
|
|
withTransferrer program batchmaker pool a = do
|
2014-01-06 21:07:08 +00:00
|
|
|
(mi, leftinpool) <- atomically (popTransferrerPool pool)
|
|
|
|
i@(TransferrerPoolItem (Just t) check) <- case mi of
|
|
|
|
Nothing -> mkTransferrerPoolItem pool =<< mkTransferrer program batchmaker
|
|
|
|
Just i -> checkTransferrerPoolItem program batchmaker i
|
2013-03-19 22:46:29 +00:00
|
|
|
v <- tryNonAsync $ a t
|
2014-01-06 21:07:08 +00:00
|
|
|
if leftinpool == 0
|
|
|
|
then atomically $ pushTransferrerPool pool i
|
|
|
|
else do
|
|
|
|
void $ forkIO $ stopTransferrer t
|
|
|
|
atomically $ pushTransferrerPool pool $ TransferrerPoolItem Nothing check
|
2013-03-19 22:46:29 +00:00
|
|
|
either throw return v
|
assistant: Start a new git-annex transferkeys process after a network connection change
So that remotes that use a persistent network connection are restarted.
A remote might keep open a long duration network connection, and could
fail to deal well with losing the connection. This is particularly a
concern now that we have external special reotes. An external
special remote that is implemented naively might open the connection only
when PREPARE is sent, and if it loses connection, throw errors on each
request that is made.
(Note that the ssh connection caching should not have this problem; if the
long-duration ssh process loses connection, the named pipe is disconnected
and the next ssh attempt will reconnect. Also, XMPP already deals with
disconnection robustly in its own way.)
There's no way for git-annex to know if a lost network connection actually
affects a given remote, which might have a transfer in process. It does not
make sense to force kill the transferkeys process every time the NetWatcher
detects a change. (Especially because the NetWatcher sometimes polls 1
change per hour.)
In any case, the NetWatcher only detects connection to a network, not
disconnection. So if a transfer is in progress over the network, and the
network goes down, that will need to time out on its own.
An alternate approch that was considered is to use a separate transferkeys
process for each remote, and detect when a request fails, and assume that
means that process is in a failing state and restart it. The problem with
that approach is that if a resource is not available and a remote fails
every time, it degrades to starting a new transferkeys process for every
file transfer, which is too expensive.
Instead, this commit only handles the network reconnection case, and restarts
transferkeys only once the network has reconnected and another transfer needs
to be made. So, a transferkeys process will be reused for 1 hour, or until the
next network connection.
----
The NotificationBroadcaster was rewritten to use TMVars rather than MSampleVars,
to allow checking without blocking if a notification has been received.
----
This commit was sponsored by Tobias Brunner.
2014-01-06 20:03:39 +00:00
|
|
|
|
|
|
|
{- Check if a Transferrer from the pool is still ok to be used.
|
|
|
|
- If not, stop it and start a new one. -}
|
|
|
|
checkTransferrerPoolItem :: FilePath -> BatchCommandMaker -> TransferrerPoolItem -> IO TransferrerPoolItem
|
|
|
|
checkTransferrerPoolItem program batchmaker i = case i of
|
|
|
|
TransferrerPoolItem (Just t) check -> ifM check
|
|
|
|
( return i
|
|
|
|
, do
|
|
|
|
stopTransferrer t
|
|
|
|
new check
|
2013-03-19 22:46:29 +00:00
|
|
|
)
|
assistant: Start a new git-annex transferkeys process after a network connection change
So that remotes that use a persistent network connection are restarted.
A remote might keep open a long duration network connection, and could
fail to deal well with losing the connection. This is particularly a
concern now that we have external special reotes. An external
special remote that is implemented naively might open the connection only
when PREPARE is sent, and if it loses connection, throw errors on each
request that is made.
(Note that the ssh connection caching should not have this problem; if the
long-duration ssh process loses connection, the named pipe is disconnected
and the next ssh attempt will reconnect. Also, XMPP already deals with
disconnection robustly in its own way.)
There's no way for git-annex to know if a lost network connection actually
affects a given remote, which might have a transfer in process. It does not
make sense to force kill the transferkeys process every time the NetWatcher
detects a change. (Especially because the NetWatcher sometimes polls 1
change per hour.)
In any case, the NetWatcher only detects connection to a network, not
disconnection. So if a transfer is in progress over the network, and the
network goes down, that will need to time out on its own.
An alternate approch that was considered is to use a separate transferkeys
process for each remote, and detect when a request fails, and assume that
means that process is in a failing state and restart it. The problem with
that approach is that if a resource is not available and a remote fails
every time, it degrades to starting a new transferkeys process for every
file transfer, which is too expensive.
Instead, this commit only handles the network reconnection case, and restarts
transferkeys only once the network has reconnected and another transfer needs
to be made. So, a transferkeys process will be reused for 1 hour, or until the
next network connection.
----
The NotificationBroadcaster was rewritten to use TMVars rather than MSampleVars,
to allow checking without blocking if a notification has been received.
----
This commit was sponsored by Tobias Brunner.
2014-01-06 20:03:39 +00:00
|
|
|
TransferrerPoolItem Nothing check -> new check
|
|
|
|
where
|
|
|
|
new check = do
|
|
|
|
t <- mkTransferrer program batchmaker
|
|
|
|
return $ TransferrerPoolItem (Just t) check
|
2013-03-19 22:46:29 +00:00
|
|
|
|
|
|
|
{- Requests that a Transferrer perform a Transfer, and waits for it to
|
|
|
|
- finish. -}
|
2014-05-19 20:19:33 +00:00
|
|
|
performTransfer :: Transferrer -> Transfer -> TransferInfo -> IO Bool
|
|
|
|
performTransfer transferrer t info = catchBoolIO $ do
|
|
|
|
T.sendRequest t info (transferrerWrite transferrer)
|
2013-03-19 22:46:29 +00:00
|
|
|
T.readResponse (transferrerRead transferrer)
|
|
|
|
|
2013-12-11 03:19:18 +00:00
|
|
|
{- Starts a new git-annex transferkeys process, setting up handles
|
2013-03-19 22:46:29 +00:00
|
|
|
- that will be used to communicate with it. -}
|
2013-12-01 19:37:51 +00:00
|
|
|
mkTransferrer :: FilePath -> BatchCommandMaker -> IO Transferrer
|
|
|
|
mkTransferrer program batchmaker = do
|
2013-12-01 18:56:37 +00:00
|
|
|
{- It runs as a batch job. -}
|
2013-12-11 03:19:18 +00:00
|
|
|
let (program', params') = batchmaker (program, [Param "transferkeys"])
|
2013-03-19 22:46:29 +00:00
|
|
|
{- It's put into its own group so that the whole group can be
|
|
|
|
- killed to stop a transfer. -}
|
2013-12-11 03:19:18 +00:00
|
|
|
(Just writeh, Just readh, _, pid) <- createProcess
|
|
|
|
(proc program' $ toCommand params')
|
|
|
|
{ create_group = True
|
|
|
|
, std_in = CreatePipe
|
|
|
|
, std_out = CreatePipe
|
|
|
|
}
|
|
|
|
fileEncoding readh
|
|
|
|
fileEncoding writeh
|
2013-03-19 22:46:29 +00:00
|
|
|
return $ Transferrer
|
2013-12-11 03:19:18 +00:00
|
|
|
{ transferrerRead = readh
|
|
|
|
, transferrerWrite = writeh
|
2013-03-19 22:46:29 +00:00
|
|
|
, transferrerHandle = pid
|
|
|
|
}
|
|
|
|
|
|
|
|
{- Checks if a Transferrer is still running. If not, makes a new one. -}
|
2013-12-01 19:37:51 +00:00
|
|
|
checkTransferrer :: FilePath -> BatchCommandMaker -> Transferrer -> IO Transferrer
|
|
|
|
checkTransferrer program batchmaker t =
|
|
|
|
maybe (return t) (const $ mkTransferrer program batchmaker)
|
|
|
|
=<< getProcessExitCode (transferrerHandle t)
|
2013-03-19 22:46:29 +00:00
|
|
|
|
|
|
|
{- Closing the fds will stop the transferrer. -}
|
|
|
|
stopTransferrer :: Transferrer -> IO ()
|
|
|
|
stopTransferrer t = do
|
|
|
|
hClose $ transferrerRead t
|
|
|
|
hClose $ transferrerWrite t
|
|
|
|
void $ waitForProcess $ transferrerHandle t
|