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

mapStoreConfig.setWriteDelaySeconds does not perform as expected #13287

Closed
ozaydinb opened this issue Jun 12, 2018 · 1 comment
Closed

mapStoreConfig.setWriteDelaySeconds does not perform as expected #13287

ozaydinb opened this issue Jun 12, 2018 · 1 comment
Labels
Source: Community PR or issue was opened by a community user

Comments

@ozaydinb
Copy link

Hi,

We use mapStoreConfig.setWriteDelaySeconds methods (as mapStoreConfig.setWriteDelaySeconds(1))
for converting our store and load methods behavior to Async in Mapstore/MapLoader implementation.

After we apply these changes, we faced with some cases that store methods were not called. We expected that Hazelcast would respond and trigger store method after 1 sec. when there is a put operation in our map.

Our code about that case can be found below:

        final MapConfig sessionMapConfig = config.getMapConfig("MyMap");
        sessionMapConfig.setCacheDeserializedValues(CacheDeserializedValues.ALWAYS);
        sessionMapConfig.setMaxIdleSeconds(2 * 60);
        MapStoreConfig mapStoreConfig = sessionMapConfig.getMapStoreConfig();
        mapStoreConfig.setClassName("MyMapClassName");
        mapStoreConfig.setWriteDelaySeconds(1);
        mapStoreConfig.setEnabled(true);
@ahmetmircik
Copy link
Member

Hi @ozaydinb,
Closing this issue based on the answer here. If it doesn't help, please update this issue. Thanks.

@mmedenjak mmedenjak added the Source: Community PR or issue was opened by a community user label Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Community PR or issue was opened by a community user
Projects
None yet
Development

No branches or pull requests

3 participants