[jira] [Updated] (FLINK-12336) Handles HTTPS InfluxDB database Endpoint
[ https://issues.apache.org/jira/browse/FLINK-12336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Etienne Carriere updated FLINK-12336: - Summary: Handles HTTPS InfluxDB database Endpoint (was: Handle HTTPS InfluxDB database Endpoint) > Handles HTTPS InfluxDB database Endpoint > > > Key: FLINK-12336 > URL: https://issues.apache.org/jira/browse/FLINK-12336 > Project: Flink > Issue Type: Improvement > Components: Runtime / Metrics >Affects Versions: 1.8.0 >Reporter: Etienne Carriere >Priority: Major > Fix For: 1.9.0 > > > Currently, the flink-metrics-influxdb connector works only with HTTP InfluxDB > Endpoint. > Proposal : manages HTTPS InfluxDB Endpoint -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-12336) Handle HTTPS InfluxDB database
Etienne Carriere created FLINK-12336: Summary: Handle HTTPS InfluxDB database Key: FLINK-12336 URL: https://issues.apache.org/jira/browse/FLINK-12336 Project: Flink Issue Type: Improvement Components: Runtime / Metrics Affects Versions: 1.8.0 Reporter: Etienne Carriere Fix For: 1.9.0 Currently, the flink-metrics-influxdb connector works only with HTTP InfluxDB Endpoint. Proposal : manages HTTPS InfluxDB Endpoint -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-12336) Handle HTTPS InfluxDB database Endpoint
[ https://issues.apache.org/jira/browse/FLINK-12336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Etienne Carriere updated FLINK-12336: - Summary: Handle HTTPS InfluxDB database Endpoint (was: Handle HTTPS InfluxDB database) > Handle HTTPS InfluxDB database Endpoint > --- > > Key: FLINK-12336 > URL: https://issues.apache.org/jira/browse/FLINK-12336 > Project: Flink > Issue Type: Improvement > Components: Runtime / Metrics >Affects Versions: 1.8.0 >Reporter: Etienne Carriere >Priority: Major > Fix For: 1.9.0 > > > Currently, the flink-metrics-influxdb connector works only with HTTP InfluxDB > Endpoint. > Proposal : manages HTTPS InfluxDB Endpoint -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-9560) RateLimiting for FileSystem
[ https://issues.apache.org/jira/browse/FLINK-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Etienne CARRIERE updated FLINK-9560: Description: *Pain*: On our system, we see that during checkpoint , all the bandwidth is take to send the checkpoint to object storage (s3 in our case) *Proposal* : After the creation of some limitation on Filesystem (mostly number of connections with the tickets FLINK-8125/FLINK-8198/FLINK-9468), I propose to add ratelimiting "per Filesystem" . *Proposal of implementation* : Modify LimitedConnectionsFileSystem to add a ratelimiter on both Input and OutputStream. was: *Pain*: On our system, we see that during checkpoint , all the bandwidth is take to send the checkpoint to object storage (s3 in our case) *Proposal* : After the creation of some limitation on Filesystem (mostly number of connections with the tickets FLINK-8125/FLINK-8198/FLINK-9468), I propose to add ratelimiting "per Filesystem" . Proposal of implementation : Modify LimitedConnectionsFileSystem to add a ratelimiter on both Input and OutputStream. > RateLimiting for FileSystem > --- > > Key: FLINK-9560 > URL: https://issues.apache.org/jira/browse/FLINK-9560 > Project: Flink > Issue Type: Improvement > Components: FileSystem >Affects Versions: 1.5.0 >Reporter: Etienne CARRIERE >Priority: Major > > *Pain*: On our system, we see that during checkpoint , all the bandwidth is > take to send the checkpoint to object storage (s3 in our case) > *Proposal* : After the creation of some limitation on Filesystem (mostly > number of connections with the tickets FLINK-8125/FLINK-8198/FLINK-9468), I > propose to add ratelimiting "per Filesystem" . > *Proposal of implementation* : Modify LimitedConnectionsFileSystem to add a > ratelimiter on both Input and OutputStream. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-9560) RateLimiting for FileSystem
[ https://issues.apache.org/jira/browse/FLINK-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Etienne CARRIERE updated FLINK-9560: Description: *Pain*: On our system, we see that during checkpoint , all the bandwidth is take to send the checkpoint to object storage (s3 in our case) *Proposal* : After the creation of some limitation on Filesystem (mostly number of connections with the tickets FLINK-8125/FLINK-8198/FLINK-9468), I propose to add ratelimiting "per Filesystem" . Proposal of implementation : Modify LimitedConnectionsFileSystem to add a ratelimiter on both Input and OutputStream. was: *Pain*: On our system, we see that during checkpoint , all the bandwidth is take to send the checkpoint to object storage (s3 in our case) *Proposal* : After the creation of some limitation on Filesystem (mostly number of connections with the tickets FLINK-8125/FLINK-8198/FLINK-9468), I propose to add ratelimiting "per Filesystem" . Proposal of implementation : Modify LimitedConnectionsFileSystem to add a ratelimiter on both Input and OutputStream. Current issue : I would like to use the guava RateLimiter that is a good ratelimiter but it is guava and so not included in flink (dependency clash with hadoop) if I am right. What would be a right strategy in this case ? > RateLimiting for FileSystem > --- > > Key: FLINK-9560 > URL: https://issues.apache.org/jira/browse/FLINK-9560 > Project: Flink > Issue Type: Improvement > Components: FileSystem >Affects Versions: 1.5.0 >Reporter: Etienne CARRIERE >Priority: Major > > *Pain*: On our system, we see that during checkpoint , all the bandwidth is > take to send the checkpoint to object storage (s3 in our case) > *Proposal* : After the creation of some limitation on Filesystem (mostly > number of connections with the tickets FLINK-8125/FLINK-8198/FLINK-9468), I > propose to add ratelimiting "per Filesystem" . > Proposal of implementation : Modify LimitedConnectionsFileSystem to add a > ratelimiter on both Input and OutputStream. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-9560) RateLimiting for FileSystem
Etienne CARRIERE created FLINK-9560: --- Summary: RateLimiting for FileSystem Key: FLINK-9560 URL: https://issues.apache.org/jira/browse/FLINK-9560 Project: Flink Issue Type: Improvement Components: FileSystem Affects Versions: 1.5.0 Reporter: Etienne CARRIERE *Pain*: On our system, we see that during checkpoint , all the bandwidth is take to send the checkpoint to object storage (s3 in our case) *Proposal* : After the creation of some limitation on Filesystem (mostly number of connections with the tickets FLINK-8125/FLINK-8198/FLINK-9468), I propose to add ratelimiting "per Filesystem" . Proposal of implementation : Modify LimitedConnectionsFileSystem to add a ratelimiter on both Input and OutputStream. Current issue : I would like to use the guava RateLimiter that is a good ratelimiter but it is guava and so not included in flink (dependency clash with hadoop) if I am right. What would be a right strategy in this case ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLINK-8793) Only key with password are hidden in Flink web interface
Etienne CARRIERE created FLINK-8793: --- Summary: Only key with password are hidden in Flink web interface Key: FLINK-8793 URL: https://issues.apache.org/jira/browse/FLINK-8793 Project: Flink Issue Type: Bug Components: REST Affects Versions: 1.4.1 Reporter: Etienne CARRIERE Fix For: 1.5.0 Currently, we going in /jobmanager/config on the web interface, the value of the key containing "password" are replaced by "" When using s3 for checkpoint/savepoint configuration on an infrastructure which is not on AWS (where IAM is not possible), the s3.secret-key is revealed from the interface. I propose the same behaviour as key with "password" for key with "secret" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-8793) Hide key containing "secret" in web interface
[ https://issues.apache.org/jira/browse/FLINK-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Etienne CARRIERE updated FLINK-8793: Summary: Hide key containing "secret" in web interface (was: Only key with password are hidden in Flink web interface) > Hide key containing "secret" in web interface > - > > Key: FLINK-8793 > URL: https://issues.apache.org/jira/browse/FLINK-8793 > Project: Flink > Issue Type: Bug > Components: REST >Affects Versions: 1.4.1 >Reporter: Etienne CARRIERE >Priority: Minor > Fix For: 1.5.0 > > > Currently, we going in /jobmanager/config on the web interface, the value of > the key containing "password" are replaced by "" > When using s3 for checkpoint/savepoint configuration on an infrastructure > which is not on AWS (where IAM is not possible), the s3.secret-key is > revealed from the interface. > I propose the same behaviour as key with "password" for key with "secret" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
