Hello all,
I took the opportunity at the Milan Hackathon to work on improving the
Cloud VPS quota request workflow.
The result is https://cloudvps-quota.toolforge.org which gathers your
project's quota, your new quota request, justification and will pre-fill a
Phabricator task ready for you to submit. The idea is to streamline the
initial part of the quota request process. The rest is left unchanged
(policies, procedures, etc).
As usual, please reach out to WMCS on the usual channels for any comments,
feedback, bugs and so on.
HTH,
Filippo
--
*Filippo Giunchedi*
Staff Site Reliability Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello everyone,
As part of the ongoing upgrade of our Search infrastructure from OpenSearch
1.3 → 2.19 → 3.5, we recently upgraded the first production cluster (
cloudelastic).
Following the upgrade, the cluster has become unstable. In particular, some
indices have entered a read-only (red) state, which may impact search
functionality relying on this cluster.
We are currently investigating the issue from multiple angles. Early
indications suggest this may be related to readahead settings in
combination with the underlying storage hardware, but this is not yet
confirmed.
Tracking task: https://phabricator.wikimedia.org/T424852
Our current focus is on stabilizing the cluster and restoring full
functionality. We will share updates as we learn more. At this point, we
expect to have the cluster stabilized again by the end of the week.
If you are observing issues that you suspect are related, please add
details to the Phabricator task or reach out to the Search team.
Thanks for your patience,
Peter
--
Peter Fischer (he/him)
Senior Software Engineer, Search Platform
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello all,
in order to optimize Toolforge resources utilization we will be
progressively changing the default memory requests for webservice tools
from 256MB to 64MB. Memory and CPU requests are scheduler hints for
Kubernetes on how to allocate tools to worker nodes; the default memory
limit (i.e. enforced maximum memory usage) stays unchanged at 512MB. There
is no expected impact to tools using more memory than they request.
The first phase will involve changing requests from 256MB to 128MB on Wed
May 6th starting at 8 UTC, and from 128MB to 64MB on Tue May 12th starting
at 8 UTC. We will be restarting webservice tools as part of the deployment
and no action is required on tool maintainers' part.
The details of this work can be found at
https://phabricator.wikimedia.org/T420565
best,
Filippo
--
*Filippo Giunchedi*
Staff Site Reliability Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…