cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10148) batchlog dtests regression
Date Mon, 24 Aug 2015 23:15:45 GMT


Ariel Weisberg commented on CASSANDRA-10148:

This looks like a dtest or driver change. The driver retries the query 5 times. The first
two it gets the timeout exception it is expecting. Then it looks like failure detection kicks
in and it starts getting unavailable exception and that is the exception that bubbles up to
the test. 

> batchlog dtests regression
> --------------------------
>                 Key: CASSANDRA-10148
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Ariel Weisberg
> {{acknowledged_by_batchlog_not_set_when_batchlog_write_fails_test}} and {{acknowledged_by_batchlog_set_when_batchlog_write_succeeds_test}}
started failing at the same commit on CassCI:
> Looking at the commit where the errors started it's not clear what could have caused
the errors. The errors look something like:
> {code}
> Expecting TimedOutException, got:code=1000 [Unavailable exception] message="Cannot achieve
consistency level THREE" info={'required_replicas': 3, 'alive_replicas': 2, 'consistency':
> {code}

This message was sent by Atlassian JIRA

View raw message