You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/11/11 18:34:45 UTC

[GitHub] [openwhisk-package-kafka] dubee commented on issue #356: Do not update last canary everytime a database connection attempt occurs

dubee commented on issue #356: Do not update last canary everytime a database connection attempt occurs
URL: https://github.com/apache/openwhisk-package-kafka/pull/356#issuecomment-552560832
 
 
   To further clarify, the logs show the sequence below repeatedly. While the changes feed appeared to re-establish its connection, read timeouts occur when trying to read from the changes feed. This explains why an exception was not thrown before `self.lastCanaryTime = datetime.now()` was executed.
   ```
   [kafkatriggers] [canary] Exception caught from changes feed. Restarting changes feed... 
   [kafkatriggers] HTTPSConnectionPool(host='OMITTED', port=443): Read timed out. (read timeout=30) 
   [kafkatriggers] Shutting down existing DB client 
   [kafkatriggers] Starting new HTTPS connection (2): OMITTED
   [kafkatriggers] Starting changes feed 
   [kafkatriggers] Starting new HTTPS connection (1): OMITTED
   [kafkatriggers] Database exists - connecting to it. 
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services