Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selecting cache members for remote execution #26

Closed
hazelcast opened this issue Mar 23, 2012 · 1 comment
Closed

Selecting cache members for remote execution #26

hazelcast opened this issue Mar 23, 2012 · 1 comment
Labels
Source: Internal PR or issue was opened by an employee Type: Enhancement

Comments

@hazelcast
Copy link
Collaborator

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.

@ferhatsb
Copy link

ferhatsb commented Sep 6, 2012

Is this issue still valid ?

As far as I understand from documentation http://www.hazelcast.com/docs/2.3/manual/single_html/#ExecutorService
there are several ways to choose members to execute tasks.

  • on a specific cluster member you choose.
  • on the member owning the key you choose.
  • on the member Hazelcast will pick.
  • on all or subset of the cluster members.

KR.

@mdogan mdogan closed this as completed Aug 21, 2013
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Jan 28, 2020
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
Update README with versions compatibility
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
Add AWS request filtering based on tag value
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Type: Enhancement
Projects
None yet
Development

No branches or pull requests

3 participants