[
https://issues.apache.org/jira/browse/FLINK-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910188#comment-16910188
]
TisonKun commented on FLINK-13500:
----------------------------------
As for this issue it is more likely that we should not initialize
BlobStoreServices on HighAvailabilityService's constructor but on
{{#createBlobStore}} called. It would solve this issue in the right way while
we can still think of separating client/server ha services.
> RestClusterClient requires S3 access when HA is configured
> ----------------------------------------------------------
>
> Key: FLINK-13500
> URL: https://issues.apache.org/jira/browse/FLINK-13500
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination, Runtime / REST
> Affects Versions: 1.8.1
> Reporter: David Judd
> Priority: Major
>
> RestClusterClient initialization calls ClusterClient initialization, which
> calls
> org.apache.flink.runtime.highavailability.HighAvailabilityServicesUtils.createHighAvailabilityServices
> In turn, createHighAvailabilityServices calls
> BlobUtils.createBlobStoreFromConfig, which in our case tries to talk to S3.
> It seems very surprising to me that (a) RestClusterClient needs any form of
> access other than to the REST API, and (b) that client initialization would
> attempt a write as a side effect. I do not see either of these surprising
> facts described in the documentation–are they intentional?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
