@Sunile Manjee I doubt it, by design you need to specify namespace:table ... View more

I set it up using squirrel before, using this guide https://phoenix.apache.org/installation.html ... View more

@Sunile Manjee here you go https://phoenix.apache.org/installation.html ... View more

@Rosaura Maria Fran Mongardini sure thing, it could only become a problem if you install too many services on the same node as ambari server, at some point you want to spread the load across multiple ambari servers for user Ambari views but in general having agent and server on the same nodes is okay given the machine resources. ... View more

@Rosaura Maria Fran Mongardini not to worry, if the errors prevent you from running your services successfully, paste the logs here and we can address them. Thanks! ... View more

Azure cloud service: 1 Cloud Service means single IP Address interface for the entire cluster.Potential issue if you need to use the same port number for different services than you need to create multiple cloud services (e.g. Need to have Ambari and HUE both on port 8080 for the external IP) Mount points: All the mount point that has been added to master and compute nodes should not have “noexec" and the flags should be set to default. This is because if we set the mount point to “noexec” then YARN won’t be able to execute on those disks. Storage Accounts: Use one storage account for every nodes in the cluster in order to bypass IOPS limits for multiple VMs on the same Storage Account. ... View more

@Smart Solutions even more considerations Use premium storage if possible: Azure premium storage are in essence SSD and provide great performance. Premium storage gives 5,000 IOPS per disk rather than the regular storage that gives just 500 IOPS per disk. VPN Tunnel: VPN tunneling allows dedicated network connection between on premise network to azure cloud network. This allows for integration with on-prem LDAP/AD. Need to ensure IP Addresses from Azure cluster doesn’t overlap with on-prem IPs Static IPs: When rebooting the servers need to sure that Azure VMs are pinned to the same IP Address again (and nor randomly reassigned). Make sure all the instances are in the same Azure Virtual Network. By default, VMs connected to the same VNET have full connectivity between them ... View more

here are some more considerations @Smart Solutions all Vms in one Availability Set are in the same fault domain. That is, power disruptions and other things will affect all of them at once. For HDP, it means that every VM running the Master services must be place in its own Availability Set. If you have 5 Master nodes, put each of them in their own AS. Zookeeper is a master service, it should be spread across the 5 masters for quorum, and because they are in different AS, they will be guarded from abrupt shutdown disrupting the whole cluster. ... View more