You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The arbitrum documentation's [Archive DA servers] specifies that the option discard-after-timeout must be set to false for DAS S3 archiving, as shown below.
To activate the "archive mode" in your DAS, set the parameter discard-after-timeout to false in your storage method. For example:
--data-availability.s3-storage.discard-after-timeout=false
I set that option to true for pruning S3 Storage after each expiration period of Batch Data, but it didn't work as expected.
Expected behavior
The code snippet demonstrates how the discard-after-timeout option for S3 storage is implemented. Specifically, when s3s.discardAfterTimeout is enabled and the provided timeout value is valid, the code computes an expiration time from the timeout and sets it in the S3.putObjectInput.Expires field. This configuration instructs S3 to automatically expire the stored object after the specified time.
The dasever options discard-after-timeout determines whether or not the HTTP-Expire timeout is set when making data storage API requests to S3. This option has nothing to do with DAS archive mode and appears to be wrong code.
it looks like should set Expiration rather than Expires
// The date and time at which the object is no longer cacheable. For more// information, see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21// (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21).Expires*time.Time
The text was updated successfully, but these errors were encountered:
imelon2
changed the title
DAS: Option discard-after-timeout for DAS S3 storage archiving mode is setting the wrong AWS S3 option.
daserver: Option discard-after-timeout for DAS S3 storage archiving mode is setting the wrong AWS S3 option.
Mar 10, 2025
Describe the bug
The arbitrum documentation's [Archive DA servers] specifies that the option
discard-after-timeout
must be set tofalse
for DAS S3 archiving, as shown below.I set that option to
true
for pruning S3 Storage after each expiration period of Batch Data, but it didn't work as expected.Expected behavior
The code snippet demonstrates how the
discard-after-timeout
option for S3 storage is implemented. Specifically, whens3s.discardAfterTimeout
is enabled and the provided timeout value is valid, the code computes an expiration time from the timeout and sets it in theS3.putObjectInput.Expires
field. This configuration instructs S3 to automatically expire the stored object after the specified time.Permalink
The dasever options
discard-after-timeout
determines whether or not the HTTP-Expire timeout is set when making data storage API requests to S3. This option has nothing to do with DAS archive mode and appears to be wrong code.it looks like should set
Expiration
rather thanExpires
The text was updated successfully, but these errors were encountered: