[JBoss JIRA] (ISPN-2401) StateTransferManager.isStateTransferInProgress/ForKey return false at the start of state transfer
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-2401?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-2401:
------------------------------------
I'm using a separate flag to track when a rebalance starts and when it ends. We need a new issue to track changing back DistributionManagerImpl.getLocality and friends to use it.
> StateTransferManager.isStateTransferInProgress/ForKey return false at the start of state transfer
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-2401
> URL: https://issues.jboss.org/browse/ISPN-2401
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 5.2.0.Beta2
> Reporter: Dan Berindei
> Assignee: Adrian Nistor
> Fix For: 5.2.0.Final
>
>
> They only check the segments that are in progress, so they return false if state transfer started but didn't add any segment to the in-progress list yet.
> If isStateTransferInProgressForKey is fixed, DistributionManagerImpl.getLocality should be changed to use it again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (ISPN-2733) Issue with the release script (bin/release.py)
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2733?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-2733:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1590
> Issue with the release script (bin/release.py)
> ----------------------------------------------
>
> Key: ISPN-2733
> URL: https://issues.jboss.org/browse/ISPN-2733
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.CR1
> Reporter: Mircea Markus
> Assignee: Tristan Tarrant
> Priority: Critical
> Fix For: 5.2.0.Final
>
>
> I get the following exception when running the release script:
> {quote}
> [INFO] Step 6: Uploading Artifacts
> Traceback (most recent call last):
> File "./bin/release.py", line 367, in <module>
> release()
> File "./bin/release.py", line 332, in release
> do_task(upload_artifacts, [base_dir % "as-modules", version], async_processes)
> TypeError: not all arguments converted during string formatting
> {quote}
> Seems like there's an incorrect string concatenation at line 332:
> {code}
> do_task(upload_artifacts, [base_dir % "as-modules", version], async_processes)
> {code}
> Using string concatenation seems to solve the problem:
> {code}
> do_task(upload_artifacts, [base_dir + "/as-modules", version], async_processes)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (ISPN-2733) Issue with the release script (bin/release.py)
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2733?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-2733:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Issue with the release script (bin/release.py)
> ----------------------------------------------
>
> Key: ISPN-2733
> URL: https://issues.jboss.org/browse/ISPN-2733
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.CR1
> Reporter: Mircea Markus
> Assignee: Tristan Tarrant
> Priority: Critical
> Fix For: 5.2.0.Final
>
>
> I get the following exception when running the release script:
> {quote}
> [INFO] Step 6: Uploading Artifacts
> Traceback (most recent call last):
> File "./bin/release.py", line 367, in <module>
> release()
> File "./bin/release.py", line 332, in release
> do_task(upload_artifacts, [base_dir % "as-modules", version], async_processes)
> TypeError: not all arguments converted during string formatting
> {quote}
> Seems like there's an incorrect string concatenation at line 332:
> {code}
> do_task(upload_artifacts, [base_dir % "as-modules", version], async_processes)
> {code}
> Using string concatenation seems to solve the problem:
> {code}
> do_task(upload_artifacts, [base_dir + "/as-modules", version], async_processes)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (ISPN-2611) Drop rhq-pluginAnnotations and rhq-pluginGen dependencies
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2611?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-2611:
----------------------------------
Fix Version/s: 5.2.0.Final
(was: 5.3.0.Final)
> Drop rhq-pluginAnnotations and rhq-pluginGen dependencies
> ---------------------------------------------------------
>
> Key: ISPN-2611
> URL: https://issues.jboss.org/browse/ISPN-2611
> Project: Infinispan
> Issue Type: Task
> Components: JMX, reporting and management
> Affects Versions: 5.2.0.Beta5
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Minor
> Fix For: 5.2.0.Final
>
>
> The rhq-pluginAnnotations and rhq-pluginGen dependencies should be dropped since we can generate the required RHQ plugin descriptor using our own ManagedOperation and ManagedAttribute annotations.
> This will also remove the requirement to carry rhq-pluginAnnotations around to workaround a Java compiler bug
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (ISPN-2723) NPE using cache loader preload with Lucene directory
by Christopher Wong (JIRA)
[ https://issues.jboss.org/browse/ISPN-2723?page=com.atlassian.jira.plugin.... ]
Christopher Wong updated ISPN-2723:
-----------------------------------
Attachment: infinispan.cfg.xml
Attaching config file, as requested by Galder. This version uses the Jdbm store.
> NPE using cache loader preload with Lucene directory
> ----------------------------------------------------
>
> Key: ISPN-2723
> URL: https://issues.jboss.org/browse/ISPN-2723
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache, Loaders and Stores
> Affects Versions: 5.2.0.CR1
> Reporter: Christopher Wong
> Assignee: Galder Zamarreño
> Fix For: 5.2.0.Final
>
> Attachments: infinispan.cfg.xml, infinispan.log
>
>
> I am seeing an NPE that looks a lot like ISPN-1470, except this is happening in version 5.2.0.CR1 of Infinispan. I have configured Infinispan's Lucene directory provider for use in Hibernate Search. The Hibernate SessionFactory is configured with a JTA transaction manager. Starting with no index works fine, but if I shut down Tomcat (with shutdown.sh) and restart, a huge pile of exceptions occur, starting with an NPE. The cache configuration in infinispan.cfg.xml looks like the following. I will attach a log file excerpt with a sampling of the exceptions being logged. This only happens with distributed mode. Replicated mode is fine. I have seen this happen with both the Jdbm and file cache store.
> <namedCache
> name="LuceneIndexesData">
> <clustering
> mode="dist">
> <stateTransfer fetchInMemoryState="true"/>
> <sync
> replTimeout="50000" />
> <l1 enabled="false" />
> </clustering>
> <loaders shared="true" preload="true">
> <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false">
> <properties>
> <property name="location" value="/some/path/.index/data" />
> </properties>
> </loader>
> </loaders>
> </namedCache>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months