Singularity 0.22.0
Changes in 0.22.0
Check out the 0.22.0 milestone to see new features / bugfixes in detail. 0.22.0 represents an upgrade to mesos 1.6.1. This also includes an upgrade to protobuf 3 and a move to a separate fork of mesos-rxjava. Instuctions for upgrading mesos can be found here. In internal testing we found communications between old mesos master/upgraded scheduler and vice versa were both backwards compatible back to mesos 1.1.0.
New Features
- 1873 - Non-http health checks
Improvements
- 1893 - Use a profile to build for postgresql
- 1894 - Add trace logging for header passthrough authenticator
- 1895 - Add option to specify executor cleanup creds in file
- 1885 - Add guava/jdk8 modules to default SingularityClient object mapper
- 1887 - Remove all switch user bits from docker wrapper
- 1880 - Improve ExtendedTaskState readability
- 1888 - Report uploader/downloader metrics by writing to a file.
- 1891 - Add ability to set uploader additional files at deploy level
- 1849 - Slave attribute minimums
- 1876 - Better alerting for task lag
- 1877 - Update alert banner to only show when there's a widespread issue for task lag
- 1878 - Add support for inactive task history filtered by deploy ID
- 1875 - Ability to rotate at a max service log size
- 1854 - Ability to open sandbox files from SingularityUI
- 1867 - Upgrade to mesos 1.6.1 and fork of mesos-rxjava
- 1869 - Faster run now enqueue
- 1860 - Make SingularityUI snappier
Bug Fixes
- 1882 - Be sure to remove expiring bounces when a bounce completes
- 1847 - Ability to set 'shell' in deploy ui
- 1883 - Acquire a request-level lock when persisting deploy history.
- 1879 - Make task history paging less flaky
- 1881 - Don't count pending tasks limited by instance count in task lag
- 1874 - Additional updates for backpressure handling
- 1853 - Failover when we miss Mesos Master heartbeats.
- 1868 - Email unsubscription bugfix
- 1866 - Clean up logrotate files sooner
- 1871 - Add ability to ignore logrotate hourly output
- 1863 - Grab the request lock when persisting request/deploy history
Documentation
- 1884 - Fix broken docs link