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

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

Commit 5f076a8347df9a45634914c76b4117b38b5731a6 in asterixdb's branch 
refs/heads/master from Murtadha Makki Al Hubail
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=5f076a8347 ]

[ASTERIXDB-3221][REPL] Use IO scheduler for replication ops

- user model changes: no
- storage format changes: no
- interface changes: no

Details:

- To allow concurrent replication operations, use the IO scheduler
  to schedule the operations using the exact same scheduling logic
  as the flush operations.
- Maximum concurrent replication operations = maximum concurrent flush
  operations.
- Allow connections to replicas to be recycled and reused by the
  replication operations and close them when no more pending operations.
- Do not halt on replicate operations failures since failures are
  expected and replicas can be re-synced.

Change-Id: I82aeb60381f90a254ca99274f7e9a38f64bc7a46
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17635
Reviewed-by: Ali Alsuliman <ali.al.solai...@gmail.com>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>


> Slow pending replication operations processing
> ----------------------------------------------
>
>                 Key: ASTERIXDB-3221
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3221
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: REPL - Replication
>    Affects Versions: 0.9.8
>            Reporter: Murtadha Makki Al Hubail
>            Assignee: Murtadha Makki Al Hubail
>            Priority: Major
>              Labels: triaged
>             Fix For: 0.9.9
>
>
> Currently, we allow up to (2 * number of partitions) concurrent flush 
> operations. However, we have a single replication worker processing the newly 
> generated LSM components. This results in slow pending replication operations 
> processing. We should allow concurrent replication operations processing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to