Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-15545

[fiware-stackoverflow] FIWARE Cygnus: File exists in HDFS, but could not write the data

    Details

      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

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        3h 1 Backlog Manager 07/Mar/19 3:06 PM
        In Progress In Progress Answered Answered
        3h 1 Backlog Manager 07/Mar/19 6:06 PM
        Answered Answered Closed Closed
        27d 15h 56m 1 José Ignacio Carretero Guarde 04/Apr/19 11:02 AM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        jicg José Ignacio Carretero Guarde made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        fla Fernando Lopez made changes -
        Assignee Backlog Manager [ backlogmanager ]
        fla Fernando Lopez made changes -
        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
        Hide
        backlogmanager Backlog Manager added a comment -

        2019-03-07 18:06|UPDATED status: transition Answered| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2019-03-07 18:06|UPDATED status: transition Answered| # answers= 1, accepted answer= False
        backlogmanager Backlog Manager made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2019-03-07 15:06|UPDATED status: transition Answer| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2019-03-07 15:06|UPDATED status: transition Answer| # answers= 1, accepted answer= False
        backlogmanager Backlog Manager made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2019-03-07 12:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2019-03-07 12:05|CREATED monitor | # answers= 0, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            backlogmanager Backlog Manager
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: