[jira] [Commented] (METRON-495) Upgrade Storm to 1.0.x

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/METRON-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647822#comment-15647822 ] 

ASF GitHub Bot commented on METRON-495:
---------------------------------------

Github user DimaKovalyov commented on the issue:

    https://github.com/apache/incubator-metron/pull/318
  
    Hello,
    
    I am not sure if this is a good place for jumping it, but I have installed Metron with HDP 2.5 using this great article:
    https://community.hortonworks.com/articles/60805/deploying-a-fresh-metron-cluster-using-ambari-serv.html
    
    Fixed few issues here and there I was able to make it running. However all my Storm topologies are having:
    Topology spouts lag error:
    kafkaSpout	KAFKA	Unable to get offset lags for kafka. Reason: java.lang.NullPointerException at org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.getOffsetLags(KafkaOffsetLagUtil.java:269) at org.apache.storm.kafka.monitor.KafkaOffsetLagUtil.main(KafkaOffsetLagUtil.java:127)
    ![storm_kafka_error](https://cloud.githubusercontent.com/assets/22817724/20104398/8787896c-a5d6-11e6-9515-82a9fff84f4f.png)
    
    Considering that sir Michael Miklavcic said: "Modifying build versions for Storm removes the Storm Kafka lag error from the UI." I have mavened my built like that:
    mvn clean install -DskipTests -PHDP2.5.0.0
    
    Is there anything else I need to do in order to get Storm working with HDP 2.5?
    Please advise.
    Thank you.
    
    p.s. I've used latest metron code-base from apache incubator.


> Upgrade Storm to 1.0.x
> ----------------------
>
>                 Key: METRON-495
>                 URL: https://issues.apache.org/jira/browse/METRON-495
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Justin Leet
>            Assignee: Justin Leet
>             Fix For: 0.2.2BETA
>
>
> As listed at https://storm.apache.org/2016/04/12/storm100-released.html, there's a variety of improvements with Storm 1.0.  The obvious and likely most important improvement is to performance, but a variety of other improvements are noted on that link.
> There are several changes that have to occur in order to make this upgrade.  
> As noted in http://storm.apache.org/releases/current/index.html, Storm's code packages moved from backtype.storm to org.apache.storm, meaning all topologies have to be recompiled if that change.  There is a runtime converter to run things in place with backtype.storm, but this doesn't appear to be enough for our case because a couple interfaces change from byte[] to ByteBuffer (somewhat, but not entirely, related to https://issues.apache.org/jira/browse/STORM-1449). Even without this issue, the long term solution is to use the new package naming.
> In addition, our dev instances right now spin up an HDP 2.4 instance, which matches our current version of Storm. HDP 2.5 uses Storm 1.0.1, so to migrate to Storm 1.0.x, I'd prefer to match that version, rather than going to 1.0.2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)