github-actions[bot] closed issue #9444: Caused by: java.net.SocketException:
Connection reset
URL: https://github.com/apache/iceberg/issues/9444
--
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 s
github-actions[bot] commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-2597166364
This issue has been closed because it has not received any activity in the
last 14 days since being marked as 'stale'
--
This is an automated message from the Apache Gi
github-actions[bot] commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-2408754890
This issue has been automatically marked as stale because it has been open
for 180 days with no activity. It will be closed in next 14 days if no further
activity occurs.
javrasya commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-2005144637
I have a strong feeling that the Timeout error you get is also due to my
buggy code. Just because it does not close the stream when socket closed
exception is received, it ends up g
javrasya commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-2005133969
The code I share earlier @shanzi caused some data loss. It was not closing
the currently open stream, so be careful with that. I am sorry see that my
buggy code above is spreading.
shanzi commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-2003003511
After applied @javrasya 's fix, we no longer encounter the connection reset
error, but sometimes we will get
`org.apache.http.conn.ConnectionPoolTimeoutException`. So I guess it's ver
shanzi commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-2002529412
We are using the new Iceberg 1.5.0 with Flink 1.18.1 and have exactly the
same issue.
Is it possible that Flink will open more connections (especially with the
FLIP-27 sources) or
javrasya commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1904737183
Thank you for jumping in @amogh-jahagirdar . The way it is not literally
unusable for us so I had to write my own S3FileIO together with all the nested
classes so that eventually I
amogh-jahagirdar commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1899706448
There's this old PR: https://github.com/apache/iceberg/pull/4912
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
amogh-jahagirdar commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1899697135
Let me see if I can find that discussion
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abo
pvary commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1895346429
Maybe @jackye1995?
--
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.
javrasya commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1895303601
True, the same file Io can be used for Spark too, I forgot that :-)
Exactly I saw that implementation for retries in the source code. Thanks for
sharing it, it is a good referenc
pvary commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1895290384
> Because it can also be an intermittent network issue for anyone using
Iceberg with Flink and failing the entire stream for that sounds a bit harsh.
For the record, the fix you
javrasya commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1894309851
No idea tbh. It is very hard to address. This does not even happen when I
run it on a standalone Flink cluster running on my local. This happens when my
app runs on AWS Managed Flin
pvary commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1894119990
@javrasya: Why isn't this issue happening outside Flink? Isn't this a more
general S3 issue?
--
This is an automated message from the Apache Git Service.
To respond to the message, p
javrasya commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1893312918
I wrote my own `S3FileIO` which uses a custom `S3InputStream` which retries
when it hits a socket exception and it is all stable that way.
Here is the part I modified with a v
javrasya commented on issue #9444:
URL: https://github.com/apache/iceberg/issues/9444#issuecomment-1886422859
This happens more often when consumption rate is high which is like
replaying historical messages. When I run it in unbounded streaming mode and
use `INCREMENTAL_FROM_EARLIEST_SNAPS
javrasya opened a new issue, #9444:
URL: https://github.com/apache/iceberg/issues/9444
### Apache Iceberg version
1.4.2 (latest release)
### Query engine
Flink
### Please describe the bug 🐞
I am using Flink version 1.15 and trying to consume from an Iceberg
18 matches
Mail list logo
