jpmoore40 wrote
> Just for info I'm currently using the TcpDiscoveryJdbcIpFinder for grid
> discovery and partition my worker nodes using attributes e.g.
> clusterName=xxx. Is it possible to use the jdbc finder on the same
> database to specify separate grids, or would I need to set up a separate
> database for each grid? I prefer to use the jdbc method rather than hard
> coding the servers using TcpDiscoveryVmIpFinder.Thanks for any info
Hi Jonathan,
Expanding a little on what Andrey wrote above:
You can locate separate grids (clusters) within the same database, by
storing the details in separate tables. To do this, when you create
TcpDiscoverJdbcIpFinder, you can pass a custom implementation of
JdbcIpFinderDialect that accepts a table name as a parameter. If you
compare with the BasicJdbcIpFinderDialect implementation in the code you'll
easily see how to do it.
class ParameterisedJdbcDialect implements JdbcIpFinderDialect{ public
ParameterisedJdbcDialect(String tableName) { this.tableName =
tableName; } private String tableName; @Override public String
tableName() { return tableName; }}
Best regards
Mike
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Loading-a-native-library-on-a-grid-node-tp11227p11573.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
