Jira (PDB-4658) Audit how command broadcast changes will affect metrics and the dlo

[Zachary Kent (JIRA)]

Zachary Kent created an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo Issue Type: New Feature Assignee: Unassigned Created: 2020/02/21 11:36 AM Priority: Normal Reporter: Zachary Kent We need to look into how metrics will be collected as a result of these changes. Do we possibly double count commands now, etc? Similarly we need to consider what to do with the DLO if an incoming command is successfully submitted to one but not all of the dbs in the command broadcast list. In this case we could possibly have the command still end up in the dlo but with some indication of which submission failed. Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Zachary Kent (JIRA)]

Zachary Kent updated an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo

Change By: Zachary Kent Acceptance Criteria: * Create tickets with the specifics needed to address metrics and dlo handling when PDB is in command broadcast mode

Add Comment

[Zachary Kent (JIRA)]

Zachary Kent updated an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo Change By: Zachary Kent

We need to look into how metrics will be collected as a result of these changes. Do we possibly double count commands now, etc?

Similarly, we need to consider what to do with the DLO if an incoming command is successfully submitted to one but not all of the dbs in the command broadcast list. In this case we could possibly have the command still end up in the dlo DLO but with some indication of which submission failed.

Add Comment

[Zachary Kent (JIRA)]

Zachary Kent updated an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo Change By: Zachary Kent

We need to look into how metrics will be collected as a result of these changes. Do we possibly double count commands now, etc?

Similarly , we need to consider what to do with the DLO if an incoming command is successfully submitted to one but not all of the dbs in the command broadcast list. In this case we could possibly have the command still end up in the dlo but with some indication of which submission failed.

Add Comment

[Zachary Kent (JIRA)]

Zachary Kent updated an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo

Change By: Zachary Kent Acceptance Criteria: * Create tickets with the specifics needed to address metrics and dlo DLO handling when PDB is in command broadcast mode

Add Comment

[Zachary Kent (JIRA)]

Zachary Kent updated an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo

Change By: Zachary Kent Team: HA

Add Comment

[Nick Burgan (Jira)]

Nick Burgan updated an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo

Change By: Nick Burgan Sprint: HA Team (Ready For Work)

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Nick Burgan (Jira)]

Nick Burgan updated an issue

PuppetDB / PDB-4658 Audit how command broadcast changes will affect metrics and the dlo

Change By: Nick Burgan Story Points: 3

Add Comment

[Austin Blatt (Jira)]

Austin Blatt commented on PDB-4658

Re: Audit how command broadcast changes will affect metrics and the dlo For the DLO, I would vote that if it makes it to one postgres then it does not end up in the DLO because it was either a network issue, so sync will reconcile that, or it was a problem with the configuration of one of your postgres installs, and that will be easier to debug once it ends up in the primary/replica DLO after a sync run.

Add Comment