You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide easier way to select members where particular distributed task can be executed.
Currently members can be selected only by addresses/ports, which is "too dynamic" to configure externally.
Adding additional field to Member class (description field, something similar like isSuperClient()) would make filtering easier. Another option would be to enable/disable particular execution services in member configuration.
andrewkornev@hotmail.com said, at 2011-01-03T19:41:47.000Z:
I second that! Near term, you could allow applications to assign an arbitrary name to a node (as part of node configuration maybe) and make the name visible to other grid nodes via Member.getName(). This would make it easier for applications to select specific nodes for task execution.
The text was updated successfully, but these errors were encountered:
Please provide easier way to select members where particular distributed task can be executed.
Currently members can be selected only by addresses/ports, which is "too dynamic" to configure externally.
Adding additional field to Member class (description field, something similar like isSuperClient()) would make filtering easier. Another option would be to enable/disable particular execution services in member configuration.
Migrated from http://code.google.com/p/hazelcast/issues/detail?id=396
earlier comments
andrewkornev@hotmail.com said, at 2011-01-03T19:41:47.000Z:
I second that! Near term, you could allow applications to assign an arbitrary name to a node (as part of node configuration maybe) and make the name visible to other grid nodes via Member.getName(). This would make it easier for applications to select specific nodes for task execution.
The text was updated successfully, but these errors were encountered: