-
Notifications
You must be signed in to change notification settings - Fork 136
Comparing changes
Open a pull request
base repository: dCache/dcache
base: 10.2.2
head repository: dCache/dcache
compare: master
Commits on Oct 7, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 046511b - Browse repository at this point
Copy the full SHA 046511bView commit details
Commits on Oct 9, 2024
-
dcache: reject access to files with nearline QoS
Motivation: If file has QoS policy "HSM-only" then dCache should reject the access to the file, even if file is still available on disk (as transition might take some time). Modification: - Update QoS policy engine to reflect policy in the namespace attributes - Update Transfer to request policy state (as an indicate of applied policy) and reject read transfers if access latency is nearline. Result: dCache behavior compliant with selected QoS policy. Acked-by: Lea Morschel Acked-by: Dmitry Litvintsev Target: master Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 1a3c12e - Browse repository at this point
Copy the full SHA 1a3c12eView commit details -
pool manager: retry request on pool up
Motivation: If a pool with the file is online and a tape copy available, then dCache will trigger stage and wait until file is restored on disk. However, if pool becomes available again, the stage request is not interrupted and client will wait for tape. Modification: Update request container 'onPoolUp' logic to retry the request if the file expected to be on that pool. Added unit test to validate the behavior. Result: pool selection succeeds then a pool with the file becomes online despite the on-going stage request. NOTE (1): the stage request is not interrupted NOTE (2): if newly enabled pool doesn't contains the expected file, then double stage is very likely. Target: master Acked-by: Lea Morschel Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for f945c3d - Browse repository at this point
Copy the full SHA f945c3dView commit details -
Configuration menu - View commit details
-
Copy full SHA for cd9c90d - Browse repository at this point
Copy the full SHA cd9c90dView commit details -
Configuration menu - View commit details
-
Copy full SHA for e697949 - Browse repository at this point
Copy the full SHA e697949View commit details -
Configuration menu - View commit details
-
Copy full SHA for 703e5e0 - Browse repository at this point
Copy the full SHA 703e5e0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 43a6082 - Browse repository at this point
Copy the full SHA 43a6082View commit details
Commits on Oct 14, 2024
-
build(deps): bump org.eclipse.jetty:jetty-servlets
Bumps org.eclipse.jetty:jetty-servlets from 9.4.52.v20230823 to 9.4.54.v20240208. --- updated-dependencies: - dependency-name: org.eclipse.jetty:jetty-servlets dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Configuration menu - View commit details
-
Copy full SHA for c18934e - Browse repository at this point
Copy the full SHA c18934eView commit details
Commits on Oct 15, 2024
-
Merge pull request #7680 from dCache/dependabot/maven/org.eclipse.jet…
…ty-jetty-servlets-9.4.54.v20240208 build(deps): bump org.eclipse.jetty:jetty-servlets from 9.4.52.v20230823 to 9.4.54.v20240208
Configuration menu - View commit details
-
Copy full SHA for 2e4e416 - Browse repository at this point
Copy the full SHA 2e4e416View commit details -
build(deps): bump org.eclipse.jetty:jetty-server
Bumps org.eclipse.jetty:jetty-server from 9.4.52.v20230823 to 9.4.55.v20240627. --- updated-dependencies: - dependency-name: org.eclipse.jetty:jetty-server dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Configuration menu - View commit details
-
Copy full SHA for 8254b67 - Browse repository at this point
Copy the full SHA 8254b67View commit details -
Merge pull request #7679 from dCache/dependabot/maven/org.eclipse.jet…
…ty-jetty-server-9.4.55.v20240627 build(deps): bump org.eclipse.jetty:jetty-server from 9.4.52.v20230823 to 9.4.55.v20240627
Configuration menu - View commit details
-
Copy full SHA for 53e6665 - Browse repository at this point
Copy the full SHA 53e6665View commit details -
http(old): modernize color palette
Motivation: match dcache.org page colors Modification: pulled colors into css variables synced colors across pages fixed html generation Result: new look-and-feel Acked-by: Lea Morschel Target: master, 10.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 7e2040e - Browse repository at this point
Copy the full SHA 7e2040eView commit details
Commits on Oct 21, 2024
-
Target: master Requires-notes: no Requires-book: no Acked-by: Lea Morschel
Configuration menu - View commit details
-
Copy full SHA for cbff12d - Browse repository at this point
Copy the full SHA cbff12dView commit details
Commits on Oct 23, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 8d83ed5 - Browse repository at this point
Copy the full SHA 8d83ed5View commit details
Commits on Oct 28, 2024
-
xroot: handle haproxy and checksum command
Motivation: ---------- When using xrootd doors behind an HAProxy w/ `xrootd.enable.proxy-protocol=true` it has been discovered that ``` xrdcp --cksum adler32:<value> <source> <destiation> ``` hangs after upload has completed and then eventually fails after a timeout. This is due to xrootd door repoting actual door address to the client. Modification: ------------- Return destination address (that is haproxy address) if `xrootd.enable.proxy-protocol=true` is set. Result: ------- ``` xrdcp --cksum adler32:<value> <source> <destiation> ``` works as expected (and likely many other similar commands) Target: trunk Request: 10.* Request: 9.2 Patch: https://rb.dcache.org/r/14338/ Acked-by: Tigran Require-book: no Require-notes: yes Signed-off-by: Dmitry Litvintsev <litvinse@fnal.gov>
Configuration menu - View commit details
-
Copy full SHA for e98ab94 - Browse repository at this point
Copy the full SHA e98ab94View commit details
Commits on Nov 5, 2024
-
bulk/qos: shutdown executor services when stopped
Motivation: As scheduled executors are not shutdown cleanly, when dcache stops running threads logged. Modification: shutdown ConcurrentRequestManager and adjuster-executor when dcache stopped. Result: less stack traces in logs. Acked-by: Lea Morschel Target: master, 10.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 5f67bdd - Browse repository at this point
Copy the full SHA 5f67bddView commit details
Commits on Nov 6, 2024
-
tape REST api: additional fix tohandling of prefixed paths
Motivation: ----------- Users reported 2 day pin lifetime on staged files (which is a default) despite specifying different values. This is due to failure to match target key on truncated vs prefixed path in target argument map keyed on un-prefixed paths. Modification: ------------- Use full target paths throughout the system. Make sure to strip prefix when exposing paths to users. Result: ------- Observe correct user specified pin lifetime. Ticket: #7687 Patch: https://rb.dcache.org/r/14339/ Target: trunk Request: 10.2, 10.1, 10.0, 9.2 Require-book: no Require-notes: yes Signed-off-by: Dmitry Litvintsev <litvinse@fnal.gov>
Configuration menu - View commit details
-
Copy full SHA for fff8b79 - Browse repository at this point
Copy the full SHA fff8b79View commit details
Commits on Nov 12, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 404dc6d - Browse repository at this point
Copy the full SHA 404dc6dView commit details
Commits on Nov 15, 2024
-
docs: correcting typos in chapter 2
Motivation: found some typos Modification: removal of typos Result: no more typos Acked-by: Target: master Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for 47ef9a7 - Browse repository at this point
Copy the full SHA 47ef9a7View commit details
Commits on Nov 18, 2024
-
Configuration menu - View commit details
-
Copy full SHA for d92fdf1 - Browse repository at this point
Copy the full SHA d92fdf1View commit details
Commits on Nov 19, 2024
-
docs: update to the minimal dCache installation
Motivation: the minimal dCache installation file contained some confusing information Modification: wording, information, links, general aesthetic, structure Result: A more user friendly installation ...maybe? Acked-by: Tigran Mkrtchyan Target: master Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for 6a3e899 - Browse repository at this point
Copy the full SHA 6a3e899View commit details
Commits on Nov 20, 2024
-
cells: ignore empty core domain uris propagated by zk
Motivation: When Zookeeper updates core domain infos, dCache will first kill the existing cell tunnels and then later try to read and parse the new value. If the new value is an empty string (for whatever reason), parsing will fail, but a new connection will not be established. The corresponding error in the log: 18 Nov 2024 08:45:00 (c-dcache-head-xxx03_messageDomain-AAYmVA1LtnA-AAYmVA16phA) [dcache-head-xxx03_messageDomain,9.2.21,CORE] Error while reading from tunnel: java.net.SocketExceptio> 18 Nov 2024 08:45:43 (c-dcache-head-xxx03_messageDomain-AAYnKxn40fA) [] Uncaught exception in thread TunnelConnector-dcache-head-xxx03_messageDomain java.lang.NullPointerException: null at java.base/java.net.Socket.<init>(Socket.java:448) at java.base/java.net.Socket.<init>(Socket.java:264) at java.base/javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:277) at dmg.cells.network.LocationManagerConnector.connect(LocationManagerConnector.java:64) at dmg.cells.network.LocationManagerConnector.run(LocationManagerConnector.java:94) at dmg.cells.nucleus.CellNucleus.lambda$wrapLoggingContext$2(CellNucleus.java:725) at java.base/java.lang.Thread.run(Thread.java:829) Modification: before killing existing tunnel check that ZK didn't propagate empty data. Result: More roust cell communication NOTE: a non empty invalid data still accepted!!! Fixes: #7696 Acked-by: Lea Morschel Target: master, 10.2, 10.1, 10.0, 9.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 30829c9 - Browse repository at this point
Copy the full SHA 30829c9View commit details -
docs: diagram on successful write workflow
Motivation: Got curious about what the flow of a client writing to a file would look like. Modification: Adding two mermaid diagrams that show the flow of a successful write for supported protocols, specifically steps 14 and 15. Result: Help someone understand some concepts better. Acked-by: Tigran Mkrtchyan Target: master Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for 4b922a1 - Browse repository at this point
Copy the full SHA 4b922a1View commit details -
vehicles: support door requesting multiple checksums
Motivation: A client that is uploading a file or initiating an HTTP TPC pull transfer may wish to validate the transfer did not result in data corruption, using the new file's checksum / digest value. When receiving a file, the pool will calculate a set of checksums (from different checksum algorithms) based on the pool's configuration. This configured list of checksum algorithms might not include the client's desired checksum algorithm. One solution would be for the pool configuration to be updated, to include the client's desired checksum. Although technically possible, this is impractical, as it would require the person transferring the data to negotiate with the dCache admins, asking them to update the pool configuration for all pools their transfer might use. Such support operations are undesirable. As an alternative approach, the WebDAV door accepts a `Want-Digest` HTTP request header on PUT and COPY (HTTP-TPC) requests. The door uses this header to select a single desired checksum algorithm. This algorithm (if provided) is transferred to the pool, which then ensures that this algorithm is calculated during the file upload. A dCache instance may provide storage to multiple communities, with different conventions on which algorithm is use for data integrety. A client initiating a transfer between these communities (using dCache as an intermediate) would require two checksums: one to verify data integrety of the transfer to dCache and another to validate transferred within the second community. Modification: The ProtocolInfo subclasses are updated to carry a collection of algorithms, taking care to maintain backwards compatibility. Result: No user- or admin observable change, but dCache now supports a door requesting multiple checksum algorithms when a pool receives a file. Target: master Request: 10.2 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14341/ Acked-by: Tigran Mkrtchyan
Configuration menu - View commit details
-
Copy full SHA for 9023cea - Browse repository at this point
Copy the full SHA 9023ceaView commit details
Commits on Nov 27, 2024
-
weghtedPools -> weightedPools Acked-by: Paul Millar Target: master Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for 69f5c77 - Browse repository at this point
Copy the full SHA 69f5c77View commit details -
cells: remove backward compatibility 7.0
Motivation: The initial implementation of tls support cell tunneling used `/dcache/lm/core-config` file to flag dcache to start inter-cell tunnels in plain of tls modes. This have been later replaces with urls syntax tcp:// and tls://. The old code left in place for backward compatibility, so, time to drop. Modification: Remove handling of `/dcache/lm/core-config` ZK node. Removed commands `get/set core-config` Result: Less dead code. Acked-by: Lea Morschel Target: master Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for b63677e - Browse repository at this point
Copy the full SHA b63677eView commit details -
jvm: drop UseCompressedOops JVM option
Motivation: Starting java7, the UseCompressedOops is dynamically controed by heap size. ``` $ java -Xmx32g -XX:+PrintFlagsFinal 2>/dev/null | grep UseCompressedOops bool UseCompressedOops = false {product lp64_product} {default} $ java -Xmx28g -XX:+PrintFlagsFinal 2>/dev/null | grep UseCompressedOops bool UseCompressedOops = true {product lp64_product} {ergonomic} ``` The mismatch between UseCompressedOops endup with error: ``` OpenJDK 64-Bit Server VM warning: Max heap size too large for Compressed Oops ***** WARNING! INCORRECT SYSTEM CONFIGURATION DETECTED! ***** The system limit on number of memory mappings per process might be too low for the given [gc] max Java heap size (40960M). Please adjust /proc/sys/vm/max_map_count to allow for at [gc] least 73728 mappings (current limit is 65530). Continuing execution with the current ``` Modification: drop UseCompressedOops JVM option from defaults. Result: correct behavior on JVMs with large heap Acked-by: Lea Morschel Target: master Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 59ea69f - Browse repository at this point
Copy the full SHA 59ea69fView commit details
Commits on Dec 3, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 103bfeb - Browse repository at this point
Copy the full SHA 103bfebView commit details
Commits on Dec 4, 2024
-
pool: allow
max disksize
to be specified as percent of filesystemMotivation: To avoid disk dise miscalculations, it will be useful if pool is configured not with an absolute pool size, but with a percentage of available space. Modification: Update `set max diskspace` to accept percentage. Update space calculation to use percentage of filesystems total size, if configured. Result: simplified pool configuration ``` set max diskspace 94% ... Limits for maximum disk space File system (limit) : 547735052288 (94%) Statically configured: - Runtime configured : - ``` Acked-by: Dmitry Litvintsev Target: master Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 8c71927 - Browse repository at this point
Copy the full SHA 8c71927View commit details -
Configuration menu - View commit details
-
Copy full SHA for 289e9f1 - Browse repository at this point
Copy the full SHA 289e9f1View commit details
Commits on Dec 6, 2024
-
cells: always try to re-establish dead tunnel, unless stopped
Motivation: As long as cell tunnel is not explicitly stopped by calling dmg.cells.network.LocationManagerConnector#stopped, other interrupts should be ignored. Modification: Update retry logic to never give up, unless _isRunning flag set to false. Result: More robust tulles in case of network issues. Issue: #7707, #5326 Acked-by: Dmitry Litvintsev Target: master, 10.2, 10.1, 10.0, 9.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 600ed1f - Browse repository at this point
Copy the full SHA 600ed1fView commit details -
qos: QOS fails with 'Attribute is not defined: QOS_POLICY'
Motivation: Find out where in the code we throw the above error and resolve it. Modification: Removal of redundant qos policy logic. Result: Instead of checking if the qos_policy attribute is defined AND null, we will check if it is present using one of the predefined methods. If not, set it to null and resume previous logic. Acked-by: Tigran Mkrtchyan Target: master, 10.2, 10.1, 10.0, 9.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 8b9dfb3 - Browse repository at this point
Copy the full SHA 8b9dfb3View commit details -
bulk: handle absolute/relative paths in uniform fashion
Motivation: ----------- Recent change(s) that massaged user input target paths and stored absolute paths on bulk backend lead to ambiguity between user provided and dcache resolved paths and also resulted in inability to use full paths (i.e. only relative paths are supported). At Fermilab we need to use both - relative and absolute paths Modification: ------------- Revert all recent changes that appended prefix to user supplied paths, stored the result and then stripped the prefix so that only "original" paths are exposed to the user. Instead, like before, store user supplied paths but carry over request prefix which is computed from user root and door root. When calling PnfsManager using paths the full paths of the targets are reassembled using the prefix Result: ------ Restored ability to use absolute paths when using REST API. Issue: #7693 Patch: https://rb.dcache.org/r/14355/ Target: trunk Request: 10.2, 10.1, 10.0, 9.2 Require-book: no Require-notes: yes Acked-by: Lea Morschel, Tigran Mkrtchyan
Configuration menu - View commit details
-
Copy full SHA for 484e967 - Browse repository at this point
Copy the full SHA 484e967View commit details
Commits on Dec 13, 2024
-
bulk: update message returned when trying to stage a file present on …
…disk Motivation: as per ticket #10666 when a user tries to stage a file from disk it is an illegal transition. Modification: update message displayed to user. Result: user will know this is intended functionality. Acked-by:Lea Morschel Target: master Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for abe4bd9 - Browse repository at this point
Copy the full SHA abe4bd9View commit details
Commits on Dec 19, 2024
-
pool: separate cases for disk error and no space available
Motivation when there are no avvailable space on a pool, the pool will go to DISABLED mode and no data could be read anymore. This is wrong we still want to be able to read data from the file. Modification this is a temp change, trying to get the info from the eroor message, sice therer is no a specific error code, and then based on that info separate two cases DISABLED AND READONLY Acked-by: Tigran Mkrtchyan Target: master. 10.2, 10.1, 10.0, 9.2 Require-book: no Require-notes: yes Commited:master@862963e
Configuration menu - View commit details
-
Copy full SHA for bfbf240 - Browse repository at this point
Copy the full SHA bfbf240View commit details
Commits on Dec 20, 2024
-
migration: new
MigrationModule
option and copy completion message**Motivation** allow modified replication behavior to support hotspot mitigation. Specifically we need replication jobs to complete without error when the number of replicas is maximized with respect to the available pools, even if more replicas were requested. **Modification:** * In `Job.java`: `Error` -> `Note`. The names of all related methods are changed accordingly (e.g. `addError()` -> `addNote()`). * `MigrationModule` gets new option `-target-deficit-mode=(wait|limit)` (default `wait`) determining behavior when requested replicas exceeds target pool availability: * `wait` The job will wait for new pools to become available (e.g. added to specified pool group). This is the default. * `limit` If more replicas are requested than exist available pools, the job will complete successfully (with a note) when the number of replicas is maximized for the pools currently available. * In interface `TaskCompletionHandler`: new method `taskCompletedWithNote(Task, String)` with default implementation forwarding to `taskCompleted(Task)`. * New (manually-generated) files `Task_sm.dot`, and `Task_sm.dot.png` showing the state machine model encoded by `Task.sm`. * New method in `Task.java`: `moreReplicasPossible()` for use in state transition guards. * New finite state machine (FSM) action `notifyCompletedWithInsufficientReplicas()` in `Task.java`. * In `Task.sm`, `Done` entry action `notifyCompleted()` removed in favor of per-transition actions `notifyCompleted()`, or `notifyCompletedWithInsufficientReplicas()` as appropriate. It was determined by analysis that moving the post-state-change entry action to a pre-state-change transition did not disrupt the intended semantics of the state machine. * New guarded transitions to `Done` when more replicas are requested than are possible with the target pools available currently. * `Task_sm.dot`, and `Task_sm.dot.png` updated manually to reflect the changes to the state machine. **Result:** * Partially implements #7675 * Replication jobs can be issued with `-target-deficit-mode=limit` to terminate successfully when all pools available currently have been populated with replicas, but more replicas were requested. **Target:** master **Request:** - **Patch:** https://rb.dcache.org/r/14362/ **Closes:** **Requires-notes:** yes **Requires-book:** **Acked-by:** Tigran Mkrtchyan, Dmitry Litvintsev
Configuration menu - View commit details
-
Copy full SHA for f41cd3e - Browse repository at this point
Copy the full SHA f41cd3eView commit details
Commits on Jan 20, 2025
-
everthing --> everything Acked-by: Marina Sahakyan Target: master Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for 693fffa - Browse repository at this point
Copy the full SHA 693fffaView commit details
Commits on Jan 27, 2025
-
utils: use JFR events to track door interaction with other cells
Motivation: for slow transfers we want to be able to see how long cell communications took time. This information can be collected with java flight recorder. Modification: Update Transfer class to record JFR events when interaction with other cells takes place. The mover stop implementation uses an addition event holder, as mover kill uses notification, thus no callback. Result: message interaction information visible in JFR. ``` $ jfr print --categories dCache /tmp/dCacheDomain_12455560939331420208.jfr | head -20 (git)-[transfer-jfr] org.dcache.door.Messages { startTime = 09:45:35.672 duration = 37.8 ms message = "PnfsGetFileAttributes" Source = "NFS-nairi@dCacheDomain" Destination = "PnfsManager" eventThread = "proc-9" (javaThreadId = 73) stackTrace = [ org.dcache.util.Transfer.lambda$readNameSpaceEntryAsync$2(Transfer$MessageEvent, boolean, PnfsGetFileAttributes) line: 818 org.dcache.cells.CellStub.lambda$transformAsync$3(AsyncFunction, Message) line: 559 com.google.common.util.concurrent.AbstractTransformFuture$AsyncTransformFuture.doTransform(AsyncFunction, Object) line: 223 com.google.common.util.concurrent.AbstractTransformFuture$AsyncTransformFuture.doTransform(Object, Object) line: 210 com.google.common.util.concurrent.AbstractTransformFuture.run() line: 123 ] } ... ``` Acked-by: Lea Morschel Target: master Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 3b12aa7 - Browse repository at this point
Copy the full SHA 3b12aa7View commit details -
chimera: on shutdown propagate close to DB specific driver
Motivation: If chimera DB driver is statefull it might require an explicit close on shutdown. Modification: Add FsSqlDriver#close method that is called by JdbcFs#close. Result: better handling of db resources. Acked-by: Paul Millar Target: master Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for 76fe850 - Browse repository at this point
Copy the full SHA 76fe850View commit details -
Bulk: PinManagerActivity do not set state of files that are pinned in…
…definitely to SKIPPED Motivaton: ---------- Setting files having infinite pin to state SKIPPED seems to prevents them from being staged if pool goes down. Modification: ------------- Set state to COMPLETED if pin lifetime is infinite. Result: ------ As tested and reported by DESY, the staging of files that happen to be on offline pools works properly Target: trunk Request: 10.2 Request: 9.2 Patch: https://rb.dcache.org/r/14365/ Require-notes: yes Require-book: no
Configuration menu - View commit details
-
Copy full SHA for 2b5f8bc - Browse repository at this point
Copy the full SHA 2b5f8bcView commit details
Commits on Jan 29, 2025
-
libs: update Liquibase to 4.29.2
Motivation: due to compatibility breaking changes (in particular the type which is used for BLOBs) in Liquibase we ware unable to update Liquibase version. As a result, enhancements and bug fixes. liqubase uses id+author to identify changesets. In case of collisions the behavour is unpredictable, in particular, with liquibase 4.xx the wrong changeset is selected for validation. Modification: Add DB specific conditional statement to explicitly handle incompatibility. To ensure unique author+id combination. Add a concept of changeset-pre that will update checksums in databasechangelog to match new calculation rules (whitespace included vs excluded) and match checksums to new ids. `dcache database update` command as well as auto-migrate are updates to apply `pre` changes before the main change set. Result: Up-to-date liquibase version. Acked-by: Lea Morschel Acked-by: Chris Green Target: master Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 68f7ffe - Browse repository at this point
Copy the full SHA 68f7ffeView commit details
Commits on Jan 30, 2025
-
dcache-billing-indexer: add explicit dependency on commons-io
Motivation: the dcache-billing-indexer uses commons-compress to handle bz2 files, and has non-optional dependency on commons-io, which is missing. So we get: ``` /usr/sbin/dcache-billing-indexer -index /var/lib/dcache/billing/2025/01/billing-2025.01.27.bz2 ERROR - Uncaught exception java.lang.NoClassDefFoundError: org/apache/commons/io/input/CloseShieldInputStream at org.dcache.services.billing.text.Indexer$7.openStream(Indexer.java:526) at com.google.common.io.ByteSource$AsCharSource.openStream(ByteSource.java:474) at com.google.common.io.CharSource.readLines(CharSource.java:371) at org.dcache.services.billing.text.Indexer.produceIndex(Indexer.java:510) at org.dcache.services.billing.text.Indexer.index(Indexer.java:396) at org.dcache.services.billing.text.Indexer.(Indexer.java:211) at org.dcache.services.billing.text.Indexer.main(Indexer.java:686) Caused by: java.lang.ClassNotFoundException: org.apache.commons.io.input.CloseShieldInputStream at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525) ... 7 common frames omitted ``` Modification: explicitly add commons-io into dcache-billing-indexer classpath. Result: dcache-billing-indexer can process compressed files. Fixes: #7738 Acked-by: Lea Morschel Tested-by: Ville Salmela Target: master, 10.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 153a018 - Browse repository at this point
Copy the full SHA 153a018View commit details
Commits on Jan 31, 2025
-
cells: fix race condition between thread start and flag check
Motivation: If newly started thread runs before `running` flag is set, then tunnel with shutdown instantly. Thread-1: Create T2 --> | T2.start() | --> set running flag Thread-2: | check flag; exit | Modification: set `running` before thread starts. Result: race is fixed Issue: #5326 Acked-by: Paul Millar Target: master, 10.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 2440b22 - Browse repository at this point
Copy the full SHA 2440b22View commit details
Commits on Feb 4, 2025
-
billing: database fixes necessitated by Liquibase update
Motivation: [Patch](https://rb.dcache.org/r/13594/) updating Liquibase to version 4.29 omitted a necessary checksum change for a changeset for the optional billing system. Modification: * Create a new changeset for the billing system with highest priority to update the defective checksum in the DB prior to any other changesets being evaluated. * Add a new `bean` to ensure that the new changeset is loaded prior to any others. Result: Billing system will start correctly with Liquibase 4.29. Target: master Patch: https://rb.dcache.org/r/14369 Requires-notes: no Requires-book: no Acked-by: Dmitry Litvintsev
Configuration menu - View commit details
-
Copy full SHA for 705a6dd - Browse repository at this point
Copy the full SHA 705a6ddView commit details
Commits on Feb 7, 2025
-
pool: add workaround space mismanagementd by XFS (and others?)
Motivation: Some filesystems miscalculate/report free space in respect tu used space: ``` $ df /dcache/pool-a Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 558602657792 558397210232 205447560 100% /dcache/pool-a $ du -s /dcache/pool-a 554502450484 /dcache/pool-a $ bc 558602657792 - 554502450484 4100207308 ``` File system reports 200GB of the free space, however, total - real used gives ~4TB. Thus dCache assumes 4TB and write the file system full... ==> IO error Modification: use an `effective` free space, which is the minimum between disk reported and internal accounting free spaces. Result: Pool uses the effective free space instead of mathematically correct value. Acked-by: Dmitry Litvintsev Target: master, 10.2 Require-book: no Require-notes: yes
Configuration menu - View commit details
-
Copy full SHA for 208bfbe - Browse repository at this point
Copy the full SHA 208bfbeView commit details
Commits on Feb 11, 2025
-
qos: Uncaught NullPointerException due to QoS being set to null
Motivation: null is a valid value for FileAttribute.QOS_POLICY, however, it is not a valid value to be encapsulated within an Optional. Modification: Update Optional.of for Optional.ofNullable since the later will take into account null as a value and return Optional.empty() where Optional.of will not and hence throw the NPE. Result: QosPolicy can still be set to null and we will no longer show a NPE. Acked-by: Dmitry Litvintsev Target: master, 10.2, 10.1, 10.0 and 9.2 Require-book: no Require-notes: no
Configuration menu - View commit details
-
Copy full SHA for 466c97e - Browse repository at this point
Copy the full SHA 466c97eView commit details
There are no files selected for viewing