Hi,
We have a site that use Sonic ESB 8.5.1 and backend Database is Progress OE 10.2B with fathom replication.
Oh, that's a problem. For that year, I ask the PSC to made the Procluster for linux, but so far without success. That's the last time in Manchester I spoke to them about it and they promised they would do, but that's not clear when .... very bad I do not understand how they will work in the cloud, if they do not have an elementary clustering, not to mention the Real Application Cluster (RAC)
Agreed, I also contact the progress support on this and come out the same answer. This is bit issue for us now when we dont have real loadbalancing and clustering in progress RDBMS. Where other DB vendors offers. I feel this is a right time that progress to address these issues. .
I asked several times about failover cluster support in RHEL during EMEA PUG challenge BOF sessions but everytime they (Progress fellows) seem to be surprised and they look at me like I was on another planet. Four/five years ago I also send question about cluster to the PEGgers, but no luck to see any answer.
In 2010 I made some successful tests on AIX (HACMP) and Windows Server 2003 Enterprise (MSCS). I tried also with Red Hat Cluster Suite in the unsupported way and the results were quite good. OE database is not cluster aware. We used rc.d script to let RHCS to control database. The only big challenge was to write appropriate rc.d script with start|stop|monitor cases and exact return values.
After some tests the only implementation differences between supported & unsupported CMs I'd noticed is that procluster "exposes" database resources to the CM and do some changes in master block of db, so it is cluster aware.
I'm using killall -9 _mprosrv in rc.d script to stop resource, but it's not recommended. Process of relocating works fine. The worse scenario is when active node hangs, then second node cannot start db due to hostname entry in lock file.
In my opinion if the RHEL is certified for OE, the RH Cluster Suite should also be certified cluster manager for OE. In database environment the failover cluster is a basic method to increase reliability and safety and I'm wondering why it is so neglected by PSC.
AFAIK you won't succeed in load balancing because OE allow active/passive type of clustering.
I asked several times about failover cluster support in RHEL during EMEA PUG challenge BOF sessions but everytime they (Progress fellows) seem to be surprised and they look at me like I was on another planet. Four/five years ago I also send question about cluster to the PEGgers, but no luck to see any answer.
In 2010 I made some successful tests on AIX (HACMP) and Windows Server 2003 Enterprise (MSCS). I tried also with Red Hat Cluster Suite in the unsupported way and the results were quite good. OE database is not cluster aware. We used rc.d script to let RHCS to control database. The only big challenge was to write appropriate rc.d script with start|stop|monitor cases and exact return values.
After some tests the only implementation differences between supported & unsupported CMs I'd noticed is that procluster "exposes" database resources to the CM and do some changes in master block of db, so it is cluster aware.
I'm using killall -9 _mprosrv in rc.d script to stop resource, but it's not recommended. Process of relocating works fine. The worse scenario is when active node hangs, then second node cannot start db due to hostname entry in lock file.
In my opinion if the RHEL is certified for OE, the RH Cluster Suite should also be certified cluster manager for OE. In database environment the failover cluster is a basic method to increase reliability and safety and I'm wondering why it is so neglected by PSC.
Flag this post as spam/abuse.
In addition to putting some pressure on Progress Account Managers, I would suggest posting such a requirement to Ideas section (I couldn't find one). It's regularly reviewed by people with sufficient influence. It will also give the whole Community a chance to vote for that, which is the best way to show the impact of missing support for Linux CM, and add appropriate weight to such a request.
Regards
Marek