Skip to content

Commit

Permalink
Loading
Loading status checks…
update requirements
Browse files Browse the repository at this point in the history
Selfeer committed Mar 11, 2024
1 parent 52ab140 commit 70232be
Showing 2 changed files with 63 additions and 39 deletions.
34 changes: 21 additions & 13 deletions sink-connector-lightweight/tests/integration/requirements/requirements.md
View file
Original file line number Diff line number Diff line change
@@ -1342,12 +1342,14 @@ version: 1.0

[Altinity Sink Connector] SHALL be able to recover replication after network related interruptions happen, so that the data on the destination table is not lost.

List of possible network related interruptions:

- Internal network interruptions in source database cluster
- Network interruptions from source database to sink connector
- Network interruptions from sink connector to clickhouse
- Internal network interruptions in clickhouse database cluster
| List of possible network related interruptions |
|---------------------------------------------------------------|
| Internal network interruptions in source database cluster |
| Network interruptions from source database to sink connector |
| Network interruptions from sink connector to clickhouse |
| Internal network interruptions in clickhouse database cluster |


### Handling Process Interruptions

@@ -1356,22 +1358,28 @@ List of possible network related interruptions:
##### RQ.SRS-030.ClickHouse.MySQLToClickHouseReplication.SystemActions.Process.Die
version: 1.0

[Altinity Sink Connector] SHALL output an error and keep the existing data when one of the following or all of the scenarios related to processes being killed happen:
[Altinity Sink Connector] SHALL output an error and keep the existing data when one of the following or all of the
scenarios related to processes being killed happen:

- Internal processes die in source database cluster
- Sink connector dies
- Internal processes die in clickhouse database cluster
| Scenarios Related to Processes Being Killed |
|-------------------------------------------------------|
| Internal processes die in source database cluster |
| Sink connector dies |
| Internal processes die in clickhouse database cluster |

#### Behaviour When Different Processes Were Restarted

##### RQ.SRS-030.ClickHouse.MySQLToClickHouseReplication.SystemActions.Process.Restarted
version: 1.0

[Altinity Sink Connector] SHALL continue replication without losing any data after one of the following or all of the scenarios related to processes being restarted happen:
[Altinity Sink Connector] SHALL continue replication without losing any data after one of the following or
all of the scenarios related to processes being restarted happen:

- Restart of some or all nodes in source database cluster
- Restart of sink connector
- Restart of some or all nodes in clickhouse database cluster
| Scenarios Related to Processes Being Restarted |
|-------------------------------------------------------------|
| Restart of some or all nodes in source database cluster |
| Restart of sink connector |
| Restart of some or all nodes in clickhouse database cluster |

### Behaviour When There Are Issues With Disk

68 changes: 42 additions & 26 deletions sink-connector-lightweight/tests/integration/requirements/requirements.py
View file
Original file line number Diff line number Diff line change
@@ -1665,12 +1665,14 @@
description=(
"[Altinity Sink Connector] SHALL be able to recover replication after network related interruptions happen, so that the data on the destination table is not lost.\n"
"\n"
"List of possible network related interruptions:\n"
"\n"
"- Internal network interruptions in source database cluster\n"
"- Network interruptions from source database to sink connector\n"
"- Network interruptions from sink connector to clickhouse\n"
"- Internal network interruptions in clickhouse database cluster\n"
"| List of possible network related interruptions |\n"
"|---------------------------------------------------------------|\n"
"| Internal network interruptions in source database cluster |\n"
"| Network interruptions from source database to sink connector |\n"
"| Network interruptions from sink connector to clickhouse |\n"
"| Internal network interruptions in clickhouse database cluster |\n"
"\n"
"\n"
),
link=None,
@@ -1686,11 +1688,14 @@
type=None,
uid=None,
description=(
"[Altinity Sink Connector] SHALL output an error and keep the existing data when one of the following or all of the scenarios related to processes being killed happen:\n"
"[Altinity Sink Connector] SHALL output an error and keep the existing data when one of the following or all of the \n"
"scenarios related to processes being killed happen:\n"
"\n"
"- Internal processes die in source database cluster\n"
"- Sink connector dies\n"
"- Internal processes die in clickhouse database cluster\n"
"| Scenarios Related to Processes Being Killed |\n"
"|-------------------------------------------------------|\n"
"| Internal processes die in source database cluster |\n"
"| Sink connector dies |\n"
"| Internal processes die in clickhouse database cluster |\n"
"\n"
),
link=None,
@@ -1706,11 +1711,14 @@
type=None,
uid=None,
description=(
"[Altinity Sink Connector] SHALL continue replication without losing any data after one of the following or all of the scenarios related to processes being restarted happen:\n"
"[Altinity Sink Connector] SHALL continue replication without losing any data after one of the following or \n"
"all of the scenarios related to processes being restarted happen:\n"
"\n"
"- Restart of some or all nodes in source database cluster\n"
"- Restart of sink connector\n"
"- Restart of some or all nodes in clickhouse database cluster\n"
"| Scenarios Related to Processes Being Restarted |\n"
"|-------------------------------------------------------------|\n"
"| Restart of some or all nodes in source database cluster |\n"
"| Restart of sink connector |\n"
"| Restart of some or all nodes in clickhouse database cluster |\n"
"\n"
),
link=None,
@@ -3827,12 +3835,14 @@
[Altinity Sink Connector] SHALL be able to recover replication after network related interruptions happen, so that the data on the destination table is not lost.
List of possible network related interruptions:
- Internal network interruptions in source database cluster
- Network interruptions from source database to sink connector
- Network interruptions from sink connector to clickhouse
- Internal network interruptions in clickhouse database cluster
| List of possible network related interruptions |
|---------------------------------------------------------------|
| Internal network interruptions in source database cluster |
| Network interruptions from source database to sink connector |
| Network interruptions from sink connector to clickhouse |
| Internal network interruptions in clickhouse database cluster |
### Handling Process Interruptions
@@ -3841,22 +3851,28 @@
##### RQ.SRS-030.ClickHouse.MySQLToClickHouseReplication.SystemActions.Process.Die
version: 1.0
[Altinity Sink Connector] SHALL output an error and keep the existing data when one of the following or all of the scenarios related to processes being killed happen:
[Altinity Sink Connector] SHALL output an error and keep the existing data when one of the following or all of the
scenarios related to processes being killed happen:
- Internal processes die in source database cluster
- Sink connector dies
- Internal processes die in clickhouse database cluster
| Scenarios Related to Processes Being Killed |
|-------------------------------------------------------|
| Internal processes die in source database cluster |
| Sink connector dies |
| Internal processes die in clickhouse database cluster |
#### Behaviour When Different Processes Were Restarted
##### RQ.SRS-030.ClickHouse.MySQLToClickHouseReplication.SystemActions.Process.Restarted
version: 1.0
[Altinity Sink Connector] SHALL continue replication without losing any data after one of the following or all of the scenarios related to processes being restarted happen:
[Altinity Sink Connector] SHALL continue replication without losing any data after one of the following or
all of the scenarios related to processes being restarted happen:
- Restart of some or all nodes in source database cluster
- Restart of sink connector
- Restart of some or all nodes in clickhouse database cluster
| Scenarios Related to Processes Being Restarted |
|-------------------------------------------------------------|
| Restart of some or all nodes in source database cluster |
| Restart of sink connector |
| Restart of some or all nodes in clickhouse database cluster |
### Behaviour When There Are Issues With Disk

0 comments on commit 70232be

Please sign in to comment.