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 2019/04/10 18:32:00 UTC
[jira] [Updated] (ASTERIXDB-2365) Various LSM IO Operations
Shouldn't Simply Share the Same Write Queue
[ https://issues.apache.org/jira/browse/ASTERIXDB-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till updated ASTERIXDB-2365:
----------------------------
Affects Version/s: 0.9.4
> Various LSM IO Operations Shouldn't Simply Share the Same Write Queue
> ---------------------------------------------------------------------
>
> Key: ASTERIXDB-2365
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2365
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: STO - Storage
> Affects Versions: 0.9.4
> Reporter: Chen Luo
> Priority: Major
>
> Currently the BufferCache has a single writer queue for all write operations (mainly for LSM component bulkloading). However, without a smart scheduling algorithm, this causes unnecessary stalls for short duration operations (e.g., flush) if some heavy operation (e.g., large merge) is ongoing. It is necessary to develop some sort of I/O scheduling algorithm to ensure short duration operations are not blocked by those longer ones.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)