Introduction to Cloud Dataproc: Hadoop and Spark on Google Cloud Reviews
8805 reviews
Shawn T. · Reviewed 5 months ago
Cecil A. · Reviewed 5 months ago
Andrew M. · Reviewed 5 months ago
Aidan T. · Reviewed 5 months ago
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. · Reviewed 6 months ago
Cannot get pass first step of creating cluster. When clicked on Create, encountered an permission issue
Fu Hsien N. · Reviewed 6 months ago
Ahmed A. · Reviewed 6 months ago
It wouldn't let me create the cluster. Thereby making the lab impossible.
Crazy B. · Reviewed 6 months ago
lab did not worked
Eduardo V. · Reviewed 6 months ago
Giancarlo D. · Reviewed 6 months ago
Lab need to be updated. Not able to recreate the mentioned clustor. there were additional steps involved
Ahmed A. · Reviewed 6 months ago
Muhammad N. · Reviewed 6 months ago
Mike W. · Reviewed 6 months ago
Nandan S. · Reviewed 6 months ago
Tim B. · Reviewed 6 months ago
Javier G. · Reviewed 6 months ago
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. · Reviewed 6 months ago
Laurence P. · Reviewed 6 months ago
10
JOSE MANUEL B. · Reviewed 6 months ago
Roberto I. · Reviewed 6 months ago
cant create cluster
Vyshnavi R. · Reviewed 6 months ago
Krishna D. · Reviewed 6 months ago
Rahul S. · Reviewed 6 months ago
Javier G. · Reviewed 6 months ago
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. · Reviewed 6 months ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.