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

Reduce (Map-Reduce) support for entry processor #827

Closed
enesakar opened this issue Aug 29, 2013 · 2 comments
Closed

Reduce (Map-Reduce) support for entry processor #827

enesakar opened this issue Aug 29, 2013 · 2 comments
Assignees
Labels
Source: Internal PR or issue was opened by an employee Type: Enhancement

Comments

@enesakar
Copy link
Contributor

No description provided.

@ghost ghost assigned enesakar Aug 29, 2013
@pveentjer
Copy link
Contributor

The current approach is dangerous because the resulting map is fully kept in memory.

Christopher also has been working on a map/reduce solution. I think it would be a good idea to look at that. We should prevent that we get a lot of similar but a little bit different solutions in the system. I would rather have a single solution that is configurable.

@pveentjer
Copy link
Contributor

The thing I'm also worried about using the entry processor, is that it will run on top of the partition (operation) thread. If there for example are a million entries in a given partition, no other operations can be executed during the processing of these million map entries and this could cause not only starvation problems (to other partitions.. and not only of this particular map.. but to all distributed objects within a given member), it can also lead to uncontrollable members; partitions operations can't be executed.

@mdogan mdogan closed this as completed May 28, 2014
@mmedenjak mmedenjak added Internal breaking change Source: Internal PR or issue was opened by an employee and removed Internal breaking change labels Jan 28, 2020
devOpsHazelcast pushed a commit that referenced this issue Feb 26, 2024
GitOrigin-RevId: 180d4b5e7a2d7ec2e4c3c05888af7c631b06267a
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

4 participants