InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Add a new idea Subscribe
Status Will not implement
Categories InterSystems IRIS
Created by Gary Holt
Created on Oct 3, 2022

RELATED IDEAS

Mirror Async Member Time Delay in Applying Journals

Currently a async member will be in sync with the primary, however in the event of an issue such as a global being deleted then both the servers would have the same issue. However if the async member had a delay journal process property then the async member could be a copy of the primary but behind by 24 hours as a example. The journals for the mirror would still be transferred in real time to the async mirror and in the event that the system is need to be current then they can be processed.

  • ADMIN RESPONSE
    Oct 23, 2023

    Thank you for submitting the idea. Based on information from our experts the status of your idea was changed to "Will not implement". Please look for details in the comments on the idea. Good luck!

  • Post comment
  • Admin
    Vadim Aniskin
    Oct 23, 2023

    There are comments on this idea from an InterSystems product manager and a community portal moderator.

    The idea was transferred to the status “Will not be implemented”, since the author did not respond to comments for several months.

    If the author responds to these comments, the status of this idea may be changed.

    Reply
  • Admin
    Vadim Aniskin
    Jun 23, 2023

    @Gary Holt, you have comments on your idea. Please answer them to help your idea to be promoted.

    Reply
  • Benjamin De Boe
    Jan 19, 2023

    Hi Gary,

    thanks for suggesting this.

    It feels like 24h may be a bit of an arbitrary window. If you only notice the issue after 25h, this delay doesn't really help and if you do notice it within the 24h window, are you planning to still roll journal files forward up to right before? If that is the case, you could as well stick with the current async behaviour and roll back till right before the faulty set/kill.

    If you meant to stick with that 24h granularity, maybe you're actually more talking about a daily backup/restore cycle rather than deploying this as a mirror?


    Thanks,
    benjamin

    Reply
  • Dmitry Maslennikov
    Oct 27, 2022

    I'm sure, if you need it that way, you just can do nightly sync instead. The mirror is stopped during the day, and on at night. I think it's doable with a right configuration.

    Reply