Jira (PDB-2071) Sticky failover in terminus queries

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-2071 Sticky failover in terminus queries Change By: Russell Mull Summary: Sticky failover in  for  terminus queries Add Comment

This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)

[Russell Mull (JIRA)]

Russell Mull assigned an issue to Russell Mull

PuppetDB / PDB-2071 Sticky failover in terminus queries

Change By: Russell Mull Assignee: Russell Mull

Add Comment

[Russell Mull (JIRA)]

[Kenneth Barber (JIRA)]

Kenneth Barber updated an issue

PuppetDB / PDB-2071 Sticky failover in terminus queries

Change By: Kenneth Barber Fix Version/s: PDB 4.0.0

Add Comment

[Kurt Wall (JIRA)]

Kurt Wall updated an issue

PuppetDB / PDB-2071 Sticky failover in terminus queries

Change By: Kurt Wall QA Status: Reviewed QA Risk Assessment: Low QA Contact: Kurt Wall

Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[Kurt Wall (JIRA)]

Kurt Wall assigned an issue to Kurt Wall

PuppetDB / PDB-2071 Sticky failover in terminus queries

Change By: Kurt Wall Assignee: Kurt Wall

Add Comment

[Kurt Wall (JIRA)]

Kurt Wall commented on PDB-2071

Re: Sticky failover in terminus queries Given a running HA setup with 2 puppetdb nodes, is the following the correct way to test this? Start a stream of requests at node 1 Fail over to node 2 Watch the rest of the requests go to node 2 Will the failed request route to node 2 as well?

Add Comment

[Russell Mull (JIRA)]

Russell Mull commented on PDB-2071

Re: Sticky failover in terminus queries

Yes, the failed request should move over as well. But: when combined with PDB-2072, we should see all write requests going to all of the nodes when possible. read requests (like exported resource) should fail over as you described, but they should keep going to node 2 once you bring node 1 back up.

Add Comment

[Kurt Wall (JIRA)]

Kurt Wall commented on PDB-2071

Re: Sticky failover in terminus queries

Great, thanks for the additional information!

Add Comment

[Kurt Wall (JIRA)]

Kurt Wall commented on PDB-2071

Re: Sticky failover in terminus queries

Following the PDB HA test plan doc, I got to the point below vagrant up, and don't know how to proceed further. It's working for others, so I imagine it's a local config problem but don't know how to proceed, being unfamiliar with both vagrant and r10k. ERROR warden: Error occurred: RuntimeError: vagrant-r10k configuration error; cannot continue INFO warden: Beginning recovery process... INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000101c27958> INFO warden: Beginning recovery process... INFO warden: Recovery complete. INFO warden: Recovery complete. INFO warden: Beginning recovery process... INFO warden: Recovery complete. ERROR warden: Error occurred: RuntimeError: vagrant-r10k configuration error; cannot continue INFO warden: Beginning recovery process... INFO warden: Recovery complete. INFO warden: Beginning recovery process... INFO warden: Recovery complete. ERROR warden: Error occurred: RuntimeError: vagrant-r10k configuration error; cannot continue INFO warden: Beginning recovery process... INFO warden: Recovery complete. INFO warden: Beginning recovery process... INFO warden: Recovery complete. INFO warden: Beginning recovery process... INFO warden: Recovery complete. INFO environment: Released process lock: machine-action-2899bd2c76b314f77f1fe81453e3faa7 INFO environment: Running hook: environment_unload INFO runner: Preparing hooks for middleware sequence... INFO runner: 1 hooks defined. INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x000001032d06c8> ERROR vagrant: Vagrant experienced an error! Details: ERROR vagrant: #<VagrantPlugins::R10k::Helpers::ErrorWrapper: RuntimeError: vagrant-r10k configuration error; cannot continue> ERROR vagrant: RuntimeError: vagrant-r10k configuration error; cannot continue ERROR vagrant: /Users/kwall/.vagrant.d/gems/gems/vagrant-r10k-0.4.0/lib/vagrant-r10k/action/validate.rb:26:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_box.rb:56:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action' /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run' INFO interface: error: RuntimeError: vagrant-r10k configuration error; cannot continue RuntimeError: vagrant-r10k configuration error; cannot continue INFO interface: Machine: error-exit ["VagrantPlugins::R10k::Helpers::ErrorWrapper", "RuntimeError: vagrant-r10k configuration error; cannot continue"]

Add Comment

[Kurt Wall (JIRA)]

Kurt Wall assigned an issue to Unassigned

PuppetDB / PDB-2071

Sticky failover in terminus queries

Change By: Kurt Wall Assignee: Kurt Wall

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

PuppetDB / PDB-2071 Sticky failover in terminus queries

Change By: Claudia Petty Labels: new-feature

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)