Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for DataProc
    • DataProc cluster is in the Unknown state immediately after creation
    • Resolving the error of access to S3 buckets from a DataProc 1.4 cluster

In this article:

  • Issue description
  • Solution
  • If the issue persists
  1. DataProc
  2. DataProc cluster is in the Unknown state immediately after creation

DataProc cluster is in the Unknown state immediately after creation

Written by
Yandex Cloud
Updated at December 16, 2024
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

When you create a DataProc cluster, its nodes remain in the Unknown state immediately after creation

SolutionSolution

The cluster can be in the UNKNOWN state because its instances are created without public IP addresses
They are not available from the internet and do not have internet access by default.

To grant online access to these instances, use the NAT gateway functionality.

  1. Create a NAT gateway.
  2. Add a routing table by selecting the created gateway as a NextHop node.
  3. Link the routing table to the subnet with the cluster's instances:
  4. Set up security groups if required.
    If you do not use security groups, skip this step.

As a result of these actions, the cluster should change to Running within several minutes.

If the issue persistsIf the issue persists

If the above actions didn't help, create a request for support.
In the request, specify the following information:

  1. ID of the problem DataProc cluster.
  2. Date and time when the cluster creation started.

Was the article helpful?

Previous
All solutions for DataProc
Next
Resolving the error of access to S3 buckets from a DataProc 1.4 cluster
© 2025 Direct Cursus Technology L.L.C.