By using AWS re:Post, you agree to the Terms of Use

Questions tagged with Amazon DocumentDB

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Failed to stabilize Instance with id

I have this problem: Failed to stabilize Instance with id. My CF looks like: Resources: DocumentDBSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: GroupName: 'DocumentDB SG' GroupDescription: !Sub 'Security Group for the DocumentDb' VpcId: !Ref VPC DocumentDBSubnetGroup: Type: AWS::DocDB::DBSubnetGroup Properties: DBSubnetGroupDescription: "Subnet group for Document DB cluster" DBSubnetGroupName: "document-db-subnet-group" SubnetIds: !Ref PrivateSubnetIds DocumentDBParameterGroup: Type: AWS::DocDB::DBClusterParameterGroup Properties: Description: "Parameter group for Document DB cluster" Family: docdb4.0 Name: "document-db-paramater-group" Parameters: audit_logs: "disabled" DocumentDBCluster: Type: AWS::DocDB::DBCluster Properties: BackupRetentionPeriod: 7 DBClusterIdentifier: "docdb" DBSubnetGroupName: !Ref DocumentDBSubnetGroup DBClusterParameterGroupName: !Ref DocumentDBParameterGroup Port: 27017 PreferredBackupWindow: "07:00-09:30" PreferredMaintenanceWindow: "tue:07:00-tue:11:00" VpcSecurityGroupIds: - !Ref DocumentDBSecurityGroup StorageEncrypted: true DocumentDBInstance: Type: AWS::DocDB::DBInstance DependsOn: - DocumentDBCluster Properties: DBClusterIdentifier: !Ref DocumentDBCluster DBInstanceClass: db.t3.medium DBInstanceIdentifier: "docdb" PreferredMaintenanceWindow: "tue:07:00-tue:11:00" If i search this problem i find information about RDS (snapshot), but i don't use snapshot in this deployment..
1
answers
0
votes
15
views
asked 2 days ago

DocumentDB mongorestore index fails to create with error 303: Field currently not supported

I have a DocDB instance running the 4.0 engine version. As stated here: [https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html#mongo-apis-index](https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html#mongo-apis-index), 2dsphere indexes are supported in this engine version, and that is correct, I have been able to create 2dsphere indexes. The problem comes when the index gets created. Default option fields will be added to the index metadata when created, and between those, the `v` field and the `2dsphereIndexVersion` field will be added to the index metadata options. These are the fields that are not supported when trying to restore an index definition from a mongodump containing a 2dsphere index. Steps to reproduce: Create the index: ``` db.collection.createIndex({ loc : "2dsphere" }) ``` Default option fields will be added to the index: ``` { "v" : 4, "name" : "loc_2dsphere", "ns" : "db.field", "2dsphereIndexVersion" : 1 } ``` So, when running a mongodump, the dump will contain this index metadata. Then, when trying to run a mongorestore of that dump, you get an error like this: ``` { "ok" : 0.0, "code" : 303.0, "errmsg" : "Field '2dsphereIndexVersion' is currently not supported", "operationTime" : Timestamp(1657665107, 1) } ``` or ``` { "ok" : 0.0, "code" : 303.0, "errmsg" : "Field 'v' is currently not supported", "operationTime" : Timestamp(1657665203, 1) } ``` mongorestore can be run with `--noIndexRestore` option but is there a way to restore the indexes?
1
answers
0
votes
30
views
asked 3 months ago

AWS 2dsphere limitation

Hi all, I am using DocumentDB with Mongo support on AWS and we are having documents that include geolocation. We have read the documentation of AWS for mongo support [here](https://docs.aws.amazon.com/documentdb/latest/developerguide/mongo-apis.html) but despite it says that it's supported we are receiving error during the creation of the index. The error we are getting when creating the index is : "*Command createIndexes failed : Index type not supported : 2dsphere*" The c# code that should generate the index is the below : ``` var prefixIndexName = nameof(Account.Address)+"."+nameof(Account.Address.Geolocation); if (!accountCollection.ExistIndex(prefixIndexName+"_2dsphere")) { Console.WriteLine("Seeding Geolocation Geo2DSphere Index ..."); var geoLocation = new StringFieldDefinition<Account>(prefixIndexName); var indexDefinition = new IndexKeysDefinitionBuilder<Account>().Geo2DSphere(geoLocation); var indexModel = new CreateIndexModel<Account>(indexDefinition, new CreateIndexOptions { Background = false }); accountCollection.CreateIndex(indexModel); } ``` The field that we are trying to add in the index is the "Address" and it looks like this : ``` "Address": { "CountryId": number, "PostCode": string, "AddressLine1": string, "AddressLine2": string, "City": string, "State": string, "Geolocation": { "type": "Point", "coordinates": decimal[] // e.g. [xx.xxxxxxx, xx.xxxxxxx] } } ``` The code is working on my local MongoDB installation, so I believe I am missing something to make it run on AWS. Any help you could provide is valuable, thanks in advance for your time!
0
answers
2
votes
35
views
asked 3 months ago

Quicksight Athena - analysis error: "HIVE_UNSUPPORTED_FORMAT: Unable to create input format"

Hello. I'm trying to create an analysis from my DocumentDB instance. I'm using the aws services Glue, Athena and Quicksight. In Glue I have created a connection to the DocumentDB and a crawler for auto creating tables. This works as expected and tables are created and displayed in glue. Even though I specify that the crawler should not give the tables any prefixes, it does add the database name as a prefix. When I look at the Glue catalog in Athena (the default AwsDataCatalog) I do see the database that was created in glue, however it does not show any tables. If I click on edit, it takes me to the correct database in glue which displays the tables that have been created by the previously mentioned crawler. So my first question is **Why doesn't the tables show up in Athena?** This is blocking me from performing queries in Athena. When I go to QuickSight and select the default Athena glue catalog ("AwsDataCatalog") I DO get the tables created by the crawler, and I can create datasets. However, when I try to create an analysis using these datasets, I get the error: ``` sourceErrorCode: 100071 sourceErrorMessage: [Simba][AthenaJDBC](100071) An error has been thrown from the AWS Athena client. HIVE_UNSUPPORTED_FORMAT: Unable to create input format ``` I have looked a bit around and some people said that this error is due to the table properties **"Input format"** and **"Output format"** being empty (which they indeed are for me). I have tried entering almost all the different formats to the table, but I keep on getting the Quicksight error above only now it has the input format at the end ``` HIVE_UNSUPPORTED_FORMAT: Unable to create input format json ``` **So my second questions is** I do not see anywhere in the crawler where I can specify input or output format. Does it have to be done manually? And What are the correct input and output formats for my setup?
0
answers
0
votes
84
views
asked 4 months ago