You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Till (JIRA)" <ji...@apache.org> on 2018/11/12 22:11:00 UTC
[jira] [Updated] (ASTERIXDB-2478) Feed Ingestion stuck after
ingesting millions records.
[ https://issues.apache.org/jira/browse/ASTERIXDB-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till updated ASTERIXDB-2478:
----------------------------
Summary: Feed Ingestion stuck after ingesting millions records. (was: Feed Ingestion stucks after ingesting millions records.)
> Feed Ingestion stuck after ingesting millions records.
> ------------------------------------------------------
>
> Key: ASTERIXDB-2478
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2478
> Project: Apache AsterixDB
> Issue Type: Bug
> Affects Versions: 0.9.4
> Reporter: Taewoo Kim
> Assignee: Murtadha Hubail
> Priority: Major
> Attachments: logs2.tar.gz
>
>
> This is the new cloudberry cluster that consists of five NUC machines. Originally, about three months ago, we were able to ingest 1.2 billion records to this cluster. The day before yesterday, we started ingesting our tweet records using the current master branch. After ingesting 70 million records, the feed process was not progressing at all. The log record at that moment did not show any particular errors.
> [~idleft] and [~luochen01] investigated this issue and suggested us to try another commit (b2eb44177e7ac6bd180c7bc325cf007fb925c9e2) to see whether it works. It does not work. The symptom happened again.
>
> Here, (1) the log records for the current master and (2) the log records for the commit b2eb44177e7ac6bd180c7bc325cf007fb925c9e2 are attached.
> (1) [https://drive.google.com/file/d/1LZNPjcIvZXbYYk53wZ4Pc6emfjCwFrUi/view?usp=sharing]
> (2) logs2.tar.gz (see the attachment)
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)