Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML Services
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed PostgreSQL
    • Recovering a Managed Services for PostgreSQL cluster after its disks become Read Only
    • You are unable to delete your Managed Service for PostgreSQL cluster in the Dead status if deletion protection was enabled for it
    • Managed Service for PostgreSQL cluster switches to the Unknown state immediately after creation
    • Resolving issues with updating configurations of clusters with local-ssd disks
    • Resolving the consequences of cluster storage overflow with WAL logs
    • Resolving the psql error "could not translate host name to address nodename nor servname provided, or not known"
    • Resolving the error Unrecognized configuration parameter "stats_temp_directory"
    • Resolving the "max_connections conn_limit is too high" error
    • Resolving the "422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries" error
    • Understanding the Conn limit parameter
    • How to set up SQL query filtering
    • How to enable SQL query logging

In this article:

  • Issue description
  • Solution
  1. Managed PostgreSQL
  2. Managed Service for PostgreSQL cluster switches to the Unknown state immediately after creation

Managed Service for PostgreSQL cluster switches to the Unknown state immediately after creation

Written by
Yandex Cloud
Updated at September 12, 2023
  • Issue description
  • Solution

Issue descriptionIssue description

Trying to create a cluster with the b1.nano host class fails, and the cluster switches to the Unknown status.

SolutionSolution

It may take a long time to deploy a cluster with this host type. This is because of too low a percentage of guaranteed CPU uptime: 5% for b1.nano.
Clusters with this host type have two vCPUs with the guaranteed uptime of 5% and 2 GB RAM.

We cannot consistently forecast the behavior for the guaranteed CPU uptime of less than 50%. Generally speaking, creating clusters with b1.nano host classes is a longer process because of limited resources used for deploying components to the hosts.

When creating your clusters, better select more powerful configurations with CPU uptime of more than 50%, for example, c3-c2-m4.

Alert

The b1.nano host class is being phased out.
You will not be able to create a new cluster with this host class.

For an up-to-date list of host classes, see the documentation section.

Was the article helpful?

Previous
You are unable to delete your Managed Service for PostgreSQL cluster in the Dead status if deletion protection was enabled for it
Next
Resolving issues with updating configurations of clusters with local-ssd disks
© 2025 Direct Cursus Technology L.L.C.