You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: release-notes-10.2
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ HTML header: <title>dCache 10.2 Release Notes</title>
71
71
72
72
## Incompatibilities
73
73
74
-
- Pool Manager partitions by default allowed to stage
74
+
- Pool Manager partitions by default are allowed to stage
75
75
- Dropped gPlazma ARGUS plugin
76
76
- A stage request canceled in the poolmanager will propagate the cancel to pool
77
77
- Pool internal health check is disabled if an external check command is configured.
@@ -80,30 +80,30 @@ HTML header: <title>dCache 10.2 Release Notes</title>
80
80
81
81
## Acknowledgments
82
82
83
-
- Anton Schwarz, Heidelberg University, DESY Summer Stutent Programm
83
+
- Anton Schwarz, Heidelberg University, DESY Summer Student Program
84
84
85
85
86
86
## Release 10.2.15
87
87
88
88
### gplazma
89
89
90
90
Excessive caching of failed login attempts leads to system has been reported.
91
-
92
-
The current relase fexed that and now following properties could be used to control the overload:
91
+
The current release has introduced a property that could be used to control the cache size:
93
92
94
93
`gplazma.authz.loginFailure.cache.size=10000`
95
94
96
-
When the cache reaches this size, older entries are evicted. Remove the least-recently-used (LRU) entries when that limit is exceeded. important: the cache size is an approximate size not exact.
97
-
98
-
`gplazma.authz.loginFailure.cache-size-expiry=1`
95
+
When that limit is exceeded, the oldest cache entry is removed.
96
+
> Important: the cache size is approximate, not exact.
99
97
100
-
timeout cache entry life time. By default expire entries 1 hour after they are written. If a key is expired due to time, it is gone even if the cache is not full.
98
+
In addition, the cache of failed logins can be evicted based on time. By default, entries expire 1 hour after they are written.
99
+
If a key expires due to time, it is gone even if the cache is not full. The expiry time can be adjusted by:
0 commit comments