You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by sachingsachin <gi...@git.apache.org> on 2017/02/23 17:37:21 UTC

[GitHub] storm pull request #1961: Storm 2290: Upgrading zookeeper to 3.4.9 for stabi...

GitHub user sachingsachin opened a pull request:

    https://github.com/apache/storm/pull/1961

    Storm 2290: Upgrading zookeeper to 3.4.9 for stability

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sachingsachin/storm STORM-2290

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1961.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1961
    
----
commit 53574d44fe070523ac8e83e7df02e925d86efb06
Author: Sachin Goyal <sg...@l-sb8m1heg8w-m.local>
Date:   2016-04-01T00:37:40Z

    Improve "_lostMessageCount" metric if a failed offset is beyond the configured "_spoutConfig.maxOffsetBehind"
    
    Other small changes:
    1) Rename offset to lowestValidOffset (Avoids confusion with generically-named variable "offset")
    2) Move a warning to its proper place (no point warning if there are no omitted offsets)
    3) Improve a second warning to convey the magnitude of lost offsets.

commit 1972bc4649418c8ccdc37304b1e794fe9d1c977a
Author: Sachin Goyal <sg...@l-sb8m1heg8w-m.local>
Date:   2017-02-23T17:24:02Z

    STORM-2290: Upgrade zk version

commit 8f50a383f4c743683938e29511c02b70652d8349
Author: Sachin Goyal <sg...@l-sb8m1heg8w-m.local>
Date:   2017-02-23T17:31:49Z

    REVERT back some local changes

commit 084211404356df5a9ecd6298701ec95880c16260
Author: Sachin Goyal <sg...@l-sb8m1heg8w-m.local>
Date:   2017-02-23T17:33:23Z

    REVERT back some local changes

commit fb9f5c010a34b7229097be3a532482f0aa56fa4c
Author: Sachin Goyal <sg...@l-sb8m1heg8w-m.local>
Date:   2017-02-23T17:34:34Z

    REVERT back some local changes

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm pull request #1961: Storm 2290: Upgrading zookeeper to 3.4.9 for stabi...

Posted by sachingsachin <gi...@git.apache.org>.
Github user sachingsachin closed the pull request at:

    https://github.com/apache/storm/pull/1961


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm issue #1961: Storm 2290: Upgrading zookeeper to 3.4.9 for stability

Posted by sachingsachin <gi...@git.apache.org>.
Github user sachingsachin commented on the issue:

    https://github.com/apache/storm/pull/1961
  
    @harshach - Created https://github.com/apache/storm/pull/1967 and https://github.com/apache/storm/pull/1968


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] storm issue #1961: Storm 2290: Upgrading zookeeper to 3.4.9 for stability

Posted by harshach <gi...@git.apache.org>.
Github user harshach commented on the issue:

    https://github.com/apache/storm/pull/1961
  
    @sachingsachin can you squash your commits.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---