Skip to content
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

Fix: Health lambas still time out occasionally (#6097) #6118

Merged

Conversation

achave11-ucsc
Copy link
Member

@achave11-ucsc achave11-ucsc commented Apr 2, 2024

Connected issues: #6097

Checklist

Author

  • PR is a draft
  • Target branch is develop
  • Name of PR branch matches issues/<GitHub handle of author>/<issue#>-<slug>
  • On ZenHub, PR is connected to all issues it (partially) resolves
  • PR description links to connected issues
  • PR title matches1 that of a connected issue or comment in PR explains why they're different
  • PR title references all connected issues
  • For each connected issue, there is at least one commit whose title references that issue

1 when the issue title describes a problem, the corresponding PR
title is Fix: followed by the issue title

Author (partiality)

  • Added p tag to titles of partial commits
  • This PR is labeled partial or completely resolves all connected issues
  • This PR partially resolves each of the connected issues or does not have the partial label

Author (chains)

  • This PR is blocked by previous PR in the chain or is not chained to another PR
  • The blocking PR is labeled base or this PR is not chained to another PR
  • This PR is labeled chained or is not chained to another PR

Author (reindex, API changes)

  • Added r tag to commit title or the changes introduced by this PR will not require reindexing of any deployment
  • This PR is labeled reindex:dev or the changes introduced by it will not require reindexing of dev
  • This PR is labeled reindex:anvildev or the changes introduced by it will not require reindexing of anvildev
  • This PR is labeled reindex:anvilprod or the changes introduced by it will not require reindexing of anvilprod
  • This PR is labeled reindex:prod or the changes introduced by it will not require reindexing of prod
  • This PR is labeled reindex:partial and its description documents the specific reindexing procedure for dev, anvildev, anvilprod and prod or requires a full reindex or carries none of the labels reindex:dev, reindex:anvildev, reindex:anvilprod and reindex:prod
  • This PR and its connected issues are labeled API or this PR does not modify a REST API
  • Added a (A) tag to commit title for backwards (in)compatible changes or this PR does not modify a REST API
  • Updated REST API version number in app.py or this PR does not modify a REST API

Author (upgrading deployments)

  • Ran make image_manifests.json and committed the resulting changes or this PR does not modify azul_docker_images, or any other variables referenced in the definition of that variable
  • Documented upgrading of deployments in UPGRADING.rst or this PR does not require upgrading deployments
  • Added u tag to commit title or this PR does not require upgrading deployments
  • This PR is labeled upgrade or does not require upgrading deployments
  • This PR is labeled deploy:shared or does not modify image_manifests.json, and does not require deploying the shared component for any other reason
  • This PR is labeled deploy:gitlab or does not require deploying the gitlab component
  • This PR is labeled deploy:runner or does not require deploying the runner image

Author (hotfixes)

  • Added F tag to main commit title or this PR does not include permanent fix for a temporary hotfix
  • Reverted the temporary hotfixes for any connected issues or the none of the stable branches (anvilprod and prod) have temporary hotfixes for any of the issues connected to this PR

Author (before every review)

  • Rebased PR branch on develop, squashed old fixups
  • Ran make requirements_update or this PR does not modify requirements*.txt, common.mk, Makefile and Dockerfile
  • Added R tag to commit title or this PR does not modify requirements*.txt
  • This PR is labeled reqs or does not modify requirements*.txt
  • make integration_test passes in personal deployment or this PR does not modify functionality that could affect the IT outcome

Peer reviewer (after approval)

  • PR is not a draft
  • Ticket is in Review requested column
  • PR is awaiting requested review from system administrator
  • PR is assigned to only the system administrator

System administrator (after approval)

  • Actually approved the PR
  • Labeled connected issues as demo or no demo
  • Commented on connected issues about demo expectations or all connected issues are labeled no demo
  • Decided if PR can be labeled no sandbox
  • A comment to this PR details the completed security design review
  • PR title is appropriate as title of merge commit
  • N reviews label is accurate
  • Moved ticket to Approved column
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Checked reindex:… labels and r commit title tag
  • Checked that demo expectations are clear or all connected issues are labeled no demo
  • Squashed PR branch and rebased onto develop
  • Sanity-checked history
  • Pushed PR branch to GitHub
  • Ran _select dev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select dev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Ran _select anvildev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select anvildev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Checked the items in the next section or this PR is labeled deploy:gitlab
  • PR is assigned to only the system administrator or this PR is not labeled deploy:gitlab

System administrator

  • Background migrations for dev.gitlab are complete or this PR is not labeled deploy:gitlab
  • Background migrations for anvildev.gitlab are complete or this PR is not labeled deploy:gitlab
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Ran _select dev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Ran _select anvildev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Added sandbox label or PR is labeled no sandbox
  • Pushed PR branch to GitLab dev or PR is labeled no sandbox
  • Pushed PR branch to GitLab anvildev or PR is labeled no sandbox
  • Build passes in sandbox deployment or PR is labeled no sandbox
  • Build passes in anvilbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in sandbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in anvilbox deployment or PR is labeled no sandbox
  • Deleted unreferenced indices in sandbox or this PR does not remove catalogs or otherwise causes unreferenced indices in dev
  • Deleted unreferenced indices in anvilbox or this PR does not remove catalogs or otherwise causes unreferenced indices in anvildev
  • Started reindex in sandbox or this PR is not labeled reindex:dev
  • Started reindex in anvilbox or this PR is not labeled reindex:anvildev
  • Checked for failures in sandbox or this PR is not labeled reindex:dev
  • Checked for failures in anvilbox or this PR is not labeled reindex:anvildev
  • The title of the merge commit starts with the title of this PR
  • Added PR # reference to merge commit title
  • Collected commit title tags in merge commit title but only included p if the PR is also labeled partial
  • Moved connected issues to Merged lower column in ZenHub
  • Pushed merge commit to GitHub

Operator (chain shortening)

  • Changed the target branch of the blocked PR to develop or this PR is not labeled base
  • Removed the chained label from the blocked PR or this PR is not labeled base
  • Removed the blocking relationship from the blocked PR or this PR is not labeled base
  • Removed the base label from this PR or this PR is not labeled base

Operator (after pushing the merge commit)

  • Pushed merge commit to GitLab dev
  • Pushed merge commit to GitLab anvildev
  • Build passes on GitLab dev
  • Reviewed build logs for anomalies on GitLab dev
  • Build passes on GitLab anvildev
  • Reviewed build logs for anomalies on GitLab anvildev
  • Ran _select dev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Ran _select anvildev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Deleted PR branch from GitHub
  • Deleted PR branch from GitLab dev
  • Deleted PR branch from GitLab anvildev

Operator (reindex)

  • Deindexed all unreferenced catalogs in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed all unreferenced catalogs in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Deindexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Indexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Indexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Started reindex in dev or this PR does not require reindexing dev
  • Started reindex in anvildev or this PR does not require reindexing anvildev
  • Checked for, triaged and possibly requeued messages in both fail queues in dev or this PR does not require reindexing dev
  • Checked for, triaged and possibly requeued messages in both fail queues in anvildev or this PR does not require reindexing anvildev
  • Emptied fail queues in dev or this PR does not require reindexing dev
  • Emptied fail queues in anvildev or this PR does not require reindexing anvildev

Operator

  • Propagated the deploy:shared, deploy:gitlab, deploy:runner, reindex:partial, reindex:anvilprod and reindex:prod labels to the next promotion PRs or this PR carries none of these labels
  • Propagated any specific instructions related to the deploy:shared, deploy:gitlab, deploy:runner, reindex:partial, reindex:anvilprod and reindex:prod labels, from the description of this PR to that of the next promotion PRs or this PR carries none of these labels
  • PR is assigned to no one

Shorthand for review comments

  • L line is too long
  • W line wrapping is wrong
  • Q bad quotes
  • F other formatting problem

@github-actions github-actions bot added the orange [process] Done by the Azul team label Apr 2, 2024
Copy link

codecov bot commented Apr 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.90%. Comparing base (7bd1543) to head (63b8a78).
Report is 1 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #6118   +/-   ##
========================================
  Coverage    84.89%   84.90%           
========================================
  Files          156      156           
  Lines        20690    20692    +2     
========================================
+ Hits         17565    17568    +3     
+ Misses        3125     3124    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@coveralls
Copy link

coveralls commented Apr 2, 2024

Coverage Status

coverage: 85.158% (+0.006%) from 85.152%
when pulling a75eb6e on issues/achave11-ucsc/6097-retry-cachehealth-failures
into fb58b01 on develop.

dsotirho-ucsc
dsotirho-ucsc previously approved these changes Apr 3, 2024
Copy link
Contributor

@dsotirho-ucsc dsotirho-ucsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@dsotirho-ucsc dsotirho-ucsc marked this pull request as ready for review April 3, 2024 18:13
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is becoming unwieldy and a little brittle.

Can you try something like this, which is based on how we handle the thresholds:

Subject: [PATCH] [A 2/2] Derive manifest config for AnVIL from field mapping (#6110)

Name special fields in camel case on AnVIL. This repairs the IT.
---
Index: src/azul/chalice.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/src/azul/chalice.py b/src/azul/chalice.py
--- a/src/azul/chalice.py	(revision 3b2831b32aa4c463218ddff66830a3df41567f14)
+++ b/src/azul/chalice.py	(date 1712209742788)
@@ -108,6 +108,13 @@
     value: int
 
 
+@attr.s(auto_attribs=True, frozen=True, kw_only=True)
+class Retry:
+    lambda_name: str
+    handler_name: Optional[str] = attr.ib(default=None)
+    value: int
+
+
 C = TypeVar('C', bound='AppController')
 
 
@@ -526,6 +533,24 @@
                                                       value=threshold))
         return thresholds
 
+    def retry(self, retries: int):
+        def wrapper(f):
+            assert isinstance(f, chalice.app.EventSourceHandler), f
+            f.retries = 2
+            return f
+
+        return wrapper
+
+    def retries(self) -> list[Retry]:
+        lambda_name, _ = config.unqualified_resource_name(self.app_name)
+        retries = []
+        for handler_name, handler in self.handler_map.items():
+            if isinstance(handler, chalice.app.EventSourceHandler):
+                value = getattr(handler, 'retries', 0)
+                retries.append(MetricThreshold(lambda_name=lambda_name,
+                                               handler_name=handler_name,
+                                               value=value))
+
 
 @attr.s(auto_attribs=True, frozen=True, kw_only=True)
 class AppController:
Index: lambdas/indexer/app.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/lambdas/indexer/app.py b/lambdas/indexer/app.py
--- a/lambdas/indexer/app.py	(revision 3b2831b32aa4c463218ddff66830a3df41567f14)
+++ b/lambdas/indexer/app.py	(date 1712209286051)
@@ -337,6 +337,7 @@
     app.index_controller.contribute(event, retry=True)
 
 
+@app.retry(2)
 @app.log_forwarder(
     config.alb_access_log_path_prefix(deployment=None)
 )
Index: terraform/api_gateway.tf.json.template.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/terraform/api_gateway.tf.json.template.py b/terraform/api_gateway.tf.json.template.py
--- a/terraform/api_gateway.tf.json.template.py	(revision 3b2831b32aa4c463218ddff66830a3df41567f14)
+++ b/terraform/api_gateway.tf.json.template.py	(date 1712208689183)
@@ -5,11 +5,14 @@
 import json
 
 from azul import (
+    cached_property,
     config,
 )
+from azul.chalice import AzulChaliceApp
 from azul.deployment import (
     aws,
 )
+from azul.modules import load_app_module
 from azul.objects import (
     InternMeta,
 )
@@ -40,6 +43,10 @@
                        *config.api_lambda_domain_aliases(name)
                    ],
                    policy=json.dumps(getattr(policy_module, 'policy')))
+    
+    @cached_property
+    def chalice(self) -> AzulChaliceApp:
+        return load_app_module(self.name).app
 
 
 apps = [
@@ -372,16 +379,10 @@
             'aws_lambda_function_event_invoke_config': {
                 function_name: {
                     'function_name': '${aws_lambda_function.%s.function_name}' % function_name,
-                    'maximum_retry_attempts': retry_attempts
+                    'maximum_retry_attempts': retry.value
                 }
-                for function_name, retry_attempts in
-                [
-                    (f'indexer_{lm}', 0)
-                    for lm in ['forward_alb_logs', 'forward_s3_logs']
-                    if config.enable_log_forwarding
-                ] + [
-                    (f'{lm}_{lm}cachehealth', 1) for lm in ['indexer', 'service']
-                ]
+                for app in apps
+                for retry in app.chalice.retries()
             }
         },
         *(

This has not been tested and may not handle config.enable_log_forwarding being False.

@hannes-ucsc hannes-ucsc added the 0 reviews [process] Lead didn't request any changes label Apr 4, 2024
@hannes-ucsc hannes-ucsc removed their assignment Apr 4, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6097-retry-cachehealth-failures branch 3 times, most recently from 342a8a6 to d97fda1 Compare April 4, 2024 20:57
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6097-retry-cachehealth-failures branch 3 times, most recently from 5d71952 to 6dc6024 Compare April 5, 2024 02:54
@achave11-ucsc
Copy link
Member Author

achave11-ucsc commented Apr 5, 2024

@hannes-ucsc, I've dropped the patch you suggested during PL (adding it to the end of this comment), since the default retry limit is two and in the conversation of when this retry constrictions to the forwarder lambdas were employed (#4920 (comment)) it's also confirmed. There is no longer a need for these lambdas to be part of the aws_lambda_function_event_invoke_config Terraform resource, since we do want them to have a retry limit of two.

Subject: [PATCH] Increase retry for the log forwarder Lambdas
---
Index: lambdas/indexer/app.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/lambdas/indexer/app.py b/lambdas/indexer/app.py
--- a/lambdas/indexer/app.py	
+++ b/lambdas/indexer/app.py	
@@ -338,6 +338,7 @@
     app.index_controller.contribute(event, retry=True)
 
 
+@app.retry(2 if config.enable_log_forwarding else None)
 @app.log_forwarder(
     config.alb_access_log_path_prefix(deployment=None)
 )
@@ -345,6 +346,7 @@
     app.log_controller.forward_alb_logs(event)
 
 
+@app.retry(2 if config.enable_log_forwarding else None)
 @app.log_forwarder(
     config.s3_access_log_path_prefix(deployment=None)
 )
Index: src/azul/chalice.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/src/azul/chalice.py b/src/azul/chalice.py
--- a/src/azul/chalice.py	
+++ b/src/azul/chalice.py	
@@ -533,7 +533,7 @@
                                                       value=threshold))
         return thresholds
 
-    def retry(self, retries: int):
+    def retry(self, retries: int | None):
         """
         Use this decorator to specify a custom number of retries that should be
         different from the default (which is two) for any of the Azul async
@@ -541,8 +541,9 @@
         https://docs.aws.amazon.com/lambda/latest/dg/invocation-retries.html
         """
         def wrapper(f):
-            assert isinstance(f, chalice.app.EventSourceHandler), f
-            f.retries = retries
+            if retries is not None:
+                assert isinstance(f, chalice.app.EventSourceHandler), f
+                f.retries = retries
             return f
 
         return wrapper

src/azul/chalice.py Outdated Show resolved Hide resolved
@hannes-ucsc hannes-ucsc added 1 review [process] Lead requested changes once and removed 0 reviews [process] Lead didn't request any changes labels Apr 5, 2024
@hannes-ucsc hannes-ucsc removed their assignment Apr 5, 2024
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6097-retry-cachehealth-failures branch 2 times, most recently from ad335e0 to e25a9a1 Compare April 15, 2024 21:21
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/5622-bump-fwdr-alarm-threshold branch 3 times, most recently from a915bb0 to b24d6f0 Compare May 13, 2024 18:33
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/5622-bump-fwdr-alarm-threshold branch 5 times, most recently from e2fb053 to e3c8430 Compare May 24, 2024 05:47
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/5622-bump-fwdr-alarm-threshold branch 3 times, most recently from c61cf7e to 0b7c3c4 Compare June 3, 2024 22:00
@hannes-ucsc hannes-ucsc force-pushed the issues/achave11-ucsc/5622-bump-fwdr-alarm-threshold branch from c6124a7 to 6a4d709 Compare June 6, 2024 07:27
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/5622-bump-fwdr-alarm-threshold branch 2 times, most recently from 484f245 to 1854a8e Compare June 7, 2024 00:24
@achave11-ucsc achave11-ucsc changed the base branch from issues/achave11-ucsc/5622-bump-fwdr-alarm-threshold to develop June 7, 2024 17:39
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6097-retry-cachehealth-failures branch 2 times, most recently from ea8e82e to a75eb6e Compare June 7, 2024 17:52
@achave11-ucsc achave11-ucsc requested a review from hannes-ucsc June 7, 2024 21:58
@hannes-ucsc
Copy link
Member

Security design review

  • Security design review completed; this PR does not
    • … affect authentication; for example:
      • OAuth 2.0 with the application (API or Swagger UI)
      • Authentication of developers with Google Cloud APIs
      • Authentication of developers with AWS APIs
      • Authentication with a GitLab instance in the system
      • Password and 2FA authentication with GitHub
      • API access token authentication with GitHub
      • Authentication with Terra
    • … affect the permissions of internal users like access to
      • Cloud resources on AWS and GCP
      • GitLab repositories, projects and groups, administration
      • an EC2 instance via SSH
      • GitHub issues, pull requests, commits, commit statuses, wikis, repositories, organizations
    • … affect the permissions of external users like access to
      • TDR snapshots
    • … affect permissions of service or bot accounts
      • Cloud resources on AWS and GCP
    • … affect audit logging in the system, like
      • adding, removing or changing a log message that represents an auditable event
      • changing the routing of log messages through the system
    • … affect monitoring of the system
    • … introduce a new software dependency like
      • Python packages on PYPI
      • Command-line utilities
      • Docker images
      • Terraform providers
    • … add an interface that exposes sensitive or confidential data at the security boundary
    • … affect the encryption of data at rest
    • … require persistence of sensitive or confidential data that might require encryption at rest
    • … require unencrypted transmission of data within the security boundary
    • … affect the network security layer; for example by
      • modifying, adding or removing firewall rules
      • modifying, adding or removing security groups
      • changing or adding a port a service, proxy or load balancer listens on
  • Documentation on any unchecked boxes is provided in comments below

@achave11-ucsc achave11-ucsc mentioned this pull request Jun 11, 2024
7 tasks
@achave11-ucsc achave11-ucsc force-pushed the issues/achave11-ucsc/6097-retry-cachehealth-failures branch from a75eb6e to 63b8a78 Compare June 11, 2024 20:58
@achave11-ucsc achave11-ucsc added the sandbox [process] Resolution is being verified in sandbox deployment label Jun 11, 2024
@achave11-ucsc achave11-ucsc merged commit fcdec05 into develop Jun 11, 2024
11 checks passed
@achave11-ucsc achave11-ucsc deleted the issues/achave11-ucsc/6097-retry-cachehealth-failures branch June 12, 2024 00:45
@achave11-ucsc achave11-ucsc removed their assignment Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 review [process] Lead requested changes once orange [process] Done by the Azul team sandbox [process] Resolution is being verified in sandbox deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants