arvindshmicrosoft commented on issue #1850: URL: https://github.com/apache/accumulo/issues/1850#issuecomment-752200173
@Viv1986 I think Karthick's suggestion to leverage Hadoop 3.2.x is a good one, given almost all of our testing with this configuration was done with Hadoop 3.2.1+ That said, given you seem to be able to access the ADLS Gen2 account through Hadoop commands, but Accumulo cannot see it, in my experience this is an indication of something missing in the classpath specified for Accumulo. Hadoop looks for the hdfs-site.xml and core-site.xml files (which is where the necessary security key information for accessing ADLS Gen 2 is located), within the classpath specified for the current binary. As another option, if this is a dev/test cluster, it may be easier if you use the [Muchos](https://github.com/apache/fluo-muchos) project to set up the cluster on Azure. There is out-of-the-box support in Muchos, for using ADLS Gen 2 with Accumulo. Muchos also [correctly populates](https://github.com/apache/fluo-muchos/blob/b21c3da46b99c7ed8d28fc24b232f7908a264eb5/ansible/roles/accumulo/templates/accumulo-env.sh#L51-L62) the Accumulo classpath with the required paths. Further, when using Muchos, the ADLS Gen 2 account is accessed using Azure Managed Identities, which leverage OAuth, and avoid hard-coded storage account key based access. You may also use a cluster setup using Muchos to compare and check for differences in classpaths between your custom setup above and the "reference" setup done through Muchos. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
