This repository has been archived by the owner on Mar 17, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 57
Need to verify if rh-che is stable with the upstream CHE_CORE_JSONRPC setting and 1 GB of RAM #1337
Comments
ibuziuk
added
kind/task
kind/enhancement
level/intermediate
and removed
kind/task
labels
Mar 28, 2019
About default upstream values, I was able to cause the OOM crash on upstream defaults as well. They will require some tweaking (namely message queue size) |
cc: @skabashnyuk ^ wdyt shoud upstream values be adjusted. IMO it would be great if che.openshift.io would use upstream setup for |
@ScrewTSW are you planning to provide upstream PR for review as part of this issue? |
Already doing some adjustment eclipse-che/che#13034 |
@skabashnyuk wdyt, once the adjustments are done upsteam - does it makes sense to fall back on those defaults in rh-che? |
6 tasks
ibuziuk
changed the title
Need to verify if rh-che is stable wit upstream CHE_CORE_JSONRPC setting and 1 GB of RAM
Need to verify if rh-che is stable with the upstream CHE_CORE_JSONRPC setting and 1 GB of RAM
Jun 3, 2020
PR sent - #1927 |
applied on production |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
PR introduced a few changes of CHE_CORE_JSONRPC which are most likely not needed and upstream values can be safely used - #1323
Need to verify if che.openshift.io works stable without sideeffects with 1Gb of RAM and upstream settings of
CHE_CORE_JSONRPC
.The text was updated successfully, but these errors were encountered: