Eclipse che - volume mount error while launching more than 5 workspace at a time
See original GitHub issueDescribe the bug
Logged in 10 different users at the same time and launched 10 workspaces of each users at a time. 3 - 5 users are able to launch the workspace successfully, for remaining users getting time out error in mount volume, some users keep on loading the workspace and nothing is initialised in log window.
Che version
- latest
Advanced configuration:
Runtime
- kubernetes (include output of
kubectl version
)- kubectl version - Client Version: version.Info{Major:“1”, Minor:“20”, GitVersion:“v1.20.4”, GitCommit:“e87da0bd6e03ec3fea7933c4b5263d151aafd07c”, GitTreeState:“clean”, BuildDate:“2021-02-18T16:12:00Z”, GoVersion:“go1.15.8”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“18+”, GitVersion:“v1.18.12-gke.1210”, GitCommit:“199a41188dc0ca5d6d95b1cc7e8ba96e05f9dd0a”, GitTreeState:“clean”, BuildDate:“2021-02-05T18:03:16Z”, GoVersion:“go1.13.15b4”, Compiler:“gc”, Platform:“linux/amd64”}
Installation method
- chectl
- chectl installation command - sudo chectl server:deploy --installer=helm --platform=k8s --domain=cl-ide.domain.com --multiuser --installer=operator
- chectl version - chectl/7.27.1 linux-x64 node-v12.21.0
Environment
- my computer
- Linux
- Cloud
- GCE
- Google Kubernete Engine (GKE) - with 2 nodes running
- Node Configuration - 2 core 8 GB memory Machine with 30 GB hardisk
- Auto scale is enabaled
- GCE
Screenshots
Steps to reproduce
- Login 10 users at a time.
- launch 10 different workspace at time.
Expected behavior
It should be able to launch more than 50 workspaces at a time.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Eclipse che - volume mount error while launching workspace ...
Logged in 10 different users at the same time and launched 10 workspaces of each users at a time. 3 - 5 users...
Read more >Newcomers » Unable to bring up the workspace for Eclipse che.
I am trying to run che locally on a Ubuntu system for single user. I have the setup over Minikube. I have been...
Read more >Installation Guide Red Hat CodeReady Workspaces 2.7
This Can be:`common` (all workspaces PVCs in one volume), per-workspace (one PVC per workspace for all ... The installation might take more than...
Read more >Build Docker CLIs Your Users Will Love | Eclipse Che Blog
After 9 months of development, we recently released Eclipse Che 5. ... familiar with the nuances of volume mounting and syntax errors on...
Read more >Devfile v2 and the DevWorkspace Operator - Part 1
A user cannot have more than one running workspace at a time. This limitation is related to the persistent volume strategy (“common”) that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Changed the configuration as follows:
Now tested with 20 users and launched 20 workspaces of random stacks. Most of the workspace skipped the error with
kubernetes failed to sync configmap cache timed out
but able to launch the workspace successfully. Nearly 15 - 17 workspace were launched successfully and nearly 4 - 5 workspace gotworkspace launch time out
error.Next step is to test about to launch 50 workspace simultaneously, and I will post the result here once the test is done.
Issues go stale after
180
days of inactivity.lifecycle/stale
issues rot after an additional7
days of inactivity and eventually close.Mark the issue as fresh with
/remove-lifecycle stale
in a new comment.If this issue is safe to close now please do so.
Moderators: Add
lifecycle/frozen
label to avoid stale mode.