asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xikui Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ASTERIXDB-1906) Throw exception when socket server address is occupied.
Date Thu, 11 May 2017 21:16:04 GMT

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

Xikui Wang commented on ASTERIXDB-1906:
---------------------------------------

[~tillw] It's not easy. One intuitive solution could be test the connection when user submitting
the query, but this also cannot guarantee that by the time the feed job reaches the designated
node, this port is still available. I'm working on extending the RestAPI to expose the feed
stats to users. I think this could be one way for user to know their feed adapter is not working
properly.

> Throw exception when socket server address is occupied.
> -------------------------------------------------------
>
>                 Key: ASTERIXDB-1906
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1906
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>            Reporter: Xikui Wang
>            Assignee: Xikui Wang
>
> Currently, if the address is occupied when starting the socket adapter, the exception
will be thrown at backend, but front user will get a successful response. It would be good
to throw an exception and let user know the feed is not started.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message