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

AWS 2-2: Use New mmw-geoprocessing in Worker VM #3614

Closed
rajadain opened this issue Feb 14, 2024 · 1 comment · Fixed by #3620
Closed

AWS 2-2: Use New mmw-geoprocessing in Worker VM #3614

rajadain opened this issue Feb 14, 2024 · 1 comment · Fixed by #3620
Assignees
Labels
AWS Funding Source: AWS

Comments

@rajadain
Copy link
Member

Once a new, upgraded mmw-geoprocessing is available, post WikiWatershed/mmw-geoprocessing#106, import it to the Worker VM, performing appropriate upgrades (dependencies such as Java, Scala, etc).

@rajadain rajadain added the AWS Funding Source: AWS label Feb 14, 2024
@rajadain rajadain mentioned this issue Feb 14, 2024
49 tasks
@rajadain rajadain changed the title AWS 2-1: Use New mmw-geoprocessing in Worker VM AWS 2-2: Use New mmw-geoprocessing in Worker VM Feb 27, 2024
@rajadain rajadain self-assigned this Apr 8, 2024
@rajadain
Copy link
Member Author

rajadain commented May 3, 2024

Doesn't look like any Java upgrades are needed.

I am getting this message when using the 6.0.0 version:

Exception: [convert_data] huc8__1748 Geoprocessing Error.
Details: The request content was malformed:
EntityStreamSizeException: incoming entity size (8426814) exceeded size limit (8388608 bytes)! This may have been a parser limit (set via `akka.http.[server|client].parsing.max-content-length`), a decoder limit (set via `akka.http.routing.decode-max-size`), or a custom limit set with `withSizeLimit`.

This is even after setting MMW_GEOPROCESSING_MAXLEN to 150m. Will investigate further ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AWS Funding Source: AWS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant