[jira] [Updated] (FLINK-7582) Rest client may buffer responses indefinitely under heavy laod

2019-11-08 Thread Till Rohrmann (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till Rohrmann updated FLINK-7582:
-
Priority: Minor  (was: Major)

> Rest client may buffer responses indefinitely under heavy laod
> --
>
> Key: FLINK-7582
> URL: https://issues.apache.org/jira/browse/FLINK-7582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / REST
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The RestClient uses an executor for sending requests and parsing responses. 
> Under heavy load, i.e. lots of requests being sent, the executor may be used 
> exclusively for sending requests. The responses that are received by the 
> netty threads are thus never parsed and are buffered in memory, until either 
> requests stop coming in or all memory is used up.
> We should let the netty receiver thread do the parsing as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-7582) Rest client may buffer responses indefinitely under heavy laod

2019-11-08 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-7582:
--
Labels: pull-request-available  (was: )

> Rest client may buffer responses indefinitely under heavy laod
> --
>
> Key: FLINK-7582
> URL: https://issues.apache.org/jira/browse/FLINK-7582
> Project: Flink
>  Issue Type: Bug
>  Components: Runtime / REST
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Major
>  Labels: pull-request-available
>
> The RestClient uses an executor for sending requests and parsing responses. 
> Under heavy load, i.e. lots of requests being sent, the executor may be used 
> exclusively for sending requests. The responses that are received by the 
> netty threads are thus never parsed and are buffered in memory, until either 
> requests stop coming in or all memory is used up.
> We should let the netty receiver thread do the parsing as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (FLINK-7582) Rest client may buffer responses indefinitely under heavy laod

2018-12-18 Thread Thomas Weise (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Weise updated FLINK-7582:

Fix Version/s: (was: 1.5.6)

> Rest client may buffer responses indefinitely under heavy laod
> --
>
> Key: FLINK-7582
> URL: https://issues.apache.org/jira/browse/FLINK-7582
> Project: Flink
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Major
>
> The RestClient uses an executor for sending requests and parsing responses. 
> Under heavy load, i.e. lots of requests being sent, the executor may be used 
> exclusively for sending requests. The responses that are received by the 
> netty threads are thus never parsed and are buffered in memory, until either 
> requests stop coming in or all memory is used up.
> We should let the netty receiver thread do the parsing as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-7582) Rest client may buffer responses indefinitely under heavy laod

2018-09-15 Thread Till Rohrmann (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till Rohrmann updated FLINK-7582:
-
Fix Version/s: (was: 1.5.4)

> Rest client may buffer responses indefinitely under heavy laod
> --
>
> Key: FLINK-7582
> URL: https://issues.apache.org/jira/browse/FLINK-7582
> Project: Flink
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.5.5
>
>
> The RestClient uses an executor for sending requests and parsing responses. 
> Under heavy load, i.e. lots of requests being sent, the executor may be used 
> exclusively for sending requests. The responses that are received by the 
> netty threads are thus never parsed and are buffered in memory, until either 
> requests stop coming in or all memory is used up.
> We should let the netty receiver thread do the parsing as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-7582) Rest client may buffer responses indefinitely under heavy laod

2018-09-15 Thread Till Rohrmann (JIRA)


 [ 
https://issues.apache.org/jira/browse/FLINK-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till Rohrmann updated FLINK-7582:
-
Fix Version/s: 1.5.5

> Rest client may buffer responses indefinitely under heavy laod
> --
>
> Key: FLINK-7582
> URL: https://issues.apache.org/jira/browse/FLINK-7582
> Project: Flink
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.5.4, 1.5.5
>
>
> The RestClient uses an executor for sending requests and parsing responses. 
> Under heavy load, i.e. lots of requests being sent, the executor may be used 
> exclusively for sending requests. The responses that are received by the 
> netty threads are thus never parsed and are buffered in memory, until either 
> requests stop coming in or all memory is used up.
> We should let the netty receiver thread do the parsing as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-7582) Rest client may buffer responses indefinitely under heavy laod

2018-05-25 Thread Till Rohrmann (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till Rohrmann updated FLINK-7582:
-
Fix Version/s: (was: 1.5.0)
   1.5.1

> Rest client may buffer responses indefinitely under heavy laod
> --
>
> Key: FLINK-7582
> URL: https://issues.apache.org/jira/browse/FLINK-7582
> Project: Flink
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.5.1
>
>
> The RestClient uses an executor for sending requests and parsing responses. 
> Under heavy load, i.e. lots of requests being sent, the executor may be used 
> exclusively for sending requests. The responses that are received by the 
> netty threads are thus never parsed and are buffered in memory, until either 
> requests stop coming in or all memory is used up.
> We should let the netty receiver thread do the parsing as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FLINK-7582) Rest client may buffer responses indefinitely under heavy laod

2017-10-18 Thread Chesnay Schepler (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chesnay Schepler updated FLINK-7582:

Fix Version/s: (was: 1.4.0)
   1.5.0

> Rest client may buffer responses indefinitely under heavy laod
> --
>
> Key: FLINK-7582
> URL: https://issues.apache.org/jira/browse/FLINK-7582
> Project: Flink
>  Issue Type: Bug
>  Components: REST
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
> Fix For: 1.5.0
>
>
> The RestClient uses an executor for sending requests and parsing responses. 
> Under heavy load, i.e. lots of requests being sent, the executor may be used 
> exclusively for sending requests. The responses that are received by the 
> netty threads are thus never parsed and are buffered in memory, until either 
> requests stop coming in or all memory is used up.
> We should let the netty receiver thread do the parsing as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)