FAQ About STEPS FAQ TOOL
The challenge of device overload persists due to the high volume of data being written to the Aerospike server, causing the SSD to fall behind. While there is a solution for the Aerospike connector, it hasn’t been highlighted by Sir John in any official communication.
Currently, submit a ticket to the operations team to initiate the rebalancing of the Aerospike server.
As previously discussed with Solution Designer Eli, utilizing a counter in the aggregation component is not feasible.
XS - 2 days development : 1 day QA
S - 3 days development : 2 days QA
M - 6 days development : 4 days QA
L - 9 days development : 6 days QA
Performance testing is necessary only for high transactions per second (TPS) and new data sources
Can we verify whether a particular subscriber is listed in the whitelist or recurrence table in yhe production environment?
Only the Operations team has the authority to perform aerospike queries in the production environment; please submit a ticket to request their assistance
The duplication of the application/bootstrap is restricted to the operations team only
What should be done if the Jarvis campaign undergoes iterations with different logic in the technical flow that is not aligned with the Jarvis process?
Start with the creation of the legacy campaign, or if feasible and within the timeline, consider incorporating the feature into Jarvis
Navigate to the current branch you intend to delete, and execute "git push origin --delete <branch name>
Consider consulting the Solutions Designer to determine if it is acceptable to permanently store the subscriber in the whitelist table. Propose implementing a design that removes the data after the transaction is completed
To determine if Jarvis can handle the campaign logic, please refer to the documentation available at: https://gogs-cicd.steps-dev-apps.edo.globe.com.ph/arrow-arch/project-jarvis/src/develop/README.md
Why are campaign pods unable to scale up in OKD Staging, and what does the event log message "pod didn't trigger scale-up (it wouldn't fit if a new node is added)" mean?
This message suggests that the pod cannot scale up because it would not fit even if a new node is added. To address this issue, file Service Request with details:
Service Category: ARROW Platform Requests
Service Request Title: Failed scaling up of pods in OKD STG
Describe your request and provide justification : Campaign pods are unable to scale up in OKD Stg with event log "pod didn't trigger scale-up (it wouldn't fit if a new node is added)".
Campaign affected are the ff: <insert campaign affected>