Accumulo-1.8-Integration-Tests - Build # 958 - Failure! -- master
Accumulo-1.8-Integration-Tests - Build # 958 - Failure: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-1.8-Integration-Tests/958/ to view the results.
Accumulo-1.8-Integration-Tests - Build # 957 - Aborted! -- 1.7
Accumulo-1.8-Integration-Tests - Build # 957 - Aborted: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-1.8-Integration-Tests/957/ to view the results.
Accumulo-1.8-Integration-Tests - Build # 956 - Fixed! -- 1.6
Accumulo-1.8-Integration-Tests - Build # 956 - Fixed: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-1.8-Integration-Tests/956/ to view the results.
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292050#comment-15292050 ] Sean Busbey commented on ACCUMULO-3470: --- that's what I figured. [~dlmarion] can we make sure to have a release note covering this change that points to the release notes for the VFS release (presuming that includes some docs on the breakage)? > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-925) Launch scripts should use a PIDfile
[ https://issues.apache.org/jira/browse/ACCUMULO-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291973#comment-15291973 ] Josh Elser commented on ACCUMULO-925: - bq. Is there a reason why we can't apply this back to 1.6? Should probably have a discussion about it -- need to consider the impact on user automation around our scripts. We haven't really identified how the scripts should be covered by our compatibility statement (we have nothing about them now which is probably negligence). My gut reaction is that it wouldn't be worth it, but I'm not against someone doing the work to backport it (as long as we're sure we don't break scripts). It also would require the .out/.err file rotation (or at least splitting that logic out). IIRC, the hope was that usage of the existing start/stop-server and start/stop-all scripts didn't change, but I don't remember enough to say it is definitely compatible. > Launch scripts should use a PIDfile > --- > > Key: ACCUMULO-925 > URL: https://issues.apache.org/jira/browse/ACCUMULO-925 > Project: Accumulo > Issue Type: Improvement > Components: scripts >Reporter: Christopher Tubbs >Assignee: Billie Rinaldi > Fix For: 1.8.0 > > Attachments: ACCUMULO-925.1.patch, ACCUMULO-925.2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Start scripts should create PIDfiles to store the PID of running processes in > a well known location (example: /var/run/accumulo/tserver.pid or > $ACCUMULO_HOME/tserver.pid), for the following benefits: > # Identify running services on a machine without executing and parsing the > system process list, so stop scripts can kill them when they are unresponsive. > # Prevent multiple instances of the same application from starting up (an > environment variable for the location of the PIDfile can be used to allow > multiple instances if it is desirable to do so). > # Potentially provide an alternate mechanism for terminating a process by > deleting its PIDfile rather than its lock in Zookeeper. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-925) Launch scripts should use a PIDfile
[ https://issues.apache.org/jira/browse/ACCUMULO-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291960#comment-15291960 ] Dave Marion commented on ACCUMULO-925: -- Is there a reason why we can't apply this back to 1.6? > Launch scripts should use a PIDfile > --- > > Key: ACCUMULO-925 > URL: https://issues.apache.org/jira/browse/ACCUMULO-925 > Project: Accumulo > Issue Type: Improvement > Components: scripts >Reporter: Christopher Tubbs >Assignee: Billie Rinaldi > Fix For: 1.8.0 > > Attachments: ACCUMULO-925.1.patch, ACCUMULO-925.2.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Start scripts should create PIDfiles to store the PID of running processes in > a well known location (example: /var/run/accumulo/tserver.pid or > $ACCUMULO_HOME/tserver.pid), for the following benefits: > # Identify running services on a machine without executing and parsing the > system process list, so stop scripts can kill them when they are unresponsive. > # Prevent multiple instances of the same application from starting up (an > environment variable for the location of the PIDfile can be used to allow > multiple instances if it is desirable to do so). > # Potentially provide an alternate mechanism for terminating a process by > deleting its PIDfile rather than its lock in Zookeeper. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291442#comment-15291442 ] Dave Marion commented on ACCUMULO-3470: --- I have been using 2.1-SNAPSHOT for a while now with no issues. > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291394#comment-15291394 ] Josh Elser commented on ACCUMULO-3470: -- bq. Or do the known fixed issues outweigh the risk to downstream folks impacted by our classpath? IMO, it's unusable presently, so yeah, I don't think we should be worried about compat (and the final scope of backwards compatibility that was broken was pretty small). This is likely also brutally obvious given my previous chatter on dev@c.a.o :) > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291387#comment-15291387 ] Sean Busbey commented on ACCUMULO-3470: --- (I'm guessing based on the long history around VFS that the answer to that last questions is yes?) > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291386#comment-15291386 ] Sean Busbey commented on ACCUMULO-3470: --- re: inclusion in 1.6.z or 1.7.z maintenance releases, do we care about any of the compatibility things flagged in the 2.1 release? Or do the known fixed issues outweigh the risk to downstream folks impacted by our classpath? > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291308#comment-15291308 ] Josh Elser commented on ACCUMULO-3470: -- Also, shouldn't this also be tagged for 1.6 and 1.7? > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291305#comment-15291305 ] Josh Elser commented on ACCUMULO-3470: -- bq. VFS 2.1 has been released. I hope to get to this soon. Careful... it has not been officially released (PMC has not sent out a notice yet), but there are voted-upon JARs up in Nexus yes... :) > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3470) Upgrade to Commons VFS 2.1
[ https://issues.apache.org/jira/browse/ACCUMULO-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291135#comment-15291135 ] Dave Marion commented on ACCUMULO-3470: --- VFS 2.1 has been released. I hope to get to this soon. > Upgrade to Commons VFS 2.1 > -- > > Key: ACCUMULO-3470 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3470 > Project: Accumulo > Issue Type: Task >Reporter: Dave Marion >Assignee: Dave Marion > Fix For: 1.8.0 > > > Commons VFS 2.1 is nearing release. When released we need to remove the VFS > related classes in the start module, update the imports, and update the > version in the pom. Will set fixVersions when VFS is released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
