You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/21 16:08:02 UTC

[jira] [Commented] (ASTERIXDB-2137) Feeds status REST API hangs after a feed is stopped

    [ https://issues.apache.org/jira/browse/ASTERIXDB-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213992#comment-16213992 ] 

ASF subversion and git services commented on ASTERIXDB-2137:
------------------------------------------------------------

Commit 799046dfaaa97e30758ab77e3974d00c1a1ed017 in asterixdb's branch refs/heads/master from [~idleft]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=799046d ]

[ASTERIXDB-2137][ING][API] Prevent REST API hang on stopped feeds

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
1. Due to the ActiveEventListener change, current implementation will
try to issue stats request to stopped feed and never get back. This is
fixed.
2. Now we only request stats for active feeds.
3. When feed stopped, the cached stats will be reinitialized. This is to
prevent users see the previous active stats after immediate start after
stop.

Change-Id: Ifd35ba0e61ac73086c6ba276e1f25a0cd094cf8c
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2085
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <ba...@gmail.com>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>


> Feeds status REST API hangs after a feed is stopped
> ---------------------------------------------------
>
>                 Key: ASTERIXDB-2137
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2137
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Ildar Absalyamov
>            Assignee: Xikui Wang
>
> GET on feed status REST endpoint localhost:19002/admin/active goes into an endless loop and never returns a result if any feed successfully completes or is stopped by the user.
> After the following AQL "curl http://127.0.0.1:19002/admin/active" hangs forever:
> {code}
> drop dataverse test if exists;
> create dataverse test;
> use dataverse test;
> create type TestType as open {
>         "id": int8
> }
> create dataset TestDataset(TestType) primary key id;
> create feed TestFeed using socket_adapter
> (
>     ("sockets"="localhost:10001"),
>     ("address-type"="IP"),
>     //type of the record
>     ("type-name"="TestType"),
>     //format of the record
>     ("format"="adm")
> );
> connect feed TestFeed to dataset TestDataset;
> set wait-for-completion-feed "no";
> start feed TestFeed;
> stop feed TestFeed;
> {code}



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