SpaceManager: Message processing failed: Attribute is not defined: SIZE #7211
Labels
Comments
|
Hi Carlos, thanks for reporting. I checked and there is already an issue for this problen: #7162. I am closing the other one as it is not as detailed. Which version are you running? |
|
Sorry, I should have added it before. 8.2.15 |
lemora
added a commit
to lemora/dcache
that referenced
this issue
Sep 28, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: dCache#7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
lemora
added a commit
to lemora/dcache
that referenced
this issue
Sep 28, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: dCache#7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
This was referenced Sep 28, 2023
lemora
added a commit
to lemora/dcache
that referenced
this issue
Sep 28, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: dCache#7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
lemora
added a commit
to lemora/dcache
that referenced
this issue
Sep 28, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: dCache#7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
This was referenced Sep 28, 2023
lemora
added a commit
to lemora/dcache
that referenced
this issue
Sep 28, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: dCache#7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
lemora
added a commit
that referenced
this issue
Oct 5, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: #7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
lemora
added a commit
that referenced
this issue
Oct 5, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: #7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
lemora
added a commit
that referenced
this issue
Oct 5, 2023
Motivation: Sometimes, when an upload fails, it results in a replica of size 0 that is then flagged to be removed (ReplicaState.REMOVED). The finished transfer is nevertheless reported to SpaceManager when the serice exists. It requires the file size to be defined, which may not have been set in such cases, leading to an exception being logged. In general, we should make sure that the file size is set properly when a transfer finishes, whether it is successful or not. SpaceManager should ignore a `DoorTransferFinishedMessage` only when it reports a CacheException: the corresponding file is gone from the name space. Otherwise, even if the file size is not defined, it should update its database to reflect that the file of size 0 bytes is stored. It should receive a `PnfsDeleteEntryNotificationMessage` on removal of the actual namespace entry later on, which will trigger the correct removal of the space manager database entry. Modification: On failure, when the replica size is 0, update the file attributes accordingly before setting the replica into state `REMOVED`. Additionally, safeguard SpaceManager by storing a file size of 0 when the SIZE attribute in the `DoorTransferFinishedMessage` is not defined and log a warning. Result: No more logged stack traces due to `IllegalStateException: Attribute is not defined: SIZE` errors. Target: master Request: 9.0 Request: 8.2 Request: 8.1 Request: 8.0 Fixes: #7211 Requires-notes: yes Requires-book: no Patch: https://rb.dcache.org/r/14061/ Acked-by: Tigran Mkrtchyan
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
The transfer seems to fail as the source is not able to provide the size of the file.
The billing log shows this note I anonymized the source site DNS using XXXXXX
SpaceManager cell is reporting this, should not log this if the transfer the size of the file is not supplied?:
The text was updated successfully, but these errors were encountered: