awslabs/aws-athena-query-federation

[BUG] Cloudwatch Logs Connector Request Size Exceeded

Open

#74 opened on Dec 6, 2019

View on GitHubContributor guide
 (1 comment) (1 reaction) (1 assignee)Java (346 forks)auto 404
buggood first issue

Repository metrics

Stars
 (611 stars)
PR merge metrics
 (PR metrics pending)

Description

In the ANT222r workshop a customer ran into an issue querying the all_log_streams table. Mert / Anthony have the query id that generated the error. On the surface we suspect that the query created too many partitions or one of the log lines was so big that it exceeded the Lambda response size but somehow did not get spilled. this error needs to be investigated as it probably represents an edge case in the sdk or connector that our scale tests did not catch.

Contributor guide

Research direction
Investigate the CloudWatch Logs connector to understand how request size is handled. Look for any spilling mechanism or partition creation logic that might cause the Lambda response size to be exceeded. Trace the code path for large log lines or excessive partitions.
Tech stack
java
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
JavaAWS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35