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 2016/05/03 17:03:12 UTC

[jira] [Commented] (ASTERIXDB-1415) Freezes after feeder is connected

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

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

Commit 6fcf88e4e040946e5556bd4651fb0201b427b356 in incubator-asterixdb's branch refs/heads/master from [~alamoudi]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git;h=6fcf88e ]

ASTERIXDB-1415 Fix Feed Freeze with Indexed Dataset

A feed might cause the system to freeze when connected to
a dataset that has secondary indexes. This case happen if
a frame contains all duplicate records pass the primary index
insert operator. The root cause is that the assign runtime in
the pipeline assumes at least a single record. Hence, a corrupted
tuple will reach the commit operator which will create a bad log
record with a PK of size 0. The log record will cause the log
flusher thread to die.

Change-Id: Ib0fa0bc08cf4224dcf64f83ea72c227f63affc73
Reviewed-on: https://asterix-gerrit.ics.uci.edu/839
Reviewed-by: Till Westmann <ti...@apache.org>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>


> Freezes after feeder is connected
> ---------------------------------
>
>                 Key: ASTERIXDB-1415
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1415
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: Feeds
>            Reporter: Christopher Green
>            Assignee: Abdullah Alamoudi
>
> We're up to about 1.6 million entries and I have recently began adding indices to about 6 fields.  After adding the indices, I connected the classad feeder and the database seems to be non-responsive.  I attempted to stop the instance, but I was unable and was forced to kill running java processes.  Once the processes were killed I was able to stop/start and query the database, but after the feeder was connected the database was back to non-responsive.  
> Please let me know if you need any further information.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)