[SERVER-23188] Sever log, backup and TTL on delayed memeber quesions? Created: 16/Mar/16  Updated: 16/Mar/16  Resolved: 16/Mar/16

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.3.0, 3.3.2
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Mark Solomon Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I checked online but I didn't find a way of adding the IP to every log. Is there a way or a config to do it?

Also I want to set TTL but maintain a backup of the data before deletion.as well. Do you have a recommendation?
If we run another delayed member of a replica set with maximum compression, Will that Backup replica have the backup data or will the TTL delete the data from that backup? Example, main replica sets have 2016/2015 data with 1 year TTL. A backup Replica will be running with a one year delay. Will the backup member have 2015/2014?



 Comments   
Comment by Ramon Fernandez Marina [ 16/Mar/16 ]

Thanks for your report mohymmf. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. Questions like these involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Generated at Thu Feb 08 04:02:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.