What’s new in dCache 8.2
Release notes
Highlights
- support for nested groups in the PoolManager
Incompatibilities
- pool group names can’t start with
@
symbol - hard links on directories is not allowed
- GET api/v1/bulk-requests has a new return value (see below)
- The QoS API functionality now requires some services to operate. These are described in the dCache Book version 8.2.
- With version 8.2.40+, empty and non-existent banfiles will be treated the same
Release 8.2.41
chimera
Fixed a bug that made it possible to create a loop on directory move.
Changelog 8.2.40..8.2.41
- 17f073e46e
- [maven-release-plugin] prepare release 8.2.41
- 09d2ac2db8
- chimera: fix loop creation on directory move
- e525fd15e1
- ci: drop –ftp-create-dirs option (as we switch to https)
- 35ead7e08b
- ci: use minimal almalinux–9 to upload packages
- c37e2bee6d
- [maven-release-plugin] prepare for next development iteration
Release 8.2.40
gplazma
Previously, a missing banfile would result in every successive login attempt failing with an NPE. Now, even if configured, an empty or inexistent banfile will be ignored and logins should succeed. WARNING: This changes the banfile plugin behaviour! Empty and non-existent banfiles will be treated the same.
Changelog 8.2.39..8.2.40
- f02ea04672
- [maven-release-plugin] prepare release 8.2.40
- 1206a1895f
- Fix unit test for commit 6b47354
- 3321de1359
- gplazma: configured banfile plugin should ignore non-existent ban file
- 1c3a8229b4
- [maven-release-plugin] prepare for next development iteration
Release 8.2.39
xroot
Regression eliminated, previous behavior with anonymous read restored.
Changelog 8.2.38..8.2.39
- 209c91f32d
- [maven-release-plugin] prepare release 8.2.39
- 8a67eb3f6f
- dcache-xroot: check that descriptor is not null before calling close
- 9f13584175
- [maven-release-plugin] prepare for next development iteration
Release 8.2.38
dependencies
The MongoDB driver was updated. This might lead to different log messages.
Changelog 8.2.37..8.2.38
- 5f7fc22a12
- [maven-release-plugin] prepare release 8.2.38
- 28b8b4623d
- pom: Update mongodb-driver
- 429cb16d35
- [maven-release-plugin] prepare for next development iteration
Release 8.2.37
bulk
The current releae fixed handling of uncaught exception during perform.
Changelog 8.2.36..8.2.37
- 912cb72676
- [maven-release-plugin] prepare release 8.2.37
- c4a92eddc8
- dcache-bulk: fix handling of uncaught exception during perform
- 01e61783a2
- dcache-frontend,common: check parsing of Duration in STAGE
- fc117f6415
- [maven-release-plugin] prepare for next development iteration
Release 8.2.36
webdav
The urls similar to this https://door.domain.foo:1234//pnfs/domain.foo/path/to/file
were strip into /domain.foo/path/to/file
.
The current release fixed the parsing of urls with two slashes in the path.
Changelog 8.2.35..8.2.36
- 46b65a2e22
- [maven-release-plugin] prepare release 8.2.36
- e2e42899a1
- webdav: fix infinite recursion in Requests.stripToPath
- ca01798b71
- webdav: fix parsing of urls with two slashes in the path
- be62bce99c
- [maven-release-plugin] prepare for next development iteration
Release 8.2.35
door
Exception handling is improuved for Kafka.
oidc
Storgae scopes
without path will be rejected now.
Changelog 8.2.34..8.2.35
- 57ef3621bf
- [maven-release-plugin] prepare release 8.2.35
- 977f84334e
- door,pool: handle multiple possible KafkaExceptions
- 820524c901
- oidc: fix remove invalid testcase
- 1176f2cf8f
- oidc: reject storage scopes without path
- 8cba1f571a
- [maven-release-plugin] prepare for next development iteration
Release 8.2.34
webdav
This patch fixes a bug that led to wrong paths on redirects.
Changelog 8.2.33..8.2.34
- b16cb29733
- [maven-release-plugin] prepare release 8.2.34
- c1bb4b323f
- dcache-qos: correction to the threshold warning
- 644c6577ac
- wevdav: fix redirect path
- 8a157617c9
- [maven-release-plugin] prepare for next development iteration
Release 8.2.33
bulk
No more NPE/stack trace in the bulk PIN
activity.
Online files should not accumulate useless user pins anymore.
cli
No more false stack trace/bug output on the admin shell.
gplazma
dCache will now accept non-targeted explicit AuthZ statements in the scope claim (e.g., storage.read). dCache will consider tokens containing compute explicit AuthZ statements but without any storage explicit AuthZ statements as tokens with explicit authorisation; the lack of any storage explicit authorisation statements will result in all requests with that token being denied.
dCache should continue to accept JWTs for longer, if there is a problem with the OP.
pool
No more logged stack traces due to IllegalStateException: Attribute is not defined: SIZE errors.
Changelog 8.2.32..8.2.33
- 9003926b7a
- [maven-release-plugin] prepare release 8.2.33
- 75fc075a37
- pool: on failed upload set file size to zero for space reporting
- 61ef34d395
- dcache-bulk: guard against erroneous argument names
- a95b429bd5
- dcache-bulk: do not PIN or STAGE files with AL ONLINE
- 999f593d66
- dcache-cli: convert IllegalArgumentException to CommandException on call()
- ea36d479cb
- gplazma: oidc increase cache duration for OP public key material
- 86ac3c4444
- gplazma: oidc update explicit AuthZ parsing
- 10eae1a55e
- [maven-release-plugin] prepare for next development iteration
Release 8.2.32
packages
A problem was fixed that prevented system-test
to run on MacOS.
webdav
This patch reverts the efficiency improvement of the last patch as it may lead to failing requests if set to PERFORMANCE.
Changelog 8.2.31..8.2.32
- b194a511f4
- [maven-release-plugin] prepare release 8.2.32
- f4648fe984
- packages: fix system test populate sed expression
- c2c509aceb
- dcache-webdav: revert improve efficiency of directory listing (14085/14088)
- b9bdc6938e
- doc: clean up the multiple protocol configuration explanation for xroot
- 4f45bcf004
- ci: pin all jobs to dcache-dev runners (temporary)
- 89c22062fb
- [maven-release-plugin] prepare for next development iteration
Release 8.2.31
logback
Redundant replications of unused log files are removed and the qos activity is now recorded as well.
qos
A bug was fixed that let to the message queue being blocked.
webdav
This patch speeds up listing of directories through webdav. All attributes are no longer supported/returned from PROPFIND, unless you set the following property on the WebDav door:
# --- Default PROPFIND properties
#
# The PROPFIND request allows a client to discover information
# (properties) of dCache content. When making a PROPFIND request,
# the client normally indicates which properties are of interest. If
# not specified then the WebDAV server (dCache) is free to return a
# default set of information.
#
# Certain clients make PROPFIND requests without specifying
# the desired set of properties, triggering a default set of
# properties. There are two problems with this: first, the
# clients may react badly if information is missing from this default;
# second, some of the required properties may have an adverse
# performance impact for dCache.
#
# This property controls whether to support client-side requests for
# properties beyond a minimal set or not.
#
# PERFORMANCE -- always return only a minimal set of information that does
# not incur any additional overhead. (These are basically
# the same as what a POSIX list request would proviode).
#
# CLIENT_COMPATIBLE -- return the set of information required by
# the clients. If the client does not specify the properties,
# it will get a maximal default set.
#
# Because the performance impact of the latter under the most common usage scenarios
# could be considerable, the default is set to PERFORMANCE.
#
(one-of?PERFORMANCE|CLIENT_COMPATIBLE)webdav.default-propfind-properties = PERFORMANCE
Changelog 8.2.30..8.2.31
- 55830cf523
- [maven-release-plugin] prepare release 8.2.31
- 636207179f
- dcache-webdav: fix incorrect parameter value given to DcacheDirectoryResource constructor
- 269fbd42df
- dcache-webdav: improve efficiency of directory listing
- 3fd7a8d990
- dcache-qos,dcache-bulk: allow qos update to call engine asynchronously
- 694ef4fe94
- skel,logback: make the .resilience and .qos log files singletons
- c8985d35fb
- [maven-release-plugin] prepare for next development iteration
Release 8.2.30
bulk
Each time a bulk request is started, the container is given a new semaphore based on the number of permits defined for the activity in question. This patch sets the default per-container permit values to something more reasonable.
Changelog 8.2.29..8.2.30
- 6f539cb4db
- [maven-release-plugin] prepare release 8.2.30
- bfa40695c6
- dcache-bulk: adjust semaphore permits to something more reasonable
- c23b711102
- [maven-release-plugin] prepare for next development iteration
Release 8.2.29
dcache-bulk
RT 10496: Odd errors in Bulk logs for some requests in 9.1.0
This ticket uncovered a bug in the abort procedure.
The stored targets were not cancelled on abort. this is now fixed.
dcache-xroot
Improve efficiency of stat list (ls -l
) has been introduced.
ls -l
returns in approximately the
same amount of time as a non-stat listing
ls
.
xrootd4j
Upgraded to 4.5.8 which improves handling/logging of Ssl exceptions.
Changelog 8.2.28..8.2.29
- 3976300fe7
- [maven-release-plugin] prepare release 8.2.29
- b78215d959
- docs: fix external link to nfsmapid and DNS TXT Records docs
- e7fc640849
- dcache-bulk: cancel all stored targets on abort
- 4737f27b79
- common: modify the way the flag on isRestricted works
- 1af82e716a
- dcache-xroot: improve efficiency of stat list (ls -l)
- 2a9e49af9d
- pom.xml: upgrade to xrootd4j 4.5.8
- 5dbcd5e01f
- [maven-release-plugin] prepare for next development iteration
Release 8.2.28
pnfsmanager
List scheduling behavior is now optional.
pnfsmanager.enable.parallel-listing
property variable allows to restore previous behavior - listing requests
are dispatched to a single queue that is prrocessed by multiple parallel workers.
dCache admin can change behavior of listing scheduler.
Changelog 8.2.27..8.2.28
- 6bf80ef559
- [maven-release-plugin] prepare release 8.2.28
- aeaa5f633a
- pnfsmanager: make list scheduling behavior optional (selectable)
- 47369afe25
- [maven-release-plugin] prepare for next development iteration
Release 8.2.27
gplazma
gPlazma incompatibiliti detween version before and after 8.2.13 has been detected.
This is now fixed.
pool
If http client issues two GET requests then zero-copy enabled http mover will try to remove the IdleStateHandler twice and fail with NoSuchElementException.
This is now fixed.
qos
A bug in storing and retrieving tried
value for verify operation has been fixed.
xroot
Modify mkdir to ignore dir exists on make parent option. The result conforms to vanilla xroot server.
Changelog 8.2.26..8.2.27
- 0a106d97a7
- [maven-release-plugin] prepare release 8.2.27
- a441e69f4a
- dcache-gplazma: add serialVersionUID to MultiTargetedRestriction
- 82b171d18c
- pool: handle double remove of IdleStateHandler
- 78dfe046df
- add desc to OIDC properties
- c243b26105
- dcache-qos: fix bug in storing and retrieving ‘tried’ value for verify operation
- 37bef133ed
- dcache-xroot: modify mkdir to ignore dir exists on make parent option
- b8fbec0f04
- [maven-release-plugin] prepare for next development iteration
Release 8.2.26
frontend
All of the REST GET methods now allow anonymous users to get the data if the global property allows it. In the case of NONE, 401 not authorized is returned at login.
nfs
A race condition was fixed that let to sending a READ request to a pool when the mover was alreay stopped.
qos
The behaviour was changed to not scan all pools on startup or periodic rescanning of all pools outside the periodic window.
A bug was fixed that prevented the bulk request to complete.
The error reporting of aborted verification was improved to get a better understanding, what went wrong.
xrootd
A missing vomsdir is now throwing an exception instead of a stacktrace.
xrootd4j
Update xrootd4j to a new version, that fixes a byte buffer leak in ZTNCredentialUtils.
Changelog 8.2.25..8.2.26
- 45fa6ae6ce
- [maven-release-plugin] prepare release 8.2.26
- 4d6b3e0055
- nfs: fix race condition of LAYOUTRETURN and LAYOUTGET
- 60b7c4444b
- xrootd: throw FileNotFoundException if vomsdir doesn’t exist
- b17d8da7b7
- dcache-qos: fix adjuster task cloning to reset state
- 3df0101e39
- dcache-qos: improve exception reported on aborted verification
- 356245bf5e
- ci: add gitlab-ci.yml
- 91f36d8289
- dcache-frontend: remove authz checks in Quota GET methods
- bcc2ebb590
- pom.xml: bump xrootd4j to next version (4.5.7, 4.4.8, 4.3.9, 4.2.13)
- c6bbcde6ae
- dcache-qos: remove trigger to rescan pools on tag change
- e7c9880134
- [maven-release-plugin] prepare for next development iteration
Release 8.2.25
bulk
RuntimeException
s should not cause the request ls
to fail globally.
other
Update our citations file.
pnfs
A modest speed-up of directory listing by not always resolving symlinks when checking restrictions.
qos
Two small incompatibilities with subject and attributes are fixed.
Improvements in triggering QoS operation queues, which reduces the potential for queue starvation.
Changelog 8.2.24..8.2.25
- 37235a0946
- [maven-release-plugin] prepare release 8.2.25
- 68327fdaaf
- dcache-qos(verifier,engine): fix incompatibility issues with Subject and attributes
- f15ba0450a
- dcache-bulk: catch Exception from getSubject()
- 87f87d8d0f
- dcache-qos: repair faulty queue refresh algorithm in verifier
- 316b33a6c5
- dcache,pnfs: skip symlink resolution when checking restrictions on directory children during listing
- 156a3dc1ed
- Update the CITATION.cff version field and date-released field for dCache 8.2.
- 3c892db9e6
- [maven-release-plugin] prepare for next development iteration
Release 8.2.24
webdav
Fixes the webdav dropdown menu layout so it stays in the page.
Changelog 8.2.23..8.2.24
- 60954d17a5
- [maven-release-plugin] prepare release 8.2.24
- f76242757f
- webdav: fix dropdown menu layout
- d104f145ab
- [maven-release-plugin] prepare for next development iteration
Release 8.2.23
bulk
Now REST API (Frontend) distinguishes Not Found
from Invalid
request.
dcache
netty library has been updated to 4.1.92 with minor bugfix release.
metadata
No user- or admin observable changes.
pnfsmanager
Multiple batch jobs executing listings of the same directories especially if directories contain many entries quickly exhaust active threads, each thread executing the same listing, denying listing to all other customers and creating significant load on namespace server (and DB). Clients time out and retry creating even more load on dCache.
This is now fixed and lists of large directories no longer hog PnfsManage denying service to all other list calls. Additionally observed significnat reduction of CPU and IO load on chimera DB host.
webdav
The current release fixed visual element regression after bootstrap 5 upgrade
Changelog 8.2.22..8.2.23
- 3b3a71b8f2
- [maven-release-plugin] prepare release 8.2.23
- 6d1b842ce8
- webdav: fix regression of visual elements with bootstrap 5
- 0ec32afa24
- webdav: fix visual element regression after bootstrap 5 upgrade
- 6e8297f760
- metadata: add (some) ORCIDs to CITATION.cff
- a8a6912fdb
- pnfsmanager: process listings of the same path sequentially, implement list message folding
- e0a838d19f
- dcache-bulk,dcache-frontend: distinguish “Not Found” from “Invalid” request
- 1ef8b526fd
- libs: use netty–4.1.92
- ced6e088c7
- [maven-release-plugin] prepare for next development iteration
Release 8.2.22
bulk
Increase the database column path
to 1024 chars, so ATLAS and others will
not experience failures because paths are too long.
dcache
Symlinks on both constraints and targets are permitted; thus macaroons will also work.
gplazma
If there is a login failure involving a OIDC JWT then potentially important information is now extracted from the JWT and included in the logged login failure report.
POSC works with tokens when user root is ‘/’.
kafka
Change the LoggingProducerListener so that when a TimeoutException is caught, the error message will indicate that there is a connection issue or the broker is down.
nfs
When on LAYOUTGET door returned an error back to the client, then, as the operation failed, the client will not issue LAYOUT_RETURN. Thus such transfers would stay in the door. This is now fixed.
Changelog 8.2.21..8.2.22
- 255e3bb1aa
- [maven-release-plugin] prepare release 8.2.22
- 30a9ab0f68
- dcache-bulk: increase path col to VARCHAR 1024
- 807c9dbc02
- kafka:fix issue 7123 Kafka events fail to post
- 8d6d7c7c68
- gplazma: print selected JWT claims for failed logins
- 05c185fa18
- nfs: remove failed to start read transfers
- 5ac4726788
- Motivation:
- 109ee53f4a
- commons,dcache: alternative symlinks resolution on restrictions
- f7b2ac248f
- [maven-release-plugin] prepare for next development iteration
Release 8.2.21
systemtest
The populate
script now generates a valid dCache configuration if
oidc-agent is installed and at least one configuration has been loaded.
Changelog 8.2.20..8.2.21
- 5750f69569
- [maven-release-plugin] prepare release 8.2.21
- e6f11e3832
- systemtest: fix support for oidc testing
- 1aa9d84f51
- [maven-release-plugin] prepare for next development iteration
Release 8.2.20
bulk
QoS properties have been set to default to WLCG values. Also decreased the number of targets in a shallow request and increased number of threads available for target activities to 200.
qos
Proper handling of the QoSModify requests: propagate the subject downstream to the actual adjustment tasks.
webdav
Correct behaviour on redirect with prefix.
Changelog 8.2.19..8.2.20
- 703caa83d5
- [maven-release-plugin] prepare release 8.2.20
- 5ce3a48cba
- dcache-bulk: reset policy defaults
- bc44544ddd
- webdav: preserve request URL in protocol info
- 9341981052
- dcache-qos: propagate subject to QoS Adjuster
- ed3736f76f
- [maven-release-plugin] prepare for next development iteration
Release 8.2.19
chimera
Fixed a bug that produced SQL errors.
libs
Update nfs4j to 0.24.3 that add fixes in open-stateid handling that aims to fix issues with concurrent opens of a single file by a same client.
nfs
Improve door behaviour.
Changelog 8.2.18..8.2.19
- 18134a9a43
- [maven-release-plugin] prepare release 8.2.19
- 66b8f42edc
- bulk: let bulk propagate Subject for pin/stage
- 06e7cf6783
- Revocation entries are defunct since gplazma–1 is discontinued
- 8dd9a5dd38
- libs: update nfs4j to 0.23.2
- 23454e6f40
- nfs: bind layout disposal to layout state id
- ac9976d7a4
- [maven-release-plugin] prepare for next development iteration
- 86d0179893
- chimera: fix bug in resolve_path stored procedure
Release 8.2.18
bulk
TAPE API: Executing stage request with duplicate file paths ends up with SQL exception in the client output. this is now fixed
frontend
Better error message reporting.
kafka
Ensure, that exception is converted to a string. Better logging.
migration
When broken files were discovered during migration the migration module was going into sleeping state. This is now fixed.
pnfsmanger
The current release fixed migration move/copy going into SLEEP mode when the file on the pool has been deleted.
pool
Now the reduce possibility of stacked movers in CANCELED
state is ensured.
webdav
The observed NPE should disappear.
xrootd4j
update to next xrootd4j version (4.5.6, 4.4.7, 4.3.8, 4.2.12)
Changelog 8.2.17..8.2.18
- 92b16fd404
- [maven-release-plugin] prepare release 8.2.18
- 49a6a4078d
- pnfsmanager: fix migration move/copy going into SLEEP mode when the file on the pool has been deleted
- 6e5e469e96
- migration: fixing sleeping state for broken files
- 09d7ec506b
- nfs: ensure that mover always associated with an open-stateid
- 91f7a8f8a7
- dcache-frontend: improve error message for empty string or non-JSON payload
- 2afcb95f81
- kafka: ensure that errors are logged properly
- 36fab3fee2
- dcache-bulk: add neglected backport of duplicate path check to 8.2
- ce2355574a
- webdav: return empty list instead of null as an empty collection
- dce52665b6
- dcache-frontend: improve Swagger annotations for release and archiveinfo
- f144c99ade
- pom.xml: update to next xrootd4j version (4.5.6, 4.4.7, 4.3.8, 4.2.12)
- 6ca2292651
- pool: ensure that nfs mover completion takes place
- 6e91911c6f
- [maven-release-plugin] prepare for next development iteration
Release 8.2.17
bulk
No more uncaught JSON object key not found exception.
dcache
Application of restrictions is correct in that the ownership and scope of the resolved link is examined.
frontend
Add description to Stage, but also to the generic Bulk request TAPE REST API in the swagger page.
gplazma
It is now possible to configure dCache so the oidc plugin does not check audience fields. This should be used where necessary and only for a short transition period.
An OP declaration now supports the -suppress=offline
argument to force
dCache to query the userinfo endpoint, even if the access token is a
JWT. A warning is logged on startup if offline verification is
suppressed.
pom
Update stable branches to include bug fix to the TPC client behavior so that it establishes a secure connection to its source when the source TLS setting is STRICT.
Changelog 8.2.16..8.2.17
- 9eeb616cca
- [maven-release-plugin] prepare release 8.2.17
- e67aec9c04
- pom.xml: update to next xrood4j version (4.5.5, 4.3.7, 4.2.11)
- f925377d8c
- gplazma: oidc add suppress for audience claim verification
- c50771d802
- gplazma: oidc allow suppression of offline verification
- e4f1fbbb38
- gplazma: oidc add support for suppress option
- b87a8e7628
- dcache-frontend: add more detailed description of request objects for bulk and stage
- 9d1a56eb99
- dcache-bulk: small improvement to RB 13915
- 4ed841fba7
- dcache-bulk: fix JSON object key not found exception
- 18fa39ee27
- dcache,chimera: resolve symlink before applying Restriction
- 36abf271d5
- [maven-release-plugin] prepare for next development iteration
Release 8.2.16
frontend
Use of relative path when issuing mv through the RESTful /api/v1/namespace was broken. This is fixed now.
Changelog 8.2.15..8.2.16
- 0c62c74bab
- [maven-release-plugin] prepare release 8.2.16
- 8af6a7e4df
- dcache-frontend: resolve on parent of source when renaming
- 268ef0b8ff
- [maven-release-plugin] prepare for next development iteration
Release 8.2.16
frontend
Use of relative path when issuing mv through the RESTful /api/v1/namespace was broken. This is fixed now.
Changelog 8.2.15..8.2.16
- 0c62c74bab
- [maven-release-plugin] prepare release 8.2.16
- 8af6a7e4df
- dcache-frontend: resolve on parent of source when renaming
- 268ef0b8ff
- [maven-release-plugin] prepare for next development iteration
Release 8.2.16
frontend
Use of relative path when issuing mv through the RESTful /api/v1/namespace was broken. This is fixed now.
Changelog 8.2.15..8.2.16
- 0c62c74bab
- [maven-release-plugin] prepare release 8.2.16
- 8af6a7e4df
- dcache-frontend: resolve on parent of source when renaming
- 268ef0b8ff
- [maven-release-plugin] prepare for next development iteration
Release 8.2.15
bulk
The Economy and consistency of error metadata for bulk target information listings was improved.
gplazma
dCache now handles malformed .info policies correctly: logging the problem but continuing to allow logins.
xroot
Port is closed now if client prematurely disconnects or the channel goes inactive for some other reason.
Bad login token warning produced by xrdcp clients with versions prior to v5.5.0 are now logged at debug-level
Changelog 8.2.14..8.2.15
- fdbb31c2c6
- [maven-release-plugin] prepare release 8.2.15
- 545da39fc0
- dcache-bulk: remove target error object and always convert to type + message
- 3d57fcf25c
- gplazma: x509 do not report bad .info files as a dCache bug
- 8556643e63
- dcache-xroot: demote bad login token warning to debug
- bea306c310
- dcache-xroot: add missing shutdown on proxy inactive channel
- 6b0aec6629
- [maven-release-plugin] prepare for next development iteration
Release 8.2.14
bulk, frontend
Fixed a bug that lead to inconsistencies of pin lifetime.
docs
The documentation about .well-known endpoints was improved.
frontend
A property was added to optionally turn off the newer implementation of the QoSEngine and revert to the legacy one.
Request for pin without lifetime unit specified works now.
gplazma
The ‘gplazma.oidc.audience-targets’ configuration property now allows values to be placed in double-quote-marks. This is to support ‘aud’ claim values with spaces.
psu
Newly added pgroups are now displayed. Also a bug was fixed that deleted nested pgroups after restart.
qos
QoS can now resolve regex in psu when the regex option is on
.
qos, resilience
The database properties for qos and resilience are now configurable.
telemetry
Caught exceptions are now logged without a stacktrace.
webdav
File transferred with http-tpc preserve extended attributes provided by FTS now.
xroot
Clients should be blocked from pre-emptive removal if a file/directory already exists when doing copy.
Changelog 8.2.13..8.2.14
- 73fa79b2d1
- [maven-release-plugin] prepare release 8.2.14
- 63cb8b6c23
- webdav: respect xattrs for COPY request
- c0c6ff6076
- Lifted the storage unit resolution code out from match method into an auxiliary for reuse (as in master).
- cf39b5b642
- kafka: delete not important log message
- ef70d4e064
- docs: add Xroot User Guide page
- dede55b10c
- gplazma: oidc support ‘aud’ with spaces
- 948b4fce6c
- dcache-qos,psu: allow getStorageUnit to resolve regex
- 326528991b
- dcache-frontend: provide optional legacy qos request in namespace resource
- 74061d2270
- dcache-qos,dcache-resilience: allow db endpoint to have separately configurable properties
- 0e817bd358
- dcache-frontend: convert empty to null when processing TimeUnit attribute
- f6ab530eb4
- dcache-bulk,dcache-frontend: fix bug in tape/stage and in argument extraction from DB
- 765ccc0db2
- docs: add more information concerning support for .well-known
- 67648cbcb1
- dcache-xroot: return kXR_ItExists error code when file exists
- 09759ad1dd
- delete wrongly inserted import
- 6493ec25c2
- telemetry: Don’t log stacktrace for caught expceptions
- 47990f51e6
- psu:fix issue for nested pgroups
- ddbe2ad9af
- [maven-release-plugin] prepare for next development iteration
Release 8.2.13
common
Prevent two potential NPEs in common utility methods.
IndexOutOfBoundsException should not occur during timeseries histogram creation; stack trace is replaced by a logging statement.
gplazma
For xrootd “persist on successful close” (POSC), authorization is successful for both x509 and OIDC/Scitokens.
history
The history service should no longer generate the reported NaN stack trace in the histogram pipeline.
Changelog 8.2.12..8.2.13
- dbe3848748
- [maven-release-plugin] prepare release 8.2.13
- 0d8931c49f
- gplazma: allow upload permissions with MultiTargetRestriction
- 738feb292f
- common: prevent NPE by explict cast of (Double)double in ternary condition
- 9ada6193ae
- commons: add null check to nanToZero method
- 0f1d2d92b3
- dcache-history: avoid NaN stack trace in histogram conversion
- dcfcc598c8
- common: provisional fix for out of bounds error in timeseries histogram
- 95c27cfccb
- [maven-release-plugin] prepare for next development iteration
Release 8.2.12
chimera
There should be less load on the trash table database of the cleaner and thus higher performance.
dcache-xroot
With xrootd.authz.anonymous-operations=READONLY
, anonymous login allows world-readable files to
be read; with xrootd.authz.anonymous-operations=NONE
, it does not allow anonymous operations. This is
for two-party interactions. Third-party copy
with OIDC tokens will work regardless of the
value given to this property.
dcap
Update dcap door to always start mover in a passive mode.
Changelog 8.2.11..8.2.12
- 16823e94e0
- [maven-release-plugin] prepare release 8.2.12
- 1a0b3d5d47
- skel: deprecate unused dcache path for bulk
- ee56f18aff
- dcap: always enforce passive mode
- 3ee440547a
- dcache-xroot: make handling of anonymous restrictions consistent
- ad0b5cd4ac
- pom.xml: update to next xrood4j version (4.5.4, 4.4.5, 4.3.6, 4.2.10)
- a85d43e117
- dcache-chimera: reduce frequency of expensive cleaner inode deletion
- bfa54cf620
- [maven-release-plugin] prepare for next development iteration
Release 8.2.11
docs
Added a note to the user guide that the chart comparing URLs and requirements for stage vs. bulk-requests is out of date.
Changelog 8.2.10..8.2.11
- a37a62acbb
- [maven-release-plugin] prepare release 8.2.11
- 60441acfcc
- docs: update User Guide to reflect correct WLCG URL prefix
- 43627caa10
- [maven-release-plugin] prepare for next development iteration
Release 8.2.10
bulk
Links are handled as they should be when they are refetched from prestored targets and the requests complete.
Expanded directories are now marked as SKIPPED if activity does not apply to directories.
chimera
When receiving a reply from a pool it is no longer waiting for, cleaner-hsm will not send a new delete request or forget the currently-waited-on pool anymore. Logging is added to inform when cleaner-hsm receives a reply from a pool it is no longer waiting for, indicating that the timeout might be too small.
pool
Updated host certificate is available to https mover. Fixed p2p transfers over HTTPS.
skel
Add the necessary deprecations to bulk.properties and qos.properties.
xroot
There should be no longer exceptions reporting no exception handler to handle the exception.
Changelog 8.2.9..8.2.10
- 52aa5e5dd3
- [maven-release-plugin] prepare release 8.2.10
- 13efcaf4ab
- The properties
- 60288e70f3
- skel: add missing property deprecations for qos and bulk
- 6edffbc619
- dcache-bulk: mark expanded directory skipped if activity does not apply to directories
- ed67febf5f
- dcache-bulk: make sure LINK types are handled when refetched from prestored targets
- de291e8cdf
- dcache-xroot: handle outbound errors on channel promise
- 4724df7158
- pool: reload host certificate if changed
- 2fc86e0381
- dcache-chimera: cleaner better handles stale delete reply
- 4654613b02
- [maven-release-plugin] prepare for next development iteration
Release 8.2.9
book
Improved documentation: Sites running proxies need to be aware of the direct-memory consumption of the xroot proxy door.
Add information on domain naming and uniqueness.
dcache-frontend, webdav
A .well-known/security.txt
(see https://securitytxt.org/) is now
exposed on both the webdav (2880) and frontend (3880) ports.
Changelog 8.2.8..8.2.9
- 5e7dcdbe74
- [maven-release-plugin] prepare release 8.2.9
- b0c817b587
- doc: add recommendation for direct memory setting on xrootd proxy door
- fd5404a3ee
- dcache-frontend,webdav: add support for .well-known/security.txt
- 25066ea2ac
- book: add NOTE on domain naming, uniqueness
- 228eca6d31
- [maven-release-plugin] prepare for next development iteration
Release 8.2.8
Bulk
Changed bulk request limits to default values that make a little more sense.
Stack traces from Jdbc and Hikari should not appear on shutdown if activities were in progress.
frontend
Frontend now returns 500 with error message when services are not reachable.
QoS, Frontend
Frontend now returns 500 with error message when services are not reachable.
Pool, Chimera
Prevent NullPointerExceptions in the cleaner and repeating pool restarted messages in PoolManager when pools report null as their connected hsm instances.
Changelog 8.2.7..8.2.8
- 4d22a621a3
- [maven-release-plugin] prepare release 8.2.8
- ec3435f892
- pool,chimera: fix pool pings having a
null
-valued hsm field - 80a4656c69
- dcache-bulk: manage executor and data source shutdown explicitly
- dc727538d2
- dcache-bulk: modify request limits to be something more reasoned
- 57ef15f524
- dcache-frontend: handle parse exceptions in bulk and tape resources
- 8199c72549
- dcache-qos,frontend: add exception to remote client method and return 500 if fails
- d7760adb39
- [maven-release-plugin] prepare for next development iteration
Release 8.2.7
bulk
Version 2 of the Bulk service was not properly supporting the expectation that the target paths of a submitted request be immediately visible to the user who issues a GET on the request. This has now been rectified by storing them in the dedicated database table at arrival rather than when the request begins to run.
chimera
A bug was fixed that threw a NullPointerException when the associated hsms for a pool are stored as null
.
pool
A bug was fixed that falsely triggered idle connection handler on zero-copy transfers.
xroot
The default plugins were reordered to conform to ZTN-first.
Proxying through the door has been fixed so that the IP version used by the proxy client matches what is available on the pools. Before this, proxying through a dual stack door to pools which were IPv4 only was failing. Note also that billing now reflects the door IP as the client of the billing transfer, but maintains the originating IP as the client of the door transaction.
Update xrootd4j to support kXR_prefname in kXR_locate request.
Changelog 8.2.6..8.2.7
- 50b0d9640d
- [maven-release-plugin] prepare release 8.2.7
- 42609539d6
- dcache-chimera: prevent PoolInformationBase NPE
- 70ced3c0b0
- pom.xml: update xrootd4j (4.5.3, etc.)
- e459914203
- dcache-xroot: send door address to pool as client for proxied transfers
- 2a00667418
- pool: disable idle connection handler when zero-copy is used
- 4c82479164
- dcache-xroot: fix the default order for the gplazma plugins
- 286c2db3dc
- dcache-bulk: change long => Long in DAO update to conform with target class
- 58b82a7960
- dcache-bulk: remove redundant update of request target in container start
- 207a18ab4c
- dcache-bulk: insert targets immediately on submit
- 07e977262e
- [maven-release-plugin] prepare for next development iteration
Release 8.2.6
bulk
The bulk service now only locks at the beginning until the namespace has been successfully pinged. All reloading of previous tasks takes place under the covers. Note that the manager still starts only after the reloading activity has completed. Incoming requests will of course be deprioritized as their timestamps are posterior to the reloaded requests.
A bug was fixed that prevented an update of counts reported by info().
Improvements were made to significantly speed-up retrieval of target rows if the table grows to more than 100M.
bulk,frontend
A bug was fixed that prevented cancel on a QUEUED request to move the request from CANCELLING to CANCELLED state. If a BulkRequest contains an empty target list it will now complete and return a 400 BadRequest.
chimera
Cleaner cells that do not have leadership will now more strictly enforce not triggering delete runs.
frontend
Bulk resource target now supports both string and array/list definitions.
nfs-proxy
Proxy-IO with posix locks now works as expected.
xroot
xrdcp –cksum now works again.
Changelog 8.2.5..8.2.6
- 13d40b4fcf
- [maven-release-plugin] prepare release 8.2.6
- c1d972d122
- dcache-xroot: do not publish link local address for door
- ac66330992
- nfs-proxy: use open-stateid when proxying IO request to a pool
- c6ef849424
- dcache-bulk, frontend: fix two small bugs
- 32d7def46c
- dcache-bulk: initialize/load and reset on executor thread
- 6db83a20ee
- dcache-bulk: fix liquibase add index statement to be non-postgresql-specific
- 3e55e61428
- dcache-bulk: fix liquibase so that hsql ignores index CONCURRENTLY
- 1b77dd6612
- dcache-bulk: fix type error in updateCounts
- 6735eba067
- dcache-bulk: add id,rid index on request target table
- c91ec65334
- dcache-chimera: make sure non-leader does not execute clean run
- d7025fad44
- dcache-frontend: make bulk resource target backward compatible with 7.2
- c2ec7a239c
- [maven-release-plugin] prepare for next development iteration
Release 8.2.5
bulk
The garbled request policy command output is fixed now
There was a wrong option for target type (REGULAR, not FILE). This is now fixed and admin commands are now consistent.
nearline-storage
A NPE on error path has been fixed.
The race condition when flushing removed file is fixed now.
poolmanager
Motivation: When a new entry is added to the RequestContainer the file pnfsid and netunit is used as an unique identity. However, despite the fact that two different units are a members of the same unit group, we might get two requests created, thus two stages are triggered. For instance:
0.0.0.0/0.0.0.0 & ::/0 => world-net
00007BBC36AB359E47A383A75CFA2AB6CDEF@0.0.0.0/0.0.0.0-/ m=1 r=1339 [pool_A] [Waiting for stage: pool_A 10.05 16:41:55] {0,}
00007BBC36AB359E47A383A75CFA2AB6CDEF@::/0 m=1 r=1339 [pool_B] [Waiting for stage: pool_B 10.05 16:43:23] {0,}
now it should work with:
00007BBC36AB359E47A383A75CFA2AB6CDEF@world-net-/ m=1 r=1339 [pool_A] [Waiting for stage: pool_A 10.05 17:11:37] {0,}
Changelog 8.2.4..8.2.5
- c9b209d41c
- [maven-release-plugin] prepare release 8.2.5
- 0c4e620bfb
- dcache-bulk: fix garbled request policy command output
- 34a183b4cd
- poolmanager: use net unit groups to identify the request
- 560a641bf6
- nearline-storage: fix race in flushing removed file
- 1d7e7f374c
- dcache-bulk: fix message thread invocation of database query for statistics
- 15868b0e17
- dcache-bulk: fix admin command options (uppercase)
- b663601d0f
- nearline-storage: fix NPE on error path
- 4c432f2b34
- [maven-release-plugin] prepare for next development iteration
Release 8.2.4
dcache-qos
A minor regressions in handling of pool info diffs has been fixed.
Full scan of pool info diff behavior is available.
dcache-rest
A new optional query parameter to retriveve a wealth of information about a file has been added.
frontend
The current release fixed type default of RESTful pool/nearline/queues resource
pool
The pools with disabled HSM operations are not visible to hsm cleaner.
Changelog 8.2.3..8.2.4
- c09832c5a1
- [maven-release-plugin] prepare release 8.2.4
- e7f4a31e3c
- dcache.properties: Fyx synax erorr
- 202ff9aa1a
- dcache-rest namespace resource: add optional query parameter to retrieve a wealth of information about a file
- f83316996a
- dcache-qos: fix minor regressions in handling of pool info diffs
- 0dad875fd0
- pool: don’t publish attached HSM if lfs mode is
precious
- d516bc3e5e
- dcache-frontend: fix type default of RESTful pool/nearline/queues resource
- 29da88f7b3
- pom.xml: bump xrootd4j to 4.5.2
- 0df499cc65
- dcache-qos: fix two more regressions in the PoolOpChangeHandler
- d0c3b0dc00
- dcache-qos: add missing pool tag comparison in PoolOpChangeHandler
- fb82a9f366
- [maven-release-plugin] prepare for next development iteration
Release 8.2.3
bulk
The command \s bulk request submit -activity=STAGE
now overrides the -prestore
option to true. This makes it consistent with the RESTful API.
Cancellation of PIN requests via bulk module which were not marked with -prestore=true no longer fail to complete.
chimera
Pools that are no longer actively being cleaned were previously falsely still listed as active in the admin interface when the cleaning attempt ended due to an exception. This has been fixed.
core
If a pin is unpinned while a pin request for that same pin is still ongoing in pinmanager, pinning will not be retried.
pnfsmanager
On massive uploads (create entries) to a single directory we observed performance degradation leading to all available threads being busy, denying other users from accessing the namespace. This has been alleviated.
pool
The performance of downloading over plain http is increased by using zero-copy mode.
Less CPU load on pools in case of client accessing a file with invalid/expired state id.
xroot
A warning was added to the documentation about the default TLS option,
which changed. OFF
is the only option for TLS which does not
require the presence of the host cert/key.
Changelog 8.2.2..8.2.3
- d108a4d82d
- [maven-release-plugin] prepare release 8.2.3
- d590276b20
- pool: use zero-copy send for plaintext http transfers
- dccb9ccddb
- pool: avoid exception based flow in case of nfs bad stateid error
- a5e1a082fc
- dcache-xroot: add note about TLS and host cert/key to documentation
- b0b922a22e
- dcache-bulk: force admin command STAGE activity to prestore=true, as with REST API
- 4c52046162
- dcache-bulk: fix missing pnfsid on cancel of PIN/STAGE
- f7a7c6c038
- dcache-core: let pinmanager stop retrying pinning upon unpin state
- adb206be77
- pnfsmanager: dispatch create entry messages to threads associated with parent entries
- 4c5ad228ed
- dcache-chimera: disk-cleaner, error handling in parallel pool deletes
- 1e773a6731
- [maven-release-plugin] prepare for next development iteration
Release 8.2.2
spacemanager
Fixes NullPointerException that occurs on startup of space manager when spacemanager.authz.link-group-file-name is not set.
Changelog 8.2.1..8.2.2
- 364638a55a
- [maven-release-plugin] prepare release 8.2.2
- db004422fd
- dcache-spacemanager: fix NPE when link-group-file-name is not set
- 04bdcef478
- [maven-release-plugin] prepare for next development iteration
Release 8.2.1
Changes affecting multiple services
The commands psu match and psux match can now be used with pnfsid or path.
core
ac_psu(x)_match commands has been improved to handle null/globbed values correctly in psu match.
frontend
It is now possible to filter and sort the results of the RESTful API call GET /restores by path, owner and group.
NOTE: This resource is protected by the frontend.authz.unlimited-operation-visibility property, which means that proprietary information can be optionally protected by limiting it to those with admin privileges.
gplazma2-grid
An empty requires field in IGTF policy is now accepted. Files with invalid or unexpected policies are ignored.
webdav
A bug was fixed that caused a NullPointerException while sending Kafka messages.
jquery was updated to version 3.6.1 and bootstrap was updated to version 5.2.1
xroot
The proxy is now bind to a local address that respects the network of the client and is likely reachable by it.
Changelog 8.2.0..8.2.1
- 6d2670057e
- [maven-release-plugin] prepare release 8.2.1
- 6d46d60d8c
- dcache-core,dcache-frontend: add pnfsid and path options to ac psu match and RESTful resource
- dbae6e778c
- dcache: NPE on removal via WebDAV and token
- eff5548052
- webdav: update 3rd party js libraries
- a10630d44c
- dcache-frontend: add filtering and sorting on owner, group and path to restore info API
- ca6486cd98
- dcache-core: handle null/globbed values correctly in psu match
- c2694d4200
- dcache-xroot: explictly close the proxy’s bound port channel
- a6696f9193
- dcache-xroot: select proxy door address on basis of reachability for client
- a0de98f35c
- doc: add recipe to cookbook for migration/draining of resilient pools
- 9a09718207
- [maven-release-plugin] prepare for next development iteration
- c25d4246ef
- qos-engine: prevent NPE if pool monitor not available
- 9c37633ce2
- gplazma2-grid: invalid IGTF policy file should fail with ParserException
Release 8.2.0
Bulk
The bulk service has undergone a major revision. There have been numerous internal changes and enhancements, but the most important have to do with persistence and scalability.
The bulk service now requires a database which holds request information (instead of raw files, as in version 1). Bulk requests are serviced concurrently, but each request runs in its own container in order to optimize threading and I/O.
The UPDATE_QOS activity communicates with (and thus requires the presence of) the new QoS Engine, but the other bulk activities can be run without QoS being present.
Aside from being accessed through frontend REST APIs, the bulk service has a full set of admin shell commands which are useful for spot-checking its operational state and the status of requests (along with their individual targets).
A fuller explanation is available in The Book chapter on the bulk service.
Cleaner
An admin command was added to the cleaner
cell that allows forgetting a pool, meaning removing any corresponding delete target entries from the cleaner’s trash table database. If the requested pool is not currently blacklisted, the admin is required to explicitly enforce the operation.
Frontend
For the bulk-requests API: the typing of primitive parameters in the JSON bulk request has been loosened so that booleans and numerics can also be specified as strings.
The RESTful options for QoS (for instance, in api/v1/namespace) as of version 8.1 communicate with the new QoS Engine.
The JSON returned from GET api/v1/bulk-requests is no longer a simple array of URLs, but an array of objects with fuller info concerning each request (hence this return value now requires parsing; see the SWAGGER page for fuller information). All matching requests are now returned (rather than those owned only by the user), though it is possible to filter the result by a comma-delimited list of user/owner ids.
A new TAPE API has been made available for the purposes of
bulk staging (api/v1/tape); it implements the WLCG TAPE specification,
and thus includes api/v1/tape/archiveinfo [=locality for dCache],
api/v1/tape/stage and api/v1/tape/release [=unpin for dCache].
See the SWAGGER pages for fuller info. There is also a section
in the User Guide (Frontend/BulkRequests) which details the APIs
for bulk-requests and tape along with their differences.
PNFS Manager
Historically, the dCache namespace was allowing hard links on directories. This violates POSIX restrictions and is a source of file system cyclic loops. With dCache release 8.2 creation of hard links on directories is not allowed any more. The existing hard links will work as before; however, it is recommended to replace them with soft links.
To allow pool, nearline storage and other components to make scheduling decisions based on file creation time, PnfsManager will include the CREATION_TIME attribute whenever STORAGEINFO is requested.
Pool
Added rm kill
command that canceles a pending file remove request from HSM.
When a pool decides which storage class to flush it uses the last submission time. However, submission time is re-set when a pool fails to flush the file and re-submit the file. Starting with 8.2, a pool will sort the flushing based on the time when files are created on the pool.
Poolmanager
PoolManager has been updated to support pool groups that contain other pool groups. For example:
psu create pgroup -dynamic -tags=hw-class=IO io-pools
psu create pgroup -dynamic -tags=hw-class=replica replica-pools
psu create pgroup all-pools
psu addto pgroup all-pools @io-pools @replica-pools
The values prefixed by @
in the psu addto pgroup
command are treated as groups.
Resilience / QoS Engine
The fully refactored QoS Engine first became available in 8.1. Among other things, its components are intended to replace Resilience. While Resilience is still available in 8.2, it will eventually be deprecated, so it is advisable to begin switching to QoS with this Golden Release.
There is a chapter on the QoS service components in The Book, which includes instructions on how to set it up to emulate Resilience (the differences are minor).
Note that a major change between Resilience and QoS is that the QoS Verifier uses a database whereas none was used by Resilience.
XRootD
Several improvements have been made so that the door endpoint address is consistently reported.
An important oversight in the door code has been corrected. A client disconnect now also interrupts any thread waiting on a response from PoolManager; otherwise, all available threads could be tied up, potentially blocking further client connections.
The xroot door is now capable of running in “proxy” mode; when this switch is turned on, the client connects through the door instead of directly to the pool in order to read or write data (allowing for outside communication with pools protected on an internal network, for instance). An internal address (subnet) can also be given which will be used for the Pool Manager pool selection. Details are available in the xroot chaper of The Book.
Zookeeper
The Zookeeper version has been updated to the latest stable release 5.7.1
Changelog from 8.1.0 to 8.2.0
- 9a09718207
- [maven-release-plugin] prepare for next development iteration
- 826c56fe3d
- [maven-release-plugin] prepare release 8.2.0
- 283c8b75c3
- nfs4: return EACCESS when stage is not allowed
- 312ea69bdf
- gplazma: vo-group plugin
- 3d04e98d26
- [maven-release-plugin] prepare branch 8.2
- e04424facf
- gplazma: update gplazma config loader to use ParsableFile
- 7f1cdae61b
- gplazma: fix year in copyright statement
- 3829bcd5e9
- common: add hashCode and equals methods for Result
- 317f9a6832
- pool: order storage classes by oldest entry in the queue
- e929f9c0e9
- util,namespace: ensure that files’ creation time is always populated
- e0ebf992f3
- Revert “common: remove orphaned test file”
- 70f97b6766
- common: remove orphaned test file
- 89dbaec931
- gplazma: switch configuration parser to use LineBasedParser
- 31aa21f2f9
- gplazma: refactor ConfigurationParserFactory layer
- ac18e03164
- gplazma: remove dead code
- 5a3b0909aa
- libs: update to the latest stable zk version 3.7.1
- 689f76c38b
- dcache-bulk,dcache-frontend: modify GET for bulk-requests to be somewhat more useful
- 13e497d7b9
- dcache-xroot: add configurable internal address for proxying
- 1624bee957
- common: have ParsableFile return Result
- 32f3dbaeca
- nearline: add
rm kill
command to cancel pending removes from HSM - ad67ecbee2
- src: add benchmark module
- c01b89d6e3
- dcache-xroot: add Book section on direct memory requirements for pools
- 1bcc5ecebb
- dcache-xroot: add optional max write buffer size to decoder
- 2bacd47d70
- webdav: fix NPE if client aborts transfer
- c16d516d4f
- webdav: http-tpc do not keep retrying to cancel transfer
- e1d0d7114e
- src: don’t use repackaged guava
- 8fc9957358
- Revert “src: drop dependency on jython”
- 59fd0d8da8
- gplazma: oidc drop support for ‘gplazma.oidc.hostname’
- 6b5fa34f0c
- src: drop dependency on jython
- c429647bb5
- build(deps): bump jetty-webapp from 9.4.43.v20210629 to 9.4.44.v20210927
- e769dbc7bc
- dcache-xroot: interrupt doOnOpen thread in the event of channel inactive
- 0acb2433ea
- spacemanager: switch linkgroupauthz file to use ParsableFile
- 7bd4abc6c0
- common: add support for discovering file path
- 6310d9c9fc
- spacemanager: remove dead code
- 7a734e3196
- commons: move generic configuration file support
- 2b799c6093
- properties: report that remote transfer manager is replicable
- 9873e45b30
- cleaner: add better cleaner logging
- 0dcd5e4fd2
- dcache-xroot: add section to The Book on proxying through the door
- 858ea9529c
- dcache-xroot: use door address only on PoolManager protocol info
- 16376625c2
- dcache-xroot: add proxying capability to door
- 7cc887929e
- pom.xml: upgrade xrootd4j to 4.4.0
- 651a4e06a8
- Switch to using grep for the java version check.
- e5b49d81a4
- chimera: disallow hard links on directories
- 1222d3d4ee
- pool: switch from Iterable to Collection
- fa9bbd5059
- docs: update SRR documentation to address WLCG complains
- 126560b18c
- dcache-bulk: (version 2) handle unexpected exceptions in container manager
- 4b9fef7833
- build(deps): bump spring-core from 5.2.20.RELEASE to 5.2.22.RELEASE
- e0bd9ce990
- Revert “webdav,dcache: update deprecated netty http usages”
- 8b68eeecdb
- dcache-frontend: move wlcg tape rest resources under common ‘tape’ path
- 7fc973c448
- webdav,dcache: update deprecated netty http usages
- 388c7c3a78
- pool: minor refactor of ReplicaDescriptor
- 4f70939350
- UPDATE_METADATA is needed for staging
- 77f0369431
- pool: finalise on-the-fly checksums on channel close
- 3e9190e04e
- core: update FileAttributes to allow adding extra checksum values.
- 16247d7450
- webdav/httpd/frontend: add HTTP-TPC transfers to transfer list
- 62de9e9759
- 9a09718207
- [maven-release-plugin] prepare for next development iteration
- 826c56fe3d
- [maven-release-plugin] prepare release 8.2.0
- 283c8b75c3
- nfs4: return EACCESS when stage is not allowed
- 312ea69bdf
- gplazma: vo-group plugin
- 3d04e98d26
- [maven-release-plugin] prepare branch 8.2
- e04424facf
- gplazma: update gplazma config loader to use ParsableFile
- 7f1cdae61b
- gplazma: fix year in copyright statement
- 3829bcd5e9
- common: add hashCode and equals methods for Result
- 317f9a6832
- pool: order storage classes by oldest entry in the queue
- e929f9c0e9
- util,namespace: ensure that files’ creation time is always populated
- e0ebf992f3
- Revert “common: remove orphaned test file”
- 70f97b6766
- common: remove orphaned test file
- 89dbaec931
- gplazma: switch configuration parser to use LineBasedParser
- 31aa21f2f9
- gplazma: refactor ConfigurationParserFactory layer
- ac18e03164
- gplazma: remove dead code
- 5a3b0909aa
- libs: update to the latest stable zk version 3.7.1
- 689f76c38b
- dcache-bulk,dcache-frontend: modify GET for bulk-requests to be somewhat more useful
- 13e497d7b9
- dcache-xroot: add configurable internal address for proxying
- 1624bee957
- common: have ParsableFile return Result
- 32f3dbaeca
- nearline: add
rm kill
command to cancel pending removes from HSM - ad67ecbee2
- src: add benchmark module
- c01b89d6e3
- dcache-xroot: add Book section on direct memory requirements for pools
- 1bcc5ecebb
- dcache-xroot: add optional max write buffer size to decoder
- 2bacd47d70
- webdav: fix NPE if client aborts transfer
- c16d516d4f
- webdav: http-tpc do not keep retrying to cancel transfer
- e1d0d7114e
- src: don’t use repackaged guava
- 8fc9957358
- Revert “src: drop dependency on jython”
- 59fd0d8da8
- gplazma: oidc drop support for ‘gplazma.oidc.hostname’
- 6b5fa34f0c
- src: drop dependency on jython
- c429647bb5
- build(deps): bump jetty-webapp from 9.4.43.v20210629 to 9.4.44.v20210927
- e769dbc7bc
- dcache-xroot: interrupt doOnOpen thread in the event of channel inactive
- 0acb2433ea
- spacemanager: switch linkgroupauthz file to use ParsableFile
- 7bd4abc6c0
- common: add support for discovering file path
- 6310d9c9fc
- spacemanager: remove dead code
- 7a734e3196
- commons: move generic configuration file support
- 2b799c6093
- properties: report that remote transfer manager is replicable
- 9873e45b30
- cleaner: add better cleaner logging
- 0dcd5e4fd2
- dcache-xroot: add section to The Book on proxying through the door
- 858ea9529c
- dcache-xroot: use door address only on PoolManager protocol info
- 16376625c2
- dcache-xroot: add proxying capability to door
- 7cc887929e
- pom.xml: upgrade xrootd4j to 4.4.0
- 651a4e06a8
- Switch to using grep for the java version check.
- e5b49d81a4
- chimera: disallow hard links on directories
- 1222d3d4ee
- pool: switch from Iterable to Collection
- fa9bbd5059
- docs: update SRR documentation to address WLCG complains
- 126560b18c
- dcache-bulk: (version 2) handle unexpected exceptions in container manager
- 4b9fef7833
- build(deps): bump spring-core from 5.2.20.RELEASE to 5.2.22.RELEASE
- e0bd9ce990
- Revert “webdav,dcache: update deprecated netty http usages”
- 8b68eeecdb
- dcache-frontend: move wlcg tape rest resources under common ‘tape’ path
- 7fc973c448
- webdav,dcache: update deprecated netty http usages
- 388c7c3a78
- pool: minor refactor of ReplicaDescriptor
- 4f70939350
- UPDATE_METADATA is needed for staging
- 77f0369431
- pool: finalise on-the-fly checksums on channel close
- 3e9190e04e
- core: update FileAttributes to allow adding extra checksum values.
- 16247d7450
- webdav/httpd/frontend: add HTTP-TPC transfers to transfer list
- 62de9e9759
- webdav/transfermanager: support multiple RemoteTransferManager
- 2d59373489
- dcache-bulk: (version 2) ensure container cancellation under RuntimeException
- e240dda600
- build(deps): bump spring-expression
- 0c11b64c5b
- build(deps): bump opensaml from 2.4.1 to 2.6.5
- f48da3140c
- chimera,srm: remove deprecation warning propagateIfInstanceOf
- 97dd8dfe82
- srm,poolmanager: replace buggy murmur3_32 with fixed implementation
- 69b6a3d698
- dcache-frontend,bulk: fix typing of argument values
- f6035f9f39
- dcache-frontend: protect against RuntimeError in case of denied anonymous access
- 7cc8367c9c
- dcache-frontend: bulk-requests POST, allow either string or boolean for boolean values
- fd2b56f637
- poolmanager: add possibility to create nested pool groups.
- 7d79a2210a
- xrootd/pool: Use login token to identify door endpoint
- 22b1a8bcf0
- xrootd: update door to send the pool the advertised endpoint
- 511adea3a2
- core: refactor LoginBrokerProvider
- 6bb0b357b1
- pool: fix enforcecrc checksum policy, always verify expected checksums
- 3d657b140b
- pool: don’t treat an empty file as a sparse file
- c916141a1e
- dcache-core: do not report InterruptedException as bug
- 107c03e87c
- pool-monitor: throttle and limit the number of fetches after start
- 6a593e33f0
- srm-client: fix leftovers from guava migration
- b7d864501d
- libs: use up-to-date guava–31
- 8370c107d6
- dcache-bulk: fix target cancellation
- 83659da6cd
- dcache-bulk: add checks for file type and RP to PIN and STAGE activities
- 208e458211
- dcache-bulk,dcache-frontend,dcache-vehicles: add activity check for WLCG
- 6247095f69
- dcache-bulk: do not return the (internal) root request path with file info
- 9f84650e73
- pool: improve handling empty saved state by scrubber
- 5499f80e18
- src: stop using deprecated CheckedFuture class
- 031b679439
- dcache-xroot,pom.xml: bump xrootd4j to 4.3.1
- 98228466d1
- dcache-qos,skel: parse out qos properties by component and correct the db properties for visibility
- ab0ee3c77e
- system-test,sbin: fix build of tests for bulk and update of database
- 8c3be49c59
- bulk,qos documentation: Add missing image files for TheBook and UserGuide
- 763e2dfbb4
- dcache-bulk,dcache-frontend,documentation: add Bulk version 2 with frontend APIs and documentation
- 319029827a
- Revert “dcache-xroot,pom.xml: bump xrootd4j to 4.3.1”
- ed3794cc85
- dcache-xroot,pom.xml: bump xrootd4j to 4.3.1
- 566800bd2a
- srm-server: don’t use deprecated guava’s CharMatcher#JAVA_LETTER_OR_DIGIT
- abde13cee1
- dcache-xroot: modernize door admin shell commands
- 802f090cad
- dcache-xroot: flesh out channel inactive and exception caught
- 07f21394c0
- info: increase delay between messages
- e84d189d55
- src: explicitly specify
directExecutor
when using guava async - 3e54167c3d
- dcache-info: clean code, improve readability and logged values
- 6d348ec29c
- build(deps-dev): bump gson from 2.8.0 to 2.8.9
- 50aff71517
- Updated instructions for ssh2 keys
- 7e5a17e0e8
- ChimeraVfs: Check file level in addition to inode type when disallowing file size change
- d7e83bf391
- dcache-chimera: add cleaner command to forget a pool
- 4e7abc9ac6
- dcache-chimera: clean code, remove likelihood of NPEs
- 676ac65262
- dcache: updating kafka libs part 2
- b4bd4b90e4
- pool: http-tpc fix NPE if ‘Content-MD5’ response header is absent
- 08d6e791d8
- gplazma: introduce support for observers
- 52820415d1
- pool: http-tpc add more sources of checksum information
- b7f7595b25
- pool: http-tpc refactor remote checksum handling
- 718e3af4df
- pool: switch off IGTF namespace checking (by default) for clients
- 213f9206ca
- dcache:improve documentation for kafka properties
- 5811373f40
- nfs: re-send kill only for write movers
- f703b2661b
- dcache: updating kafka libs
- 1fd2e3b7a0
- frontend: fix NPE in SRR when space information is not available yet.
- 5633b31af0
- [maven-release-plugin] prepare for next development iteration
- f520e9147a
- Fix java version check.
(tbd as soon as the branching is done)