Opiniones sobre Introducción a Managed Service para Apache Spark: Hadoop y Spark en Google Cloud

Cecil A. · Se revisó hace más de 2 años

Andrew M. · Se revisó hace más de 2 años

Aidan T. · Se revisó hace más de 2 años

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. · Se revisó hace más de 2 años

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

Fu Hsien N. · Se revisó hace más de 2 años

Ahmed A. · Se revisó hace más de 2 años

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

Crazy B. · Se revisó hace más de 2 años

lab did not worked

Eduardo V. · Se revisó hace más de 2 años

Giancarlo D. · Se revisó hace más de 2 años

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

Ahmed A. · Se revisó hace más de 2 años

Muhammad N. · Se revisó hace más de 2 años

Mike W. · Se revisó hace más de 2 años

Nandan S. · Se revisó hace más de 2 años

Tim B. · Se revisó hace más de 2 años

Javier G. · Se revisó hace más de 2 años

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. · Se revisó hace más de 2 años

Laurence P. · Se revisó hace más de 2 años

10

JOSE MANUEL B. · Se revisó hace más de 2 años

Roberto I. · Se revisó hace más de 2 años

cant create cluster

Vyshnavi R. · Se revisó hace más de 2 años

Krishna D. · Se revisó hace más de 2 años

Rahul S. · Se revisó hace más de 2 años

Javier G. · Se revisó hace más de 2 años

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. · Se revisó hace más de 2 años

Alexander C. · Se revisó hace más de 2 años