Uploading assets will now happen in the background by default (a blocking=true can be used in the query string to block until the asset uploads)
[x] Specify the timeout on the asset elasticsearch upload request (to avoid dealing with the default elasticsearch timeout of 2m)
[x] Add the platform / arch / node_version support in the asset.json and store it in the elasticsearch (which will be used for finding the right asset to use)
Set the timeout on the api server and proxy request from the cluster master to the api server
Reduce the number of file system writes needs to load an asset
Simplify the asset loading process by not trying to magically move the asset directory up a directory when it is not built correctly.
Improves error handling when saving assets
v0.65.1
Updates dev dependencies and cleans up some dependency use
Replace use of request with got (because request was deprecated a long time ago)
v0.65.0
This release includes the following changes:
Add api_response_timeout to prevent socket timeouts when posting assets (this is a stop gap measure)
Add kubernetes_worker_antiaffinity server configuration option
Add cpu_execution_controller and memory_execution_controller job and configuration options, using low values by default to prevent over reserving resources.
v0.64.5 - Update base docker image to fix node-rdkafka
Updates docker base image to terascope/node-base:10.19.0-2, fixes node-rdkafka ssl issues. The base image switches back to using alpine.
This release removes the Kubernetes service that the workers used to communicate with the execution controller. They now just communicate directly with the pod IP from the execution controller. When high availability execution controllers are implemented, this will need to be reconsidered.
All teraslice jobs should be stopped before upgrading Teraslice master.
v0.64.1 - memory leak fixes in utils
... (truncated)
Commits
6645fb1 Merge pull request #1933 from terascope/node-12-rc
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps @terascope/scripts from 0.63.0 to 0.67.0.
Release notes
Sourced from
@terascope/scripts
's releases.... (truncated)
Commits
6645fb1
Merge pull request #1933 from terascope/node-12-rc360f003
release: (minor) teraslice@0.67.0f4c9572
release: (preminor) teraslice@0.67.0-rc.0bbefe3c
use base image that uses the older node-rdkafka / libkafkac476747
release: (preminor) teraslice@0.67.0-rc.0a585042
release: (prerelease) teraslice@0.66.0-rc.4b50e1df
Switch docker image to use node-rdkafka 2.9.x (terascope/node-base:12.18.0-1)fd828fe
use node 12.18454b742
release: (prerelease) teraslice@0.66.0-rc.303ab665
switch to using the latest kafka connectorDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show