Timeout configurations
About
This wiki documents all the timeout configurations and the relationships between each other.
Timeouts and Relationships
| Timeout Name | Description | Default Value As per 4.3.1 | Related Timeouts | Recommendation |
|---|---|---|---|---|
| http.client.connection.timeout.ms | Timeout set by all HTTP Clients used by CDAP for establishing a HTTP connection. If the server doesn't respond within the specified connection timeout then the http request will fail. | 60000 | ||
| http.client.read.timeout.ms | Timeout on waiting to read the data from a server. If the server doesn't not send a byte of data within the read timeout configure a read timeout error will be raised which will interrupt the http connection. | 60000 | hbase.rpc.timeout | This should be greater than hbase.rpc.timeout |
| master.startup.checks.yarn.connect.timeout.seconds | Connection timeout to connect to yarn resource maanger for performing master startup checks | 60 | hbase.rpc.timeout | |
| master.startup.service.timeout.seconds | Timeout in seconds for master services to wait for their dependent services to be available. | 600 | ||
| zookeeper.session.timeout.millis | ZooKeeper session timeout in milliseconds | 40000 | ||
| zookeeper.client.startup.timeout.millis | Duration in milliseconds to wait for a successful connection to a server in the ZooKeeper quorum | 60000 | ||
| router.connection.idle.timeout.secs | Time in seconds after an HTTP request completes that idle router connections are closed | 15 | ||
| monitor.handler.service.discovery.timeout.seconds | Timeout in seconds for service discovery used in monitor handler service status check | 1 | ||
| explore.active.operation.timeout.secs | Timeout value in seconds for an SQL operation whose result was not fetched completely | 82800 | ||
| explore.inactive.operation.timeout.secs | Timeout value in seconds for an SQL operation which does not have any more results to be fetched | 3600 | ||
| explore.http.timeout | The timeout in seconds for HTTP requests to the CDAP Explore service. | 20 | data.tx.timeout | This should be less than data.tx.timeout |
| twill.no.container.timeout | Duration in milliseconds to wait for at least one container for Apache Twill runnable | 120000 | ||
| app.meta.upgrade.timeout.secs | Timeout value in seconds while upgrading application versions | 60 | data.tx.timeout | Should be greater than data.tx.timeout |
| audit.publish.timeout.ms | Timeout to publish audit logs to Transactional messaging system. The TMS implementation is based on Hbase | 2000 | data.tx.timeout, hbase.rpc.timeout | This should be greater than hbase.rpc.timeout |
| data.tx.timeout | Timeout value in seconds for a transaction; if the transaction is not finished in that time, it is marked invalid | 30 | ||
| dashboard.router.check.timeout.secs | Interval in seconds that the CDAP UI waits before exiting when unable to connect to the CDAP Router service on startup; use a timeout of 0 to wait indefinitely | 0 | ||
| kafka.server.zookeeper.connection.timeout.ms | Maximum time in milliseconds that the CDAP Kafka service will wait to establish a connection to ZooKeeper | 1000000 | ||
| log.pipeline.cdap.file.cleanup.transaction.timeout | Transaction timeout in seconds used by the log cleanup thread. | 60 | data.tx.timeout | Should be greater than data.tx.timeout |
| hbase.rpc.timeout | Set in Hbase-(default/)site.xml the value indicates the timeout for HBase RPC operations. | 60000 |
Created in 2020 by Google Inc.