[
https://issues.apache.org/jira/browse/CASSANDRA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743446#action_12743446
]
Arin Sarkissian edited comment on CASSANDRA-299 at 8/14/09 2:09 PM:
--------------------------------------------------------------------
but instances_ is only used in Table.open() and the constructor's private...
should be pretty safe IMO.
Table.open() is the only public interface to the constructor or _instances...
aka its the only public way to get a Table
was (Author: phatduckk):
but instances_ is only used in Table.open() and the constructor's
private... should be pretty safe IMO.
Table.open() is the only public interface to the constructor or _instances...
> make table directory creation lazy
> ----------------------------------
>
> Key: CASSANDRA-299
> URL: https://issues.apache.org/jira/browse/CASSANDRA-299
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
> Fix For: 0.5
>
> Attachments:
> 0001-lazy-creation-of-Table-dirs.-only-open-tables-that-h.patch
>
>
> checking that each subdir for each table is present on startup -- _every_
> startup -- could be a real pita.
> i think that to support 100k tables (not impossible, in a
> hosted-cassandra-as-a-service scenario) we're going to want to make table dir
> creation lazy.
> then we would want to make scanning for sstables faster by only doing one
> listdir call per datadir, to see which table subdirs are present, and then
> checking only those for sstable files. this would involve some re-org of the
> onstart code.
> (note that we don't want to prune directories if there are no sstables left
> in them, since we'd end up re-creating them at some point anyway; we just
> want to allow the lack of a table subdir to imply the same thing as an empty
> one.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
