Upstream
/
harbor
mirror of https://github.com/goharbor/harbor.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated Harbor FAQs (markdown)

stonezdj(Daojun Zhang) 2024-02-28 14:15:09 +08:00
parent ee82cf58a9
commit b806d76878
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Harbor-FAQs.md

@ -133,6 +133,15 @@ POSTGRES_MAX_CONNECTIONS = 1000
```
Then restart harbor-db container or pod, it will pickup the configuration from env.
## Duplicate repository name in the same project
As described in issue https://github.com/goharbor/harbor/issues/17544, user found two repositories with the same name in a project, but there is a unique constraint for repository name in database.
[**Root cause**]: Postgresql use glibc to sort string data and create index, the unique constraint relies on the index to check if the current key exist. in glibc2.28, there is a [change](https://wiki.postgresql.org/wiki/Locale_data_changes) caused the sorting order change. The upgrade from Harbor v2.2.x to v2.3.0 happens to span across this fix. it means that indexes created before v2.3.0 may be invalid after upgrade to v2.3.0 and the postgres will use the invalid indexes until you delete them and reindex manually. the invalid index causes the unique constraint invalid. especially when the string contains special characters such as `-`,`_`,`$`,`#`,`%` mixed with characters.
To solve this issue you should cleanup duplicated records with this workaround: https://github.com/goharbor/harbor/issues/17544#issuecomment-1257385150
It may impact the latest Harbor version and all tables with unique constraint column, because the invalid indexes persist until you delete them manually.
## Replication
1. What happens if I update a same name image to Harbor with replication enabled?