Re: memory usage problem of Metadata.tokenMap.tokenToHost

There are still a couple of tickets being worked on for 2.1.10 and the release will come afterwards. You can check the list: https://datastax-oss.atlassian.net/browse/JAVA-989?jql=project%20%3D%20JAVA%20AND%20fixVersion%20%3D%202.1.10 On Mon, Jan 4, 2016 at 5:57 AM, joseph gao

Re: memory usage problem of Metadata.tokenMap.tokenToHost

By the way, when would be the version 2.1.10 published? 2015-12-15 10:02 GMT+08:00 joseph gao : > That's great. Thanks, Alex! > > 2015-10-02 0:36 GMT+08:00 Alexandre Dutra : > >> I confirm that the optional schema metadata feature (JAVA-828

Re: memory usage problem of Metadata.tokenMap.tokenToHost

That's great. Thanks, Alex! 2015-10-02 0:36 GMT+08:00 Alexandre Dutra : > I confirm that the optional schema metadata feature (JAVA-828 > ) has been merged > upstream and is included in driver 3.0.0-alpha3 and will

Re: memory usage problem of Metadata.tokenMap.tokenToHost

I confirm that the optional schema metadata feature (JAVA-828 ) has been merged upstream and is included in driver 3.0.0-alpha3 and will as well be included in the forthcoming 2.1.8 version. On a side note, JAVA-664

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Besides the others' advice that 2000+ keyspaces might be too much, the latest Java driver (2.0.11) includes an option to disable the Metadata API http://www.datastax.com/dev/blog/datastax-java-driver-2-0-11-released. I'm not sure at this moment if this has been merged into 2.1 already. On Sun,

Re: memory usage problem of Metadata.tokenMap.tokenToHost

In practice there are not many good reasons to use that many keyspaces and tables. If the use case is multi tenancy then you’re almost always better off just using a combination of version tables and tenantId to give you flexibility as well as separation of client data. If you have that many

Re: memory usage problem of Metadata.tokenMap.tokenToHost

On Sun, Sep 20, 2015 at 9:22 AM, joseph gao wrote: >My application uses 2000+ keyspaces, and will dynamically create > keyspaces and tables. > While I agree with your observation (and think you should file a ticket at issues.apache.org and let the list know the URL)

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Hi Joseph, I think 2000 keyspaces might be just too much. Fewer keyspaces (and CFs) will probably work much better. kind regards, Christian On Tue, Sep 22, 2015 at 9:29 AM, joseph gao wrote: > Hi, anybody could help me? > > 2015-09-21 0:47 GMT+08:00 joseph gao

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Hi, anybody could help me? 2015-09-21 0:47 GMT+08:00 joseph gao : > ps : that's the code in java drive , in MetaData.TokenMap.build: > > for (KeyspaceMetadata keyspace : keyspaces) > { > ReplicationStrategy strategy = keyspace.replicationStrategy(); > Map

memory usage problem of Metadata.tokenMap.tokenToHost

cassandra: 2.1.7 java driver: datastax java driver 2.1.6 Here is the problem: My application uses 2000+ keyspaces, and will dynamically create keyspaces and tables. And then in java client, the Metadata.tokenMap.tokenToHost would use about 1g memory. so this will cause a lot of full gc. As