[jira] [Created] (STORM-3306) Some tests in storm-core/test/jvm/org/apache/storm/integration/TopologyIntegrationTest.java are using Thrift to build topologies. They should use TopologyBuilder instead.
Stig Rohde Døssing created STORM-3306: - Summary: Some tests in storm-core/test/jvm/org/apache/storm/integration/TopologyIntegrationTest.java are using Thrift to build topologies. They should use TopologyBuilder instead. Key: STORM-3306 URL: https://issues.apache.org/jira/browse/STORM-3306 Project: Apache Storm Issue Type: Task Components: storm-core Affects Versions: 2.0.0 Reporter: Stig Rohde Døssing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3295) Blacklist scheduling doesn't handle multiple supervisors on a host properly
[ https://issues.apache.org/jira/browse/STORM-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3295. Resolution: Fixed Fix Version/s: 2.0.0 Thanks [~agresch], I merged this into master > Blacklist scheduling doesn't handle multiple supervisors on a host properly > --- > > Key: STORM-3295 > URL: https://issues.apache.org/jira/browse/STORM-3295 > Project: Apache Storm > Issue Type: Bug >Affects Versions: 2.0.0 >Reporter: Aaron Gresch >Assignee: Aaron Gresch >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 2h > Remaining Estimate: 0h > > If two supervisors on a host are blacklisted, the RasBlacklistStrategy code > can release one supervisor and keep the other blacklisted. The > BlacklistScheduler then sees the one blacklisted supervisor and considers > that host still blacklisted, preventing scheduling from operating properly. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3303) update some logging priorities
[
https://issues.apache.org/jira/browse/STORM-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-3303.
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~agresch],
I merged this into master
> update some logging priorities
> --
>
> Key: STORM-3303
> URL: https://issues.apache.org/jira/browse/STORM-3303
> Project: Apache Storm
> Issue Type: Bug
>Reporter: Aaron Gresch
>Assignee: Aaron Gresch
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Some log messages could use some tweaking in priorities:
>
> Sample: this could be a warning, as retries/reconnects are built-in:
> {code:java}
> 2018-12-06 06:36:56.439 o.a.s.p.PacemakerClient timer [ERROR] Not getting
> response or getting null response. Making 6 more attempts for .
> {code}
> * [|https://jira.ouroath.com/secure/AddComment!default.jspa?id=3421505]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (STORM-3300) Potential NPE in Acker when using reset timeout
[ https://issues.apache.org/jira/browse/STORM-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing updated STORM-3300: -- Affects Version/s: (was: 1.2.2) > Potential NPE in Acker when using reset timeout > --- > > Key: STORM-3300 > URL: https://issues.apache.org/jira/browse/STORM-3300 > Project: Apache Storm > Issue Type: Bug > Components: storm-client >Affects Versions: 2.0.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (STORM-3300) Potential NPE in Acker when using reset timeout
[ https://issues.apache.org/jira/browse/STORM-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723866#comment-16723866 ] Stig Rohde Døssing commented on STORM-3300: --- I'm not sure this bug is actually in 1.2.2. Removing that version from affected versions. > Potential NPE in Acker when using reset timeout > --- > > Key: STORM-3300 > URL: https://issues.apache.org/jira/browse/STORM-3300 > Project: Apache Storm > Issue Type: Bug > Components: storm-client >Affects Versions: 2.0.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3300) Potential NPE in Acker when using reset timeout
[ https://issues.apache.org/jira/browse/STORM-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing resolved STORM-3300. --- Resolution: Fixed Fix Version/s: 2.0.0 > Potential NPE in Acker when using reset timeout > --- > > Key: STORM-3300 > URL: https://issues.apache.org/jira/browse/STORM-3300 > Project: Apache Storm > Issue Type: Bug > Components: storm-client >Affects Versions: 2.0.0, 1.2.2 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3270) Build Storm with JDK 11, excluding incompatible modules
[ https://issues.apache.org/jira/browse/STORM-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Rohde Døssing resolved STORM-3270. --- Resolution: Fixed Fix Version/s: 2.0.0 > Build Storm with JDK 11, excluding incompatible modules > --- > > Key: STORM-3270 > URL: https://issues.apache.org/jira/browse/STORM-3270 > Project: Apache Storm > Issue Type: Sub-task >Affects Versions: 2.0.0 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
