Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Runtime Analytics Basics

...

CPU capacity has the highest probability of being the limiting factor. When optimizing for the best performance for largest datasets, you are diminishing the chances RTA calculates multiple requests at the same time. RTA can process concurrent requests and the impact on response times vary depending on deployment configuration. When deployment is optimized for the best performance for largest datasets, RTA should be able to handle 10 concurrent queries comfortably. It is important to understand though that concurrency is a function of the amount of resources allocated for RTA in the cluster.

Runtime Analytics REST API

The Runtime Analytics process can be started, stopped, and have the status checked though Datameer's REST API. 

Security

  • RTA deploys and it's compatible in Secured Hadoop clusters with Kerberos and Impersonation enabled.
  • In Secured Hadoop clusters, the RTA Yarn application is launched as the Datameer service user.
    • It is important to understand that the service user that launches the RTA Yarn application doesn't attempt to access data.
    • Every query that comes from Visual Explorer is answered using the user in context through the authentication and Kerberos ticket information in RTA.
  • In Secured MapR clusters, the maximum uptime of RTA is limited to the configured yarn.mapr.ticket.expiration property in yarn-site.xml (default observed to be 7 days).

...