Member since
09-18-2015
3274
Posts
1159
Kudos Received
426
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2208 | 11-01-2016 05:43 PM | |
6882 | 11-01-2016 05:36 PM | |
4308 | 07-01-2016 03:20 PM | |
7338 | 05-25-2016 11:36 AM | |
3570 | 05-24-2016 05:27 PM |
10-23-2015
02:55 PM
@Ronald McCollam Jira on the same
... View more
10-23-2015
02:42 PM
@bsaini@hortonworks.com Continue to the above explanation of Container expiring Very good explanation in this blog "With YARN and MapReduce 2, there are no longer pre-configured static slots for Map and Reduce tasks. The entire cluster is available for dynamic resource allocation of Maps and Reduces as needed by the job" With YARN and MapReduce 2, there are no longer pre-configured static slots for Map and Reduce tasks. The entire cluster is available for dynamic resource allocation of Maps and Reduces as needed by the job. In our example cluster, with the above configurations, YARN will be able to allocate on each node up to 10 mappers (40/4) or 5 reducers (40/8) or a permutation within that.
... View more
10-23-2015
09:24 AM
3 Kudos
@dbaev@hortonworks.com Tivoli Access Manager has been renamed to ISAM This blog talks about TAM integration with Knox. Based on this , the answer is Yes Blog With Knox, we support SSO, so for all the REST APIs that you expose to your Hadoop end users, you can support the SSO through Knox. For example, when you deploy Knox, it supports CA SiteMinder, Oracle Access Management Suite or Tivoli Access Manager. You can deploy Knox with an Apache HTTP Server and leverage its integration, or you can directly integrate with Knox. IBM Tivoli Access Manager (TAM) is an authentication and authorization solution for corporate web services, operating systems, and existing applications.[1] Tivoli Access Manager runs on various operating system platforms such as Unix (AIX, Solaris, HP-UX), Linux, and Microsoft Windows. It has been renamed as IBM Security Access Manager (ISAM), in line with the renaming of other Tivoli products, such as TIM turned ISIM.
... View more
10-23-2015
08:11 AM
@Cassandra Slider and HBase requires special attention. Slider can be installed in any of the master but when you configure HBase to run on slider then you have to pay attention to memory and other parameters. Link
... View more
10-23-2015
02:42 AM
Thanks @vperiasamy@hortonworks.com
... View more
10-22-2015
08:40 PM
4 Kudos
Thanks for posting the solution. Only 1 entry needs to be updated. Don't change the following entry
... View more
10-22-2015
07:45 PM
@bsaini@hortonworks.com This may help..link
ContainerAllocationExpirer: This component is in charge of ensuring that all allocated containers are used by AMs and subsequently launched on the correspond NMs. AMs run as untrusted user code and can potentially hold on to allocations without using them, and as such can cause cluster under-utilization. To address this, ContainerAllocationExpirer maintains the list of allocated containers that are still not used on the corresponding NMs. For any container, if the corresponding NM doesn’t report to the RM that the container has started running within a configured interval of time, by default 10 minutes, the container is deemed as dead and is expired by the RM.
... View more
10-22-2015
10:40 AM
@hosako@hortonworks.com Do you have Capacity scheduler configured? I high recommend to deploy Capacity Scheduler view and configure queues and allocate resources appropriately Link
... View more
10-22-2015
12:00 AM
@amcbarnett@hortonworks.com Yes Voltage Safenet-inc
... View more