I've added a comment on [1] asking how we should handle snapshot uploads,
which are currently failing.
[1] https://issues.apache.org/jira/browse/INFRA-26732
On Tue, Apr 22, 2025 at 8:04 PM Dawid Weiss wrote:
> Nice! I can't think of anything. I guess we just let it burn? I can't
> see any downs
Nice! I can't think of anything. I guess we just let it burn? I can't
see any downside to just letting it go - it's just one more CI.
D.
On Tue, Apr 22, 2025 at 7:30 PM Christos Malliaridis
wrote:
>
> Infra provided us with two new nodes – lucene-solr-3 and lucene-solr-4 – to
> replace the old
Infra provided us with two new nodes – lucene-solr-3 and lucene-solr-4 – to
replace the old ones. They come with upgraded hardware:
16GB -> 32GB RAM
> 4CPU -> 16CPU
> 256/350GB -> 500GB disk
Once we are ready to turn off the old nodes, I'll respond to the Jira issue.
*What steps are still remai
I've requested an upgrade here:
https://issues.apache.org/jira/browse/INFRA-26732
I hope I didn't forget anything. :)
On Wed, Apr 2, 2025 at 10:19 PM Uwe Schindler wrote:
> Can you make sure that the same people get sudo/root acces slike before?
> It would also be ideal to maybe ask them to pre
@Uwe Did you have the time to run a backup of the home directory? I would
proceed and open an infra ticket if we are ready, I just need to know what "all
packages we
need for Jenkins Slaves" includes, as I am not sure how to look this up to
include it in the ticket.
Christos
Hi,
> I tried the d
Can you make sure that the same people get sudo/root acces slike before?
It would also be ideal to maybe ask them to preserve the jenkins
directory. I cleaned them up a bit already.
If we get a new machine, could you ask them for more power and memory?
The current machines are very slow, looks
Hi,
go ahead. I preserved some config files. Actually the Gradle builds are
easier to maintain as Ant, so basically it is just 2 files.
Uwe
Am 02.04.2025 um 17:21 schrieb Uwe Schindler:
Oh sorry, will do! I ping you.
Uwe
Am 02.04.2025 um 17:02 schrieb Christos Malliaridis:
@Uwe Did you hav
Oh sorry, will do! I ping you.
Uwe
Am 02.04.2025 um 17:02 schrieb Christos Malliaridis:
@Uwe Did you have the time to run a backup of the home directory? I would
proceed and open an infra ticket if we are ready, I just need to know what "all
packages we
need for Jenkins Slaves" includes, as I a
The do-release-upgrade sounds like the way to go then.
If you are willing and have the time to upgrade the machines as you
recommended, I would love to join you, if possible, so that I have more
insights about these processes. Personally, if I would have to upgrade the
machines myself, I would jus
Hi,
I have root access on both machines. Indeed one of them (lucene-solr1)
is Ubuntu 18.04 LTS and the other one (lucene-solr - no digit) is
Unbuntu 20.04 LTS. In fact, both are outdated, whereas the first one is
out of support as far as I remember.
There are two ways:
* do-release-upgrade
Security updates ongoing... reboot ongoing... running again... 😉
Uwe
Am 27.03.2025 um 16:40 schrieb Uwe Schindler:
Hi,
see my mails on the lucene ML, these ones were lost as they only got
to Solr.
Actually, I was involved together with Jenkins and I also have root
access. Yes, they were pr
Hi,
see my mails on the lucene ML, these ones were lost as they only got to
Solr.
Actually, I was involved together with Jenkins and I also have root
access. Yes, they were provided by Infra, but there was some additional
work needed to make them Jenkins nodes. It is long ago that I touched
Small update: both machines already use netplan and not old interfaces
file, so do-release-upgrade is a no-brainer.
Uwe
Am 27.03.2025 um 16:23 schrieb Uwe Schindler:
Hi,
I have root access on both machines. Indeed one of them (lucene-solr1)
is Ubuntu 18.04 LTS and the other one (lucene-solr
>
> That is indeed helpful, I am just not familiar enough with the node setup
> to provide that kind of information.
>
None of us do I think. I believe both these boxes were provisioned by infra
but I have no idea how they were set up
(manually or via some sort of automation). I would think it's a
>
> Was it actually only one machine that was too out-of-date?
lucene-solr-1 is too out-of-date to cause an error, yes. lucene-solr-2 LTS
reaches EOL at the end of this year (?). So I think upgrading both is the
way to go.
a plan of what needs to be done and in which order would be useful. :)
Was it actually only one machine that was too out-of-date?
On Wed, Mar 26, 2025 at 1:05 PM Christos Malliaridis
wrote:
> Hello everyone,
>
> In consultation with David Smiley, I am planning to request an OS upgrade
> for our build nodes *lucene-solr-1* and *lucene-solr-2* on Monday, March
> 31,
I do have access to those machines and I can help, but a plan of what needs
to be done and in which order would be useful. :)
Dawid
On Wed, Mar 26, 2025 at 6:05 PM Christos Malliaridis
wrote:
> Hello everyone,
>
> In consultation with David Smiley, I am planning to request an OS upgrade
> for o
Hello everyone,
In consultation with David Smiley, I am planning to request an OS upgrade
for our build nodes *lucene-solr-1* and *lucene-solr-2* on Monday, March
31, as they are running older operating systems and causing OS-related
build errors in the Solr project.
Since the nodes will be repla
18 matches
Mail list logo
