-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add DJM init script for EMR #32328
Add DJM init script for EMR #32328
Conversation
fd4fab2
to
281d10c
Compare
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision |
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv aws.create-vm --pipeline-id=51682520 --os-family=ubuntu Note: This applies to commit 918a260 |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: c60d01f Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.31 | [-0.47, +1.09] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.31 | [+0.27, +0.34] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_idle_all_features | memory utilization | +0.20 | [+0.11, +0.29] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_logs | % cpu utilization | +0.07 | [-3.18, +3.32] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.07 | [-0.78, +0.92] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.07 | [-0.57, +0.71] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.07 | [-0.40, +0.53] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.03 | [-0.73, +0.80] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | +0.02 | [-0.66, +0.71] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.01 | [-0.76, +0.78] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.11, +0.12] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.00 | [-0.87, +0.87] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.02 | [-0.88, +0.85] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.25 | [-0.34, -0.16] | 1 | Logs |
➖ | file_tree | memory utilization | -0.48 | [-0.61, -0.35] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.65 | [-2.32, -0.98] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | |
✅ | quality_gate_logs | memory_usage | 10/10 |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
b08ec60
to
e69d123
Compare
Gitlab CI Configuration ChangesModified Jobsinstaller-install-scripts installer-install-scripts:
artifacts:
expire_in: 2 weeks
paths:
- $OMNIBUS_PACKAGE_DIR
image: registry.ddbuild.io/ci/datadog-agent-buildimages/deb_x64$DATADOG_AGENT_BUILDIMAGES_SUFFIX:$DATADOG_AGENT_BUILDIMAGES
needs:
- go_mod_tidy_check
- go_deps
rules:
- if: $CI_COMMIT_BRANCH =~ /^mq-working-branch-/
when: never
- when: on_success
script:
- mkdir -p $GOPATH/pkg/mod/cache && tar xJf modcache.tar.xz -C $GOPATH/pkg/mod/cache
- rm -f modcache.tar.xz
- echo "About to build for $RELEASE_VERSION"
- mkdir -p $OMNIBUS_PACKAGE_DIR
- inv -e installer.build-linux-script "databricks" "$RELEASE_VERSION"
+ - inv -e installer.build-linux-script "emr" "$RELEASE_VERSION"
- mv ./bin/installer/install-*.sh $OMNIBUS_PACKAGE_DIR/
- ls -la $OMNIBUS_PACKAGE_DIR
stage: package_build
tags:
- arch:amd64
variables:
KUBERNETES_CPU_REQUEST: 8
KUBERNETES_MEMORY_LIMIT: 16Gi
KUBERNETES_MEMORY_REQUEST: 16Gi
RELEASE_VERSION: $RELEASE_VERSION_7 Changes Summary
ℹ️ Diff available in the job log. |
39a41a9
to
3f00482
Compare
677d732
to
3d97699
Compare
17f91b6
to
dd7289b
Compare
1b58b8d
to
5126a80
Compare
Devflow running:
|
|
||
tests := []struct { | ||
name string | ||
env map[string]string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think this is used
5126a80
to
ad9ff10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! This definitely makes it easier to handle the installation for DJM!
3aba9cc
to
c9cd812
Compare
c9cd812
to
6a7354c
Compare
pkg/fleet/installer/setup/djm/emr.go
Outdated
if err != nil { | ||
log.Warn("error describing emr cluster, using cluster id as name") | ||
return info.IsMaster, extraInfo.JobFlowID, nil | ||
} | ||
var response emrResponse | ||
if err = json.Unmarshal(emrResponseRaw, &response); err != nil { | ||
return info.IsMaster, extraInfo.JobFlowID, fmt.Errorf("error unmarshalling AWS EMR response, using cluster id as name: %w", err) | ||
} | ||
clusterName := response.Cluster.Name | ||
if clusterName == "" { | ||
log.Warn("clusterName is empty, using cluster id as name") | ||
clusterName = extraInfo.JobFlowID | ||
} | ||
setHostTag(s, "cluster_name", clusterName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's never return an error if anything fails on the describe-cluster
and just use the cluster id as a fallback for the name
Since this operation can be a source of error, i think we should create a span for it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the good idea. I addressed it by isolating the command execution in a separate function and having spans for it so the error is easily trackable.
/merge |
Devflow running:
|
What does this PR do?
Add a new Data Jobs Monitoring init script flavor for AWS EMR.
Motivation
Describe how you validated your changes
Possible Drawbacks / Trade-offs
Additional Notes