You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-2Lines changed: 25 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,9 @@ are additional methods used by the token connector to guess at the contract ABI
29
29
but is the preferred method for most use cases.
30
30
31
31
To leverage this capability in a running FireFly environment, you must:
32
+
32
33
1.[Upload the token contract ABI to FireFly](https://hyperledger.github.io/firefly/tutorials/custom_contracts/ethereum.html)
33
-
as a contract interface.
34
+
as a contract interface.
34
35
2. Include the `interface` parameter when [creating the pool on FireFly](https://hyperledger.github.io/firefly/tutorials/tokens).
35
36
36
37
This will cause FireFly to parse the interface and provide ABI details
@@ -119,7 +120,29 @@ that specific token. If omitted, the approval covers all tokens.
119
120
120
121
The following APIs are not part of the fftokens standard, but are exposed under `/api/v1`:
121
122
122
-
*`GET /receipt/:id` - Get receipt for a previous request
123
+
-`GET /receipt/:id` - Get receipt for a previous request
124
+
125
+
## Retry behaviour
126
+
127
+
Most short-term outages should be handled by the blockchain connector. For example if the blockchain node returns `HTTP 429` due to rate limiting
128
+
it is the blockchain connector's responsibility to use appropriate back-off retries to attempt to make the required blockchain call successfully.
129
+
130
+
There are cases where the token connector may need to perform it's own back-off retry for a blockchain action. For example if the blockchain connector
131
+
microservice has crashed and is in the process of restarting just as the token connector is trying to query an NFT token URI to enrich a token event, if
132
+
the token connector doesn't perform a retry then the event will be returned without the token URI populated.
133
+
134
+
The token connector has configurable retry behaviour for all blockchain related calls. By default the connector will perform up to 15 retries with a back-off
135
+
interval between each one. The default first retry interval is 100ms and doubles up to a maximum of 10s per retry interval. Retries are only performed where
136
+
the error returned from the REST call matches a configurable regular expression retry condition. The default retry condition is `._ECONN._` which ensures
137
+
retries take place for common TCP errors such as `ECONNRESET` and `ECONNREFUSED`.
138
+
139
+
Setting the retry condition to "" disables retries. The configurable retry settings are:
0 commit comments