Open manjotnms opened 9 years ago
Paste from email trail -
Ankit,
We don't have an implementation plan for #572 right now. Implementing it the right way would involve upgrading underlying DataNucleus libraries but that has unintended consequences to our existing implementation that already works.
We see this as a 'nice to have' since state-service undeployments are very rare events that seldom happen in production environments. Even those events happen during after-hours service windows or emergency service shutdown is an acceptable cause for temporary disruptions due to restart.
Feel free to make your case if you believe this is show-stopper for you. I'm happy to skype with Manjot as well, to understand your case better.
Thanks, Koshal
Hi @koshalt We understand it is a rare event but GUI is a feature to facilitate this and avoid any unnecessary action like MoTech restart even in afterhours and inspite of being a minor issue, it is a issue. So it can be taken on low priority but should be fixed.
And this is not just for deployed service entity, other entities also have this random behavior , So when or how do you plan to implement #572 ?
@rahulgaurnms I don't really have a good answer for this yet. As mentioned earlier, we don't have a plan to get to this until our backlog is clear and higher priority items like performance, etc are resolved.
Refer to Bug https://applab.atlassian.net/browse/NIP-107, so raising new feature request, so as MOTECH restart is not required to undeploy any service.