[
https://issues.apache.org/jira/browse/ASTERIXDB-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16714149#comment-16714149
]
ASF subversion and git services commented on ASTERIXDB-2478:
------------------------------------------------------------
Commit 821c072313633f1ef052b167fd0eb679bb7c6e52 in asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=821c072 ]
[ASTERIXDB-2478][NET] Calculate Buffer Remaining Before Reusing It
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- When recycling a buffer, calculate the buffer remaining before
releasing it for reuse to prevent other threads from changing
its remaining.
- Add test case.
Change-Id: Icca3284feae800dd6c37694bdefec3516cd4c506
Reviewed-on: https://asterix-gerrit.ics.uci.edu/3036
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Till Westmann <[email protected]>
> Feed Ingestion stucks 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: jstack-11132018.zip, logs-11132018.zip, 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)
