You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by GitBox <gi...@apache.org> on 2022/09/07 11:58:13 UTC

[GitHub] [solr-operator] alfonsomunozpomer opened a new issue, #470: Target port of common and headless services are 0 in GKE Autopilot clusters

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

   I created a SolrCloud on a [GKE Autopilot cluster](https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview) with the following YAML:
   ```yaml
   # https://apache.github.io/solr-operator/example/test_solrcloud.yaml
   apiVersion: solr.apache.org/v1beta1
   kind: SolrCloud
   metadata:
     name: gxa
     namespace: jenkins-gene-expression
   spec:
     dataStorage:
       persistent:
         reclaimPolicy: Retain
         pvcTemplate:
           spec:
             resources:
               requests:
                 storage: "15Gi"
     replicas: 2
     solrImage:
       tag: 8.7.0
     solrJavaMem: "-Xms1g -Xmx3g"
   #  solrModules:
   #    - jaegertracer-configurator
   #    - ltr
     customSolrKubeOptions:
       podOptions:
         resources:
           limits:
             memory: "1G"
           requests:
             cpu: "65m"
             memory: "156Mi"
     zookeeperRef:
       provided:
   #      chroot: "/this/will/be/auto/created"
         persistence:
           spec:
             storageClassName: fast
             resources:
               requests:
                 storage: "1Gi"
         replicas: 3
         zookeeperPodPolicy:
           resources:
             limits:
               memory: "512Mi"
             requests:
               cpu: "65m"
               memory: "156Mi"
   #  solrOpts: "-Dsolr.autoSoftCommit.maxTime=10000"
     solrGCTune: "-XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8"
   ```
   
   The target port of the headless and common services is set to 0, which is a minor annoyance because I need to create another service to do port-forwarding. It looks like the reason is that the `targetPort` is set to `solr-client`, rather than 8983.
   
   This is the relevant block in the headless service:
   ```yaml
     - appProtocol: http
       name: solr-client
       port: 8983
       protocol: TCP
       targetPort: solr-client
   ```
   
   And this is the one from the client service:
   ```yaml
     - appProtocol: http
       name: solr-client
       port: 80
       protocol: TCP
       targetPort: solr-client
   ```
   
   Is this expected behaviour or something specific to GKE clusters?


-- 
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] alfonsomunozpomer commented on issue #470: Target port of common and headless services are 0 in GKE Autopilot clusters

Posted by GitBox <gi...@apache.org>.
alfonsomunozpomer commented on issue #470:
URL: https://github.com/apache/solr-operator/issues/470#issuecomment-1239664337

   Thanks @HoustonPutman. I’ve checked and MCS are disabled in our cluster. I’ll try to find my way in GKE to report the issue.


-- 
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] alfonsomunozpomer closed issue #470: Target port of common and headless services are 0 in GKE Autopilot clusters

Posted by GitBox <gi...@apache.org>.
alfonsomunozpomer closed issue #470: Target port of common and headless services are 0 in GKE Autopilot clusters
URL: https://github.com/apache/solr-operator/issues/470


-- 
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] alfonsomunozpomer commented on issue #470: Target port of common and headless services are 0 in GKE Autopilot clusters

Posted by GitBox <gi...@apache.org>.
alfonsomunozpomer commented on issue #470:
URL: https://github.com/apache/solr-operator/issues/470#issuecomment-1239688233

   Well, guess what, it looks like something’s wrong in GKE. [I reported the issue](https://issuetracker.google.com/issues/245363154).


-- 
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 #470: Target port of common and headless services are 0 in GKE Autopilot clusters

Posted by GitBox <gi...@apache.org>.
HoustonPutman commented on issue #470:
URL: https://github.com/apache/solr-operator/issues/470#issuecomment-1239510779

   Are you using Multi Cluster Services in GKE? If so there is a known issue with them and named target ports that will be fixed in a future version: https://cloud.google.com/kubernetes-engine/docs/how-to/multi-cluster-services#container_port
   
   If not, then I would suggest issuing a bug-report with GKE. Using a targetPort name is very much supported by Kubernetes, and GKE not supporting it would be a pretty big deal, I think.
   
   Sorry that you are facing this annoyance, and hopefully we can figure out why GKE is behaving in this way...
   
   


-- 
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] alfonsomunozpomer commented on issue #470: Target port of common and headless services are 0 in GKE Autopilot clusters

Posted by GitBox <gi...@apache.org>.
alfonsomunozpomer commented on issue #470:
URL: https://github.com/apache/solr-operator/issues/470#issuecomment-1239694186

   To clarify, the issue is at the web dashboard level, the service works as expected.


-- 
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