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

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

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

[ASTERIXDB-3219][REPL] Add timeout to log replication

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

Details:

- Do not wait indefinitely for logs to be replicated.

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


> indefinite wait for logs to be replicated
> -----------------------------------------
>
>                 Key: ASTERIXDB-3219
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3219
>             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 can wait indefinitely if logs replication acks are lost. We 
> should have some timeout on that waiting.



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

Reply via email to