[ASTERIXDB-1302] Deadlock while trying to drop dataverse of disconnected feed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: ING - Ingestion
• Assignee: Abdullah Alamoudi
• Reporter: Ildar Absalyamov
• Created: 19/Feb/16 07:49
• Updated: 07/Mar/18 23:33
• Resolved: 26/Feb/16 15:02

Description

Consider the following feed definition:

drop dataverse experiments if exists;
create dataverse experiments;
use dataverse experiments;

create type TwitterUserType as closed {
    screen-name: string,
    lang: string,
    friends_count: int32,
    statuses_count: int32,
    name: string,
    followers_count: int32
}

create type TweetMessageType as closed {
    tweetid: int64,
    user: TwitterUserType,
    sender-location: point,
    send-time: datetime,
    referred-topics: {{ string }},
    message-text: string
}

create dataset Tweets(TweetMessageType) primary key tweetid;

create feed TweetFeed using socket_adapter
(
    ("sockets"="127.0.0.1:10001"),
    ("address-type"="IP"),
    ("type-name"="TweetMessageType"),
    ("format"="adm")
);

set wait-for-completion-feed "false";

connect feed TweetFeed to dataset Tweets;
disconnect feed TweetFeed from dataset Tweets;

Even after the feed is in disconnected state any modification operation on dataset\dataverse such as drop would result in a deadlock

 
drop dataverse experiments;