Failed to fetch schema in MongoDB Datasource

  • Is this your first time deploying Airbyte?: Yes
  • Memory / Disk: you can use something like 16Gb / 25 Gb and 6 vCPU
  • Deployment: Docker on Local Mac M1 Macbook pro
  • Airbyte Version: 0.39.21-alpha
  • Source name/version: Mongodb 0.1.15
  • Destination name/version: Redshift 0.3.10
  • Step: The issue is happening during sync
  • Description: Remove this with the description of your problem.

Hello everyone,

So I’m trying to ingest from mongodb datasource and when I try to sync the error show related to fetch schema.

airbyte-worker | 2022-06-20 22:11:47 INFO i.a.w.i.DefaultAirbyteStreamFactory(lambda$create$0):61 - 2022-06-20 22:11:47 ERROR i.a.i.b.AirbyteExceptionHandler(uncaughtException):26 - Something went wrong in the connector. See the logs for more details.
airbyte-worker | 2022-06-20 22:11:47 INFO i.a.w.i.DefaultAirbyteStreamFactory(lambda$create$0):61 - com.mongodb.MongoCommandException: Command failed with error 148 (ReadConcernMajorityNotEnabled): ‘Majority read concern requested, but server was not started with --enableMajorityReadConcern.’ on server The full response is {“ok”: 0.0, “errmsg”: “Majority read concern requested, but server was not started with --enableMajorityReadConcern.”, “code”: 148, “codeName”: “ReadConcernMajorityNotEnabled”}

Im really dont know what is the problem, Im using for example and I dont have any configuration additional in the source.

error.log (96.3 KB)

Thanks a lot for your help !

Hey could ou check the resources (CPU/RAM) if there a peak could you increase them and try again?

Hi @harshith this is my actual configuration in docker

Do you think I need another configuration?

Yeah could you increase the resources and try again. For reference:

Perfect, Im going to increase with this new configuration

Sure let us know if you see the same error again

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.