Hi Kamal, Solr (which includes the operator) is a volunteer community. So we don't really offer timeline estimates around fixes, because there's no way to predict if or when a volunteer might happen to pick up the ticket.
To your other question: opening an "Issue" on Github is sufficient for operator-related things. Issues for the Solr server itself still rely on JIRA for issue-tracking. I hope we'll unify and simplify that advice soon, but that's the current state of things... One last note: some of the discussion on the issue you linked suggest that this might be caused by your Solr pods running out of disk space. Have you looked into that theory? That might get you unblocked in practice without needing a volunteer to come along for #754. Good luck! Best, Jason On Tue, Jun 24, 2025 at 7:12 AM KAMAL SAI <kamalsa...@gmail.com> wrote: > > Dear Solr Dev Team, > > I hope this message finds you well. > > I created the following issue on GitHub: > https://github.com/apache/solr-operator/issues/754 > > I would like to check if there is any estimated timeline for when a fix for > this issue might be available. Additionally, could you please confirm > whether it's necessary for me to raise a corresponding bug in the Apache > Solr JIRA issue tracker, or if tracking it on GitHub is sufficient? > > Looking forward to your guidance. > > Best regards, > *Kamal Sai* --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
