bogdan: I think if the shared file system would be required just for
attachments, it wouldn't need to be very fancy. I think OTRS doesn't modify
what it has already written on disk for articles / attachments. So it only does
reads and additional writes. No editing.
It does rely on a consistent
I would love OTRS to shift the ticket increment into the database, the less
I can store in the filesystem the better as far as I'm concerned. Does
anyone know if this has been suggested or would anyone be willing to give
their code to the project to try and get it implemented mainstream.
Steve
---
nagement, but it easily allows multiple
>>> otrs instances to use the same data safely. It also lets you take advantage
>>> of the clustering features in the dbms software. You also eliminate any
>>> need for shared storage.
>>>
>>> ** **
&g
Beautiful. Thanks a LOT for sharing this info. It took a big uncertainty
off the table as I was unsure if OTRS can handle load balancing without
tweaking it in some ugly ways.
The DMS integration is very nice. If authentication / authorization against
the DMS were an issue in your setup, how did y
I'm not familiar with LVS or Linux-HA (mostly used MS platforms until ~
recently) so the next question may be born out of confusion: You have the load
balancing performed by machines runnings LVS and the Linux-HA is running on the
app nodes?
Correct. LVS handles session distribution and session
| That is what I have always assumed, if you look in the sessions table in
the DB in the session_value column you can see that there is all of the
user's configuration in one big string.
bogdan: Efficient and simple. I'm surprised. I assumed OTRS stores some
user session data in memory/disk to pro
Now this is some mighty useful info. Thanks a lot.
I'm not familiar with LVS or Linux-HA (mostly used MS platforms until ~
recently) so the next question may be born out of confusion: You have the
load balancing performed by machines runnings LVS and the Linux-HA is
running on the app nodes?
Just
It is, but that would mean it wouldn't be able to process incoming emails from
the other OTRS system, the system ID gets embedded in the full ticket "number",
the system ID is primarily used to allow separate OTRS systems to send emails
back and forth (assuming the system IDs are different) wit
On 29 January 2013 19:29, Bogdan Iosif wrote:
> bogdan: Thanks for this info. I was under the impression the SystemID is
> used by OTRS only when deciding which emails to process from an assigned
> inbox via PostMaster
>
It is, but that would mean it wouldn't be able to process incoming emails
f
While I appreciate the general advice, please note I'm not trying to reinvent
anything. Instead, I want to prepare for natural problems that OTRS will run
into when reaching a size that requires load balancing.
OK, I was jotting down some thoughts – sorry if it came off wrong. More details
inli
;>>
>>> If you store everything in the database (including attachments), you can
>>> easily separate the application logic from the database server; that
>>> introduces a bit more database management, but it easily allows multiple
>>> otrs instance
e same data safely. It also lets you take advantage
>> of the clustering features in the dbms software. You also eliminate any
>> need for shared storage.
>>
>> ** **
>>
>> If you use shared storage, you MUST use a cluster-aware filesystem like
>>
**
>
> If you use shared storage, you MUST use a cluster-aware filesystem like
> GFS2 or OCFS. NFS won’t work reliably.
>
> ** **
>
> *From:* otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] *On Behalf
> Of *Bogdan Iosif
> *Sent:* Tuesday, January 29, 2013
uesday, January 29, 2013 5:21 AM
To: OTRS User Mailing List
Subject: [otrs] NLB (load balancing) OTRS
Hi,
Can anyone help with some obvious issues around setting up a load balanced OTRS?
- Does last db write always win?
I imagine there's no built in protection against it.
- Are HTTP sticky sessio
Hi,
Can anyone help with some obvious issues around setting up a load balanced
OTRS?
- Does last db write always win?
I imagine there's no built in protection against it.
- Are HTTP sticky sessions required and if so, how can they be configured?
I imagine OTRS needs some built in support to
15 matches
Mail list logo
