RussellSpitzer commented on issue #15306:
URL: https://github.com/apache/iceberg/issues/15306#issuecomment-3893033376

   That's interesting, I don't think I've ever seen this behavior before. Do
   you have any more details about your writers? How many are there? What
   other code might be running? Are you using S3?
   
   On Thu, Feb 12, 2026 at 4:40 AM Lukas Valatka ***@***.***>
   wrote:
   
   > *astronautas* created an issue (apache/iceberg#15306)
   > <https://github.com/apache/iceberg/issues/15306>
   > Apache Iceberg version
   >
   > 1.10.1
   > Query engine
   >
   > Spark > 4
   > Please describe the bug 🐞
   >
   > Hey,
   >
   > We are experimenting with Spark 4 and Iceberg 1.10.1 setup. We noticed a
   > peculiar issue. We tried to activate
   > write.metadata.delete-after-commit.enabled=true for one of our tables to
   > make sure metadata-log entry does infinitely grow. It unfortunately failed,
   > with 500. Apparently the latest metadata.json.metadata-log references some
   > metadata.json files that are no more on cloud storage.
   >
   > We have exhausted the options of trying to find-out why the file got
   > deleted. It is rather unfortunate that we cannot remove old metadata now
   > since this file is missing. Maybe we're incorrectly running
   > write.metadata.delete-after-commit.enabled?
   > Willingness to contribute
   >
   >    - I can contribute a fix for this bug independently
   >    - I would be willing to contribute a fix for this bug with guidance
   >    from the Iceberg community
   >    - I cannot contribute a fix for this bug at this time
   >
   > —
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/iceberg/issues/15306>, or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/AADE2YMDT2V6VBR6FVQDUY34LRYE7AVCNFSM6AAAAACU4ODIH2VHI2DSMVQWIX3LMV43ASLTON2WKOZTHEZTCNRVHE2DINY>
   > .
   > You are receiving this because you are subscribed to this thread.Message
   > ID: ***@***.***>
   >
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to