Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Enabler:Cygnus
Description
Created question in FIWARE Q/A platform on 07-03-2019 at 09:03
Please, ANSWER this question AT https://stackoverflow.com/questions/55039350/fiware-cygnus-file-exists-in-hdfs-but-could-not-write-the-data
Question:
FIWARE Cygnus: File exists in HDFS, but could not write the data
Description:
I am using NGSIHDFSSink to persist on an HDFS through Cygnus. When the first notification from Orion is received, it creates the directory and the correct file with the data:
/user/hdfs/openiot/Lamp_001_Lamp/Lamp_001_Lamp.txt
However, for the next notifications received it shows the following error:
There was some problem with the current endpoint, trying other one.
Details: CygnusPersistenceError.
/user/hdfs/openioLamp/Lamp_001_Lamp.txt file exists in HDFS, but could
not write the data. Server response: 403 Forbidden.
This is my Sink configuration:
cygnus-ngsi.sinks.hdfs-sink.type = com.telefonica.iot.cygnus.sinks.NGSIHDFSSink
cygnus-ngsi.sinks.hdfs-sink.channel = hdfs-channel
cygnus-ngsi.sinks.hdfs-sink.enable_encoding = false
cygnus-ngsi.sinks.hdfs-sink.enable_grouping = false
cygnus-ngsi.sinks.hdfs-sink.enable_lowercase = false
cygnus-ngsi.sinks.hdfs-sink.enable_name_mappings = false
cygnus-ngsi.sinks.hdfs-sink.data_model = dm-by-entity
cygnus-ngsi.sinks.hdfs-sink.file_format = json-column
cygnus-ngsi.sinks.hdfs-sink.backend.impl = rest
cygnus-ngsi.sinks.hdfs-sink.backend.max_conns = 500
cygnus-ngsi.sinks.hdfs-sink.backend.max_conns_per_route = 100
cygnus-ngsi.sinks.hdfs-sink.hdfs_host = my_hdfs_ip
cygnus-ngsi.sinks.hdfs-sink.hdfs_port = 50070
cygnus-ngsi.sinks.hdfs-sink.hdfs_username = hdfs
cygnus-ngsi.sinks.hdfs-sink.hdfs_password =
cygnus-ngsi.sinks.hdfs-sink.oauth2_token =
cygnus-ngsi.sinks.hdfs-sink.service_as_namespace = false
cygnus-ngsi.sinks.hdfs-sink.batch_size = 100
cygnus-ngsi.sinks.hdfs-sink.batch_timeout = 30
cygnus-ngsi.sinks.hdfs-sink.batch_ttl = 10
cygnus-ngsi.sinks.hdfs-sink.batch_retry_intervals = 5000
cygnus-ngsi.sinks.hdfs-sink.hive = false
cygnus-ngsi.sinks.hdfs-sink.krb5_auth = false
Any ideas?
Thank you so much
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
HD-Enabler | Cygnus [ 11304 ] | |
Description |
Created question in FIWARE Q/A platform on 07-03-2019 at 09:03 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/55039350/fiware-cygnus-file-exists-in-hdfs-but-could-not-write-the-data +Question:+ FIWARE Cygnus: File exists in HDFS, but could not write the data +Description:+ I am using NGSIHDFSSink to persist on an HDFS through Cygnus. When the first notification from Orion is received, it creates the directory and the correct file with the data: /user/hdfs/openiot/Lamp_001_Lamp/Lamp_001_Lamp.txt However, for the next notifications received it shows the following error: There was some problem with the current endpoint, trying other one. Details: CygnusPersistenceError. /user/hdfs/openioLamp/Lamp_001_Lamp.txt file exists in HDFS, but could not write the data. Server response: 403 Forbidden. This is my Sink configuration: cygnus-ngsi.sinks.hdfs-sink.type = com.telefonica.iot.cygnus.sinks.NGSIHDFSSink cygnus-ngsi.sinks.hdfs-sink.channel = hdfs-channel cygnus-ngsi.sinks.hdfs-sink.enable_encoding = false cygnus-ngsi.sinks.hdfs-sink.enable_grouping = false cygnus-ngsi.sinks.hdfs-sink.enable_lowercase = false cygnus-ngsi.sinks.hdfs-sink.enable_name_mappings = false cygnus-ngsi.sinks.hdfs-sink.data_model = dm-by-entity cygnus-ngsi.sinks.hdfs-sink.file_format = json-column cygnus-ngsi.sinks.hdfs-sink.backend.impl = rest cygnus-ngsi.sinks.hdfs-sink.backend.max_conns = 500 cygnus-ngsi.sinks.hdfs-sink.backend.max_conns_per_route = 100 cygnus-ngsi.sinks.hdfs-sink.hdfs_host = my_hdfs_ip cygnus-ngsi.sinks.hdfs-sink.hdfs_port = 50070 cygnus-ngsi.sinks.hdfs-sink.hdfs_username = hdfs cygnus-ngsi.sinks.hdfs-sink.hdfs_password = cygnus-ngsi.sinks.hdfs-sink.oauth2_token = cygnus-ngsi.sinks.hdfs-sink.service_as_namespace = false cygnus-ngsi.sinks.hdfs-sink.batch_size = 100 cygnus-ngsi.sinks.hdfs-sink.batch_timeout = 30 cygnus-ngsi.sinks.hdfs-sink.batch_ttl = 10 cygnus-ngsi.sinks.hdfs-sink.batch_retry_intervals = 5000 cygnus-ngsi.sinks.hdfs-sink.hive = false cygnus-ngsi.sinks.hdfs-sink.krb5_auth = false Any ideas? Thank you so much |
Created question in FIWARE Q/A platform on 07-03-2019 at 09:03
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/55039350/fiware-cygnus-file-exists-in-hdfs-but-could-not-write-the-data +Question:+ FIWARE Cygnus: File exists in HDFS, but could not write the data +Description:+ I am using NGSIHDFSSink to persist on an HDFS through Cygnus. When the first notification from Orion is received, it creates the directory and the correct file with the data: /user/hdfs/openiot/Lamp_001_Lamp/Lamp_001_Lamp.txt However, for the next notifications received it shows the following error: There was some problem with the current endpoint, trying other one. Details: CygnusPersistenceError. /user/hdfs/openioLamp/Lamp_001_Lamp.txt file exists in HDFS, but could not write the data. Server response: 403 Forbidden. This is my Sink configuration: cygnus-ngsi.sinks.hdfs-sink.type = com.telefonica.iot.cygnus.sinks.NGSIHDFSSink cygnus-ngsi.sinks.hdfs-sink.channel = hdfs-channel cygnus-ngsi.sinks.hdfs-sink.enable_encoding = false cygnus-ngsi.sinks.hdfs-sink.enable_grouping = false cygnus-ngsi.sinks.hdfs-sink.enable_lowercase = false cygnus-ngsi.sinks.hdfs-sink.enable_name_mappings = false cygnus-ngsi.sinks.hdfs-sink.data_model = dm-by-entity cygnus-ngsi.sinks.hdfs-sink.file_format = json-column cygnus-ngsi.sinks.hdfs-sink.backend.impl = rest cygnus-ngsi.sinks.hdfs-sink.backend.max_conns = 500 cygnus-ngsi.sinks.hdfs-sink.backend.max_conns_per_route = 100 cygnus-ngsi.sinks.hdfs-sink.hdfs_host = my_hdfs_ip cygnus-ngsi.sinks.hdfs-sink.hdfs_port = 50070 cygnus-ngsi.sinks.hdfs-sink.hdfs_username = hdfs cygnus-ngsi.sinks.hdfs-sink.hdfs_password = cygnus-ngsi.sinks.hdfs-sink.oauth2_token = cygnus-ngsi.sinks.hdfs-sink.service_as_namespace = false cygnus-ngsi.sinks.hdfs-sink.batch_size = 100 cygnus-ngsi.sinks.hdfs-sink.batch_timeout = 30 cygnus-ngsi.sinks.hdfs-sink.batch_ttl = 10 cygnus-ngsi.sinks.hdfs-sink.batch_retry_intervals = 5000 cygnus-ngsi.sinks.hdfs-sink.hive = false cygnus-ngsi.sinks.hdfs-sink.krb5_auth = false Any ideas? Thank you so much |
Assignee | Backlog Manager [ backlogmanager ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Fix Version/s | 2021 [ 12600 ] |