chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhijit Dhar (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CHUKWA-632) Logs getting lost in hbase using TsProcessor
Date Thu, 02 Feb 2012 22:26:53 GMT

     [ https://issues.apache.org/jira/browse/CHUKWA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhijit Dhar updated CHUKWA-632:
--------------------------------

    Description: 
When collector writes to hbase using TsProcessor, it is using timestamp as the key. If there
are multiple log statements with the same timestamp, which is the key, it looses them in hbase.

As a fix, I extended AbstractProcessor and built my key using timestamp and the AbstractProcessor.startOffset.
But, for that, it has to be protected or a getter on it in AbstractProcessor class to be able
to use it.

Also, the way OutputCollector.collect method works, it might need to redo the way rowKey is
created.

  was:
When collector writes to hbase using TsProcessor, it is using timestamp as the key. If there
are multiple log statements with the same timestamp, which is the key, it looses them in hbase.

As a fix, I extended AbstractProcessor and built my key using timestamp and the AbstractProcessor.startOffset.
But, for that, it has to be protected or a getter on it in AbstractProcessor class to be able
to use it

    
> Logs getting lost in hbase using TsProcessor
> --------------------------------------------
>
>                 Key: CHUKWA-632
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-632
>             Project: Chukwa
>          Issue Type: Bug
>            Reporter: Abhijit Dhar
>
> When collector writes to hbase using TsProcessor, it is using timestamp as the key. If
there are multiple log statements with the same timestamp, which is the key, it looses them
in hbase.
> As a fix, I extended AbstractProcessor and built my key using timestamp and the AbstractProcessor.startOffset.
But, for that, it has to be protected or a getter on it in AbstractProcessor class to be able
to use it.
> Also, the way OutputCollector.collect method works, it might need to redo the way rowKey
is created.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message