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

Berenguer Blasi commented on CASSANDRA-13606:
---------------------------------------------

[~adelapena]

- If I understood correctly your first point, I'll log writable (and queryable 
while I am at it) index set 
[here|https://github.com/apache/cassandra/pull/570/files#diff-3f2c8994c4ff8748c3faf7e70958520dR658]
 and we silently ignore writes to a failed index.  +1 on that.
- Correct, I left the 'recovery path' unused as I saw it more as a future 
proofing thing than an actual replacement to the rebuild. I am -1 on adding a 
{{recover_index}}. What if we add to {{rebuild_index}} a {{recover}} param that 
defaults to false? That would be less 'noisy' and backwards compatible etc.

wdyt?

> Improve handling of 2i initialization failures
> ----------------------------------------------
>
>                 Key: CASSANDRA-13606
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13606
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/2i Index
>            Reporter: Sergio Bossa
>            Assignee: Berenguer Blasi
>            Priority: Normal
>             Fix For: 4.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> CASSANDRA-10130 fixes the 2i build management, but initialization failures 
> are still not properly handled, most notably because:
> * Initialization failures make the index non-queryable, but it can still be 
> written to.
> * Initialization failures can be recovered via full rebuilds.
> Both points above are probably suboptimal because the initialization logic 
> could be more complex than just an index build, hence it shouldn't be made 
> recoverable via a simple rebuild, and could cause the index to be fully 
> unavailable not just for reads, but for writes as well.
> So, we should better handle initialization failures by:
> * Allowing the index implementation to specify if unavailable for reads, 
> writes, or both. 
> * Providing a proper method to recover, distinct from index rebuilds.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to