[jira] [Updated] (HDDS-12308) HA Aware Reads for Snapdiff
[ https://issues.apache.org/jira/browse/HDDS-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDDS-12308: --- Parent: HDDS-15130 (was: HDDS-13747) > HA Aware Reads for Snapdiff > --- > > Key: HDDS-12308 > URL: https://issues.apache.org/jira/browse/HDDS-12308 > Project: Apache Ozone > Issue Type: Sub-task > Components: Ozone Manager >Reporter: Ivan Andika >Assignee: Ivan Andika >Priority: Major > > Currently Snapdiff request will always go to the leader. The leader will > start a Snapdiff job if it does not exist yet and once it's finished, the > user can rerun the snapdiff command again to receive the snapshot diffs. > However, if there is a OM leader change and snapshot diff is called, the new > OM leader needs to generate a new snapdiff again, which adds another overhead. > We can try to read from a single OM by specifying the OM Node ID. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (HDDS-12308) HA Aware Reads for Snapdiff
[ https://issues.apache.org/jira/browse/HDDS-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDDS-12308: --- Parent: HDDS-13747 (was: HDDS-12940) > HA Aware Reads for Snapdiff > --- > > Key: HDDS-12308 > URL: https://issues.apache.org/jira/browse/HDDS-12308 > Project: Apache Ozone > Issue Type: Sub-task > Components: Ozone Manager >Reporter: Ivan Andika >Assignee: Ivan Andika >Priority: Major > > Currently Snapdiff request will always go to the leader. The leader will > start a Snapdiff job if it does not exist yet and once it's finished, the > user can rerun the snapdiff command again to receive the snapshot diffs. > However, if there is a OM leader change and snapshot diff is called, the new > OM leader needs to generate a new snapdiff again, which adds another overhead. > We can try to read from a single OM by specifying the OM Node ID. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (HDDS-12308) HA Aware Reads for Snapdiff
[ https://issues.apache.org/jira/browse/HDDS-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei-Chiu Chuang updated HDDS-12308: --- Parent: HDDS-12940 (was: HDDS-8544) > HA Aware Reads for Snapdiff > --- > > Key: HDDS-12308 > URL: https://issues.apache.org/jira/browse/HDDS-12308 > Project: Apache Ozone > Issue Type: Sub-task > Components: Ozone Manager >Reporter: Ivan Andika >Assignee: Ivan Andika >Priority: Major > > Currently Snapdiff request will always go to the leader. The leader will > start a Snapdiff job if it does not exist yet and once it's finished, the > user can rerun the snapdiff command again to receive the snapshot diffs. > However, if there is a OM leader change and snapshot diff is called, the new > OM leader needs to generate a new snapdiff again, which adds another overhead. > We can try to read from a single OM by specifying the OM Node ID. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (HDDS-12308) HA Aware Reads for Snapdiff
[ https://issues.apache.org/jira/browse/HDDS-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Andika updated HDDS-12308: --- Description: Currently Snapdiff request will always go to the leader. The leader will start a Snapdiff job if it does not exist yet and once it's finished, the user can rerun the snapdiff command again to receive the snapshot diffs. However, if there is a OM leader change and snapshot diff is called, the new OM leader needs to generate a new snapdiff again, which adds another overhead. We can try to read from a single OM by specifying the OM Node ID. was: Currently Snapdiff request will go always to go to the leader. The leader will start a Snapdiff job if it does not exist yet and once it's finished, the user can rerun the snapdiff command again to receive the snapshot diffs. However, if there is a OM leader change and snapshot diff is called, the new OM leader needs to generate a new snapdiff again, which adds another overhead. We can try to read from a single OM by specifying the OM Node ID. > HA Aware Reads for Snapdiff > --- > > Key: HDDS-12308 > URL: https://issues.apache.org/jira/browse/HDDS-12308 > Project: Apache Ozone > Issue Type: Sub-task > Components: Ozone Manager >Reporter: Ivan Andika >Assignee: Ivan Andika >Priority: Major > > Currently Snapdiff request will always go to the leader. The leader will > start a Snapdiff job if it does not exist yet and once it's finished, the > user can rerun the snapdiff command again to receive the snapshot diffs. > However, if there is a OM leader change and snapshot diff is called, the new > OM leader needs to generate a new snapdiff again, which adds another overhead. > We can try to read from a single OM by specifying the OM Node ID. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
