You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Dhru205 (via GitHub)" <gi...@apache.org> on 2023/06/23 05:59:10 UTC

[GitHub] [solr-operator] Dhru205 opened a new issue, #579: Observed generation field addition in solr-operator code

Dhru205 opened a new issue, #579:
URL: https://github.com/apache/solr-operator/issues/579

   Hi,
   I am running solr operator 0.6.0 and solr version 9.1.0 in kubernetes environment and I want to configure the below changes:
   I want to add a status field called observed generation in solr-operator code, this field will help me to check how many times changes were made in solr were successful.
   Whenever we are describing the CustomResource deployed for a Solr cluster we should be able to display current status of cluster deployment such as Pending, Running or Failed. I want to see this is under status section while describing  CustomResource. Also I want observed generation field to be increase with every successful solr deployment.
   So let me know where exactly I need to add this feature in solr operator code.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org


[GitHub] [solr-operator] Dhru205 commented on issue #579: Observed generation field addition in solr-operator code

Posted by "Dhru205 (via GitHub)" <gi...@apache.org>.
Dhru205 commented on issue #579:
URL: https://github.com/apache/solr-operator/issues/579#issuecomment-1608857649

   Hi @HoustonPutman 
   I am attaching screenshots of one DB which has already in built feature of observed generation so that you can get the clarity of what exactly is the feature that I want to add in Solr.
   
   ![MicrosoftTeams-image (3)](https://github.com/apache/solr-operator/assets/69868710/d6470a1c-46b5-4eda-b8a6-183a149a3cdf)
   
   As you can see in the above screenshot I checked the CR of Cassandra.
   
   ![operator](https://github.com/apache/solr-operator/assets/69868710/21e290cc-2970-4755-86c2-2e7bc8bcc3ea)
   
   ![MicrosoftTeams-image (4)](https://github.com/apache/solr-operator/assets/69868710/f404b730-64a0-4769-8d3e-9e06af2296b5)
   
   The operator is in ready state and observed generation value is 1 since no changes are made in the configurations.
   
   ![MicrosoftTeams-image (5)](https://github.com/apache/solr-operator/assets/69868710/a3c2b4a5-f3a1-4396-aaf8-9ca3aaba2e43)
   ![MicrosoftTeams-image (6)](https://github.com/apache/solr-operator/assets/69868710/63d11c26-b459-4e59-b0a2-c1d0104432f4)
   
   I  changed the CPU and resources of Cassandra and only after all the pods are up and running then only observed Gen value is changed from 1 to 2.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org


[GitHub] [solr-operator] HoustonPutman commented on issue #579: Observed generation field addition in solr-operator code

Posted by "HoustonPutman (via GitHub)" <gi...@apache.org>.
HoustonPutman commented on issue #579:
URL: https://github.com/apache/solr-operator/issues/579#issuecomment-1688527179

   Not sure what you mean by "this feature", but if you mean the locked cluster operations, its a feature of the solr operator and has been merged in for the next release (v0.8.0).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org


[GitHub] [solr-operator] HoustonPutman commented on issue #579: Observed generation field addition in solr-operator code

Posted by "HoustonPutman (via GitHub)" <gi...@apache.org>.
HoustonPutman commented on issue #579:
URL: https://github.com/apache/solr-operator/issues/579#issuecomment-1631442015

   Yeah, given #560 , we will have a pretty good idea as to when operations start/end. This could certainly be implemented. It looks like it's following a similar paradigm to pod status conditions. Not sure when it will get in, but this is certainly possible to do, and will be easier when the linked issue is resolved.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org


[GitHub] [solr-operator] HoustonPutman commented on issue #579: Observed generation field addition in solr-operator code

Posted by "HoustonPutman (via GitHub)" <gi...@apache.org>.
HoustonPutman commented on issue #579:
URL: https://github.com/apache/solr-operator/issues/579#issuecomment-1604512311

   > Whenever we are describing the CustomResource deployed for a Solr cluster we should be able to display current status of cluster deployment such as Pending, Running or Failed. I want to see this is under status section while describing CustomResource.
   
   Do the `Replicas`, `Ready Replicas` and `Up to date Replicas` values not provide this information already? It's hard for the solr operator to determine whether a non-ready cloud is "pending" or "failed", so this is would be difficult to implement.
   
   > Also I want observed generation field to be increase with every successful solr deployment.
   So let me know where exactly I need to add this feature in solr operator code.
   
   `increase with every successful solr deployment` needs to be more clear here. It could mean any update to the StatefulSet, or it could mean any update to the SolrCloud resource. Also what value does this provide?
   
   The statefulSet.Status has an `observedGeneration` field, is this what you are looking for?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org


[GitHub] [solr-operator] Dhru205 commented on issue #579: Observed generation field addition in solr-operator code

Posted by "Dhru205 (via GitHub)" <gi...@apache.org>.
Dhru205 commented on issue #579:
URL: https://github.com/apache/solr-operator/issues/579#issuecomment-1634237166

   Hi @HoustonPutman,
   When can we see this feature added in solr or is it still in the testing phase?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org


[GitHub] [solr-operator] rashiga commented on issue #579: Observed generation field addition in solr-operator code

Posted by "rashiga (via GitHub)" <gi...@apache.org>.
rashiga commented on issue #579:
URL: https://github.com/apache/solr-operator/issues/579#issuecomment-1721110058

   Hi ,
      I could understand that we are showing status per solr Node. Is there any way by which we can show an aggregated status through Observed Generation which tells us that the change in the spec that we have done is applied to the solr pods and they are running successfully?
      


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org