[jira] [Updated] (IGNITE-20719) [ducktests] CDC ducktests do not work if HTTP metrics export is enabled
[ https://issues.apache.org/jira/browse/IGNITE-20719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Korotkov updated IGNITE-20719: - Labels: ise (was: ) > [ducktests] CDC ducktests do not work if HTTP metrics export is enabled > --- > > Key: IGNITE-20719 > URL: https://issues.apache.org/jira/browse/IGNITE-20719 > Project: Ignite > Issue Type: Task >Reporter: Sergey Korotkov >Assignee: Sergey Korotkov >Priority: Minor > Labels: ise > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > There are several problems preventing the CDC ducktests to work correctly if > HTTP metrics exporter (opencensus prometheus) is enabled: > # Prometheus metrics HTTP port conflict between ignite.sh and ignite-cdc.sh > processes. > # StandaloneGridKernalContext used in ignite-cdc.sh returns null as ignite > instance name but it's needed by the opencensus metrics exporter with the > sendInstanceName=True (which in turn is needed for ducktests to bound metrics > to particular test instance). > # Current ignite_spec overrides the ignite_instance_name if metrics were > enabled preventing using of different custom names. Which is needed for CDC > tests there two ignite configurations are specified in the same XML config > file on the same node (one for source and another for the target cluster). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20719) [ducktests] CDC ducktests do not work if HTTP metrics export is enabled
[ https://issues.apache.org/jira/browse/IGNITE-20719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-20719: - Ignite Flags: (was: Docs Required,Release Notes Required) > [ducktests] CDC ducktests do not work if HTTP metrics export is enabled > --- > > Key: IGNITE-20719 > URL: https://issues.apache.org/jira/browse/IGNITE-20719 > Project: Ignite > Issue Type: Task >Reporter: Sergey Korotkov >Assignee: Sergey Korotkov >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > There are several problems preventing the CDC ducktests to work correctly if > HTTP metrics exporter (opencensus prometheus) is enabled: > # Prometheus metrics HTTP port conflict between ignite.sh and ignite-cdc.sh > processes. > # StandaloneGridKernalContext used in ignite-cdc.sh returns null as ignite > instance name but it's needed by the opencensus metrics exporter with the > sendInstanceName=True (which in turn is needed for ducktests to bound metrics > to particular test instance). > # Current ignite_spec overrides the ignite_instance_name if metrics were > enabled preventing using of different custom names. Which is needed for CDC > tests there two ignite configurations are specified in the same XML config > file on the same node (one for source and another for the target cluster). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20719) [ducktests] CDC ducktests do not work if HTTP metrics export is enabled
[ https://issues.apache.org/jira/browse/IGNITE-20719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-20719: - Fix Version/s: 2.16 > [ducktests] CDC ducktests do not work if HTTP metrics export is enabled > --- > > Key: IGNITE-20719 > URL: https://issues.apache.org/jira/browse/IGNITE-20719 > Project: Ignite > Issue Type: Task >Reporter: Sergey Korotkov >Assignee: Sergey Korotkov >Priority: Minor > Fix For: 2.16 > > Time Spent: 20m > Remaining Estimate: 0h > > There are several problems preventing the CDC ducktests to work correctly if > HTTP metrics exporter (opencensus prometheus) is enabled: > # Prometheus metrics HTTP port conflict between ignite.sh and ignite-cdc.sh > processes. > # StandaloneGridKernalContext used in ignite-cdc.sh returns null as ignite > instance name but it's needed by the opencensus metrics exporter with the > sendInstanceName=True (which in turn is needed for ducktests to bound metrics > to particular test instance). > # Current ignite_spec overrides the ignite_instance_name if metrics were > enabled preventing using of different custom names. Which is needed for CDC > tests there two ignite configurations are specified in the same XML config > file on the same node (one for source and another for the target cluster). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20719) [ducktests] CDC ducktests do not work if HTTP metrics export is enabled
[ https://issues.apache.org/jira/browse/IGNITE-20719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Korotkov updated IGNITE-20719: - Description: There are several problems preventing the CDC ducktests to work correctly if HTTP metrics exporter (opencensus prometheus) is enabled: # Prometheus metrics HTTP port conflict between ignite.sh and ignite-cdc.sh processes. # StandaloneGridKernalContext used in ignite-cdc.sh returns null as ignite instance name but it's needed by the opencensus metrics exporter with the sendInstanceName=True (which in turn is needed for ducktests to bound metrics to particular test instance). # Current ignite_spec overrides the ignite_instance_name if metrics were enabled preventing using of different custom names. Which is needed for CDC tests there two ignite configurations are specified in the same XML config file on the same node (one for source and another for the target cluster). was: There are several problems preventing the CDC ducktests to work correctly if HTTP metrics exporter (opencensus prometheus) is enabled: # Prometheus metrics HTTP port conflict between ignite.sh and ignite-cdc.sh processes. # StandaloneGridKernalContext returns null as ignite instance name but it's needed by the opencensus metrics exporter with the sendInstanceName=True (which in turn is needed for ducktests to bound metrics to particular test instance). # Current ignite_spec overrides the ignite_instance_name if metrics were enabled preventing using of different custom names. Which is needed for CDC tests there 2 ignite configurations are specified in the same XML config file (one for source and another for the target cluster). > [ducktests] CDC ducktests do not work if HTTP metrics export is enabled > --- > > Key: IGNITE-20719 > URL: https://issues.apache.org/jira/browse/IGNITE-20719 > Project: Ignite > Issue Type: Task >Reporter: Sergey Korotkov >Assignee: Sergey Korotkov >Priority: Minor > > There are several problems preventing the CDC ducktests to work correctly if > HTTP metrics exporter (opencensus prometheus) is enabled: > # Prometheus metrics HTTP port conflict between ignite.sh and ignite-cdc.sh > processes. > # StandaloneGridKernalContext used in ignite-cdc.sh returns null as ignite > instance name but it's needed by the opencensus metrics exporter with the > sendInstanceName=True (which in turn is needed for ducktests to bound metrics > to particular test instance). > # Current ignite_spec overrides the ignite_instance_name if metrics were > enabled preventing using of different custom names. Which is needed for CDC > tests there two ignite configurations are specified in the same XML config > file on the same node (one for source and another for the target cluster). -- This message was sent by Atlassian Jira (v8.20.10#820010)
