flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From subhankarb <...@git.apache.org>
Subject [GitHub] flink issue #1813: [FLINK-3034] Redis Sink Connector
Date Thu, 14 Jul 2016 05:05:45 GMT
Github user subhankarb commented on the issue:

    https://github.com/apache/flink/pull/1813
  
    Hi @kl0u, IMO that is the expected behavior. The sink would not know that if the Redis
is down or not unless it tries to send the next data to the Redis. When ever a new message
reaches the sink it tries to use the connection pool, then an then only it can throw exception
that it can not send the data to Redis.
    You can build a heartbeat mechanism to check periodically that Redis serve is up or down,
and can cancel the job if Redis is down. 
    @mjsax please correct me if my understanding is wrong.  


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message