[
https://issues.apache.org/jira/browse/CASSANDRA-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434713#comment-15434713
]
Sam Tunnicliffe commented on CASSANDRA-12039:
---------------------------------------------
I've rebased both the C* and dtest branches, but I'm still seeing some issues
on the CI runs. The dtest failure on the trunk branch looks unrelated and I
can't repro locally, but the one on the 3.9 branch looks relevant. I've tried
to repro that but it consistently times out for me when run locally.
I'm also concerned about the test counts; the 3.0, 3.9 & trunk runs are
reporting 692, 863 & 669 tests respectively compared to the mainline jobs
reporting 858. As of last night when I kicked off the last run, the custom
dtest branch was completely up to date with riptano/master so I'm not sure how
to account for those discrepancies. I know we had some setup issues recently
which presented like this, but I thought those were all fixed now. Any ideas
[~philipthompson]?
||branch||testall||dtest||
|[12039-3.0|https://github.com/beobal/cassandra/tree/12039-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12039-3.0-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12039-3.0-dtest]|
|[12039-3.9|https://github.com/beobal/cassandra/tree/12039-3.9]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12039-3.9-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12039-3.9-dtest]|
|[12039-trunk|https://github.com/beobal/cassandra/tree/12039-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12039-trunk-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12039-trunk-dtest]|
dtest branch:
[CASSANDRA-12039|https://github.com/beobal/cassandra-dtest/tree/CASSANDRA-12039]
> Add an index callback to be notified post bootstrap and before joining the
> ring
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-12039
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12039
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Sergio Bossa
> Assignee: Sergio Bossa
>
> Custom index implementations might need to be notified when the node finishes
> bootstrapping in order to execute some blocking tasks before the node itself
> goes into NORMAL state.
> This is a proposal to add such functionality, which should roughly require
> the following:
> 1) Add a {{getPostBootstrapTask}} callback to the {{Index}} interface.
> 2) Add an {{executePostBootstrapBlockingTasks}} method to
> {{SecondaryIndexManager}} calling into the previously mentioned callback.
> 3) Hook that into {{StorageService#joinTokenRing}}.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
