Introduction to Managed Service for Apache Spark: Hadoop and Spark on Google Cloud recensioni

Cecil A. · Recensione inserita oltre 2 anni fa

Andrew M. · Recensione inserita oltre 2 anni fa

Aidan T. · Recensione inserita oltre 2 anni fa

Another very good lab, taught me about dataproc clusters, and how to submit spark jobs, and also on top of that how to shut down the cluster.

Harry B. · Recensione inserita oltre 2 anni fa

Cannot get pass first step of creating cluster. When clicked on Create, encountered an permission issue

Fu Hsien N. · Recensione inserita oltre 2 anni fa

Ahmed A. · Recensione inserita oltre 2 anni fa

It wouldn't let me create the cluster. Thereby making the lab impossible.

Crazy B. · Recensione inserita oltre 2 anni fa

lab did not worked

Eduardo V. · Recensione inserita oltre 2 anni fa

Giancarlo D. · Recensione inserita oltre 2 anni fa

Lab need to be updated. Not able to recreate the mentioned clustor. there were additional steps involved

Ahmed A. · Recensione inserita oltre 2 anni fa

Muhammad N. · Recensione inserita oltre 2 anni fa

Mike W. · Recensione inserita oltre 2 anni fa

Nandan S. · Recensione inserita oltre 2 anni fa

Tim B. · Recensione inserita oltre 2 anni fa

Javier G. · Recensione inserita oltre 2 anni fa

Seem there are some mismatch in permission role for account. I cannot create the cluster, so I failed this lab Detailed: ```Permissions are missing for the default service account '863204665550-compute@developer.gserviceaccount.com', missing permissions: [storage.buckets.get, storage.objects.create, storage.objects.delete, storage.objects.get, storage.objects.list, storage.objects.update] on the project 'projects/qwiklabs-gcp-01-4e363bb3c79a'. This usually happens when a custom resource (ex: custom staging bucket) or a user-managed VM Service account has been provided and the default/user-managed service account hasn't been granted enough permissions on the resource. See https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/service-accounts#VM_service_account.```

Vong H. · Recensione inserita oltre 2 anni fa

Laurence P. · Recensione inserita oltre 2 anni fa

10

JOSE MANUEL B. · Recensione inserita oltre 2 anni fa

Roberto I. · Recensione inserita oltre 2 anni fa

cant create cluster

Vyshnavi R. · Recensione inserita oltre 2 anni fa

Krishna D. · Recensione inserita oltre 2 anni fa

Rahul S. · Recensione inserita oltre 2 anni fa

Javier G. · Recensione inserita oltre 2 anni fa

please resolve: Multiple validation errors: - Insufficient 'SSD_TOTAL_GB' quota. Requested 700.0, available 500.0. Your resource request exceeds your available quota. See https://cloud.google.com/compute/resource-usage. Use https://cloud.google.com/docs/quotas/view-manage#requesting_higher_quota to request additional quota. - Permissions are missing for the default service account '142410756184-compute@developer.gserviceaccount.com', missing permissions: [storage.buckets.get, storage.objects.create, storage.objects.delete, storage.objects.get, storage.objects.list, storage.objects.update] on the project 'projects/qwiklabs-gcp-03-7f26ae5689d0'. This usually happens when a custom resource (ex: custom staging bucket) or a user-managed VM Service account has been provided and the default/user-managed service account hasn't been granted enough permissions on the resource. See https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/service-accounts#VM_service_account. - Subnetwork 'default' does not support Private Google Access which is required for Dataproc clusters when 'internal_ip_only' is set to 'true'. Enable Private Google Access on subnetwork 'default' or set 'internal_ip_only' to 'false'. Request ID: 5702995233770175482 Multiple validation errors: - Permissions are missing for the default service account '142410756184-compute@developer.gserviceaccount.com', missing permissions: [storage.buckets.get, storage.objects.create, storage.objects.delete, storage.objects.get, storage.objects.list, storage.objects.update] on the project 'projects/qwiklabs-gcp-03-7f26ae5689d0'. This usually happens when a custom resource (ex: custom staging bucket) or a user-managed VM Service account has been provided and the default/user-managed service account hasn't been granted enough permissions on the resource. See https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/service-accounts#VM_service_account. - Subnetwork 'default' does not support Private Google Access which is required for Dataproc clusters when 'internal_ip_only' is set to 'true'. Enable Private Google Access on subnetwork 'default' or set 'internal_ip_only' to 'false'. Request ID: 8136817433604887835 Subnetwork 'default' does not support Private Google Access which is required for Dataproc clusters when 'internal_ip_only' is set to 'true'. Enable Private Google Access on subnetwork 'default' or set 'internal_ip_only' to 'false'. Request ID: 4564149215411688472

Artsiom N. · Recensione inserita oltre 2 anni fa

Alexander C. · Recensione inserita oltre 2 anni fa