You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by GitBox <gi...@apache.org> on 2021/05/17 09:23:43 UTC
[GitHub] [incubator-streampipes-installer] doemski opened a new pull request #15: [STREAMPIPES-no-issue-#] Document steps which were required to install StreamPipes into a k8s cluster in a new Troubleshooting segment in the README.
doemski opened a new pull request #15:
URL: https://github.com/apache/incubator-streampipes-installer/pull/15
<!--
Thanks for contributing! Here are some tips you can follow to help us incorporate your contribution quickly and easily:
1. If this is your first time, please read our contributor guidelines:
- https://streampipes.apache.org/getinvolved.html
- https://cwiki.apache.org/confluence/display/STREAMPIPES/Getting+Started
2. Make sure the PR title is formatted like: `[STREAMPIPES-<Jira issue #>] PR title ...`
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., `[WIP][STREAMPIPES-<Jira issue #>] PR title ...`.
4. Please write your PR title to summarize what this PR proposes/fixes.
5. Be sure to keep the PR description updated to reflect all changes.
6. If possible, provide a concise example to reproduce the issue for a faster review.
7. Make sure tests pass via `mvn clean install`.
8. (Optional) If the contribution is large, please file an Apache ICLA
- http://apache.org/licenses/icla.pdf
-->
### Purpose
<!--
Please clarify what changes you are proposing and describe how those changes will address the issue.
-->
Facilitation of the installation of StreamPipes into a Kubernetes cluster. This will document an issue which I came across and how I fixed it.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-streampipes-installer] mohanvive commented on pull request #15: [STREAMPIPES-no-issue-#] Document steps which were required to install StreamPipes into a k8s cluster in a new Troubleshooting segment in the README.
Posted by GitBox <gi...@apache.org>.
mohanvive commented on pull request #15:
URL: https://github.com/apache/incubator-streampipes-installer/pull/15#issuecomment-850980618
@doemski Thanks for the update. It seems there are some conflicts in this PR due to some recent changes. Would you mind resolving these conflicts? Then we could get it merged.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-streampipes-installer] doemski commented on a change in pull request #15: [STREAMPIPES-no-issue-#] Document steps which were required to install StreamPipes into a k8s cluster in a new Troubleshooting segment in the README.
Posted by GitBox <gi...@apache.org>.
doemski commented on a change in pull request #15:
URL: https://github.com/apache/incubator-streampipes-installer/pull/15#discussion_r633417791
##########
File path: k8s/README.md
##########
@@ -108,3 +108,31 @@ We'd love to hear your feedback! Subscribe to [users@streampipes.apache.org](mai
## License
[Apache License 2.0](../LICENSE)
+
+## Troubleshooting
+### Some of the Deployments Never Reach 'Ready' State
+#### ui
+The UI Deployment specifies so-called init containers which wait for the following deployments:
+* backend
+* connect-master
+* consul
+* couchdb
+* activemq
+
+This means that when at least one of these deployments are not reachable the containers running the UI will not start up. Chances are when you fix the issues with the the others it will start up fine.
+
+#### backend
+##### Multi-Attach Error
+###### Problem
+`kubectl describe pod <backend-pod-name>` shows the following message:
+
+```Multi-Attach error for volume "pvc-xxx-xxx" Volume is already exclusively attached to one node and can't be attached to another```
+
+The issue is that the 'backend' Deployment and the 'pipeline-elements-all-jvm' are specified to use the same PersistentVolume. For this to be possible without restrictions, the used StorageClass (which defaults to your cluster 'default') needs to create PersistentVolumes which are set to "ReadWriteMany". This means that the same volume can be accessed by multiple Nodes of the Kubernetes cluster.
+
+If you see this error then your 'default' StorageClass does not fulfill those requirements.
+
+###### Solution
+The easiest way would be to switch to a StorageClass which allows for "ReadWriteMany" if possible.
+
+If that is not possible assign the Pods of the two Deployments (backend and pipeline-elements-all-jvm) to be always deployed on the same Node. For one way to do so see the Kubernetes documentation (https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/)
Review comment:
```suggestion
If that is not possible, assign the Pods of the two Deployments (backend and pipeline-elements-all-jvm) to be always deployed on the same Node. For one way to do so see the Kubernetes documentation (https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/). **Be aware that this will decrease StreamPipes' built-in scalability and potentially its uptime. A single Kubernetes node has limited resources and cannot guarantee an uptime of 100%**
```
##########
File path: k8s/README.md
##########
@@ -108,3 +108,31 @@ We'd love to hear your feedback! Subscribe to [users@streampipes.apache.org](mai
## License
[Apache License 2.0](../LICENSE)
+
+## Troubleshooting
+### Some of the Deployments Never Reach 'Ready' State
+#### ui
+The UI Deployment specifies so-called init containers which wait for the following deployments:
+* backend
+* connect-master
+* consul
+* couchdb
+* activemq
+
+This means that when at least one of these deployments are not reachable the containers running the UI will not start up. Chances are when you fix the issues with the the others it will start up fine.
Review comment:
```suggestion
This means that when at least one of these deployments are not reachable the containers running the UI will not start up. Chances are when you fix the issues with the others it will start up fine.
```
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-streampipes-installer] dominikriemer commented on pull request #15: [STREAMPIPES-no-issue-#] Document steps which were required to install StreamPipes into a k8s cluster in a new Troubleshooting segment in the README.
Posted by GitBox <gi...@apache.org>.
dominikriemer commented on pull request #15:
URL: https://github.com/apache/incubator-streampipes-installer/pull/15#issuecomment-842648720
Hi @doemski thanks for the PR and the useful additions to the README!
Can you please change the target branch of the PR from master to dev? Our master branch is synched with the latest official release and ASF regulations prevent us from changing already released artifacts.
Once your merge is in dev, it will be also available in the next official release (hopefully soon).
Thanks again for your contribution!
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-streampipes-installer] doemski commented on pull request #15: [STREAMPIPES-no-issue-#] Document steps which were required to install StreamPipes into a k8s cluster in a new Troubleshooting segment in the README.
Posted by GitBox <gi...@apache.org>.
doemski commented on pull request #15:
URL: https://github.com/apache/incubator-streampipes-installer/pull/15#issuecomment-842897863
Hi @dominikriemer
of course, my bad for not reading the guidelines. I just encountered this during work hours and wanted to document it quickly.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [incubator-streampipes-installer] doemski commented on a change in pull request #15: [STREAMPIPES-no-issue-#] Document steps which were required to install StreamPipes into a k8s cluster in a new Troubleshooting segment in the README.
Posted by GitBox <gi...@apache.org>.
doemski commented on a change in pull request #15:
URL: https://github.com/apache/incubator-streampipes-installer/pull/15#discussion_r633417791
##########
File path: k8s/README.md
##########
@@ -108,3 +108,31 @@ We'd love to hear your feedback! Subscribe to [users@streampipes.apache.org](mai
## License
[Apache License 2.0](../LICENSE)
+
+## Troubleshooting
+### Some of the Deployments Never Reach 'Ready' State
+#### ui
+The UI Deployment specifies so-called init containers which wait for the following deployments:
+* backend
+* connect-master
+* consul
+* couchdb
+* activemq
+
+This means that when at least one of these deployments are not reachable the containers running the UI will not start up. Chances are when you fix the issues with the the others it will start up fine.
+
+#### backend
+##### Multi-Attach Error
+###### Problem
+`kubectl describe pod <backend-pod-name>` shows the following message:
+
+```Multi-Attach error for volume "pvc-xxx-xxx" Volume is already exclusively attached to one node and can't be attached to another```
+
+The issue is that the 'backend' Deployment and the 'pipeline-elements-all-jvm' are specified to use the same PersistentVolume. For this to be possible without restrictions, the used StorageClass (which defaults to your cluster 'default') needs to create PersistentVolumes which are set to "ReadWriteMany". This means that the same volume can be accessed by multiple Nodes of the Kubernetes cluster.
+
+If you see this error then your 'default' StorageClass does not fulfill those requirements.
+
+###### Solution
+The easiest way would be to switch to a StorageClass which allows for "ReadWriteMany" if possible.
+
+If that is not possible assign the Pods of the two Deployments (backend and pipeline-elements-all-jvm) to be always deployed on the same Node. For one way to do so see the Kubernetes documentation (https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/)
Review comment:
```suggestion
If that is not possible, assign the Pods of the two Deployments (backend and pipeline-elements-all-jvm) to be always deployed on the same Node. For one way to do so see the Kubernetes documentation (https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes/). **Be aware that this will decrease StreamPipes' built-in scalability and potentially its uptime. A single Kubernetes node has limited resources and cannot guarantee an uptime of 100%**
```
##########
File path: k8s/README.md
##########
@@ -108,3 +108,31 @@ We'd love to hear your feedback! Subscribe to [users@streampipes.apache.org](mai
## License
[Apache License 2.0](../LICENSE)
+
+## Troubleshooting
+### Some of the Deployments Never Reach 'Ready' State
+#### ui
+The UI Deployment specifies so-called init containers which wait for the following deployments:
+* backend
+* connect-master
+* consul
+* couchdb
+* activemq
+
+This means that when at least one of these deployments are not reachable the containers running the UI will not start up. Chances are when you fix the issues with the the others it will start up fine.
Review comment:
```suggestion
This means that when at least one of these deployments are not reachable the containers running the UI will not start up. Chances are when you fix the issues with the others it will start up fine.
```
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org