[
https://issues.apache.org/jira/browse/HADOOP-19567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-19567:
------------------------------------
Description:
When you close an s3a filesystem there is a lot of ERROR level stack traces
about a CancellationException -despite that being exactly what is wanted.
Core of it comes from netty.
{code}
Suppressed: software.amazon.awssdk.core.exception.SdkClientException:
Request attempt 1 failure: Unable to execute HTTP request: The connection was
closed during the request. The request will usually succeed on a retry, but if
it does not: consider disabling any proxies you have configured, enabling debug
logging, or performing a TCP dump to identify the root cause. If this is a
streaming operation, validate that data is being read or written in a timely
manner. Channel Information: ChannelDiagnostics(channel=[id: 0x801baead,
L:0.0.0.0/0.0.0.0:59534 !
R:bucket.vpce-0117f6033eaf7aee5-2hxd9fg4.s3.us-west-2.vpce.amazonaws.com/10.80.134.179:443],
channelAge=PT0.676S, requestCount=1, responseCount=0,
lastIdleDuration=PT0.006284125S)
Caused by: java.lang.IllegalStateException: executor not accepting a task
{code}
was:
When you close an s3a filesystem just after initialisation -and before any file
reads have taken place- there is a lot of ERROR level stack traces about a
CancellationException -despite that being exactly what is wanted.
Core of it comes from netty.
{code}
Suppressed: software.amazon.awssdk.core.exception.SdkClientException:
Request attempt 1 failure: Unable to execute HTTP request: The connection was
closed during the request. The request will usually succeed on a retry, but if
it does not: consider disabling any proxies you have configured, enabling debug
logging, or performing a TCP dump to identify the root cause. If this is a
streaming operation, validate that data is being read or written in a timely
manner. Channel Information: ChannelDiagnostics(channel=[id: 0x801baead,
L:0.0.0.0/0.0.0.0:59534 !
R:bucket.vpce-0117f6033eaf7aee5-2hxd9fg4.s3.us-west-2.vpce.amazonaws.com/10.80.134.179:443],
channelAge=PT0.676S, requestCount=1, responseCount=0,
lastIdleDuration=PT0.006284125S)
Caused by: java.lang.IllegalStateException: executor not accepting a task
{code}
> S3A) error stack traces printed on analytics stream factory close
> -----------------------------------------------------------------
>
> Key: HADOOP-19567
> URL: https://issues.apache.org/jira/browse/HADOOP-19567
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.4.2
> Reporter: Steve Loughran
> Priority: Major
>
> When you close an s3a filesystem there is a lot of ERROR level stack traces
> about a CancellationException -despite that being exactly what is wanted.
> Core of it comes from netty.
> {code}
> Suppressed: software.amazon.awssdk.core.exception.SdkClientException:
> Request attempt 1 failure: Unable to execute HTTP request: The connection was
> closed during the request. The request will usually succeed on a retry, but
> if it does not: consider disabling any proxies you have configured, enabling
> debug logging, or performing a TCP dump to identify the root cause. If this
> is a streaming operation, validate that data is being read or written in a
> timely manner. Channel Information: ChannelDiagnostics(channel=[id:
> 0x801baead, L:0.0.0.0/0.0.0.0:59534 !
> R:bucket.vpce-0117f6033eaf7aee5-2hxd9fg4.s3.us-west-2.vpce.amazonaws.com/10.80.134.179:443],
> channelAge=PT0.676S, requestCount=1, responseCount=0,
> lastIdleDuration=PT0.006284125S)
> Caused by: java.lang.IllegalStateException: executor not accepting a task
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
