B-22205 B-22209 B-22210 Fix TGET ingestion for good

[cameroncaci]

B-22205
B-22209
B-22210

Warning

Hard blocked by I-13833

Note

Feature E-06422 will help resolve the blocker

See parent PR
transcom/trdm-lambda#34

[danieljordan-caci]

migrations look good

[traskowskycaci]

No concerns here, blocker noted and agree with the plan in the new future to resolve.

[deandreJones]

@cameroncaci for the blocking issue- RDS likely unable to perform
do we hav a plan forward to get this in? could we run these scripts over night- 1 by 1?

or are we hoping to get RDS scaled up ?

[cameroncaci]

@cameroncaci for the blocking issue- RDS likely unable to perform do we hav a plan forward to get this in? could we run these scripts over night- 1 by 1?

or are we hoping to get RDS scaled up ?

Pinged the BAs about it again in the issue ticket to try and make it a priority, it's currently at the architects. The plan (Or at least my plan, arch's haven't reached out to me yet) is to run one full DB sync, and then immediately replace it with incremental. We'll reserve full DB syncing for if any issues or HDTs pop up, but the incremental should be entirely fixed now.

BUT, the current RDS db can't even handle 1 full DB sync. Meaning we need to either:

• Temporarily scale up RDS for the full sync (Cost effective but less preferred as it's less predictable when budgeting)
• Temporarily have milmove downtime for 15 minutes while it can sync with TRDM
• Permanently scale up RDS (My preferred as it supports the application's growth and prevents unpredictable budget changes)

[deandreJones]

@cameroncaci for the blocking issue- RDS likely unable to perform do we hav a plan forward to get this in? could we run these scripts over night- 1 by 1?
or are we hoping to get RDS scaled up ?

Pinged the BAs about it again in the issue ticket to try and make it a priority, it's currently at the architects. The plan (Or at least my plan, arch's haven't reached out to me yet) is to run one full DB sync, and then immediately replace it with incremental. We'll reserve full DB syncing for if any issues or HDTs pop up, but the incremental should be entirely fixed now.

BUT, the current RDS db can't even handle 1 full DB sync. Meaning we need to either:

• Temporarily scale up RDS for the full sync (Cost effective but less preferred as it's less predictable when budgeting)
• Temporarily have milmove downtime for 15 minutes while it can sync with TRDM
• Permanently scale up RDS (My preferred as it supports the application's growth and prevents unpredictable budget changes)

We might be able to get a temp outage for the sync - if the other 2 options don't pan out- but would need some planning
If you havnet already- might be a good idea to put the COAs in the issue so folks know the options