Comments (11)
periklis
commented on September 24, 2024
1
@davidkarlsen Thanks for the reporting this. I am currently investigating this one on a running cluster and attached pprof to get some details.
from elasticsearch-operator.
jcantrill
commented on September 24, 2024
We do not control the department created by OLM unless that is a value that can be set in the manifest, which sounds like a unpreferred option. @ecordell ?
from elasticsearch-operator.
davidkarlsen
commented on September 24, 2024
from elasticsearch-operator.
jcantrill
commented on September 24, 2024
@davidkarlsen which operator is at issue here. Is it the Elasticsearch-operator or the image you referenced: cluster-logging-operator
from elasticsearch-operator.
periklis
commented on September 24, 2024
After some intensive profiling, I am sure we hit this issue: kubernetes/apimachinery#124 as per elasticsearch-operator still using k8s 1.18 deps. I am preparing a PR for master to bump the deps to 1.20.2.
from elasticsearch-operator.
periklis
commented on September 24, 2024
I am running the operator with k8s 1.21 deps on #775 for 4h and we get a steady 200Mi heap usage.
from elasticsearch-operator.
openshift-bot
commented on September 24, 2024
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
from elasticsearch-operator.
periklis
commented on September 24, 2024
/close A fix is release with 5.3.0 so closing this one:
from elasticsearch-operator.
openshift-bot
commented on September 24, 2024
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
from elasticsearch-operator.
openshift-bot
commented on September 24, 2024
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
from elasticsearch-operator.
openshift-ci
commented on September 24, 2024
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from elasticsearch-operator.
Related Issues (20)
- Running elasticsearch on CRC HOT 7
- Please prepare bundle for OCP 4.7 HOT 3
- Not launching kibana instance from elasticsearch operator HOT 1
- Unable to launch a Kibana CR instance using latest ElasticSearch operator, Steps needed HOT 12
- Kibana POD is not getting created in OCP 4.6 cluster (Elasticsearch instance + POD got created, Kibana instance created but POD is not created) HOT 6
- Index creation permission HOT 9
- Feature request: Allow setting shard allocation awareness HOT 4
- Elasticsearch-operator scaling info/documentation/manual HOT 2
- Avoid copying all file to the image HOT 1
- OLM doesn't trigger CSV update even though catalog has newer version HOT 2
- Unable to read /etc/elasticsearch/secret/searchguard-key.p12 HOT 4
- elastic-search pod not starting up HOT 8
- keytool error: java.io.IOException: parseAlgParameters failed: PBE AlgorithmParameters not available HOT 6
- Search query with bearer token returning no results HOT 5
- index rollover cronjob fails on openshift-logging operator HOT 7
- DNS flood coming from elasticsearch-operator pod HOT 4
- CrashLoopBackoff when installing on kind 0.18 (GOMAXPROCS?)
- How to install from the command line HOT 7
- OpenShift Elasticsearch Operator (v5.7.6) error (Received an empty response from elasticsearch -- server may not be ready) HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from elasticsearch-operator.