Don't spam log when connection is abruptly closed

It's a somewhat common scenario (e.g strict/excessive client timeout or bad network) and the client will detect this anyway.

1 files changed, 2 insertions, 1 deletions

diff --git a/vespaclient-container-plugin/src/main/java/com/yahoo/document/restapi/resource/DocumentV1ApiHandler.java b/vespaclient-container-plugin/src/main/java/com/yahoo/document/restapi/resource/DocumentV1ApiHandler.java
index 5ff7b4592a1..f8dc1844c15 100644
--- a/vespaclient-container-plugin/src/main/java/com/yahoo/document/restapi/resource/DocumentV1ApiHandler.java
+++ b/vespaclient-container-plugin/src/main/java/com/yahoo/document/restapi/resource/DocumentV1ApiHandler.java
@@ -843,7 +843,8 @@ public class DocumentV1ApiHandler extends AbstractRequestHandler {
                     ackDocuments();
                 }
                 @Override public void failed(Throwable t) {
-                    log.log(WARNING, "Error writing documents", t);
+                    // This is typically caused by the client closing the connection during production of the response content.
+                    log.log(FINE, "Error writing documents", t);
                     completed();
                 }
             });