diff --git a/Filer-Store-Replication.md b/Filer-Store-Replication.md
index 55dfde9..a1c6bba 100644
--- a/Filer-Store-Replication.md
+++ b/Filer-Store-Replication.md
@@ -14,7 +14,7 @@ So when a filer was added or removed from the cluster, there is no configuration
 
 What's more, adding a fresh new filer will automatically synchronize the metadata with other filers. Resuming a paused filer will also resume the metadata synchronization from when it was stopped. Everything will/should just work!
 
-Note however that using multiple replicated embedded filers is only eventually consistent. So using this setup behind a load-balancer might not work as expected. 
+Note however that using multiple replicated embedded filers is only eventually consistent. So using this setup behind a load-balancer might not work as expected, although this can be solved with load balancer configuration, such as hashing connections based on the `uploadId` GET query, or temporary sticky sessions to ensure the objects requested are available.
 
 # Metadata synchronization