Member since
09-24-2015
4
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1470 | 09-24-2015 08:53 AM |
08-12-2021
11:10 AM
1 Kudo
The Impala Virtual Warehouses within Cloudera Data Warehouse (CDW) give users an intelligent way to run fast BI queries. Coordinators are the ones that BI tools, such as HUE or Tableau, connect to. There is either one of these running, or two of them if you choose HA mode. Previously, these nodes were always running so that the BI tool connections would not break, and new queries could always be accepted. Now, CDW is able to terminate Coordinators automatically when all queries stop, and restart them once new queries arrive - all without interfering with BI tool connections. Since Impala Executor nodes already had the ability to auto-suspend, this means that all of the largest (i.e. most expensive) nodes used by the Impala Virtual Warehouse now support auto-suspend, dramatically reducing your CDW cost. This capability is currently released as a Tech Preview feature, so please request the Impala Coordinator Auto-Suspend entitlement from your Cloudera account team if you want to try it out. Once this is granted you will have an option to select Allow Shutdown Of Coordinator when creating your Impala Virtual Warehouse. You will then be able to select the Trigger Shutdown Delay, which is how long to keep the Coordinator(s) running after queries have stopped arriving. During runtime, once this idle time has passed, CDW will automatically stop the Coordinator(s). However, there is is still a very lightweight proxy service which is running on another existing housekeeping node. This is what now listens for incoming query requests. When this proxy receives a query it automatically starts up the Coordinator(s) again so they can do their job of query planning, cost based optimization, and orchestrating execution by the executor nodes. CDW is capable of serving 1,000s of BI users within an organization, letting them run their queries at the speed of thought. End users expect the capacity to always be available, but admins only want to pay for capacity when it is actually needed. With this new level of intelligence, CDW is better able to satisfy both groups. Now that is modern data warehousing at its best.
... View more
Labels:
04-30-2021
05:22 PM
The Cloudera Data Warehouse service (CDW) now allows you to use an AKS internal load balancer to prevent the pods in your cluster from having public endpoints. This ensures that no clients are able to access your services via the public Internet. To use this feature, you simply select the Enable AKS Internal Load Balancer field in the popup that you use to initially activate the CDW environment. CDW will then take care of the required network configuration behind the scenes. This makes your Kubernetes services accessible only to applications running in the same Azure VNET as the Kubernetes cluster, or to a peered VNET. Applications running in on-premises networks that are connected using Azure ExpressRoute circuits can also access your services. CDW lets you run a more cost effective data warehouse platform, where SLAs are easier to meet. CDW also helps you increase your agility and self-service capabilities so that you can more quickly respond to the needs of the business. But network security is critical. With this new feature users can more confidently deploy sensitive workloads to CDW without worrying about exposures via public endpoints. To learn more, check out the documentation for this feature.
... View more
Labels:
09-24-2015
08:53 AM
Hi Bagal, In the URL, I think you are missing a "i" in roleConfigGroups. You have http://localhost:7180/api/v10/clusters/TestCluster/services/hdfs/roleConfgGroups/hdfs-DATANODE-BASE/config. Give it a shot with the "i" in there and let me know if it works. Regards, Justin
... View more