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

Implement disk persistence feature in Hazelcast #22

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

Implement disk persistence feature in Hazelcast #22

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

See http://groups.google.com/group/hazelcast/browse_thread/thread/a51547df2e558c17

Migrated from http://code.google.com/p/hazelcast/issues/detail?id=330

@mdogan mdogan removed the ACCEPTED label May 16, 2014
@mdogan mdogan closed this as completed May 16, 2014
@karussell
Copy link

As this is not implemented I think, I would really like to have at least a configuration option which makes 'local' databases or files possible. The problem is that the MapStore interface assumes a central database, see my question here

@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
Avoid caching temporary DNS lookup failures
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
SeriyBg pushed a commit to SeriyBg/hazelcast that referenced this issue Jul 9, 2021
…azelcast#30)

* fixes for hazelcast-aws Github issues hazelcast#29 and hazelcast#22

* fixes for checkstyle errors

* fixes for checkstyle errors

* extended strategy factory tests

* removed Configuration to AwsConfig

* Configuration fixes, we now allow w/out any creds, or iam-role defined in config file.

* missing default value for timeout added
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