Solucionado (ver solução)
Solucionado
(ver solução)
1
resposta

"Sharding"

Olá! Tudo bem?

Eu estava seguindo as aulas e desenvolvendo os exercícios tranquilamente, sempre iniciando o mongo com mongod --dbpath e o "path" do banco de dados dentro da pasta do curso, porém agora o processo trava devido a um tal de "sharding". Já tentei resolver olhando no google, mas só encontro o que é sharding e não como resolver o problema. Alguém poderia me ajudar, por favor?

2019-10-07T19:51:35.805-0300 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none' 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] MongoDB starting : pid=10486 port=27017 dbpath=/home/samsung/Documentos/workspace/alura-mongo/db 64-bit host=Samsung 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] db version v4.2.0 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] git version: a4b751dcf51dd249c5865812b390cfd1c0129c30 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.1b 26 Feb 2019 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] allocator: tcmalloc 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] modules: none 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] build environment: 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] distmod: ubuntu1804 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] distarch: x86_64 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] target_arch: x86_64 2019-10-07T19:51:35.808-0300 I CONTROL [initandlisten] options: { storage: { dbPath: "/home/samsung/Documentos/workspace/alura-mongo/db" } } 2019-10-07T19:51:35.808-0300 I STORAGE [initandlisten] Detected data files in /home/samsung/Documentos/workspace/alura-mongo/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2019-10-07T19:51:35.809-0300 I STORAGE [initandlisten] 2019-10-07T19:51:35.809-0300 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine 2019-10-07T19:51:35.809-0300 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem 2019-10-07T19:51:35.809-0300 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3430M,cache_overflow=(file_max=0M),session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress], 2019-10-07T19:51:36.437-0300 I STORAGE [initandlisten] WiredTiger message [1570488696:437622][10486:0x7f76857e3d40], txn-recover: Recovering log 3 through 4 2019-10-07T19:51:36.492-0300 I STORAGE [initandlisten] WiredTiger message [1570488696:492205][10486:0x7f76857e3d40], txn-recover: Recovering log 4 through 4 2019-10-07T19:51:36.563-0300 I STORAGE [initandlisten] WiredTiger message [1570488696:563073][10486:0x7f76857e3d40], txn-recover: Main recovery loop: starting at 3/6528 to 4/256 2019-10-07T19:51:36.670-0300 I STORAGE [initandlisten] WiredTiger message [1570488696:670899][10486:0x7f76857e3d40], txn-recover: Recovering log 3 through 4 2019-10-07T19:51:36.778-0300 I STORAGE [initandlisten] WiredTiger message [1570488696:778850][10486:0x7f76857e3d40], txn-recover: Recovering log 4 through 4 2019-10-07T19:51:36.842-0300 I STORAGE [initandlisten] WiredTiger message [1570488696:842623][10486:0x7f76857e3d40], txn-recover: Set global recovery timestamp: (0,0) 2019-10-07T19:51:37.203-0300 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0) 2019-10-07T19:51:37.229-0300 I STORAGE [initandlisten] Timestamp monitor starting 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database. 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted. 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** WARNING: This server is bound to localhost. 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** Remote systems will be unable to connect to this server. 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** Start the server with --bind_ip

to specify which IP 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** addresses it should serve responses from, or with --bind_ip_all to 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** bind to all interfaces. If this behavior is desired, start the 2019-10-07T19:51:37.325-0300 I CONTROL [initandlisten] ** server with --bind_ip 127.0.0.1 to disable this warning. 2019-10-
1 resposta
solução!

Oi Lígia, tudo bem? Não encontrei nenhuma referência no erro que colorou falando sobre o sharding. Você poderia me dar mais informações sobre o que está acontecendo? Se você troca o dbpath, o que acontece? Ele consegue iniciar normalmente? Você está no Ubuntu?

Quer mergulhar em tecnologia e aprendizagem?

Receba a newsletter que o nosso CEO escreve pessoalmente, com insights do mercado de trabalho, ciência e desenvolvimento de software