[GitHub] [druid] dgregoire commented on issue #7522: Peon cannot write segments to GCS but can write index logs

[GitBox <gi...@apache.org>]

dgregoire commented on issue #7522: Peon cannot write segments to GCS but can write index logs
URL: https://github.com/apache/druid/issues/7522#issuecomment-599512943
 
 
   > hello. I have same case. What you solved problem?
   
   Using the version of the gcs hdfs connector that was recommended at that time (almost a year ago) did not work and I had switched to using the latest.
   
   There's been developments more recently and there is a GCS extension now, perhaps things have changed?
   
   I'm not working on this project anymore, but I have theses excerpts to share.
   
   I was using this from a `dockerfile` to add the gcs connector.
   
   ```dockerfile
   # GCS connector
   ADD https://storage.googleapis.com/hadoop-lib/gcs/gcs-connector-hadoop2-latest.jar /opt/druid/extensions/druid-hdfs-storage
   ```
   
   `core-site.xml` placed in `_common`, I had a startup script replacing the KV of the keys `GCS_PROJECT_ID`  and `GCS_KEY_FILE`.
   
   ```xml
   <configuration>  
     <property>
       <name>fs.gs.impl</name>
       <value>com.google.cloud.hadoop.fs.gcs.GoogleHadoopFileSystem</value>
       <description>The FileSystem for gs: (GCS) uris.</description>
     </property>
     <property>
       <name>fs.AbstractFileSystem.gs.impl</name>
       <value>com.google.cloud.hadoop.fs.gcs.GoogleHadoopFS</value>
       <description>
         The AbstractFileSystem for gs: (GCS) uris. Only necessary for use with Hadoop 2.
       </description>
     </property>
     <property>
       <name>fs.gs.project.id</name>
       <value>GCS_PROJECT_ID</value>
       <description>
         Required. Google Cloud Project ID with access to configured GCS buckets.
       </description>
     </property>
     <property>
       <name>google.cloud.auth.service.account.enable</name>
       <value>true</value>
       <description>
         Whether to use a service account for GCS authorizaiton. If an email and
         keyfile are provided (see google.cloud.auth.service.account.email and
         google.cloud.auth.service.account.keyfile), then that service account
         willl be used. Otherwise the connector will look to see if it running on
         a GCE VM with some level of GCS access in it's service account scope, and
         use that service account.
       </description>
     </property>
     <property>
       <name>google.cloud.auth.service.account.json.keyfile</name>
       <value>GCS_KEY_FILE</value>
       <description>
         The JSON key file of the service account used for GCS
         access when google.cloud.auth.service.account.enable is true.
       </description>
     </property>
     <property>
       <name>hadoop.tmp.dir</name>
       <value>/var/druid</value>
     </property>
   </configuration>
   ```
   
   and `common.runtime.properties` including the hdfs storage extension.
   
   ```properties
   # This is not the full list of Druid extensions, but common ones that people often use. You may need to change this list
   # based on your particular setup.
   druid.extensions.directory=/opt/druid/extensions
   druid.extensions.loadList=["druid-histogram", "druid-datasketches", "mysql-metadata-storage", "druid-hdfs-storage", "druid-kafka-indexing-service", "druid-protobuf-extensions"]
   ```
   
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org