Unless there is a shared configuration which changes when you add a new
instance, Bosh will not trigger deploy on your remaining instances. Can you
paste your manifest here (masking secrets)?
On Mon, Aug 7, 2017 at 12:41 PM, hemant patre <hbpatre(a)gmail.com> wrote:
I am using bosh to deploy one database cluster on n instances. After
while scaling cluster I want to add one more instance to this cluster (so
new cluster size will be n+1). I am changing manifest file to have
instances value as n+1. When I am executing deploy command with modified
manifest file, it is creating cluster of n+1 instances (n old instances and
1 new VM started). It is as per expectation. But in this process, job
(database service) on all instances got restarted. I just want to add new
instance without disturbing running jobs (services) on already running VMs.
How to achieve this?