[
https://issues.apache.org/jira/browse/CASSANDRA-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-5430:
-----------------------------------------
Attachment: 5430.txt
Right. We need some delay for the node to see enough peers to reach quorum (and
not spam the logs with 'some nodes where not ready'). But even though the setup
only matters once in the cluster lifetime, I still don't want to set it to
RING_DELAY, which is 30 seconds by default - that's too much, considering that
setup() is called after the node has already joined the cluster anyway.
So I made it min(10, StorageService.RING_DELAY) instead. You can override the
delay by lowering RING_DELAY, but it won't exceed 10 seconds.
> Make Auth.SUPERUSER_SETUP_DELAY configurable
> --------------------------------------------
>
> Key: CASSANDRA-5430
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5430
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.2
> Reporter: John Sanda
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Labels: authentication
> Attachments: 5430.txt
>
>
> I would like to make SUPERUSER_SETUP_DELAY configurable for automated tests.
> I have tests that stand up a local cluster, and sometimes if I just run a
> single test class, the total execution time to stand up the (usually two)
> nodes and run the tests takes less than 20 seconds. I am running on fast
> hardware, so I can probably get by with a lower value in most cases, but
> maybe one of my teammates runs on slower hardware and needs a larger value.
> I do not see this as a problem for production use. It would just be nice to
> have it configurable for dev environments.
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
