Platform notifications PLAT-943 & ACP-2603
Posted by Gordon Vaughan on 30 August 2016 02:55 PM
Please find below a couple of advisory notices that we would like your consideration and understanding on. It is important that these are read and understood at the appropriate level, so please ensure that all administrators of your WANdisco products are made aware to prevent any issues in future. As always, if there are any questions you are welcome to respond to this ticket and we’ll get back to you with any support needed as soon as possible.
PLAT-943 – Issues with ‘Voter Only’ nodes
Affected product(s): Subversion MultiSite Plus and Git MultiSite
Content: The use of ‘Voter Only’ node type has been found to cause issues with nodes potentially encountering an non-graceful stop, which then invokes a failure to fully restart. The impact of the addition of a voter only node can result in a need to reinstall that node, resulting in a need for a maintenance window to resolve.
Context: WANdisco has, to date, not deployed any customer with an environment that makes use of the voter only node functionality, and furthermore has not recommended this to any customer. It is expected that any customer wishing to add new nodes would reach out to WANdisco and, with this current issue in mind, provide us the opportunity to steer away from this voter type. However, as the functionality exists for a customer to take this step without WANdisco engagement, it is important that we highlight this for all potential customers who could make this change.
Workaround/Recommendation: The workaround is simple; do not use the voter only role for any node. Should you be in a position where you have deployed a voter only node please contact WANdisco Support ASAP. This issue is expected to be fixed in a forthcoming release across both platforms affected.
ACP-2603 – GFR log file growth, rotation needed
Affected product(s) – Access Control Plus
Content: It has been noted that GFR log files can grow very quickly, and as such WANdisco need to recommend that a rotation is put in place to ensure this does not impact Access Control Plus.
Context: While this is not a bug within Access Control Plus, the impact of this GFR log file growing can create serious issues for our product, and as such we must issue an advisory on rotation methodology.
Workaround/Recommendation: One such method, on some Linux distros, would be to create the file: /etc/logrotate.d/wandisco
With the following contents:
The above will keep 31 log files, compress them 1 day after rotating them (gzip -9) and use name of "_YYYYMMDD.gz" (after compression). Log rotation via the "logrotate" command is normally run via cron via the "/etc/cron.daily/logrotate" crontab file. The logrotate command, itself, is normally configured via "/etc/logrotate.conf" to include all files in "/etc/logrotate.d".
WANdisco recommend implementing this as soon as possible to prevent issues in future.