From c78fc1407c56441a67fd02aabe7a23f513998b62 Mon Sep 17 00:00:00 2001
From: Jiaqiang Xu <jonathan.xu@seafile.com>
Date: Mon, 14 Jun 2021 17:54:34 +0800
Subject: [PATCH] Update changelog-for-seafile-professional-server.md

Add breaking change warning to 8.0.3 changelog.
---
 .../changelog/changelog-for-seafile-professional-server.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/manual/changelog/changelog-for-seafile-professional-server.md b/manual/changelog/changelog-for-seafile-professional-server.md
index 9920e120..be225408 100644
--- a/manual/changelog/changelog-for-seafile-professional-server.md
+++ b/manual/changelog/changelog-for-seafile-professional-server.md
@@ -22,6 +22,13 @@ Please check our document for how to upgrade to 8.0: <https://manual.seafile.com
 * [fix] Fix file locking
 * [fix] Fix anothoer bug in upload files to a sharing link with upload permission
 
+Potential breaking change in Seafile Pro 8.0.3: You can set the maximum number of files contained in a library that can be synced by the Seafile client. The default is 100000. When you download a repo, Seafile client will request fs id list, and you can control the timeout period of this request through `fs_id_list_request_timeout` configuration, which defaults to 5 minutes. These two options are added to prevent long fs-id-list requests from overloading the server. If you have large libraries on the server, this can cause "internal server error" returned to the client. You have to set a large enough limit for these two options.
+
+```
+[fileserver]
+max_sync_file_count = 100000
+fs_id_list_request_timeout = 300
+```
 
 ### 8.0.2 (2021/04/21)